agentleFS
hiromailyhiromaily/go-crypto-wallet/.cursor/rules/internal/domain-layer.mdc

go-crypto-wallet / internal

Cursor rule128 starsChanged 6 months agoMITView on GitHub

Domain Layer Rules

We split this domain-layer.mdc into the rules it gives an agent

9 rules. About 0 are common, 7 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Add business rules and validators

    line 41
  2. Distinctive:

    Create domain interfaces for infrastructure to implement

    line 43
  3. Distinctive:

    Write pure functions (no side effects)

    line 44
  4. Very specific:

    NEVER: import from infrastructure/, application/, or interface-adapters/

    line 48
  5. Distinctive:

    NEVER: use database, API clients, or file I/O

    line 49
  6. Very specific:

    NEVER: add logging (use pkg/logger/ only if absolutely necessary)

    line 50
  7. Distinctive:

    Use pure unit tests without mocks

    line 54
  8. Distinctive:

    Test business logic in isolation

    line 55
  9. Distinctive:

    No infrastructure dependencies required

    line 56

≈ “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
domain-layer.mdc
---
description: Domain Layer Rules
globs: ["internal/domain/**/*.go"]
alwaysApply: false
---


# Domain Layer Rules

## Overview

Rules for working in the domain layer (`internal/domain/`).
The domain layer contains **pure business logic with ZERO infrastructure dependencies**.

## Key Principles

1. **NO dependencies** on infrastructure (no database, no API clients, no file I/O)
2. Defines interfaces that infrastructure must implement (Dependency Inversion)
3. Contains pure business logic testable without mocks
4. Most stable layer - changes here affect all other layers

## Structure

| Package | Purpose |
|---------|---------|
| `account/` | Account types, validators, multisig configurations |
| `address/` | Address entity and types |
| `auth/` | Authentication account keys and full public keys |
| `bitcoin/` | Bitcoin-specific types (address, transactions, inputs/outputs) |
| `coin/` | Cryptocurrency type definitions |
| `ethereum/` | Ethereum-specific types (account keys, transactions) |
| `key/` | Key value objects, validators, fingerprint, seed |
| `multisig/` | Multisig validators, MuSig2 implementation |
| `payment/` | Payment request types |
| `transaction/` | Transaction entity, types, validators |
| `wallet/` | Wallet types, descriptor builder |
| `xrp/` | XRP-specific types (constants, account keys) |

## Allowed

- Add business rules and validators
- Define value objects and entities
- Create domain interfaces for infrastructure to implement
- Write pure functions (no side effects)

## Forbidden

- **NEVER** import from `infrastructure/`, `application/`, or `interface-adapters/`
- **NEVER** use database, API clients, or file I/O
- **NEVER** add logging (use `pkg/logger/` only if absolutely necessary)

## Testing

- Use pure unit tests **without mocks**
- Test business logic in isolation
- No infrastructure dependencies required
- Tests should be fast and deterministic

## Example: Domain Interface

```go
// internal/domain/multisig/nonce_repository.go
// Domain defines the interface, infrastructure implements it
type NonceRepositorier interface {
    Store(ctx context.Context, nonce *NonceCommitment) error
    GetBySignerAndTx(ctx context.Context, signerID, txID string) (*NonceCommitment, error)
}
```

## Related Rules

- @.claude/rules/internal/clean-architecture.md - Layer dependency rules
- @.claude/rules/go/conventions.md - Go conventions

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.