Skip to content
cccskills
FreePublished on GitHub

brainstorming

User asks for design, planning, or approach exploration before implementation. Covers new features, components, refactors, or architecture decisions. Creates design docs and proposes approaches with trade-offs.

The English summary is being prepared. Showing the original description.

See how to install

Files included (3)

  • SKILL.md2.1 KB
  • guidelines.md1.1 KB
  • spec-document-reviewer-prompt.md1.7 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Brainstorming — Design Exploration

Turn ideas into fully formed designs through collaborative dialogue.

When triggered, present a design before implementation. The design scales to complexity: short (few sentences) for simple tasks, detailed (pages) for architectural changes. Always get approval before proceeding to code.

When to Activate

  • User explicitly asks: "design this", "how should i build", "what's the approach", "plan this out"
  • User describes a feature/component/refactor and asks for guidance before coding
  • User wants to explore trade-offs or multiple approaches to a problem

Process

  1. Explore context — check relevant code files, docs, recent commits
  2. Ask clarifying questions — one at a time, prefer multiple choice, understand: purpose, constraints, success criteria, scope
  3. Propose 2-3 approaches — name each, describe trade-offs, state your recommendation
  4. Present design — scale to complexity (1-2 sentences for trivial, multiple sections for architecture), ask approval after each section
  5. Get approval — wait for user buy-in before writing code

Design Principles

  • One question at a time — don't overwhelm
  • YAGNI ruthlessly — remove unnecessary features
  • Design for isolation — break into units with one purpose, well-defined interfaces, independently testable
  • Explore alternatives — always 2-3 approaches, with trade-offs
  • Scope check — if request spans multiple subsystems, decompose first

In Existing Codebases

  • Explore current structure and patterns before proposing changes
  • Include targeted fixes only if they block the current goal
  • Don't propose unrelated refactoring

Output

Present design as prose (short or detailed based on complexity), then ask: "Does this look right?" Wait for approval before proceeding to implementation.

Reviews

No reviews yet. Tell others what you thought.

Comments

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.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Use when starting work in a repository under repositories/ that may lack CI configuration. Detects missing CI workflows (GitHub Actions, GitLab CI, CircleCI) and alerts the user to add one. Skips repos marked as research-only.

The English summary is being prepared. Showing the original description.

Benkapner/claude-code-basecamp18Updated Oct 1, 2026

Use when the user asks to measure command execution time or optimize a feedback loop. Records explicit measurements and recommends faster alternatives such as unit tests versus integration tests. It is opt-in; it does not run on every command.

The English summary is being prepared. Showing the original description.

Benkapner/claude-code-basecamp18Updated Oct 1, 2026

Team conventions for Python development — credentials, API clients, LLM response parsing, testing patterns, and data pipeline structure. Covers dotenv loading, retry logic, secret validation, and pipeline anti-patterns.

The English summary is being prepared. Showing the original description.

Benkapner/claude-code-basecamp18Updated Oct 1, 2026

Measurement-driven code refactoring — profile before changing, measure after, keep only if metrics improve. Covers complexity reduction, extraction patterns, and bulk refactoring for mechanical changes across many files.

The English summary is being prepared. Showing the original description.

Benkapner/claude-code-basecamp18Updated Oct 1, 2026

Scan projects for credential leaks, secrets in code, insecure patterns, LLM API key exposure, PII leakage to external AI services, and .env/.gitignore misconfigurations. Especially useful for data and API integrations, regardless of implementation language.

The English summary is being prepared. Showing the original description.

Benkapner/claude-code-basecamp18Updated Oct 1, 2026

Use when committing or pushing changes and the repository needs a version bump. Analyzes commits using conventional commit prefixes to determine whether the next release is a major, minor, or patch increment. Also use when the user asks about versioning, release planning, or changelog generation.

The English summary is being prepared. Showing the original description.

Benkapner/claude-code-basecamp18Updated Oct 1, 2026

See all skills by Benkapner

Report a problem with this skill