atrium bootstrap

Engineering Community

Skill notes

Default to the scaffolder

For a vanilla host (single Python module, single frontend bundle, the standard extension shape), run the scaffolder rather than emitting files by hand: The emitted repo wires every registry slot, ships CI, and uses the published @brendanbank/atrium-host-* packages — its frontend/src/main.tsx

Up-front decisions to confirm with the user

Before writing files, confirm: Project / image name (e.g. bookings). Used as the docker image tag and project root. Python module name (e.g. bookings). Importable on PYTHONPATH; referenced by ATRIUM_HOST_MODULE=<module>.bootstrap. Must not

Procedure

Below, <your-app> is the project name and <your_pkg> is the Python module name. Replace both consistently.

1. Repo skeleton

Add a top-level .gitignore covering .env, node_modules, dist/, __pycache__/, .venv/, *.pyc.

2. Backend host package

Create these files (full contents in README.md, section Step 2): backend/pyproject.toml — hatchling, name <your-app>-host, no runtime deps (atrium image provides them). backend/src/<your_pkg>/__init__.py — empty marker.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tomevault-io · no license declared
Token usage
Moderate
Setup complexity
Manual integration
External API key
Required · Vendor-specific
Operating systems
Linux · Docker
Runtime requirements
Node.js · Python · Docker
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
  • Env read
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview atrium-bootstrap.preview
# 8. .env.example

Copy from [`README.md`](README.md) section *Step 7* and fill secrets with placeholders. Tell the user to generate `APP_SECRET_KEY` and `JWT_SECRET` with `openssl rand -hex 48`. Don't commit `.env` — only `.env.example`.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.