premortem / CO-STAR-UI-CREATOR
Cursor rule2 starsChanged 5 months agoApache-2.0View on GitHub
This file is the universal actual command for the CO-STAR UI Creator. When invoked, the AI must decide and weigh which resource to use based on the user's intent, then apply it. Pre-action (mandatory): Before doing anything else, find and locate where the files referenced in this command live in the user’s workspace: - CO-STAR-PROMPT.md - CO-STAR-CREATOR.md - AGENT.mdc (optional but useful) Search the project (e.g. .cursor/rules/CO-STAR-UI-CREATOR/, .cursor/commands/ui-template/CO-STAR-UI-CREATOR/, or elsewhere). Once you have their paths (initial data), then proceed with…
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 4,183 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 repository168 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/CO-STAR-UI-CREATOR/AGENT.mdcCursor rule
- .cursor/rules/CO-STAR-UI-CREATOR/CO-STAR-CREATOR.mdCursor rule
- .cursor/rules/CO-STAR-UI-CREATOR/CO-STAR-PROMPT.mdCursor rule
- .cursor/rules/CO-STAR-UI-CREATOR/README.mdCursor rule
- 401-403-bypass-techniquesSkill
- active-directory-acl-abuseSkill
- active-directory-certificate-servicesSkill
- active-directory-kerberos-attacksSkill
- agent-browserSkill
- ai-ml-securitySkill
- ai-seoSkill
- android-pentesting-tricksSkill
- anti-debugging-techniquesSkill
- api-auth-and-jwt-abuseSkill
- api-authorization-and-bolaSkill
- api-recon-and-docsSkill
- api-secSkill
- arbitrary-write-to-rceSkill
- arize-adminSkill
- arize-ai-provider-integrationSkill
- arize-annotationSkill
- arize-compliance-auditSkill
- arize-datasetSkill
- arize-evaluatorSkill
- arize-experimentSkill
- arize-instrumentationSkill
- arize-linkSkill
- arize-prompt-optimizationSkill
- arize-promptsSkill
- arize-traceSkill
- authbypass-authentication-flawsSkill
- auth-secSkill
- binary-protection-bypassSkill
- browser-exploitation-v8Skill
- building-nango-functions-locallySkill
- building-nango-functions-remotelySkill
- building-nango-functionsSkill
- business-logic-vulnerabilitiesSkill
- business-logic-vulnSkill
- classical-cipher-analysisSkill
- clickjackingSkill
- cmdi-command-injectionSkill
- code-obfuscation-deobfuscationSkill
- compliance-checkSkill
- compliance-trackingSkill
- container-escape-techniquesSkill
- core-engineeringSkill
- cors-cross-origin-misconfigurationSkill
- crlf-injectionSkill
- csp-bypass-advancedSkill
- csrf-cross-site-request-forgerySkill
- csv-formula-injectionSkill
- d3-visualizationSkill
- dangling-markup-injectionSkill
- defi-attack-patternsSkill
- dependency-confusionSkill
- deserialization-insecureSkill
- dns-rebinding-attacksSkill
- documentation-writerSkill
- The first 60 shown.
The file
We split this ui.md into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Pre-action (mandatory): Before doing anything else, find and locate where the files referenced in this command live in the user’s workspace:
- Very specific: line 14
Search the project (e.g. .cursor/rules/CO-STAR-UI-CREATOR/, .cursor/commands/ui-template/CO-STAR-UI-CREATOR/, or elsewhere).
- Distinctive: line 35
Keywords/signals for CO-STAR-CREATOR.md: create my prompt, custom prompt, my own CO STAR, design system doc, template for our product, …
- Very specific: line 42
If CO-STAR-PROMPT.md: Follow that file completely (role, C/O/S/T/A/R, scoped questions first, then plan, then implementation).
- Distinctive: line 43
If CO-STAR-CREATOR.md: Follow that file to help the user define their custom CO STAR prompt (context, objective, style, tone, audience, …
≈ “Common” is an estimate: at least 1 in 5 of the 6,668 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
CO-STAR UI Creator — Universal Command
This file is the universal actual command for the CO-STAR UI Creator. When invoked, the AI must decide and weigh which resource to use based on the user's intent, then apply it.
Your task
Pre-action (mandatory): Before doing anything else, find and locate where the files referenced in this command live in the user’s workspace:
- CO-STAR-PROMPT.md
- CO-STAR-CREATOR.md
- AGENT.mdc (optional but useful)
Search the project (e.g. .cursor/rules/CO-STAR-UI-CREATOR/, .cursor/commands/ui-template/CO-STAR-UI-CREATOR/, or elsewhere). Once you have their paths (initial data), then proceed with the steps below. Do not skip this step.
- Interpret the user's message or request.
- Decide which of the two resources below applies (and with what priority).
- Use that resource as the source of truth for your response. Do not mix or bypass it.
Decision: which resource to use
| If the user wants to… | Use this | Weight / priority |
| Build, implement, or change UI — components, pages, design system, integration with shadcn/Magic UI/etc., refactors, new features | CO-STAR-PROMPT.md | Primary. Follow its full flow (discovery → plan → implementation). |
| Create or customize a CO STAR prompt — their own prompt, design system, product goals, or CO-STAR template from scratch | CO-STAR-CREATOR.md | Primary. Use it to guide them through Context, Objective, Style, Tone, Audience, Response. |
| Unclear or mixed intent — e.g. “help with UI and also I want my own prompt” | Weigh by main ask. If the main ask is implementation → CO-STAR-PROMPT.md first; if the main ask is “create my prompt” → CO-STAR-CREATOR.md first. Optionally do the second as a follow-up. |
Weighing rules (how to decide)
- Keywords/signals for CO-STAR-PROMPT.md: build, implement, add, refactor, component, page, section, design system, shadcn, Tailwind, React, Next.js, hero, dashboard, landing, integrate, copy-paste registry.
- Keywords/signals for CO-STAR-CREATOR.md: create my prompt, custom prompt, my own CO STAR, design system doc, template for our product, tailor CO-STAR to our app, prompt from our goals.
- Default when purely “help with UI” or “do the CO-STAR thing”: use CO-STAR-PROMPT.md.
After you choose
- If CO-STAR-PROMPT.md: Follow that file completely (role, C/O/S/T/A/R, scoped questions first, then plan, then implementation). Do not skip steps.
- If CO-STAR-CREATOR.md: Follow that file to help the user define their custom CO STAR prompt (context, objective, style, tone, audience, response format).
This file (ui.md) is the command; CO-STAR-PROMPT.md and CO-STAR-CREATOR.md are the resources you invoke based on your decision.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.