agentleFS
hamzzaqureshihamzzaqureshi/gravidex/.agents/skills/backend-engineering/SKILL.md

backend-engineering

Skill1 starsChanged 7 days agoMITView on GitHub

Architect and build production backend services, APIs, and agent connectors. Covers REST API design, Express/Next.js API routes, robust error handling across TypeScript/Python/Go, and Model Context Protocol (MCP) server development. Use when building backend endpoints, designing data schemas, implementing typed error boundaries, or authoring MCP servers.

11 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use software-architecture.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • nek1987Skill

    software-architecture

    Guide for quality focused software architecture. This skill should be used when users want to write code, design architecture, analyze code, in any case that relates to software development.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use plural nouns for resources (/api/v1/users).

    line 29

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Backend Engineering

Consolidated capability for architecting, implementing, and securing production backend services, RESTful APIs, typed error boundaries, and Model Context Protocol (MCP) tools.

When to Activate

  • Designing REST endpoints, resource URLs, status codes, pagination, and rate limits.
  • Implementing Node.js, Express, Next.js API routes, or serverless functions.
  • Designing error architectures (typed errors, error boundaries, retries, circuit breakers).
  • Authoring or debugging Model Context Protocol (MCP) servers (tools, resources, prompts, stdio/SSE).

When NOT to Activate

  • Performing vulnerability reviews or penetration testing (use security-audit).
  • Writing client-side React UI components (use frontend-engineering).

Core Execution Workflow

  1. REST API Design & Standards:
    • Use plural nouns for resources (/api/v1/users). Use standard status codes (200, 201, 400, 401, 403, 404, 409, 429, 500).
    • Enforce cursor-based or limit/offset pagination and standard response envelopes { data, error, meta }.
    • Consult references/rest-api-design.md.
  2. Backend Architecture & Data Access:
    • Encapsulate data access behind repositories. Validate all incoming request payloads at system boundaries with schema validators (Zod/Pydantic).
    • Consult references/backend-patterns.md.
  3. Robust Error Handling & Resilience:
    • Distinguish operational errors from programmer errors.
    • Implement exponential backoff retries and circuit breakers for external API dependencies.
    • Consult references/robust-error-handling.md.
  4. MCP Server Development:
    • Build MCP servers with Node/TypeScript SDK. Define schema-validated tools, dynamic resources, and prompt templates.
    • Consult references/mcp-server-development.md.

Modular Reference Directory

Reference ModulePrimary FocusSource Provenance
rest-api-design.mdREST API patterns, status codes, pagination, filtering, versioningaffaan-m/ECC (api-design)
backend-patterns.mdNode.js, Express, Next.js API routes, repository patterns, data accessaffaan-m/ECC (backend-patterns)
robust-error-handling.mdTyped errors, error boundaries, retries, circuit breakers in TS/Python/Goaffaan-m/ECC (error-handling)
mcp-server-development.mdMCP SDK server development, tools, resources, prompts, Zod validationaffaan-m/ECC (mcp-server-patterns)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.