本文へ移動
cccskills
無料GitHub で公開

brainstorming

Transform rough ideas into solid designs through structured questioning

インストール方法を見る

含まれるファイル(1)

  • SKILL.md2.0 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Brainstorming → Design

Purpose

Turn vague ideas into actionable designs through Socratic questioning.

"I'm using the Brainstorming skill to refine your idea into a design."

The Flow

[Idea] → Phase 1: Understand → Phase 2: Explore → Phase 3: Design → [Plan]

Phase 1: Understanding (Ask Questions)

One question at a time. Prefer multiple choice.

Questions to ask:

  • What problem does this solve?
  • Who's the user?
  • What's success look like?
  • Any constraints (time, tech, integrations)?
  • What's already built that this touches?

Before asking: Check working directory for existing context.

Phase 2: Exploration (Present Options)

Present 2-3 approaches:

### Approach A: [Name]
- Architecture: [how it works]
- Pros: [benefits]
- Cons: [tradeoffs]
- Complexity: [low/medium/high]

### Approach B: [Name]
...

Ask: "Which approach resonates? Or should we explore others?"

Phase 3: Design (Incremental)

Present design in 200-300 word chunks:

  1. Architecture overview
  2. Key components
  3. Data flow
  4. Error handling
  5. Testing strategy

After each chunk: "Does this look right?"

Phase 4: Handoff

When design approved:

"Ready to create the implementation plan?"

If yes → Use writing-plans skill

Going Backwards

It's okay to revisit earlier phases:

  • New constraint discovered → Back to Phase 1
  • Design doesn't feel right → Back to Phase 2
  • Missing requirements → Back to Phase 1

Don't force linear progress.

Principles

  • YAGNI - Don't design what's not needed
  • Explore alternatives - Never settle on first idea
  • Validate incrementally - Small chunks, frequent feedback
  • Document decisions - Why, not just what

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Complete methodology for preventing AI hallucinations. Use when accuracy is critical and you need Claude to verify before claiming, cite before asserting, and admit uncertainty instead of guessing.

日本語の概要は準備中です。原文の説明を表示しています。

a-ariff/ariff-claude-plugins142026年3月29日 更新

Canvas API Connection Skill

日本語の概要は準備中です。原文の説明を表示しています。

a-ariff/ariff-claude-plugins142026年3月29日 更新

Forces every code-related claim to include file:line citations. No citation means the claim must be verified or removed. Use when building documentation, writing code reviews, or any output that others will rely on.

日本語の概要は準備中です。原文の説明を表示しています。

a-ariff/ariff-claude-plugins142026年3月29日 更新

Assign confidence scores (0-100) to every claim in a response. Helps users understand which parts are verified facts and which are educated guesses. Use when the user needs to know how much to trust each part of the answer.

日本語の概要は準備中です。原文の説明を表示しています。

a-ariff/ariff-claude-plugins142026年3月29日 更新

Forces Claude to extract exact quotes from files before making claims about them. Prevents hallucinations by grounding every statement in actual text from the codebase. Use when working with large files or unfamiliar code.

日本語の概要は準備中です。原文の説明を表示しています。

a-ariff/ariff-claude-plugins142026年3月29日 更新

Verify every claim from multiple independent angles -- code, docs, tests, git history. Use when you need high confidence that something is correct before acting on it.

日本語の概要は準備中です。原文の説明を表示しています。

a-ariff/ariff-claude-plugins142026年3月29日 更新

a-ariff のスキルをすべて見る

このスキルの問題を報告する