StackFoundry is a source registry. Every directory should either own product source, registry source, generated output, examples, or documentation.
apps/contains runnable applications.docs/contains product and maintainer documentation.examples/contains install targets and walkthroughs used to prove registry modules in realistic app shapes.packages/is reserved for extracted library packages when command behavior, registry loading, schema validation, and shared utilities outgrowapps/cli.public/r/contains generated registry output. Do not edit it by hand.registry/contains source modules, presets, recipes, and shared skills. This is the product surface.scripts/is reserved for standalone maintenance scripts that should not live inside the StackFoundry command.
apps/cli/owns thestackfoundrycommand.apps/web/owns the public website and registry hosting surface.
registry/modules/<module>/module.jsondeclares the module contract.registry/modules/<module>/files/contains installable source files.registry/modules/<module>/docs.mdexplains setup and ownership.registry/modules/<module>/skill/SKILL.mdgives maintainer guidance.registry/modules/<module>/tests/checklist.mddefines verification expectations.registry/presets/*.jsoncomposes modules into installable bundles.registry/recipes/*.jsondescribes staged install order and workflow outcomes.
Run pnpm registry:build to regenerate public/r.
public/r/registry.json is the shadcn-compatible registry index and is not an installable item. Generated module files such as public/r/api-keys.json are registry:block item JSON files. They include file contents, target paths, package dependencies, registry dependency URLs, environment variables, docs, and metadata.
Generated aggregate preset blocks live at public/r/<preset>.json. Raw preset manifests live under public/r/presets/*.json for StackFoundry tooling and are not shadcn registry item documents. Recipe manifests are mirrored under public/r/recipes/*.json for inspection and install-order guidance.
Run:
pnpm checkThis runs registry validation, command syntax checks, dry-run installs, real install smoke tests, registry generation, compatibility verification, and the web build.