module-focus

Name: module-focus
Author: NicoVIII

Use when creating or reviewing modules in the backend. Keep modules focused on a single concept or responsibility. Split modules that cover multiple separable concerns.

by NicoVIII(0) 0 installs

Free

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

See reviews

About

Instruction file imported from NicoVIII/full-house (.github/instructions/backend/module-focus.instructions.md). Copyright stays with the author.

Backend Module Focus

[Hard Rule] - enforcement

One module should represent one concept.

Split When

The module contains separable concepts or independently evolving types.
Consumers regularly use only part of the module.
The name needs "and" or vague terms like utils/helpers.

Keep Together When

Types/functions are tightly coupled as one concept.

Review Checklist

Can the module be described without "and"?
Do all exports belong to one concept?
Would splitting reduce accidental coupling?

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/nicoviii-full-house-module-focus-instructions/manifest   # or paste the manifest below

nicoviii-full-house-module-focus-instructions.ocm.jsonjson

{
  "ocm": "1",
  "id": "nicoviii-full-house-module-focus-instructions",
  "kind": "skill",
  "name": "module-focus",
  "description": "Use when creating or reviewing modules in the backend. Keep modules focused on a single concept or responsibility. Split modules that cover multiple separable concerns.",
  "publisher": "NicoVIII",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "general"
    ],
    "tags": [
      "skill-md",
      "github-instructions"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "Use when creating or reviewing modules in the backend. Keep modules focused on a single concept or responsibility. Split modules that cover multiple separable concerns."
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "github-instructions",
      "repository": "https://github.com/NicoVIII/full-house",
      "path": ".github/instructions/backend/module-focus.instructions.md",
      "ref": "889a0db3de48f6920ad918a95121bf793ac69b3f",
      "url": "https://github.com/NicoVIII/full-house/blob/889a0db3de48f6920ad918a95121bf793ac69b3f/.github/instructions/backend/module-focus.instructions.md",
      "key": "NicoVIII/full-house/.github/instructions/backend/module-focus.instructions.md"
    },
    "applies_to": "server/src/**/*.gleam"
  },
  "instructions": "# Backend Module Focus\n\n[Hard Rule] - enforcement\n\nOne module should represent one concept.\n\n## Split When\n\n- The module contains separable concepts or independently evolving types.\n- Consumers regularly use only part of the module.\n- The name needs \"and\" or vague terms like `utils`/`helpers`.\n\n## Keep Together When\n\n- Types/functions are tightly coupled as one concept.\n\n## Review Checklist\n\n1. Can the module be described without \"and\"?\n2. Do all exports belong to one concept?\n3. Would splitting reduce accidental coupling?",
  "cost": {
    "context_tokens": 132
  }
}

Fetch it by URL: GET /api/v1/registry/nicoviii-full-house-module-focus-instructions/manifest?version=1.0.0