Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Design & UI

brainstorm

Use this skill when exploring an open product or architecture question before choosing an approach. Activates on mentions of brainstorm, ideate, design session, explore options, what should we build, how should we approach, let's think about, new project, architecture decision, or design exploration. Skip it for a clear implementation request.

hyperb1iss · Static checks on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add hyperb1iss/hyperskills --skill brainstorm

About this skill


name: brainstorm description: Use this skill when exploring an open product or architecture question before choosing an approach. Activates on mentions of brainstorm, ideate, design session, explore options, what should we build, how should we approach, let's think about, new project, architecture decision, or design exploration. Skip it for a clear implementation request.

Collaborative Brainstorming

Turn uncertainty into a useful choice or a focused experiment. Explore only the questions that could change the design. A clear implementation request already supplies direction; act on it without manufacturing a brainstorm or approval gate.

The user's instructions take precedence over this skill's guidelines. Preserve their constraints and existing authorization. Resolve routine design details with judgment; ask only when missing information materially changes the outcome and cannot be inferred.

Choose the Work Shape

SituationUseful output
The user wants open explorationDistinct directions with concrete tradeoffs and unresolved questions
The problem is clear but the mechanism is uncertainA recommendation and the evidence that would overturn it
One assumption determines feasibilityA small test of that assumption before elaborating designs
The approach is selected and implementation is authorizedContinue into implementation
The user asks why something happensDiagnose the cause before designing a fix

Ground the Question

Read the relevant code, artifact, or workflow and recall prior decisions. When Sibyl is configured, use its installed skill for current commands (sibyl context "<decision>" --intent plan). Memory supplies leads; inspect current evidence before reusing a volatile claim.

Name the intended experience or behavior, the constraint that matters most, and what remains unknown. Treat the user's hunch as a hypothesis worth checking, not a claim to rubber-stamp. A decisive check can confirm part of the hunch and reject the rest; report both.

Translate taste into examples and observations. For "smooth," identify the interaction and visible delay. For "gorgeous," inspect the reference and name the composition, motion, or typography worth preserving. Quantification helps where a metric represents the experience; a proxy metric does not replace the experience itself.

Distinguish explicit requirements from inferred preferences. Do not downgrade "use X" to a preference merely because the user wrote casually. If the instruction conflicts with feasibility, explain the conflict and resolve it before choosing an incompatible design.

Explore the Alternatives That Matter

The Double Diamond offers a useful rhythm: widen the problem frame, narrow it, explore solutions, choose. Revisit the frame when evidence changes it. No phase requires a separate artifact or confirmation.

Generate alternatives along meaningful dimensions: ownership of state, migration cost, runtime behavior, user effort, or reversibility. Different names for the same mechanism do not create real choice. Consider reuse, configuration, or removing the need when those paths still meet the requested outcome. Include an unconventional direction when the obvious options share an untested assumption; do not invent a wildcard to fill a slot.

Compare viable options in the dimensions relevant to this decision:

ApproachWhat improvesCarrying costMain uncertaintyDecisive check
[Mechanism][User or system outcome][Maintenance, runtime, migration][What could invalidate it][Experiment or evidence]

Keep ambition and mechanism separate. Simplifying the machinery should preserve the useful destination. A small implementation that proves only connectivity may miss the actual product; an elaborate one may bury it. Use expected lifetime and likely change boundaries to judge architecture, rather than equating fewer lines with better design.

Before extending a design, ask where each responsibility belongs. A decision repeated across callers may need one owner. A wrapper may instead be enforcing a valuable boundary. Remove indirection after understanding its contract, not because forwarding looks trivial.

Test the Uncertainty Before Polishing

Choose the next action by its ability to change the decision. A compatibility check, representative benchmark, or rough interaction prototype can settle more than another design paragraph.

Evidence gapNext move
An API or model capability may have changedOpen current primary documentation and inspect the installed version
Performance determines feasibilityTest a representative workload with a baseline and explicit resource limits
Several independent domains affect the choiceDelegate bounded research when permitted, or batch independent reads locally
Stakeholders value different outcomesSurface the actual value tradeoff for the user
A favored approach has weak supportSeek a concrete counterexample or failure condition

Independent opinions can expose assumptions, but agre

Read the complete source ↗