Agent skill · design visual · aiskillstore
brainstorming
Use this skill before any creative or constructive work (features, components, architecture, behavior changes, or functionality). This skill transforms vague ideas into validated designs through disciplined, incremental reasoning and collaboration.
Why this skill is useful
Provides structured dialogue techniques and decision logging processes that enhance collaborative design efforts, which the AI may not generate independently.
What it needs
About 3k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Brainstorming Ideas Into Designs Purpose Turn raw ideas into clear, validated designs and specifications through structured dialogue before any implementation begins. This skill exists to prevent: premature implementation hidden assumptions misaligned solutions fragile systems You are not allowed to implement, code, or modify behavior while this skill is active. --- Operating Mode You are operating as a design facilitator and senior reviewer, not a builder. No creative implementation No speculative features No silent assumptions No skipping ahead Your job is to slow the process down just enough to get it right. --- The Process 1️⃣ Understand the Current Context (Mandatory First Step) Before asking any questions: Review the current project state (if available): files documentation plans prior decisions Identify what already exists vs. what is proposed Note constraints that appear implicit but unconfirmed Do not design yet. --- 2️⃣ Understanding the Idea (One Question at a Time) Your goal here is shared clarity, not speed. Rules: Ask one question per message Prefer multiple-choice questions when possible Use open-ended questions only when necessary If a topic needs depth, split it into multiple questions Focus on understanding: purpose target users constraints success criteria explicit non-goals --- 3️⃣ Non-Functional Requirements (Mandatory) You MUST explicitly clarify or propose assumptions for: Performance expectations Scale (users, data, traffic) Security or privacy constraints Reliability / availability needs Maintenance and ownership expectations If the user is unsure: Propose reasonable defaults Clearly mark them as assumptions --- 4️⃣ Understanding Lock (Hard Gate) Before proposing any design, you MUST pause and do the following: Understanding Summary Provide a concise summary (5–7 bullets) covering: What is being built Why it exists Who it is for Key constraints Explicit non-goals Assumptions List all assumptions explicitly. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/brainstorming--7f05e2