バックエンド実装時に使用。DRY原則遵守。コーディング規約準拠。
The English summary is being prepared. Showing the original description.
Use when selecting skills for a task or resolving how skill workflows apply
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Use a skill when the user requests it or its workflow materially helps the task. Read the relevant skill once before applying it, and briefly state its purpose. A matching keyword or a small chance of relevance alone does not require loading a skill. Ordinary questions and read-only exploration can proceed directly.
User instructions and project policy take precedence. Reuse decisions and authorization already present in the conversation; do not restart an approved design or ask again merely because a skill was loaded. Ask only for information or authorization that is still needed. After the design approval, "ask your human partner" in an upstream skill means: decide within the approved design, record a deviation, and report it in the final message; stop only for the exceptions in documents/development/development-policy.md §1.0 "承認後の進め方".
Scale process to the work, not the gate. Every implementation change passes the brainstorming Design Gate (design review, then user approval) before code is written, except the exemption defined there (a typo fix that involves no design choice, or an obviously correct change of a few lines; a fix within an already approved design, such as a quality-check finding, that does not change that design needs no new gate); a bounded change keeps its design short and can then be implemented by the parent with appropriate verification. Use writing-plans for dependencies or a useful handoff. Independent bounded tasks may be delegated when doing so reduces total effort; having subagent tools does not require using them.
The project's quality-check remains the independent final quality gate. Skill workflows do not add per-task reviews or another whole-branch review on top of it. Keep the project's review budget, test oracles, and evidence requirements.
For tool syntax consult only the reference relevant to your runtime, and trust the actual available tools and instructions over examples:
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
バックエンド実装時に使用。DRY原則遵守。コーディング規約準拠。
The English summary is being prepared. Showing the original description.
Use before implementing any feature, behavior change, or refactor - settles requirements and design, then gets the design independently reviewed and approved by the user before code is written
The English summary is being prepared. Showing the original description.
作業開始時に使用。mainブランチでの作業禁止。Issue先行作成必須。
The English summary is being prepared. Showing the original description.
UI実装後の検証時に使用。agent-browser CLIでブラウザ上の動作を手動検証する。「UIを確認」「画面テスト」と言われたら使用(プロジェクトの E2E スイート実行は quality-check Step 5(推奨度・範囲で自動実施または確認)/ server-startup が担当)。
The English summary is being prepared. Showing the original description.
DBマイグレーション作成時に使用。バージョン番号競合防止。mainブランチ確認必須。
The English summary is being prepared. Showing the original description.
Use when independent tasks benefit from parallel work without shared state or sequential dependencies
The English summary is being prepared. Showing the original description.