agentleFS
Fullive-AIFullive-AI/Anima/.cursor/rules/Architecture-Guardrails.mdc

Anima / rules

Cursor rule1k starsChanged 5 months agoApache-2.0View on GitHub

Protect the existing architecture unless the task explicitly requires architectural change. First identify:

We split this Architecture-Guardrails.mdc into the rules it gives an agent

12 rules. About 0 are common, 12 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈12

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Prefer local, minimal, boundary-respecting changes.

    line 9
  2. Distinctive:

    Do not introduce new layers, abstractions, or patterns unless clearly justified.

    line 11
  3. Distinctive:

    Do not widen the change surface unnecessarily.

    line 12
  4. Distinctive:

    Do not use a bug fix or small feature as an excuse for broad redesign.

    line 13
  5. Distinctive:

    Do not move logic across layers without a strong reason.

    line 29
  6. Distinctive:

    Avoid creating duplicate sources of truth.

    line 30
  7. Distinctive:

    Prefer extending an existing abstraction over inventing a parallel one.

    line 31
  8. Distinctive:

    Prefer explicit data flow over hidden coupling.

    line 32
  9. Distinctive:

    Keep cross-module changes small and intentional.

    line 33
  10. Distinctive:

    Keep the change as small as possible.

    line 48
  11. Distinctive:

    Update tests and docs affected by the architectural shift.

    line 50
  12. Distinctive:

    Avoid combining architectural cleanup with unrelated feature work.

    line 51

≈ “Common” is an estimate: at least 1 in 5 of the 6,350 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
Architecture-Guardrails.mdc
---
alwaysApply: true
---

Protect the existing architecture unless the task explicitly requires architectural change.

## Core principles

- Prefer local, minimal, boundary-respecting changes.
- Fit new work into existing module boundaries whenever possible.
- Do not introduce new layers, abstractions, or patterns unless clearly justified.
- Do not widen the change surface unnecessarily.
- Do not use a bug fix or small feature as an excuse for broad redesign.

## Before changing code

First identify:

- the owning module or subsystem
- its direct dependencies
- the inbound callers or consumers
- the outward contracts it exposes
- whether the change belongs here or elsewhere

## Guardrails

- Keep responsibilities separated.
- Respect dependency direction.
- Do not move logic across layers without a strong reason.
- Avoid creating duplicate sources of truth.
- Prefer extending an existing abstraction over inventing a parallel one.
- Prefer explicit data flow over hidden coupling.
- Keep cross-module changes small and intentional.

## Prohibited behavior unless clearly necessary

- broad refactors unrelated to the task
- introducing framework-level patterns for small local problems
- changing multiple subsystems to support a narrow fix when a local fix is possible
- creating generic helpers too early
- mixing transport, domain, UI, persistence, and integration logic in the same place

## If architectural change is genuinely required

Then:

1. State why the existing structure blocks the task.
2. Keep the change as small as possible.
3. Preserve backward compatibility where feasible.
4. Update tests and docs affected by the architectural shift.
5. Avoid combining architectural cleanup with unrelated feature work.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

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.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.