Loading...
Loading...
Found 2,136 Skills
Modern TypeScript project architecture guide for 2025. Use when creating new TS projects, setting up configurations, or designing project structure. Covers tech stack selection, layered architecture, and best practices.
Structured code review covering style, readability, and security concerns with actionable feedback. Use when reviewing pull requests or merge requests to identify issues and suggest improvements.
Organize DI registrations using IServiceCollection extension methods. Group related services into composable Add* methods for clean Program.cs and reusable configuration in tests.
Used when implementing any feature or bug fix before writing production code
Ready-to-use prompts for comprehensive .NET framework upgrade analysis and execution
RED-GREEN-REFACTOR cycle with strict phase gates. Write failing test first, implement minimum code to pass, then refactor while keeping tests green. Use when implementing new features, fixing bugs with test-first approach, improving test coverage, or when user mentions TDD. Use for "TDD", "test first", "red green refactor", "write tests", or "implement with tests". Do NOT use for debugging existing failures (use systematic-debugging) or for refactoring without new tests (use systematic-refactoring).
Development conventions and patterns for everything-claude-code. JavaScript project with conventional commits.
Use before claiming work is complete, fixed, or tested; before committing or creating a PR — you must run verification commands and confirm the output before claiming success; always back up assertions with evidence
Use when working with tdd workflows tdd refactor
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants test-first development, or requests TDD workflow.
テスト駆動開発（TDD）ワークフローを実行するスキル。 使用タイミング: (1) 新機能の実装開始時 (2) バグ修正時 (3) リファクタリング前 (4) 「テストから書いて」と言われた時 (5) 品質重視の実装が必要な時。 トリガー例: 「TDDで実装して」「テスト駆動で」「テストから書いて」 「RED-GREEN-REFACTORで」「UserServiceのテストを書いて」
Use when advanced Pytest features including markers, custom assertions, hooks, and coverage configuration.