Skip to content
Prompt

ESpice — Cursor Rules

by PM45W

AI Summary

ESpice Cursor Rules provides workflow guidance for development agents using Cursor, structuring task execution around documentation checks and complexity assessment. Developers using Cursor for structured project implementation would benefit from these standardized rules.

Install

Copy this and paste it into Claude Code, Cursor, or any AI assistant:

I want to add the "ESpice — Cursor Rules" prompt rules to my project.
Repository: https://github.com/PM45W/ESpice

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 Rules for ESpice

Primary Directive

You are a development agent implementing a project. Follow established documentation and maintain consistency.

Before Starting Any Task

• Consult /Docs/Implementation.md for current stage and available tasks • Check task dependencies and prerequisites • Verify scope understanding

Task Execution Protocol

• Task Assessment • Read subtask from /Docs/Implementation.md • Assess subtask complexity: • Simple subtask: Implement directly • Complex subtask: Create a todo list • Documentation Research • Check /Docs/Implementation.md for relevant documentation links in the subtask • Read and understand documentation before implementing • UI/UX Implementation • Consult /Docs/UI_UX_doc.md before implementing any UI/UX elements • Follow design system specifications and responsive requirements • Project Structure Compliance • Check /Docs/project_structure.md before: • Running commands • Creating files/folders • Making structural changes • Adding dependencies • Error Handling • Check /Docs/Bug_tracking.md for similar issues before fixing • Document all errors and solutions in Bug_tracking.md • Include error details, root cause, and resolution steps • Task Completion Mark tasks complete only when: • All functionality implemented correctly • Code follows project structure guidelines • UI/UX matches specifications (if applicable) • No errors or warnings remain • All task list items completed (if applicable)

File Reference Priority

• /Docs/Bug_tracking.md - Check for known issues first • /Docs/Implementation.md - Main task reference • /Docs/project_structure.md - Structure guidance • /Docs/UI_UX_doc.md - Design requirements

Discussion

0/2000
Loading comments...

Health Signals

MaintenanceCommitted 8mo ago
Stale
AdoptionUnder 100 stars
1 ★ · Niche
DocsMissing or thin
Undocumented

GitHub Signals

Stars1
Issues0
Updated8mo ago
View on GitHub
No License

My Fox Den

Community Rating

Sign in to rate this booster

Works With

Any AI assistant that accepts custom rules or system prompts

Claude
ChatGPT
Cursor
Windsurf
Copilot
+ more