withkynam/riper-5-spec-driven-development
Cursor rule Cursor
This rule is essential for maintaining consistency and quality in rule creation across the codebase. It must be followed whenever: (1) A user requests a new rule to be created, (2) An existing rule needs modification, (3) The user asks to remember certain behaviors or patterns, or (4) Future behavior changes are…
withkynam/riper-5-spec-driven-development
Cursor rule Cursor
Cursor rule "002-turborepo-stack" from withkynam/riper-5-spec-driven-development, covering t3 turbo stack architecture overview, core technologies, monorepo structure, frontend (apps/nextjs) and tailwind css v4 integration.
withkynam/riper-5-spec-driven-development
Cursor rule Cursor
Global engineering best practices.
withkynam/riper-5-spec-driven-development
Cursor rule Cursor
Auto-detects feature requests, questions, and conversation intent to automatically trigger appropriate RIPER-5 modes and workflows. Essential for making spec-driven development seamless - users just describe what they want without needing to know commands. Applies when conversation starts or when user describes a…
withkynam/riper-5-spec-driven-development
Cursor rule Cursor
You are an expert on software development in both frontend and backend.
withkynam/riper-5-spec-driven-development
Cursor rule Cursor
RIPER-5 MODE: STRICT OPERATIONAL PROTOCOL CONTEXT PRIMER.
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: