By WhiskyChoy
Technical design discussion mode — Socratic dialogue for algorithm, architecture, and design decisions. Produces implementation specs, not code.
Exit brainstorm mode. Use when the user says "exit brainstorm", "退出头脑风暴", "结束讨论", "done brainstorming", or any clear intent to leave brainstorm mode. Invocable as /brainstorm:brainstorm-end (Claude Code) or $brainstorm-end (Codex).
Save the current brainstorm discussion as a specification document. Use when the user wants to persist brainstorm progress — either a final spec or a partial checkpoint. Invocable as /brainstorm:brainstorm-save (Claude Code) or $brainstorm-save (Codex).
Technical design discussion mode — Socratic dialogue for solving algorithmic challenges, architectural decisions, and complex design problems. Suppresses coding impulse and produces implementation specs as "sufficient statistics" for code reconstruction. Use this skill whenever the user wants to brainstorm, discuss, think through, debate, or explore algorithm design, data structure choices, optimization strategies, system architecture, or technical tradeoffs BEFORE writing code. Also trigger when the user says "let's think about", "how should we approach", "what's the best strategy for", "help me figure out", or wants to compare solution approaches without immediately jumping to implementation. This is NOT plan mode (no task lists) and NOT a PRD tool (no user stories) — it's a research-oriented dialogue that raises the human's understanding to the point where the subsequent coding phase becomes almost mechanical.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
npx claudepluginhub whiskychoy/whisky-claude-plugins --plugin brainstormGenerate draw.io diagrams as .drawio files with auto-detection and portable install of the draw.io CLI. Exports to PNG/SVG/PDF with embedded XML. See NOTICE for upstream attribution.
Local Overleaf workflow — git clone, LaTeX compilation, iterative compile-fix loop, and bidirectional sync. Targets non-technical users.
Convert academic papers (PDF, LaTeX, Overleaf) into polished HTML presentations with PPTX/PDF export. Supports multiple papers, style templates, screen-aware sizing, and logo injection.
Minimal terminal statusline (directory, model, context bar). Setup recommends claude-hud for a full-featured alternative, then falls back to this.
Commit all worktree changes, sync from main branch, run tests, and merge back. Use when done working in a git worktree.
Generate architecture diagrams and technical design documents
Technical design collaboration through natural dialogue
The Answer Computer — reasoning tools for brainstorming, planning, architecture design, and deep thinking
This skill should be used when users need to generate ideas, explore creative solutions, or systematically brainstorm approaches to problems. Use when users request help with ideation, content planning, product features, marketing campaigns, strategic planning, creative writing, or any task requiring structured idea generation. The skill provides 30+ research-validated prompt patterns across 14 categories with exact templates, success metrics, and domain-specific applications.
AI-powered design thinking partner that helps explore ideas, generate visuals, and create prototypes through natural conversation
「こんな機能を作りたい」「この設計どうしよう」という技術的な意思決定を、 5人の専門エージェントチームで壁打ちするスキル。 実装アプローチの比較・技術設計の選択・アーキテクチャの意思決定に特化。 Use when: 複数の実装方法があって迷っている時、設計の良し悪しを議論したい時、 技術的トレードオフを整理したい時。 Triggers: "設計壁打ち", "design discussion", "どう設計すべき", "実装アプローチを比較", "アーキテクチャ相談", "設計どうしよう", "技術選定したい", "ADR を作りたい", "設計の議論", "技術的トレードオフ"