repo-server

Name: repo-server
Author: Luhive

Module data/server boundary for repos and server handlers

by Luhive(0) 0 installs

Free

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

See reviews

About

Instruction file imported from Luhive/luhive (.cursor/rules/modules/repo-server.mdc). Copyright stays with the author.

Repos/Server Layer Rules (Hard-Fail)

data/ repos handle queries/mutations only.
server/ contains server-only handlers and route-side server logic support.
Repos must not own route redirects, UI state, or component concerns.
Repos should be concise functions which do finite things not everything together
Use file naming intent: *.server.ts(x), *.client.ts(x), *-repo.server.ts, *-repo.client.ts.

If business/data logic is placed in wrong layer, block and provide compliant placement.

Use it

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

# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot
curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'

Manifest

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

luhive-luhive-repo-server-rule.ocm.jsonjson

{
  "ocm": "1",
  "id": "luhive-luhive-repo-server-rule",
  "kind": "skill",
  "name": "repo-server",
  "description": "Module data/server boundary for repos and server handlers",
  "publisher": "Luhive",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "general"
    ],
    "tags": [
      "skill-md",
      "github-cursor-rules"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "Module data/server boundary for repos and server handlers"
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "github-cursor-rules",
      "repository": "https://github.com/Luhive/luhive",
      "path": ".cursor/rules/modules/repo-server.mdc",
      "ref": "1762c6612ac52e058e12f9d91c8f0be32df5beb7",
      "url": "https://github.com/Luhive/luhive/blob/1762c6612ac52e058e12f9d91c8f0be32df5beb7/.cursor/rules/modules/repo-server.mdc",
      "key": "Luhive/luhive/.cursor/rules/modules/repo-server.mdc"
    },
    "applies_to": "app/modules/**/data/**/*.ts*, app/modules/**/server/**/*.ts*"
  },
  "instructions": "# Repos/Server Layer Rules (Hard-Fail)\n\n- `data/` repos handle queries/mutations only.\n- `server/` contains server-only handlers and route-side server logic support.\n- Repos must not own route redirects, UI state, or component concerns.\n- Repos should be concise functions which do finite things not everything together\n- Use file naming intent: `*.server.ts(x)`, `*.client.ts(x)`, `*-repo.server.ts`, `*-repo.client.ts`.\n\nIf business/data logic is placed in wrong layer, block and provide compliant placement.",
  "cost": {
    "context_tokens": 127
  }
}

Fetch it by URL: GET /api/v1/registry/luhive-luhive-repo-server-rule/manifest?version=1.0.0

About

Repos/Server Layer Rules (Hard-Fail)

Use it

Manifest

Reviews