yuriyarhat-cyber Backend Scaffold
Create a backend that is small, runnable, and easy to extend.
Workflow
- Identify the backend type:
- API
- background worker
- CLI service
- webhook receiver
- Choose the smallest structure that fits:
- entrypoint
- core logic
- storage or state layer
- tests
- Create only the files needed for the first useful flow.
- Add one runnable path.
- Add one test path.
- Summarize the service contract and next backend step.
Rules
- Prefer a thin vertical slice over broad architecture.
- Prefer standard library or already-approved dependencies.
- Separate app startup from business logic.
- Make config obvious and local.
- Avoid adding infra abstractions too early.
Minimum scaffold
Try to produce:
- app entrypoint
- one core module
- one test file
- one short usage example
Good defaults
- Keep handlers thin.
- Keep state mutations explicit.
- Keep validation obvious.
- Name modules by job, not by vague layers.