Loading...
Loading...
Found 8,782 Skills
Optional Stage 0 of the feature workflow — clarify vague ideas through dialogue until they are ready to enter the design phase. The role of AI is a thinking partner: dig out the real problem the user wants to solve (instead of sticking to the first solution they blurt out), actively evaluate the solution when the user brings it up, and propose better alternatives if necessary. After the discussion, output {slug}-brainstorm.md to document the results. Trigger scenarios: The user says "I have an unclear idea", "Let's brainstorm first", "The feature direction is still undecided", or the user brings a specific solution but wants to hear other ideas first. Skip this stage and proceed directly to design if the idea is already clear and the user does not want to discuss the solution further. This stage also does not handle bugs and refactoring.
Npm integration. Manage data, records, and automate workflows. Use when the user wants to interact with Npm data.
Mozilla Observatory integration. Manage data, records, and automate workflows. Use when the user wants to interact with Mozilla Observatory data.
Seam integration. Manage data, records, and automate workflows. Use when the user wants to interact with Seam data.
Termius integration. Manage data, records, and automate workflows. Use when the user wants to interact with Termius data.
Currencycloud integration. Manage data, records, and automate workflows. Use when the user wants to interact with Currencycloud data.
Scan a Cargo workspace or package monorepo and refresh per-member `CLAUDE.md` files plus a thin root `CLAUDE.md`. User-only maintenance workflow for keeping workspace-local AI context accurate after refactors, member additions, export changes, or major architectural shifts.
Amazon EventBridge integration. Manage data, records, and automate workflows. Use when the user wants to interact with Amazon EventBridge data.
Phase 3 of the feature workflow – Complete the acceptance closed-loop. Four tasks: 1. Check layer by layer against {slug}-design.md to verify if the implementation deviates from the plan; fix any deviations on the spot instead of just "noting them" in the report. 2. Incorporate this feature into the project's overall architecture documentation. 3. If this feature changes the user story or boundaries of the corresponding requirement, update the requirement doc accordingly. 4. If this feature originated from a roadmap item, change the status of the corresponding entry in roadmap items.yaml to done and sync it with the main document. Finally, produce a {slug}-acceptance.md as the closed-loop proof for the entire workflow. Prerequisite: cs-feat-impl is completed. Trigger scenarios: User says "The feature is done, let's accept it", "Do the final check", "Prepare for merge", "Generate the acceptance report".
Tomba integration. Manage data, records, and automate workflows. Use when the user wants to interact with Tomba data.
Ikas integration. Manage data, records, and automate workflows. Use when the user wants to interact with Ikas data.
Nordic API Gateway integration. Manage data, records, and automate workflows. Use when the user wants to interact with Nordic API Gateway data.