Skills-Agent / rules
Cursor rule4 starsChanged 33 days agoMITView on GitHub
Ideation, option generation, and feature exploration. Use when the user wants to brainstorm ideas, explore options, compare approaches, or generate creative solutions. Triggers: brainstorm, ideate, options, ý tưởng, so sánh phương án.
We split this brainstorm.mdc into the rules it gives an agent
16 rules. About 0 are common, 8 are distinctive, and 8 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
START: Read .ai-memory.md from project root.
- Very specific: line 11
END: Update .ai-memory.md using Memory Compaction Rules with: problem, options considered, chosen direction, constraints, and new project …
- Very specific: line 17
If brainstorm involves system architecture → read .kiro/skills/agents/agents/project-planner.md and apply its knowledge
- Very specific: line 18
If brainstorm spans multiple domains → read .kiro/skills/agents/agents/orchestrator.md and apply its knowledge
- Very specific: line 19
If brainstorm is about UI/UX → read .kiro/skills/agents/agents/frontend-specialist.md and apply its knowledge
- Very specific: line 20
If brainstorm is about APIs/backend → read .kiro/skills/agents/agents/backend-specialist.md and apply its knowledge
- Distinctive: line 23
Before generating options, verify:
- Distinctive: line 27
If any answer is unclear, ASK before proceeding.
- Distinctive: line 34
Call out the most practical option and the boldest option.
- Distinctive: line 58
Prefer practical ideas grounded in the current project.
- Distinctive: line 59
Avoid pretending uncertain assumptions are facts.
- Distinctive: line 60
If code context matters, inspect the repo structure first.
- Distinctive: line 61
If an option implies broad code changes, call it out explicitly and suggest a minimal path first.
- Distinctive: line 62
Always read and update the memory file.
- Very specific: line 65
After completing, read .kiro/skills/_scripts/checklist.md for cross-cutting quality checks.
- Very specific: line 68
All code snippets and example files referenced or produced by this skill must be UTF-8 encoded.
≈ “Common” is an estimate: at least 1 in 5 of the 6,350 Cursor rule 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
--- description: "Ideation, option generation, and feature exploration. Use when the user wants to brainstorm ideas, explore options, compare approaches, or generate creative solutions. Triggers: brainstorm, ideate, options, ý tưởng, so sánh phương án." encoding: "UTF-8" agents: [project-planner, orchestrator] globs: "" alwaysApply: false --- ## Memory Protocol **START**: Read `.ai-memory.md` from project root. Use its context to understand project history, tech stack, past decisions, and constraints. If missing, note this and create it after completing this task. **END**: Update `.ai-memory.md` using **Memory Compaction Rules** with: problem, options considered, chosen direction, constraints, and new project understanding. ## Goal Help the user explore many realistic options before implementation. ## Agent Routing - If brainstorm involves system architecture → read `.kiro/skills/agents/agents/project-planner.md` and apply its knowledge - If brainstorm spans multiple domains → read `.kiro/skills/agents/agents/orchestrator.md` and apply its knowledge - If brainstorm is about UI/UX → read `.kiro/skills/agents/agents/frontend-specialist.md` and apply its knowledge - If brainstorm is about APIs/backend → read `.kiro/skills/agents/agents/backend-specialist.md` and apply its knowledge ## Socratic Gate Before generating options, verify: 1. What problem are we solving? (clarity check) 2. What constraints exist? (budget, time, tech stack, team) 3. Who are the users/stakeholders? If any answer is unclear, ASK before proceeding. ## Workflow 1. **Read Memory** — Load `.ai-memory.md` for project context. 2. Restate the problem in one or two sentences. 3. Identify constraints, assumptions, and success criteria from the repository and the prompt. 4. Produce 3-7 strong options with pros, cons, complexity, and risks. 5. Call out the most practical option and the boldest option. 6. End with a recommended next step or implementation path. 7. **Update Memory** — Save new understanding to `.ai-memory.md`. ## Output format - Problem framing - Constraints - Options (3-7 with pros/cons/complexity/risk for each) - Recommendation (most practical + boldest) - Next step ## Checklist - [ ] Problem clearly restated - [ ] Constraints identified from repo + prompt - [ ] At least 3 viable options generated - [ ] Each option has pros, cons, complexity rating - [ ] Practical and bold options highlighted - [ ] Next step recommended - [ ] Memory file updated - [ ] Clean code chuẩn (Standard clean code applied) - [ ] Cập nhật đầy đủ tất cả các file liên quan (All related files fully updated) ## Rules - Prefer practical ideas grounded in the current project. - Avoid pretending uncertain assumptions are facts. - If code context matters, inspect the repo structure first. - If an option implies broad code changes, call it out explicitly and suggest a minimal path first. - Always read and update the memory file. ## Quality Gate After completing, read `.kiro/skills/_scripts/checklist.md` for cross-cutting quality checks. ## Encoding All code snippets and example files referenced or produced by this skill must be UTF-8 encoded. When applicable, include `encoding: "UTF-8"` in SKILL.md front-matter and ensure saved files use UTF-8 (no BOM). ## Related Skills - `/plan` → read `.kiro/skills/plan/SKILL.md` — Turn chosen option into actionable plan - `/create` → read `.kiro/skills/create/SKILL.md` — Implement the chosen option - `/orchestrate` → read `.kiro/skills/orchestrate/SKILL.md` — Coordinate multi-domain brainstorm results
Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.
Of the Cursor rule files we read, the 3,978 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository96 other files it gives its agents.
- .cursor/rules/agents.mdcCursor rule
- .cursor/rules/clean.mdcCursor rule
- .cursor/rules/create.mdcCursor rule
- .cursor/rules/debug.mdcCursor rule
- .cursor/rules/deploy.mdcCursor rule
- .cursor/rules/enhance.mdcCursor rule
- .cursor/rules/explain.mdcCursor rule
- .cursor/rules/instructions.mdcCursor rule
- .cursor/rules/integrate.mdcCursor rule
- .cursor/rules/motion-ui.mdcCursor rule
- .cursor/rules/orchestrate.mdcCursor rule
- .cursor/rules/plan.mdcCursor rule
- .cursor/rules/preview.mdcCursor rule
- .cursor/rules/status.mdcCursor rule
- .cursor/rules/test.mdcCursor rule
- .cursor/rules/ui-ux-pro-max.mdcCursor rule
- agentsSkill
- brainstormSkill
- cleanSkill
- createSkill
- debugSkill
- deploySkill
- enhanceSkill
- explainSkill
- integrateSkill
- motion-uiSkill
- orchestrateSkill
- planSkill
- previewSkill
- statusSkill
- testSkill
- ui-ux-pro-maxSkill
- agentsSkill
- brainstormSkill
- cleanSkill
- createSkill
- debugSkill
- deploySkill
- enhanceSkill
- explainSkill
- integrateSkill
- motion-uiSkill
- orchestrateSkill
- planSkill
- previewSkill
- statusSkill
- testSkill
- ui-ux-pro-maxSkill
- agentsSkill
- brainstormSkill
- cleanSkill
- createSkill
- debugSkill
- deploySkill
- enhanceSkill
- explainSkill
- integrateSkill
- motion-uiSkill
- orchestrateSkill
- planSkill
- The first 60 shown.
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.

