Cursor rule
A set of rules for generating Go model, persistence-object, and converter files from SQL CREATE TABLE statements. A persistence object is the database-facing version of a data structure.
Cursor rule
A set of rules for writing unit tests in Go, the programming language used by the examples. It covers test names, table-driven cases, subtests, mocks, assertions, file placement, and basic test quality principles.
Cursor rule
A set of rules for writing and changing Go code according to Uber's Go style guidelines. It covers formatting, imports, names, declarations, and related code conventions.
Cursor rule
A keyword-based rule set that selects other project instructions when specific words appear in a request.
Cursor rule
A project-structure rule for Go applications using domain-driven design, an approach that organizes code around business concepts. It describes folders for APIs, services, domain models, infrastructure, deployments, documentation, and shared tools.
Cursor rule
A conversation rule for handling complex questions that lack important details. It asks for context such as the role, background, goal, desired output, and ways to verify the answer.
Cursor rule
A set of rules for writing technical solution documents in a project's docs folder. The template covers requirements, purpose, design, diagrams, database and API changes, rollout notes, and task breakdowns.
Cursor rule
A set of rules for turning a product request into a clear, checkable plan. It covers gathering context, splitting work into smaller features, checking technical feasibility, and recording risks and acceptance criteria.
Cursor rule
Rules for breaking a large software request into smaller tasks with clear inputs, outputs, dependencies, status markers, and acceptance criteria. They limit each task's size and require it to be independently verifiable.
Cursor rule
A review procedure for Go code changes. It checks code quality, security risks, performance issues, affected services, release dependencies, and produces a review report.
Cursor rule
A Git commit review and message-formatting procedure. It checks code changes for risks before creating a commit and uses a structured format for the commit message.
Cursor rule
A rule for turning a code change and its chat history into a documented development procedure. It asks for a file tree, a Mermaid dependency diagram, and notes about likely problems and fixes.