project-bootstrap

Project Bootstrap

Create a ready-to-run project skeleton with core, portal, docker, and k8s resources.

Quick Start

1. Choose a project name and target directory.
2. Run the initializer script.

.claude/skills/project-bootstrap/scripts/init_project.py \
  --name acme \
  --root /path/to/acme

If --name is omitted, the script will prompt (interactive) and default to the target directory name.

By default the initializer supports a safe merge into a non-empty directory (for example a repo root that already contains README.md). It refuses to overwrite existing files and will error if any template top-level paths already exist (for example core/, portal/, .github/).

.claude/skills/project-bootstrap/scripts/init_project.py \
  --name acme \
  --root /path/to/existing-repo \

If you want strict behavior, require an empty target directory:

.claude/skills/project-bootstrap/scripts/init_project.py \
  --name acme \
  --root /path/to/acme \
  --require-empty

Optional overrides:

.claude/skills/project-bootstrap/scripts/init_project.py \
  --name acme \
  --root /path/to/acme \
  --core-port 8080 \
  --portal-port 3000 \
  --namespace acme

If host ports conflict with other local stacks, override the Docker Compose bindings at runtime:

• CORE_HOST_PORT=18080
• PORTAL_HOST_PORT=13000

Workflow

1. Confirm --root and ask the user for a project --name (used for naming, default namespace, and image identifiers). If the user has no preference, suggest a default based on the target directory name.
2. Run the initializer script with the confirmed parameters.
3. Verify local run instructions:
   • Core: cd core && cargo run
   • Portal: cd portal && npm install && npm run dev
   • Docker: cd docker && docker-compose up -d
4. Run project-readiness against the generated repo to validate local compose startup, basic tests, and k8s/gh sanity checks.
5. Hand off the generated skeleton and next steps.

Suggested Dev Loop (After Bootstrap)