Cursor rules for README documentation with best practices integration.
.cursorrules or .cursor/rules/readme-best-practices.mdc Write READMEs like landing pages, not API docs. The reader decides in 3-5 seconds. Start with a bold one-liner saying what it does and why someone should care. Not "A tool that..." - a punchline. Put a working code example in the first 5 lines. Show the value prop immediately. Use feature tables (two columns) instead of **Feature:** bullet lists. Tables scan faster. Quick Start must be copy-paste ready. No $ prefix on bash commands. Zero to running in 30 seconds. Vary sentence lengths and structure. Mix one-liners with short paragraphs and tables. Not walls of same-length bullets. Never use "seamless", "robust", "comprehensive", "cutting-edge", or other AI marketing words. Never open with "In today's..." or close with "Happy coding!" Check that referenced assets (demo.gif, screenshots) actually exist on disk before adding image links. Author section should include a visual card or badge, not just plain text "Made by username".
Write READMEs like landing pages, not API docs. The reader decides in 3-5 seconds.
Start with a bold one-liner saying what it does and why someone should care. Not “A tool that…” - a punchline. Put a working code example in the first 5 lines. Show the value prop immediately. Use feature tables (two columns) instead of Feature: bullet lists. Tables scan faster. Quick Start must be copy-paste ready. No $ prefix on bash commands. Zero to running in 30 seconds. Vary sentence lengths and structure. Mix one-liners with short paragraphs and tables. Not walls of same-length bullets. Never use “seamless”, “robust”, “comprehensive”, “cutting-edge”, or other AI marketing words. Never open with “In today’s…” or close with “Happy coding!” Check that referenced assets (demo.gif, screenshots) actually exist on disk before adding image links. Author section should include a visual card or badge, not just plain text “Made by username”.
Quantitative factor research skills for Cursor. Evaluate factors, run backtests, mine new alpha through natural language.
Prevent AI over-engineering by keeping changes scoped, simple, and directly tied to the user's request
Anti-sycophancy directives for code review and generation. Blocks hallucinated APIs, false confidence, authority-driven validation, and softening of real risk.
Cursor rules for Aspnet Abp.
Guidelines and best practices for building applications with [Beefree SDK](https://docs.beefree.io/beefree-sdk), including installation, authentication, configuration, customization, and template management
Cursor rules for embedding Beefree SDK's no-code content editors (for emails, pages, and popups) into a web application.