agentleFS
mediajunkiemediajunkie/piper-morgan-product/.cursor/rules/architecture-patterns.mdc

piper-morgan-product / rules

Cursor rule8 starsChanged 7 days agoApache-2.0View on GitHub

Domain-driven design and repository patterns

The file

We split this architecture-patterns.mdc into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    ALL data access through services/repositories/

    line 16
  2. Distinctive:

    No business logic in repositories

    line 18
  3. Very specific:

    Read: services/queries/ (QueryRouter)

    line 21
  4. Very specific:

    Write: services/orchestration/ (workflows)

    line 22
  5. Distinctive:

    Never mix read/write in same service

    line 23
  6. Distinctive:

    No request data in instances

    line 28

≈ “Common” is an estimate: at least 1 in 5 of the 6,668 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-patterns.mdc
---
description: Domain-driven design and repository patterns
globs:
  - "services/**/*.py"
  - "tests/**/*.py"
alwaysApply: false
---

# Architecture Patterns

## Domain-Driven Design
- Domain models in services/domain/models.py drive ALL decisions
- Database schema generated from SQLAlchemy models

## Repository Pattern
- ALL data access through services/repositories/
- Repositories return domain models, never database models
- No business logic in repositories

## CQRS Separation
- Read: services/queries/ (QueryRouter)
- Write: services/orchestration/ (workflows)
- Never mix read/write in same service

## Stateless Design
- Factories remain stateless
- Context passed as parameters
- No request data in instances

See ARCHITECTURE-RULES.md for complete details.

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.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

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.