The template
One versioned template every app is fabricated from, and why it compounds.
Every app is fabricated from one template: sfab-oss/sfab-starter,
the opinionated starter on the stack. As more
projects get built on it, the template gets sharper and the agents get better
at working it, and every one of those improvements flows back to everyone
building on the same foundation. Fix something once and it propagates
everywhere.
Shipped vs. landing
The starter and its stack are real today. The integrated asset model below
(the .sfab/template.json version pin, agent-loaded live docs, template-scoped
skills, and the component registry) is an accepted design currently being
built into the fabrication pipeline. Today, skills ship with the platform's
own agents and the engineering docs live alongside the code.
What the template carries
Live docs
Versioned best-practices and code-smell rules that the building agents, and the reviewing agent, read on every change. When a rule improves, every app on that template version inherits the improvement.
Skills
Bundled agent capabilities, scoped to the template version and loaded when a task needs them. Skills travel with the template, so an agent working any app on the same version has the same toolbox.
Component registry
Curated UI blocks the factory pulls from when it composes an app: never generic, always on-stack. The registry is what keeps fabricated interfaces consistent instead of one-off.
The version pin
.sfab/template.json records which template and version an app was fabricated
from. Upgrades are explicit and tracked like any other change: through a task,
a build, checks, and proof.