Content
57%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A compact, well-organized set of project-specific DDD rules whose strongest parts are the concrete constraints (private setters, ValueObject base class, DomainException, spec-*.md as the sole rule source). It is dragged down by textbook DDD definitions Claude already knows, the absence of any complete code example, and the lack of a sequenced define-write-validate workflow with checkpoints.
Suggestions
Drop or compress the textbook definitions of Entities, Value Objects, and Aggregate Roots (items 2–4) to one-line constraints, keeping only project-specific rules like extending the 'ValueObject' base class.
Add one complete example (entity or value object) showing private setters, a business method like 'AlterarStatus(Status status)', and a 'DomainException' throw, so the guidance is executable rather than rule-based.
Restructure the guidance as a short ordered flow — read the 'spec-*.md' file for the entity, define the model with private setters, validate invariants before finishing — so the promised 'definição, escrita e validação' sequence is explicit.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient — the numbered rules are short and constraint-focused — but several bullets restate textbook DDD definitions Claude already knows, e.g., 'Objetos com uma identidade única e contínua ao longo do tempo (possuem ID de entidade)' and 'Objetos imutáveis definidos unicamente por seus atributos, sem identidade própria', plus the generic aggregate-root example. This is 'some unnecessary explanation that could be tightened' rather than the noticeably padded level of 2, since the definitions are brief and the rest is project-specific guidance. | 3 / 5 |
Actionability | There is some concrete guidance — '{ get; private set; }', method examples like 'AlterarStatus(Status status)', the 'ValueObject' base class, 'DomainException', and the 'spec-*.md' source of rules — but no complete executable example of an entity, value object, or a DomainException being thrown. The guidance is closer to rules with pseudocode-level hints than copy-paste-ready instruction, matching the 3 anchor ('some concrete guidance but incomplete') and clearly below the mostly-executable level of 4. | 3 / 5 |
Workflow Clarity | The six numbered items are topic categories, not a sequence; although the header promises 'orienta a definição, escrita e validação', there is no ordered flow (e.g., read spec-*.md → define the entity → run invariant checks) and validation appears only as a rule ('Lance uma exceção de domínio') without checkpoints or a verification step. This is not incoherent (so above 2), but checkpoints and sequencing are missing, matching anchor 3. | 3 / 5 |
Progressive Disclosure | The body is under 50 lines, needs no external reference files (none exist in the bundle), and is well organized as a single 'Diretrizes do Domínio' section with six numbered, titled rules — per the simple-skill scoring note this earns the top score without external file references. | 5 / 5 |
Total | 14 / 20 Passed |