Menu
Guides structured ideation through Socratic questioning to explore problems, opportunities, and solutions. Use when brainstorming features, exploring use cases, or thinking through new ideas.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | ideation |
| description | Guides structured ideation through Socratic questioning to explore problems, opportunities, and solutions. Use when brainstorming features, exploring use cases, or thinking through new ideas. |
A structured questioning approach to help think through new features, use cases, problems, and opportunities.
Instead of jumping to solutions, guide the user through layers of understanding:
Start here to clarify what they're actually trying to do:
Dig into the mechanics of the problem:
Understand the boundaries:
Get specific about who you're building for:
Now explore options:
Stress-test the idea:
After the ideation session, offer to create:
When the skill is triggered, start with:
"Before we dive into solutions, let me understand the problem space first. What triggered this idea? What's the situation or pain point you're seeing?"
Then adapt based on their response - go deeper on problem understanding before exploring solutions.
Produce low-fidelity black-and-white UI wireframes as standalone SVG files. Use when asked to wireframe a screen, page, or flow, make a low-fi mockup or layout draft, bundle wireframes into a browsable viewer page, or publish wireframes for review.
Gate merges and commits of AI-implemented work behind a comprehension quiz that the USER must pass. Use this whenever a nontrivial implementation is complete and the user is about to commit, merge, open a PR, or ship — or whenever the user says "quiz me", "gate this", "do I understand this", or asks to review AI-generated changes before accepting them. Also use proactively at the end of any substantial implementation session, even if the user doesn't ask, offer the quiz before suggesting a commit.
Turn a working session — the docs, issues, and half-formed ideas you've fed in, plus anything you point it at — into a spec and then a set of self-contained, executable implementation plans for OTHER models/agents to build. A senior architect that plans but never implements. Use when you have that context in hand and want it distilled into a PRD-style spec and broken into dependency-ordered, verifiable work items. Publishes to the repo's configured issue tracker or to markdown files.
Audit and harden Node.js projects against npm supply chain attacks — compromised maintainer accounts, malicious package versions, and install-script payloads. Use when reviewing or setting up package.json, lockfiles, .npmrc, Dockerfile, or CI workflows for security; when the user mentions npm security, supply chain attacks, `npm audit`, lockfile policy, install scripts, or min-release-age; also when the user wants to check whether their dependencies are safe, or recover from a suspected compromise.
Manage Val Town projects using the vt CLI. Use when working with Vals (Val Town serverless functions), syncing code to Val Town, creating HTTP endpoints, streaming logs, or managing Val Town branches. Triggers on tasks involving Val Town development, val creation/editing, or when user mentions "vt", "val town", or "vals".
Use when the user gives a rough idea, broad objective, unfinished `/goal`, plan, issue, visual target, optimization target, or research task and wants it refined into a concise Codex Goal contract with one durable objective, clear boundaries, realistic environment, measurable progress, evidence-based completion, checkpoints, cleanup, blockers, and an output strictly under the hard cap of 4,000 characters.
