golid / rules
golid-ai/golid/.cursor/rules/document-module.mdc
Document an existing module — use when asked to spec, document, or map a module that's already built
The rules real projects give Cursor's agent, from .cursor/rules.
golid-ai/golid/.cursor/rules/document-module.mdc
Document an existing module — use when asked to spec, document, or map a module that's already built
golid-ai/golid/.cursor/rules/feature-flags.mdc
Feature flag patterns — use when working with feature toggles
golid-ai/golid/.cursor/rules/frontend-components-advanced.mdc
Advanced component patterns — lazy loading, production demo-state traps, raw-input exceptions
golid-ai/golid/.cursor/rules/frontend-components.mdc
Patterns for creating and maintaining SolidJS components (atoms, molecules, organisms)
golid-ai/golid/.cursor/rules/frontend-forms.mdc
Form submission and error display patterns — toast vs Alert, batch() in try/catch, field-level errors
golid-ai/golid/.cursor/rules/git-commits.mdc
Git commit and branch conventions
golid-ai/golid/.cursor/rules/go-service.mdc
Patterns for Go service layer files — business logic, DB access, auth checks
golid-ai/golid/.cursor/rules/iteration-surface.mdc
When iteration cost is high, build the iteration surface BEFORE iterating on the artifact — use when planning visual/aesthetic work, slow-deploy contexts, or any feature where the feedback loop exceeds 30 seconds
golid-ai/golid/.cursor/rules/openapi.mdc
Patterns for maintaining the OpenAPI specification
golid-ai/golid/.cursor/rules/parallel-subagents.mdc
Use parallel subagents when auditing or editing 5+ independent files, the user asks to run in parallel, or plan-execution-loop dispatches parallel implement subagents
golid-ai/golid/.cursor/rules/plan-feature-execution.mdc
Feature plan execution — readiness gates, critique loop, permissions, post-implementation handoff
golid-ai/golid/.cursor/rules/plan-feature.mdc
Framework for planning a new feature end-to-end — use when asked to plan or design a new module
golid-ai/golid/.cursor/rules/rename-tool.mdc
Patterns for the project rename tool — file coverage, domain-safe replacement, name validation
golid-ai/golid/.cursor/rules/slice-and-ship.mdc
How to break a planned feature into shippable slices — use when starting implementation of a card or plan
golid-ai/golid/.cursor/rules/solidjs-data-fetching.mdc
Route data fetching — onMount, signals, alive guard, batch; never createResource
golid-ai/golid/.cursor/rules/solidjs-pages.mdc
SolidJS route UI — Switch/Match, modals, auth gates; never nested Show or early returns
golid-ai/golid/.cursor/rules/sse-realtime.mdc
SSE and real-time event patterns — hub, ticket auth, keepalive, reconnect
golid-ai/golid/.cursor/rules/workflow-routing.mdc
Route agent workflow by risk tier before planning, implementing, or auditing
golid-ai/golid/.cursor/rules/write-rules.mdc
How to write, update, and maintain Cursor rules — use when creating a new rule or updating an existing one
golid-ai/golid/.cursor/rules/write-tests.mdc
Patterns for writing backend tests — integration tests with TestDB, unit tests for pure logic, test data seeding
Instruction files for Cursor's agent, kept in .cursor/rules/ as .mdc files.
A rule can apply only to files matching a pattern, or only when the agent asks for it. AGENTS.md always applies.
Copy the .mdc file into your project's .cursor/rules/ directory and adjust its globs.
Open a rule to see its discussion. Reports from people and their agents are coming.