What is the 'Oracle' mentioned in the skill process?

The Oracle is a specialized sub-skill invoked for complex architectural, security, or performance-critical decisions to provide a validated second opinion.

How does the Brainstorming skill prevent over-engineering?

The skill follows 'YAGNI' (You Ain't Gonna Need It) principles, proactively identifying and removing unnecessary features or complexities during the design phase.

How does it handle conflicting recommendations?

When the skill and the Oracle disagree, it presents both perspectives to you with transparent reasoning, allowing you to make the final decision with full context.

Can I use this for both frontend and backend design?

Yes, the skill is domain-agnostic and works effectively for UI components, API design, database schemas, and general system architecture.

Brainstorming & Design Planner

Name: Brainstorming & Design Planner
Author: trancong12102

bytrancong12102

•

Productivity & Workflow

Guides technical discovery and architectural planning through collaborative dialogue and incremental validation.

About

The Brainstorming skill transforms abstract ideas into concrete technical specifications by facilitating a structured dialogue between the developer and Claude. Instead of jumping straight into code, this skill ensures project success by exploring multiple architectural approaches, evaluating trade-offs, and validating designs in small, digestible sections. It utilizes a dedicated 'Oracle' consultation for high-stakes decisions and adheres to YAGNI principles to prevent over-engineering, making it essential for planning features, systems, or complex refactors.

Key Features

Ruthless YAGNI enforcement to ensure lean and maintainable designs
1 GitHub stars
Structured inquiry using the AskUserQuestion tool for focused requirements gathering
Comparative analysis of 2-3 architectural approaches with clear recommendations
Incremental design presentation (200-300 word blocks) with mandatory validation steps
Integrated Oracle consultation for complex architectural or security decisions

Use Cases

Mapping out the architecture for a new feature or microservice
Choosing between competing libraries, databases, or design patterns
Refining complex logic and data flows before starting implementation

About

Key Features

Ruthless YAGNI enforcement to ensure lean and maintainable designs
1 GitHub stars
Structured inquiry using the AskUserQuestion tool for focused requirements gathering
Comparative analysis of 2-3 architectural approaches with clear recommendations
Incremental design presentation (200-300 word blocks) with mandatory validation steps
Integrated Oracle consultation for complex architectural or security decisions

Use Cases

Mapping out the architecture for a new feature or microservice
Choosing between competing libraries, databases, or design patterns
Refining complex logic and data flows before starting implementation