ideate_skill

Overview

This skill captures a new product or feature idea and writes a single markdown file into design/ideas/. It creates a clear summary, gathers focused research from local design files and optional web sources, and produces a lightweight sketch to illustrate the concept. The output follows a strict filename and content format so ideas are easy to browse and iterate on.

How this skill works

When invoked, the skill asks up to three clarifying questions only if the idea is too vague to record. It enumerates and reads files under design/ to surface directly relevant context, then supplements with concise web research when it adds value. Finally, it creates design/ideas/, names the file by date and kebab-case title (adding numeric suffixes if needed), and writes the required markdown structure: Idea, Research, and a single Sketch code block.

When to use it

• You want to capture a brainstorming result before moving on.
• You have a new feature, UX tweak, or architecture idea to preserve.
• You need a concise research-backed proposal for later review.
• You want a simple visual sketch (ASCII/Mermaid) alongside notes.

Best practices

• Keep answers short when the skill asks clarifying questions—1–2 sentences each.
• Reference existing design/ files by name when pointing to related work.
• Allow web sources only when they materially improve technical or UX decisions.
• Choose mermaid for flows, text for ASCII wireframes, md for mixed notes.
• Use descriptive, short titles so filenames remain readable and sortable.

Example use cases

• Capture a quick idea for an Angular-driven in-browser agent UI flow with a mermaid sequence.
• Document an experiment to add a React toolbar for LLM controls with supporting links and a sketch.
• Record a typescript API ergonomic change for Hashbrown agents with local design cross-references.
• Save a UX exploration for multi-agent orchestration that references existing design diagrams.