Backend Agent Skill

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).

8k tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

238

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/telagod/code-abyss --skill backend

The instruction itself

4 sections, as written by the author

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.

Other skills for the same job

different authors, same section of the catalogue

MCP Builder

by anthropics

vendor ×13

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

774 tokens

Finishing A Development Branch

by ZhanlinCui

×7

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

Vercel React Native Skills

by vercel-labs

vendor ×6

React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.

39k tokens

Vercel React Best Practices

by ratacat

×5

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

1k tokens

How to use it

Copy the folder

Take telagod/backend from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.