backend-core

Guides backend development through a fixed pipeline of analysis, tests, implementation, review, and reporting.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/lfuuu/claude-rules --skill backend-core-lfuuu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backend-core
Source: https://github.com/lfuuu/claude-rules/tree/main/global-skills/backend-core
Command: npx skills add https://github.com/lfuuu/claude-rules --skill backend-core-lfuuu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Backend development tasks often lack a consistent process, leading to untested code, scope creep, and unclear responsibilities. This Skill provides a stack-agnostic core for a backend developer role that enforces a disciplined pipeline and clear boundaries of responsibility. ## Core Features & Use Cases - Fixed Development Pipeline: Enforces a sequence of analysis, test-first changes, minimal implementation, review via /reviewer, testing via /testing, documentation via /techwriter, and a structured final report. - Layered Architecture Rules: Defines dependency rules between API, business logic, and data access layers, treating violations as blocking review issues. - Responsibility Boundaries: Explicitly lists what the backend role may and may not change, delegating documentation, testing, and deployment concerns to other role skills. - Use Case: A project wrapper skill imports this core so that any backend task, such as adding a new API endpoint, automatically follows test-first development, peer review, and a standardized completion report. ## Quick Start Import this core from a project wrapper skill and ask the agent to implement a backend task such as adding a new API endpoint with tests.

Frequently Asked Questions about backend-core

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I use the backend-core skill in my project?

You do not call backend-core directly. Create a project-specific wrapper skill that references it with a link, then define your stack, paths, and domain rules in the wrapper while the core supplies the pipeline and boundaries.

What development pipeline does this backend role enforce?

The pipeline is analysis, writing or updating tests before changing behavior, minimal implementation, review via /reviewer, testing via /testing, documentation via /techwriter, and a final structured report covering files, checks, risks, and unfinished work.

Does backend-core depend on a specific language or framework?

No, it is stack-agnostic and contains no binding to any language, framework, ORM, or database engine. Concrete technology names, layer names, and test infrastructure are defined by the project wrapper that imports it.

What architectural rules does the skill enforce?

It enforces three layers: API/presentation, business logic, and data access, with dependencies pointing inward toward business logic. Business logic must not depend on transport or a specific database, and violating dependency direction is a blocking review issue.

When should the backend role escalate instead of fixing something itself?

It escalates after five failed review iterations to the Architect, escalates infrastructure problems to /devops with at most one iteration per incident, and never fixes frontend code, instead describing the needed change in its report.