backend

Name: backend
Author: dmbijan

Use when working on BusyTap backend APIs, Firebase Functions, Laravel server code, route contracts, validation, auth, booking logic, payment logic, and provider matching.

by dmbijan(0) 0 installs

Free

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

See reviews

About

Instruction file imported from dmbijan/BusyTap (.github/instructions/backend.instructions.md). Copyright stays with the author.

Backend Guidelines

Keep business rules out of purely presentational layers.
Validate request bodies, params, and query values on the server.
Enforce authorization server-side for customer, provider, admin, and super admin surfaces.
Prefer additive, compatibility-preserving API changes when clients already depend on existing contracts.
Use idempotent handling for retries, especially in payment, booking, and notification flows.
Fix integration mismatches at the contract boundary when possible.
Do not weaken validation or bypass checks to make a flow appear to work.

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.

dmbijan-busytap-backend-instructions.ocm.jsonjson

{
  "ocm": "1",
  "id": "dmbijan-busytap-backend-instructions",
  "kind": "skill",
  "name": "backend",
  "description": "Use when working on BusyTap backend APIs, Firebase Functions, Laravel server code, route contracts, validation, auth, booking logic, payment logic, and provider matching.",
  "publisher": "dmbijan",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "coding",
      "travel"
    ],
    "tags": [
      "skill-md",
      "github-instructions"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "Use when working on BusyTap backend APIs, Firebase Functions, Laravel server code, route contracts, validation, auth, booking logic, payment logic, and provider matching."
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "github-instructions",
      "repository": "https://github.com/dmbijan/BusyTap",
      "path": ".github/instructions/backend.instructions.md",
      "ref": "a5d43ead35bdcf7377fc36251e360dfe563b7c45",
      "url": "https://github.com/dmbijan/BusyTap/blob/a5d43ead35bdcf7377fc36251e360dfe563b7c45/.github/instructions/backend.instructions.md",
      "key": "dmbijan/BusyTap/.github/instructions/backend.instructions.md"
    },
    "applies_to": [
      "FirebaseBackend/functions/src/**/*.ts",
      "AdminPanel/Admin panel new install V3.0/app/**/*.php",
      "AdminPanel/Admin panel new install V3.0/routes/**/*.php",
      "AdminPanel/Admin panel new install V3.0/config/**/*.php"
    ]
  },
  "instructions": "# Backend Guidelines\n\n- Keep business rules out of purely presentational layers.\n- Validate request bodies, params, and query values on the server.\n- Enforce authorization server-side for customer, provider, admin, and super admin surfaces.\n- Prefer additive, compatibility-preserving API changes when clients already depend on existing contracts.\n- Use idempotent handling for retries, especially in payment, booking, and notification flows.\n- Fix integration mismatches at the contract boundary when possible.\n- Do not weaken validation or bypass checks to make a flow appear to work.",
  "cost": {
    "context_tokens": 146
  }
}

Fetch it by URL: GET /api/v1/registry/dmbijan-busytap-backend-instructions/manifest?version=1.0.0

About

Backend Guidelines

Use it

Manifest

Reviews