Skills-Agent / rules
Cursor rule4 starsChanged 33 days agoMITView on GitHub
Preview expected output, UX flows, copy, interaction design, or generated content before implementing. Use when the user wants to see what something will look like. Triggers: preview, mockup, show me, xem trước, thử xem, mô phỏng.
We split this preview.mdc into the rules it gives an agent
11 rules. About 0 are common, 4 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
7
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: what was previewed, assumptions, feedback, and confirmed decisions.
- Very specific: line 17
If previewing UI/UX → read .kiro/skills/agents/agents/frontend-specialist.md and apply its knowledge
- Very specific: line 18
If previewing documentation → read .kiro/skills/agents/agents/documentation-writer.md and apply its knowledge
- Very specific: line 19
If previewing API response → read .kiro/skills/agents/agents/backend-specialist.md and apply its knowledge
- Distinctive: line 26
If any answer is unclear, ASK before proceeding.
- Distinctive: line 48
Keep previews realistic and consistent with the current project.
- Distinctive: line 50
Avoid implying broad code changes.
- Distinctive: line 51
Always read and update the memory file.
- Very specific: line 54
After completing, read .kiro/skills/_scripts/checklist.md for cross-cutting quality checks.
- Very specific: line 62
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: "Preview expected output, UX flows, copy, interaction design, or generated content before implementing. Use when the user wants to see what something will look like. Triggers: preview, mockup, show me, xem trước, thử xem, mô phỏng." encoding: "UTF-8" agents: [frontend-specialist, documentation-writer] globs: "" alwaysApply: false --- ## Memory Protocol **START**: Read `.ai-memory.md` from project root. Check UI patterns, design decisions, existing previews, brand guidelines, and user flow notes. **END**: Update `.ai-memory.md` using **Memory Compaction Rules** with: what was previewed, assumptions, feedback, and confirmed decisions. ## Goal Show the user what the result will look or feel like before full implementation. ## Agent Routing - If previewing UI/UX → read `.kiro/skills/agents/agents/frontend-specialist.md` and apply its knowledge - If previewing documentation → read `.kiro/skills/agents/agents/documentation-writer.md` and apply its knowledge - If previewing API response → read `.kiro/skills/agents/agents/backend-specialist.md` and apply its knowledge ## Socratic Gate Before previewing, verify: 1. What artifact is being previewed? (UI, API output, document, flow?) 2. What level of fidelity is expected? (wireframe, mockup, full sample?) 3. Any specific requirements or constraints? If any answer is unclear, ASK before proceeding. ## Workflow 1. **Read Memory** — Load `.ai-memory.md` for project context and design history. 2. Infer the artifact being previewed: UI, API output, document, message, workflow, or report. 3. Produce a faithful mock, sample output, walkthrough, or structured preview. 4. Highlight assumptions behind the preview. 5. Identify what could change during implementation. 6. **Update Memory** — Save preview details and decisions to `.ai-memory.md`. ## Checklist - [ ] Artifact type identified - [ ] Preview is realistic and faithful - [ ] Assumptions clearly labeled - [ ] Mock data marked as illustrative - [ ] Implementation differences noted - [ ] 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 - Keep previews realistic and consistent with the current project. - Label illustrative content clearly when it is mock data. - Avoid implying broad code changes; if the preview would require major refactor, CALL IT OUT and ASK before implementation. - Always read and update the memory file. ## Quality Gate After completing, read `.kiro/skills/_scripts/checklist.md` for cross-cutting quality checks. ## Related Skills - `/create` → read `.kiro/skills/create/SKILL.md` — Implement the previewed design - `/ui-ux-pro-max` → read `.kiro/skills/ui-ux-pro-max/SKILL.md` — Advanced UI/UX design - `/plan` → read `.kiro/skills/plan/SKILL.md` — Plan implementation of previewed feature ## 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).
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/brainstorm.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/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.