domain-logic-style

Name: domain-logic-style
Author: iPzard

Picking Domain Model and writing transaction scripts inside it is the worst of both worlds.

by iPzard(0) 0 installs

Free

Free account. Installing gives you the manifest plus copy-paste snippets.

See reviews

About

Instruction file imported from iPzard/coding-agents (.github/instructions/architecture-scalability/domain-logic-style.instructions.md). Copyright stays with the author.

Domain-logic style

Cite as: [Domain-logic style]

Principle

Pick one and stay with it:

Transaction Script — procedural, fine for simple CRUD.
Table Module — record-set centric.
Domain Model — rich object model, scales with domain complexity.

Picking Domain Model and writing transaction scripts inside it is the worst of both worlds.

Red flags in code

A codebase mixing rich entities with transaction-script-style service functions doing the same work.
"Domain" classes that are just bags of getters / setters around procedural service functions.

Apply directly (mechanical, unambiguous)

None — style choice is project-wide.

Propose only (requires judgment)

Choosing the right style for this codebase.
Migrating between styles incrementally.

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

yaml

targets:
  - https://api.opensmartroute.ai/api/v1/registry/ipzard-coding-agents-domain-logic-style-instructions/manifest   # or paste the manifest below

Manifest

An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.

ipzard-coding-agents-domain-logic-style-instructions.ocm.jsonjson

{
  "ocm": "1",
  "id": "ipzard-coding-agents-domain-logic-style-instructions",
  "kind": "skill",
  "name": "domain-logic-style",
  "description": "Picking Domain Model and writing transaction scripts inside it is the worst of both worlds.",
  "publisher": "iPzard",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "general"
    ],
    "tags": [
      "skill-md",
      "github-instructions"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "Picking Domain Model and writing transaction scripts inside it is the worst of both worlds."
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "github-instructions",
      "repository": "https://github.com/iPzard/coding-agents",
      "path": ".github/instructions/architecture-scalability/domain-logic-style.instructions.md",
      "ref": "3684947157e3d82ee3f9916b1accdd10f79e2e2a",
      "url": "https://github.com/iPzard/coding-agents/blob/3684947157e3d82ee3f9916b1accdd10f79e2e2a/.github/instructions/architecture-scalability/domain-logic-style.instructions.md",
      "key": "iPzard/coding-agents/.github/instructions/architecture-scalability/domain-logic-style.instructions.md"
    },
    "applies_to": "**"
  },
  "instructions": "# Domain-logic style\n\n**Cite as:** `[Domain-logic style]`\n\n## Principle\nPick one and stay with it:\n- **Transaction Script** — procedural, fine for simple CRUD.\n- **Table Module** — record-set centric.\n- **Domain Model** — rich object model, scales with domain complexity.\n\nPicking Domain Model and writing transaction scripts inside it is the worst of both worlds.\n\n## Red flags in code\n- A codebase mixing rich entities with transaction-script-style service functions doing the same work.\n- \"Domain\" classes that are just bags of getters / setters around procedural service functions.\n\n## Apply dire",
  "cost": {
    "context_tokens": 198
  }
}

Fetch it by URL: GET /api/v1/registry/ipzard-coding-agents-domain-logic-style-instructions/manifest?version=1.0.0