Agent Skills › AjayIrkal23/agentic-mercy-10x › backend-standards-always-follow

backend-standards-always-follow

GitHub

后端开发强制基线技能，要求在处理任何后端任务前加载10个配套标准。涵盖Go语言最佳实践、API规范、服务层设计、错误处理及代码审查，确保架构合规与高质量交付。

skills/backend-standards-always-follow/SKILL.md AjayIrkal23/agentic-mercy-10x

触发场景

涉及后端API、路由或控制器开发进行后端bug修复或实现新功能执行后端代码审查或重构

安装

npx skills add AjayIrkal23/agentic-mercy-10x --skill backend-standards-always-follow -g -y

更多选项

不安装直接使用

npx skills use AjayIrkal23/agentic-mercy-10x@backend-standards-always-follow

指定 Agent (Claude Code)

npx skills add AjayIrkal23/agentic-mercy-10x --skill backend-standards-always-follow -a claude-code -g -y

安装 repo 全部 skill

npx skills add AjayIrkal23/agentic-mercy-10x --all -g -y

预览 repo 内 skill

npx skills add AjayIrkal23/agentic-mercy-10x --list

SKILL.md

Frontmatter

{
    "name": "backend-standards-always-follow",
    "schema": 1,
    "category": "backend",
    "surfaces": [
        "backend"
    ],
    "triggers": {
        "paths": [
            "\/models\/",
            "controller",
            "internal\/",
            "internal\/models\/",
            "server\/",
            "service"
        ],
        "intents": [
            "backend"
        ],
        "keywords": [
            "acceptance",
            "always",
            "always-on",
            "api",
            "auth",
            "backend",
            "backend\/server",
            "baseline",
            "behavior",
            "bugfix",
            "completion",
            "compliance",
            "contract",
            "controller",
            "core",
            "debugging",
            "delegation",
            "follow",
            "implementation",
            "integration",
            "member",
            "part",
            "persistence",
            "planning",
            "queue",
            "requested",
            "review",
            "route",
            "schema",
            "server\/fastify",
            "service",
            "standards",
            "surface",
            "trigger",
            "validation",
            "worker"
        ]
    },
    "platforms": [
        "linux",
        "darwin",
        "windows"
    ],
    "token-cost": 711,
    "description": "ALWAYS invoke when any backend API, route, controller, schema, service, contract, persistence, auth, validation, worker, queue, integration, server\/Fastify behavior, backend bugfix, or implementation is requested. Backend Core Compliance Set member for the always-on backend baseline — MUST use for any backend\/server trigger surface before planning, debugging, implementation, review, delegation, or completion acceptance.",
    "disable-model-invocation": false
}

Backend Standards Always Follow

🔒 MANDATORY COMPANION BUNDLE — load ALL now, every time, no exceptions

Reading this skill is the trigger. Before doing ANY backend work you MUST immediately Skill-invoke all of the following, end to end. Not "when the work clearly needs them" — always, as a set, the moment this baseline loads:

backend-api-standards

service-layer-standards

backend-error-handling

backend-performance-standards

backend-code-review

api-contract-standards

scaffold-standards

golang-patterns

golang-testing

postgres-patterns

These 10 are the companion skills for backend work — NAMED here as trigger pointers so none is lost. Load a companion's BODY lazily, only when the task actually needs it — not all 10 in full up front.

Overview

This is the always-on backend baseline. The active backend stack is Go (GO_UDP) — all examples are Go-first; Node/TS/Fastify/Mongo variants live in references/node-stack.md.

Start here for any backend task. The companion bundle above is NAMED (trigger pointers); load each companion's body LAZILY, only when the task needs it — not all in full every time.

Always Apply

Inspect existing routes, controllers, schemas, services, models, and helpers before changing behavior.
Preserve current response shapes, DB fields, and domain behavior unless the task explicitly changes them.
Keep controllers thin and keep business logic in services.
Keep filtering, sorting, pagination, and search backend-driven for list endpoints.
Validate request shapes with schemas instead of scattered ad hoc checks.
Keep manually maintained backend source files at or below 250 lines. If a touched file is already over 250 lines, split or reduce it before adding more behavior unless the user explicitly scopes that cleanup out.
Remove stale imports, replaced logic, and dead backend paths while you work.

Non-Negotiables

No guessing when the repo already shows the pattern.
No business logic hidden in controllers.
No unbounded list endpoints for real datasets.
No raw internal errors, stack traces, or driver errors leaking to clients.
No touched manually maintained backend source file may remain over 250 lines without an explicit blocker.
No partial old/new backend implementations left behind without a reason.

Load Next When Needed

service-layer-standards for controller/service boundaries and service contracts.
backend-api-standards for detailed list/search endpoint semantics.
api-contract-standards for success/error envelopes and contract compatibility.
backend-error-handling for centralized handler rules and error taxonomy.
backend-performance-standards for query-efficiency or scalability review.
scaffold-standards for new domain or feature skeletons.