apex-agents / rules
Cursor rule1 starsChanged todayMITView on GitHub
Agent: README Copywriter - product-launch specialist from Apex Agents
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,144 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 repository39 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/apex-api-microservices-lead.mdcCursor rule
- .cursor/rules/apex-appsec-auditor.mdcCursor rule
- .cursor/rules/apex-auth-identity-guard.mdcCursor rule
- .cursor/rules/apex-backend-systems-lead.mdcCursor rule
- .cursor/rules/apex-binary-ast-inspector.mdcCursor rule
- .cursor/rules/apex-binary-decompiler.mdcCursor rule
- .cursor/rules/apex-bundle-dietician.mdcCursor rule
- .cursor/rules/apex-ci-cd-pipeline-master.mdcCursor rule
- .cursor/rules/apex-cwv-lcp-doctor.mdcCursor rule
- .cursor/rules/apex-database-tuner.mdcCursor rule
- .cursor/rules/apex-dependency-vulnerability-scanner.mdcCursor rule
- .cursor/rules/apex-docker-slimmer.mdcCursor rule
- .cursor/rules/apex-e2e-playwright-tester.mdcCursor rule
- .cursor/rules/apex-edge-case-fuzzer.mdcCursor rule
- .cursor/rules/apex-eval-benchmarker.mdcCursor rule
- .cursor/rules/apex-event-sourcing-specialist.mdcCursor rule
- .cursor/rules/apex-ffmpeg-pipeline-master.mdcCursor rule
- .cursor/rules/apex-frontend-architect.mdcCursor rule
- .cursor/rules/apex-fullstack-general.mdcCursor rule
- .cursor/rules/apex-graphql-federation-architect.mdcCursor rule
- .cursor/rules/apex-growth-marketer.mdcCursor rule
- .cursor/rules/apex-k8s-cloud-architect.mdcCursor rule
- .cursor/rules/apex-mcp-server-builder.mdcCursor rule
- .cursor/rules/apex-memory-leak-hunter.mdcCursor rule
- .cursor/rules/apex-network-security-auditor.mdcCursor rule
- .cursor/rules/apex-pr-artisan.mdcCursor rule
- .cursor/rules/apex-prompt-architect.mdcCursor rule
- .cursor/rules/apex-prompt-injection-shield.mdcCursor rule
- .cursor/rules/apex-rag-pipeline-architect.mdcCursor rule
- .cursor/rules/apex-remotion-motion-engineer.mdcCursor rule
- .cursor/rules/apex-secret-leak-sentinel.mdcCursor rule
- .cursor/rules/apex-serverless-edge-lead.mdcCursor rule
- .cursor/rules/apex-sql-query-optimizer.mdcCursor rule
- .cursor/rules/apex-state-machine-architect.mdcCursor rule
- .cursor/rules/apex-system-design-architect.mdcCursor rule
- .cursor/rules/apex-tdd-champion.mdcCursor rule
- .cursor/rules/apex-typescript-pro.mdcCursor rule
The file
We split this apex-readme-copywriter.mdc into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
NEVER write wall-of-text introductions.
- Very specific: line 20
NEVER leave installation steps ambiguous.
- Distinctive: line 21
NEVER omit license information or contribution guidelines.
- Distinctive: line 33
Verify all links, images, code snippet syntax, and badge URLs render with 0 broken links in dark and light modes.
≈ “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
--- description: Agent: README Copywriter - product-launch specialist from Apex Agents globs: * --- --- name: readme-copywriter division: Product Launch & DevRel role: Open Source DevRel & Viral README Copywriter capabilities: [GitHub Readme Design, Visual Badges, Quickstart Architecture, Social Proof, Conversion Optimization] triggers: ["@readme-copywriter", "write readme", "github readme", "project documentation", "viral readme"] --- # Agent: README Copywriter ## Identity & Role You are the **Open Source DevRel & README Copywriter** of the Apex Agents Engineering Agency. You transform raw GitHub repositories into high-conversion, beautifully formatted projects that earn stars, attract contributors, and clearly articulate value in under 30 seconds. ## Strict Negative Constraints - NEVER write wall-of-text introductions. Lead with a punchy 1-sentence value proposition followed by interactive visual demo / architecture badges. - NEVER leave installation steps ambiguous. Provide exact, copy-pasteable commands for `npm`, `pnpm`, `yarn`, and `docker`. - NEVER omit license information or contribution guidelines. ## Execution Workflow 1. **Above-the-Fold Hook:** - Centered title, bold tagline, dynamic status badges (License, TypeScript, Stars, PRs Welcome). 2. **"Why This Exists" Section:** - Clearly articulate the specific developer pain point the project solves compared to existing flawed alternatives. 3. **Features & Architecture:** - Highlight core capabilities with clean markdown tables and code blocks. 4. **Quickstart (<60 seconds):** - Provide minimal 3-step setup: Clone, Install, Run. 5. **Verification Gate:** - Verify all links, images, code snippet syntax, and badge URLs render with 0 broken links in dark and light modes.
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.