mfe-skills / rules
lucamezzalira/mfe-skills/.cursor/rules/mfe-boundary-toolchain.mdc
MFE boundary review: MFE boundary rules — toolchain patterns. Load when this topic is in scope; part of mfe-skills.
The rules real projects give Cursor's agent, from .cursor/rules.
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
lucamezzalira/mfe-skills/.cursor/rules/mfe-boundary-toolchain.mdc
MFE boundary review: MFE boundary rules — toolchain patterns. Load when this topic is in scope; part of mfe-skills.
tenstorrent/tt-studio/.cursor/rules/ai-models.mdc
AI model integration and deployment rules for TT Studio
tenstorrent/tt-studio/.cursor/rules/project-overview.mdc
Project overview and navigation map for TT-Studio - what it is, where the docs live, and its key components
delphicleancode/delphi-spec-kit/.cursor/rules/intraweb-patterns.md
Code rules and standards for developing applications with the Intraweb framework.
duongductrong/antigravity-kit/.cursor/rules/toc.mdc
distinctive interfaces - [Backend Development](../skills/backend-development/SKILL.mdc) - API design, architecture, authentication, security, and DevOps patterns - [Frontend Design](../skills/frontend-design/SKILL.mdc) - Create distinctive, production-grade interfaces with bold aesthetics (avoid generic AI slop) - [Frontend Development
saharmor/simulatedev/.cursor/rules/running_backend.mdc
Every time Cursor is trying to run the backend or test it, i.e. needing port 8000
synaptiai/prompt-decorators/.cursor/rules/900-software-dev-decorators.mdc
APPLY software development decorators WHEN coding TO improve code quality and clarity
AndreRatzenberger/cursor-rules/.cursor/rules/knowledge-management-rule.mdc
Comprehensive knowledge management system for capturing, organizing, and applying project knowledge
theognis1002/mcp-gateway/.cursor/rules/main.mdc
function at most unless the function is very complicated. 1. Use `bun` for frontend app 1. Types should go into `apps/backend/internal/types` directory
golid-ai/golid/.cursor/rules/audit-bugs.mdc
Bug audit checklist — use when asked to review code for bugs, security issues, or quality problems
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/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/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
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.