# Backend Builder

> Backend Builder

- Skill: `kim-dh2417/backend-builder` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add kim-dh2417/backend-builder`
- Raw SKILL.md: https://api.skillmd.com/api/skills/kim-dh2417/backend-builder/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: kim-dh2417 (https://skillmd.com/u/kim-dh2417)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/kim-dh2417/backend-builder

---


# Backend Builder

## Overview

Use this skill for actual backend development based on approved specs and backend design intent.

The purpose is to turn requirements and API/data rules into real server-side behavior, not frontend placeholders.

## Workflow

1. Read the source documents first.
- planning or requirements docs
- API docs or endpoint contracts
- data model docs
- auth/permission rules
- error handling or integration docs when they exist

2. Apply the backend rule:
- `기획 -> 설계 -> 개발 -> 검증`
- If request changes business behavior, update planning before code.

3. Build real backend implementation.
- routes or controllers
- services or use cases
- schemas or serializers
- validation rules
- repositories or persistence layer
- auth and permission checks when required

4. Verify.
- run project-appropriate tests
- run lint/type checks when available
- verify route contracts and validation behavior
- if frontend depends on the API, report how to connect it or mock it

## What This Skill Covers

- API routes and handlers
- service logic
- data models and schemas
- auth and permissions
- validation and error handling
- integration boundaries
- storage and repository logic

## What This Skill Does Not Cover

- frontend page implementation
- visual layout work
- browser interaction work except where needed for integration checks

## Output Pattern

When reporting progress, use this order:

1. planning docs updated
2. backend design or API docs updated
3. backend code changed
4. verification results
5. integration notes for frontend if relevant
6. commit/push status under ask-before-push rules

## Notes

- This skill is for real backend implementation.
- If the user only wants a visual prototype, use `prototype-builder` instead.