Explore the guides +
Skills/init-backend
Foundation / SKILL GUIDE

init-backend

Start a backend with a structure you can keep building on.

An empty folder is easy to fill badly. This skill gives the backend a sensible starting point: routes, handlers, services, validation, configuration, and tests, without inventing layers nobody needs yet.

When I’d use it

Use it when you need a new backend. The supported starting points are Node.js with TypeScript and Express, Python with FastAPI and uv, or Go with the standard library HTTP server.

Before you start

Choose a stack if you have a preference. The default location is backend/, unless the repository already has a convention or you name another directory. Existing code should be inspected before anything is generated.

Install it. Then give it a task.

Run this in your project’s terminal. Choose your coding agent in the installer, then start a new agent session if it needs one to discover the skill.

TERMINAL
$ npx skills add akdevsaha-dev/factory-skills --skill init-backend

Once installed, send a prompt like the ones below to your agent. These are example requests to adapt to your own project, not terminal commands or recorded results.

If slash commands aren’t available in your agent, write “Use the init-backend skill to…” and describe the same task.

New to skills? Start with the installation walkthrough

What happens next

  1. Inspects the repository and checks for an existing backend.
  2. Asks for the stack when you haven’t already chosen one.
  3. Scaffolds the backend using the selected stack’s conventions.
  4. Installs dependencies and checks startup, tests, and GET /health.

A few ways to ask

5 examples

Copy the one closest to your task. Replace names, paths, dates, and refs with ones that exist in your project.

01

Let it ask about the stack

SEND TO YOUR AGENT
› /init-backend

Useful when you want to choose from the supported options after the project is inspected.

02

Start with TypeScript

SEND TO YOUR AGENT
› /init-backend use Node.js, TypeScript, and Express. Keep the backend in backend/ and follow the repository conventions.

Naming the stack avoids an extra round of questions.

03

Use Python

SEND TO YOUR AGENT
› /init-backend use Python with FastAPI and uv. I’ll add the product endpoints after the scaffold is verified.

Keep the first task about the foundation. Product features can follow separately.

04

Keep Go straightforward

SEND TO YOUR AGENT
› /init-backend use Go with the standard library HTTP server. Reuse any established Go conventions in this repository.

The skill supports the standard library stack; it doesn’t need a new web framework.

05

Use an established directory

SEND TO YOUR AGENT
› /init-backend use Node.js and TypeScript. This monorepo keeps APIs in apps/api/, so use that directory.

An explicit destination overrides the default backend/ location.

What to look for in the result

A startup command and a verified health endpoint on port 8080 by default, with an environment override. The health response is {"status":"ok"}. The report should say what ran and what couldn’t run.

A thing worth watching

A scaffold is a starting point. Database connections, authentication, and your business logic are separate decisions. If a backend already exists, decide whether to extend it before creating another.

Use it with

Based on the repository’s skill instructions.Read the source
PUT IT INTO PRACTICE

Build a workflow you can repeat.

Follow the step-by-step guide to working with agents.

Explore Learn