Before writing any implementation code, define the acceptance criteria and test cases that the code must satisfy. Agents then write code to pass these tests — not to match a vague description. Eliminates "it works on my machine" and "I think this is what you wanted" outcomes.
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
"A feature is not done when code is written. It is done when the tests pass."
Tests written before code serve three purposes:
Read the task description and extract every "must" and "should":
Example task: "Add a user registration endpoint"
Extracted criteria:
email, password, name in request bodyBefore writing any implementation, write the tests (or test outlines):
describe('registerUser()', () => {
it('creates a user with hashed password', async () => { ... })
it('throws DuplicateEmailError if email already exists', async () => { ... })
it('throws ValidationError if email format is invalid', async () => { ... })
it('never stores plaintext password', async () => { ... })
})
describe('POST /api/auth/register', () => {
it('returns 201 and user object (without password) on success', async () => { ... })
it('returns 400 when email already registered', async () => { ... })
it('returns 422 when required fields missing', async () => { ... })
})
Scenario: Successful registration
Given I am on the /register page
When I fill in valid email, password, and name
And I click "Create Account"
Then I should be redirected to /dashboard
And I should see "Welcome, <name>"
Run the tests before writing any implementation:
npm test
# or
pytest
# etc.
Expected: All new tests fail. This confirms the tests are correctly detecting the absence of the feature. If a test passes before implementation, the test is wrong — fix it.
Now implement the feature. The goal is simple: make the tests pass.
Rules during implementation:
# Keep running tests as you go
npm test --watch
Once all tests pass:
A task is complete when:
npm test exits with code 0).skip, xtest, # noqa)--coverage)## Task Complete: <feature name>
**Tests written:** <N>
**Tests passing:** <N>/<N>
**Coverage:** <X>%
**Acceptance criteria covered:**
✅ Creates user with hashed password
✅ Returns 400 on duplicate email
✅ Returns 422 on validation failure
✅ Never stores plaintext password
**Not covered (and why):**
⚠️ Email delivery test — skipped, requires mock SMTP setup
Test names must read as requirements:
✅ it('returns 400 when email already exists')
✅ it('never exposes password in API response')
❌ it('test email duplicate')
❌ it('works correctly')
If you can't name the test clearly, the requirement isn't clear enough — clarify before writing.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Before committing to an implementation plan, run this skill to stress-test the proposed architecture. Catches over-engineering, circular dependencies, missing failure modes, security gaps, and scalability cliffs — before any code is written. Acts as a "second eye" on the plan.
日本語の概要は準備中です。原文の説明を表示しています。
Systematic code review skill covering both requesting a review (pre-commit checklist) and receiving and responding to review feedback. Checks code quality, security, test coverage, architectural alignment, and documentation before any code is committed.
日本語の概要は準備中です。原文の説明を表示しています。
Periodically scan project dependencies for security vulnerabilities, outdated packages, and unused dependencies. Produces a prioritized action report. Run before every major release and at least once per month.
日本語の概要は準備中です。原文の説明を表示しています。
After any significant code change — new feature, API modification, config change, or architectural refactor — run this skill to identify which documentation files are now stale and update them. Keeps docs and code from drifting apart.
日本語の概要は準備中です。原文の説明を表示しています。
Manages all git operations (commit, push, branch management, PR creation) in a standardized, safe, and consistent way. Automatically runs the code-review skill before any commit. Enforces Conventional Commits standard. Handles the full lifecycle: branch → review → commit → push → PR.
日本語の概要は準備中です。原文の説明を表示しています。
When something breaks in production: triage the severity, gather evidence, identify root cause, deploy a fix or mitigation, and write a post-mortem. Provides a calm, structured process for high-stress moments.
日本語の概要は準備中です。原文の説明を表示しています。