EGC / rules
Fmarzochi/EGC/.cursor/rules/common-git-workflow.md
Git workflow: conventional commits, PR process
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.
Fmarzochi/EGC/.cursor/rules/common-git-workflow.md
Git workflow: conventional commits, PR process
kanyun-inc/reskill/.cursor/rules/development.mdc
docs/cli-spec.md`:** ``` 1. SPEC → Modify docs/cli-spec.md 2. REVIEW → PR review for spec changes 3. TEST → Write failing tests (integration + unit) 4. CODE → Implement minimal code to pass tests 5. REFACTOR → Improve
kanyun-inc/reskill/.cursor/rules/testing.mdc
Modify docs/cli-spec.md to define expected behavior│ │ 2. REVIEW Review spec changes │ │ 3. TEST Write failing tests based on spec (RED) │ │ 4. CODE Write minimal code to pass tests (GREEN
Kanevry/session-orchestrator/.cursor/rules/020-quality-gates.mdc
When running quality checks — typecheck, test, lint — during development or session execution
Kanevry/session-orchestrator/.cursor/rules/040-discovery.mdc
When the user types /discovery or requests quality analysis, code audit, or issue detection
Kanevry/session-orchestrator/.cursor/rules/060-evolve.mdc
When the user types /evolve or asks about session learnings, pattern extraction, or learning management
Kanevry/session-orchestrator/.cursor/rules/070-gitlab-ops.mdc
When working with GitLab or GitHub — issues, merge requests, pull requests, CI pipelines, labels
lucamezzalira/mfe-skills/.cursor/rules/mfe-architecture-boundary-design.mdc
Micro-frontend architecture: Boundary design. Load when this topic is in scope; part of mfe-skills.
lucamezzalira/mfe-skills/.cursor/rules/mfe-architecture-canvas-pointer.mdc
Micro-frontend architecture: Micro-Frontend Canvas — external skill. Load when this topic is in scope; part of mfe-skills.
lucamezzalira/mfe-skills/.cursor/rules/mfe-architecture-decisions.mdc
Micro-frontend architecture: Micro-frontends decisions framework. Load when this topic is in scope; part of mfe-skills.
lucamezzalira/mfe-skills/.cursor/rules/mfe-architecture.mdc
Provides micro-frontend architecture vocabulary, principles, and decisions framework grounded in Building Micro-Frontends (O'Reilly). Use when a user asks "should we use micro-frontends?", "how do I split my frontend into MFEs?", "what is a micro-frontend?", "help me define MFE boundaries", "should I use horizontal or vertical split?", "how do micro-frontends communicate?", or "is my architecture a distributed monolith?". Requires independent deployment or multi-team scaling as the explicit context. Does not activate for single-team frontend architecture, component design, or build tooling questions with no cross-team deployment angle.
lucamezzalira/mfe-skills/.cursor/rules/mfe-architecture-rules-ref.mdc
Micro-frontend architecture: MFE boundary rules — quick reference. Load when this topic is in scope; part of mfe-skills.
lucamezzalira/mfe-skills/.cursor/rules/mfe-boundary-routing.mdc
MFE boundary review: URL routing ownership — shell vs micro-frontend. Load when this topic is in scope; part of mfe-skills.
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.