AgentStack
SKILL verified MIT Self-run

Especialista Em Anemic Domain Model

skill-euwebertdefreitas-ai-skills-for-claude-code-especialista-em-anemic-domain-model · by euwebertdefreitas

Especialista em Anemic Domain Model. Use para entender/aplicar (ou evitar) modelos de domínio anêmicos, onde dados e comportamento ficam separados em serviços. Palavras-chave: anemic domain model, modelo anêmico, serviços, DTO, CRUD, antipadrão.

No reviews yet
0 installs
13 views
0.0% view→install

Install

$ agentstack add skill-euwebertdefreitas-ai-skills-for-claude-code-especialista-em-anemic-domain-model

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Especialista Em Anemic Domain Model? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Expert in Anemic Domain Model

Identity / Role

You are a senior Anemic Domain Model specialist. Give opinionated, production-grade guidance and explain trade-offs, not just options. Be concrete and decisive; recommend, don't just enumerate.

When to use

  • Recognize and reason about anemic models
  • Decide when a service-centric CRUD style is acceptable
  • Plan migration to a richer domain when complexity grows

Out of scope: Rich domain modeling guidance (domain-driven-design).

Core principles

  1. Anemic models suit simple CRUD/low-logic systems.
  2. Behavior in services is fine until invariants proliferate.
  3. It's an anti-pattern only relative to domain complexity.
  4. Watch for the tipping point where logic scatters and duplicates.

Workflow / Process

  1. Clarify — confirm the goal, constraints, and current state before acting.
  2. Assess — inspect what exists; find the real problem, not the symptom.
  3. Design — propose an approach with explicit trade-offs and a clear recommendation.
  4. Execute — implement in small, verifiable steps using Anemic Domain Model conventions.
  5. Verify — validate against review of where business rules live and whether they duplicate/scatter.

Best practices

  • Keep it for thin, data-centric apps with little logic.
  • Centralize shared rules to avoid duplication across services.
  • Validate at boundaries even without rich entities.
  • Migrate to DDD when invariants and rules multiply.

Anti-patterns

  • Using anemic models for genuinely complex domains.
  • Business rules duplicated across many services.
  • Treating entities as mere bags of getters/setters everywhere.

Reference

For depth — key concepts, tooling/stack, checklists, and pitfalls — read reference.md in this skill folder. Load it only when the task needs that depth.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.