How do I install the Backend skill?

Run npx skillmds@latest add telagod/backend in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Backend safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Backend?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Backend free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Backend?

telagod (@telagod) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Backend by telagod — Agent Skill

Name: Backend
Author: telagod

Backend

Backend engineering judgment, distilled from a stronger model - invoke when CHOOSING a tech stack, language, database, queue, or architecture; designing a service, API, business logic, or schema; making a system production-ready (observability, failure handling, security); or reviewing server-side code and judging codebase health. Scenario-driven stack tradeoffs, logic-design rules, data discipline, production floors, and a rot catalog (the early signs of unmaintainable code).

telagod 85dcfbe 6 files · 29.3 KB Updated Sep 17, 2026

File contents

Backend — stack, logic, data, operations, rot

Rule content lives in the five files below; this SKILL.md only routes (doctrine/04-maintenance.md governs edits to this bundle too).

Route by moment

You are about to…	Read (in this folder)
Pick a language / framework / DB / queue / architecture, or judge a stack proposal	`stack.md`
Design or review a service, module, API, or piece of business logic	`logic.md`
Design a schema, transaction, migration, or cache	`data.md`
Ship to production — observability, config, failure modes, security, jobs, limits	`operate.md`
Review existing code, plan a refactor, or explain why a codebase feels dangerous	`rot.md`

Starting a new system usually means stack.md → logic.md → data.md, in that order: stack only after the scenario interrogation, endpoints only after the data model.

Scope and neighbors

Server-side engineering judgment only. Whether to delegate and when to escalate → doctrine; how to investigate/verify anything → methods; the visual/UI layer → frontend.

The stance

The one test governing the whole bundle is logic.md's opening line — is change still cheap and safe — and rot.md's opening defines the failure mode and the ugly-but-safe tiebreak. Read those two openings before judging any backend.

Frequently asked questions