Cursor rule Cursor
Use ALWAYS when asked to CREATE A RULE or UPDATE A RULE or taught a lesson from the user that should be retained as a new rule for Cursor.
A standardized framework for enhancing how LLMs process and respond to prompts through composable decorators, featuring an official open standard specification and Python reference implementation. Claude Code plugin and MCP server integration.
This repository also configures its own agents. See what prompt-decorators tells them →
Cursor rule Cursor
Use ALWAYS when asked to CREATE A RULE or UPDATE A RULE or taught a lesson from the user that should be retained as a new rule for Cursor.
Cursor rule Cursor
Use emojis strategically in AI responses to enhance communication and user experience.
Cursor rule Cursor
ENSURE careful modifications WHEN changing code TO prevent breakage.
Cursor rule Cursor
FOLLOW coding patterns WHEN writing code TO maintain codebase quality.
Cursor rule Cursor
MAINTAIN development discipline WHEN implementing changes TO preserve codebase integrity.
Cursor rule Cursor
ALWAYS use when writing or updating Markdown files to ensure consistent formatting and readability. This rule enforces standardized Markdown practices across all documentation.
Cursor rule Cursor
APPLY software development decorators WHEN coding TO improve code quality and clarity.
Cursor rule Cursor
This is your core operating instruction set to work in the proper sequence the user demands. ALWAYS ensure you use this in every chat as this is your critical memory system also.
Cursor rule Cursor
ALWAYS use when creating a new PRD or modifying an existing one to ensure consistent structure and completeness. This rule enforces standardized PRD format with all required sections and proper documentation hierarchy.
Cursor rule Cursor
ALWAYS use when creating or updating Architecture document to ensure consistent documentation of architectural decisions. This rule enforces standardized arch format with proper context, consequences, and status tracking.
Cursor rule Cursor
ALWAYS use when creating or updating story files to ensure proper tracking and implementation. This rule enforces consistent story structure with tasks, context, and progress tracking.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: