bf-bootstrap skillB
bf-bootstrap is agent-read markdown (skill) from chan4lk/specclaw: Create the target application foundation in the NEW (rebuild) repo, before any backlog item is developed — the missing stage between "the rebuild backlog exists" and "/specclaw:propose BL-###". Consumes the architecture the rebuild already decided (decisions.md's SQ/CQ answers plus any accepted ADR in this repo) and scaffolds the skeleton for it: app shell, routing shell, API client, solution/project layout, ORM and database connectivity, dependency injection, environment/config structure, CORS,.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# specclaw bf-bootstrap **First, run** `specclaw-ensure-init .specclaw` — idempotently creates `.specclaw/` if it doesn't exist (silent if already initialized; auto-inits using the current directory's basename as the project name). Create the target application's foundation in the **new (rebuild) repo**. This is the stage that used to be missing, and its absence is what let the first backlog item proposed accidentally inherit responsibility for inventing half the application skeleton — a screen-bearing item quietly shipping as a backend-only slice because nothing else owned the frontend's existence. **The boundary that defines this command:** it creates the things every backlog item will stand on, and **not one thing any backlog item is for**. See **The foundation-only boundary** below; it is enforced by a gate, not by good intentions. Read-only side-command with respect to `.specclaw/analysis/` and `.specclaw/baseline/` — it never writes into either, never touches the legacy repo, and calls no lifecycle skill or script. It is the one brownfield command that writes application source, and it does so exactly once per repo. Invocation: ``` …
Read the whole file at its exact version.
How to install
mdr add chan4lk/specclaw/bf-bootstrap@git:20260920.62cf3f0mdr add chan4lk/specclaw/bf-bootstrap@sha256:747cc724019ad2ffPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_kui6qochj5skvep2)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260920.62cf3f0 latest | 2026-09-20 | 62cf3f0 | 18,912 B | B | view · diff |
| git:20260904.c65816a | 2026-09-04 | c65816a | 18,680 B | B | view |
Audit of the latest version
- fail: Frontmatter declares a name
- pass: Frontmatter block present
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (18912 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
chan4lk/specclaw · 12 stars · license MIT · pushed 2026-09-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_kui6qochj5skvep2 GET https://markdownregistry.com/api/v1/resolve?ref=chan4lk/specclaw/bf-bootstrap GET https://markdownregistry.com/api/v1/blob/747cc724019ad2ff2962b888a89b5c56a399896ca80f080cad131cc3bd38968b
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.