Cursor rule Cursor
A project rule set describing a four-stage workflow: design, planning, implementation, and testing. It is written in Chinese and defines documents, roles, entry conditions, exit conditions, and status labels for each stage.
Cursor rule Cursor
Product-design rules that guide an agent to turn unclear user needs into a focused product plan, with an MVP, success measures, priorities, and risks. They also define a format for storing design documents and version history.
Cursor rule Cursor
Planning-stage rules that turn an active product requirements document into an implementation plan. They break work into tasks, map dependencies, set milestones, and consider system boundaries, technical risks, and future changes.
Cursor rule Cursor
Implementation-stage rules for turning an approved product requirements document and plan into maintainable, tested code. They cover preparation, incremental work, self-testing, security, error handling, readability, and performance.
Cursor rule Cursor
A set of software testing rules written from a quality-assurance perspective. It covers unit tests for individual functions, integration tests for cooperating parts, and end-to-end tests for complete user journeys.
Cursor rule Cursor
A project rule set for planning and implementing work from Product Requirements Documents (PRDs), which describe what a software feature should do. It defines where PRDs live, how to reference them, and which project checks to run.
Cursor rule Cursor
A development rule that says to ask the user whenever the requirements do not settle an important decision. It covers architecture, implementation details, business rules, edge cases, naming, and file placement.
Cursor rule Cursor
A project-onboarding guide for a PRD toolkit. A PRD is a product requirements document describing what a project should build and how it should be checked.
Cursor rule Cursor
A workflow for turning a product requirements document, or PRD, into implemented and checked software. A PRD describes what a product or feature should do, while the workflow sets implementation constraints and reporting steps.
Cursor rule Cursor
A project rulebook for building Godot 4 games with C#. It describes how to organize game code into layers, such as screens, UI state, and shared services, and how parts of the game communicate through events.
Cursor rule Cursor
Naming rules for a Godot 4 game written mainly in C#. Godot is a game engine, and these rules explain how to name classes, scenes, nodes, scripts, and user-interface code.
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: