AI SummaryCursor-Demo provides a comprehensive set of development rules and workflows (SPARC methodology) designed to guide AI-assisted coding in Cursor with emphasis on code quality, security, and structured collaboration between human developers and autonomous agents.
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to add the "Cursor-Demo — Cursor Rules" prompt rules to my project. Repository: https://github.com/mondweep/Cursor-Demo Please read the repo to find the rules/prompt file, then: 1. Download it to the correct location (.cursorrules, .windsurfrules, .github/prompts/, or project root — based on the file type) 2. If there's an existing rules file, merge the new rules in rather than overwriting 3. Confirm what was added
Description
Cursor-Demo-Agentics-Hackathon
Core Philosophy
• Simplicity • Prioritize clear, maintainable solutions; minimize unnecessary complexity. • Iteration • Enhance existing code unless fundamental changes are clearly justified. • Focus • Stick strictly to defined tasks; avoid unrelated scope changes. • Quality • Deliver clean, well-tested, documented, and secure outcomes through structured workflows. • Collaboration • Foster effective teamwork between human developers and autonomous agents.
Development Workflow (SPARC)
• Specification • Define clear objectives, requirements, user scenarios, and acceptance criteria. • Never hard-code environment variables or credentials. • Pseudocode • Map out logical implementation pathways before coding. • Identify core functions, data structures, and algorithms. • Architecture • Design modular components with clear boundaries and interfaces. • Establish proper separation of concerns. • Refinement • Implement with TDD, debugging, security checks, and optimization. • Refactor for maintainability. • Completion • Integrate, document, test, and verify against acceptance criteria.
Code Quality Rules
• File & Function Limits • Every file ≤ 500 lines • Every function ≤ 50 lines with clear single responsibility • Security Essentials • No hard-coded secrets, credentials, or environment variables • All user inputs must be validated and sanitized • Proper error handling in all code paths • Security vulnerabilities must be proactively prevented • Best Practices • DRY (Don't Repeat Yourself): Eliminate code duplication • SOLID Principles: Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion • Clean Code: Descriptive naming, consistent formatting, minimal nesting • Testability: Design for unit testing with dependency injection
TDD Workflow (London School)
• Red: Write failing tests first (outside-in development) • Green: Implement minimal code to make tests pass • Refactor: Clean up code while maintaining test coverage Non-Negotiable Requirements: • Tests MUST be written before implementation code • Implementation MUST be minimal to pass tests • Mocks/stubs MUST be used for dependencies • Test doubles MUST verify collaboration, not just state
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster
Works With
Any AI assistant that accepts custom rules or system prompts