agentsclimarketplace
Sign in

Backend

Skill telagod/code-abyss/skills/_kernel/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).From its SKILL.md

Install
npx -y skills add telagod/code-abyss --skill backend

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

1.8 KB, 319 tokens by cl100k_base, as published. Nobody here has run it

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 proposalstack.md
Design or review a service, module, API, or piece of business logiclogic.md
Design a schema, transaction, migration, or cachedata.md
Ship to production — observability, config, failure modes, security, jobs, limitsoperate.md
Review existing code, plan a refactor, or explain why a codebase feels dangerousrot.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.

What ships with it: 5 files

27.5 KB alongside SKILL.md

Gives 0 of the 12 instructions most architecture codebase skills give in 319 tokens

Counted across 858 of the 1,304 authors here whose files we hold, read 2026-09-06

  • Apply the deletion test to identify shallow modulesin 32 of 858, across 31 files
  • Read domain glossary and ADRs before exploringin 22 of 858, across 19 files
  • Use Tailwind and Mermaid via CDN for reportsin 21 of 858, across 18 files
  • Document architecture decision recordsin 20 of 858, across 12 files
  • Offer to record ADRs for rejected candidatesin 17 of 858, across 14 files
  • Limit primary navigation to four to seven itemsin 17 of 858, across 7 files
  • Write HTML report to the system temp directoryin 17 of 858, across 14 files
  • Read product marketing context before asking questionsin 16 of 858, across 6 files
  • Use Mermaid graph TD for visual sitemapsin 15 of 858, across 5 files
  • Ensure every page has at least one internal linkin 15 of 858, across 5 files
  • Use ASCII tree format for page hierarchy draftsin 15 of 858, across 5 files
  • Enforce lowercase URLs with hyphensin 15 of 858, across 5 files

Said here and by no other author read

  • Read logic.md and rot.md before judging
  • Choose stack after scenario interrogation
  • Design endpoints after data model
  • Prioritize change safety and cost

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.