Menu
Use when shaping new features or behavior changes that need requirements clarification and option tradeoff exploration before implementation.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when designing, reviewing, or modifying backend API endpoints, schemas, validation, and API documentation.
Use when reviewing architecture boundaries, dependency direction, or multi-layer design decisions across modules.
Use when React components are too large or complex and need extraction, simplification, or separation of concerns.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Use when modeling domain concepts, aggregates, and bounded contexts or checking DDD alignment in existing code.
Use when implementing or reviewing football data logic, pitch coordinates, event modeling, or sports vision pipelines.
| name | brainstorming |
| description | Use when shaping new features or behavior changes that need requirements clarification and option tradeoff exploration before implementation. |
Help turn ideas into fully formed designs and specs through natural collaborative dialogue.
Start by understanding the current project context, then ask questions one at a time to refine the idea. Once you understand what you're building, present the design in small sections (200-300 words), checking after each section whether it looks right so far.
Understanding the idea:
Exploring approaches:
Presenting the design:
Documentation:
project/plans/YYYY-MM-DD-<topic>-design.mdImplementation (if continuing):