arch-scaffold-new

Bootstraps a complete multi-tenant Python monorepo with API, worker, portal, deployment, and CI.

89|10|Updated Sep 15, 2026
One-click install
npx skills add https://github.com/baristaze/swe_guidelines --skill arch-scaffold-new-baristaze
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: arch-scaffold-new
Source: https://github.com/baristaze/swe_guidelines/tree/main/skills/arch-scaffold-new
Command: npx skills add https://github.com/baristaze/swe_guidelines --skill arch-scaffold-new-baristaze

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Starting a new multi-tenant, service-based Python system from scratch means wiring together the monorepo skeleton, object model, storage layer with row-level security, infrastructure capabilities, Terraform deployment, CI workflows, and operational tooling by hand, which is slow and error-prone. This Skill scaffolds the entire system in the prescribed architectural shape into an empty folder in one guided run. ## Core Features & Use Cases - Full system bootstrap: Creates the uv/pnpm workspace, Makefile, docs, ADRs, runbooks, Docker Compose stack, Terraform modules and environments, six GitHub workflows, and nine operational skills. - Layered code generation: Writes the object model distribution (tenancy, events, audit, outbox, idempotency namespaces with tests), the infrastructure distribution (cache, buckets, topics, queues, secrets), the API service, an optional worker and portal, and a generated Python client plus ops package. - Verification built in: Runs the fast gate, integration tests against the local compose stack, a tenant-isolation negative control, a telemetry round trip, a light traffic run, and a full architecture review before finishing. - Use Case: Run it with a target directory, root package, and an optional first namespace and entity to get a working system with its first API, database migrations, and deployment pipeline ready for the first commit. ## Quick Start Ask the AI to scaffold a new system named acme into the folder ./acme with a first namespace inventory and entity Warehouse with a field address of type str.

Frequently Asked Questions about arch-scaffold-new

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

FAQPage Schema
How do I scaffold a new multi-tenant Python system from scratch?▼

Invoke the skill with a target directory and root package, for example ./acme acme, optionally adding --first with a namespace, entity, and fields. It writes the monorepo skeleton, object model, infrastructure, API, worker, portal, deployment, and CI, then runs the verification gates.

What does the generated project structure include?▼

The tree includes a uv workspace with om/ and infra/ distributions, services/api, an optional worker and portal, clients/python generated from OpenAPI, an ops package, Terraform modules and environment roots, Docker Compose for local development, six GitHub workflows, and nine operational skills.

Can I scaffold a system without a worker or portal?▼

Yes, pass --no-worker or --no-portal. With --no-worker the maintenance sweep moves into the API process lifespan so outbox rows are still relayed, and the outbox-lag gauge and alarm still work.

What are the requirements for the target directory?▼

The target directory must not exist, be empty, or be a fresh repository holding only .git, README.md, LICENSE, and .gitignore. The skill refuses to run inside an existing repository's parent tree and treats any other existing path as a collision.

How does the scaffold verify tenant isolation?▼

It runs a negative control: the tenant predicate is removed from one query, integration tests stay green with the row-level security policy in place, then fail when the policy is disabled, proving the second fence holds. Both runs are recorded in docs/runbooks/tenant-isolation.md.

Why does the scaffold stop before finishing?▼

The procedure stops at the first step whose gate fails, such as make check, migrations, or integration tests, and reports where it stopped. Docker-dependent steps are skipped when Docker is unavailable.