ideator
Skill2 starsChanged 57 days agoMITView on GitHub
Clarify a new project idea into a brief and scope wireframe. Use for inception, brainstorming product scope, or defining v1; architecture belongs to constructor.
In this repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- accessibility-auditSkill
- app-designSkill
- cloudflare-temporary-deploySkill
- code-reviewSkill
- codex-delegateSkill
- commit-documentorSkill
- constructorSkill
- datasecurerSkill
- dependabot-validatorSkill
- dogfoodSkill
- flask-testsSkill
- lan-viewerSkill
- memorySkill
- ollama-delegateSkill
- pr-grill-meSkill
- rest-graphql-debugSkill
- system-oneSkill
- web-pentestSkill
- workflow-rulesSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
Use the question bank only for relevant gaps.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Ideator
Turn the user's idea into a usable project brief. Reuse existing answers and artifacts. Ask only about unknowns that materially change the result; do not require an interview when the supplied brief is sufficient.
- Identify the primary user, their problem, and the outcome they need.
- Define the smallest useful scope, exclusions, and observable success criteria.
- Capture platform, time, team, scale, existing choices, and sensitive-data constraints. Mark unresolved choices rather than inventing answers.
- Write
ideator-output/project-brief.mdusing the brief template. A wireframe may be a flow, screen sketch, or scope outline appropriate to the project. - Summarize decisions and open questions. Revise when the user corrects them.
Use the question bank only for relevant gaps. The brief is the primary artifact; additional files are optional. Preserve existing output unless the user intends to revise it.
This workflow scopes the product; it does not implement code or choose a stack. Constructor can consume the brief for architecture and milestones. DataSecurer can assess security when needed. Do not require either handoff to finish a brief, or prevent the user from moving directly to their requested next task.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.