@repochan/starters
v0.1.0
Published
Built-in landing-page starters (full Astro/Tailwind project scaffolds) for RepoChan.
Readme
@repochan/starters
Complete, real project websites that can be localized for another repository. Each child directory is an independent Astro/Tailwind site copied by repochan starter pull; the package has no runtime exports or build logic.
Source Starter and Transfer Kit
A Source Starter preserves its original project name, character, URLs, copy, source code, and production assets. It is a finished website, not an anonymous wireframe. Its previews and running source are the authoritative expression of the design.
The Transfer Kit is the small, concentrated handoff surface inside that full site:
<starter-id>/
├── repochan/
│ ├── starter.json # sole manifest: previews, locales, slots, orders, postprocess
│ ├── site.json # project metadata and theme tokens
│ ├── assets.json # source/customized asset state
│ ├── i18n/{locale}.json # complete content structures
│ └── previews/{desktop,mobile}.png
├── public/ # full source assets plus optional low-information slot references
├── src/ # complete implemented site
└── package.jsonThe Transfer Kit is not a second package or manifest. It lets the Page Designer replace deterministic configuration, complete locale values, and declared asset slots without reconstructing the design or copying fields by hand.
Core owns the manifest and config schemas. The CLI owns discovery, projection, order materialization, deterministic post-processing, local-source pull, and validation.
Asset contract
Each slot is either:
scalar: oneoutput;bundle: namedpublications[]plus one exclusiveextract-gridpostprocess.
repochan/assets.json mirrors the discriminant. source means the original finished Starter asset is present and buildable. customized means the pulled instance has replaced it for the target project. Source validation accepts the preserved original; starter validate --localized requires every required slot to be customized.
For a complex baked composition, the original full asset remains in the Starter. A slot may additionally reference a low-information migration guide, such as a pose line drawing produced by official/hero-pose-lineart-extract. The guide preserves composition and safe zones while reducing character or background identity; it never replaces the original artwork.
All supported locale files must have the same complete recursive shape as the default locale, including keys, value types, and array lengths. Presentation colors live only in repochan/site.json; source files consume derived CSS variables.
Commands
repochan starter list
repochan starter get minimal --json
repochan starter pull --starter minimal
repochan starter pull --from /path/to/creator-starter
repochan starter configure [--content-file content.json --overwrite]
repochan starter create-order hero-composite --intent "..." --foundation ord-foundation-001
repochan starter asset-apply hero-composite --order ord-hero-001 --overwrite
repochan starter validate minimal
repochan starter validate --output-dir .repochan/web-starter --localized
repochan starter validate --allContributing a Starter
Starter Designer works in a creator-owned directory or repository. Official inclusion happens through a pull request containing the complete Source Starter, desktop/mobile previews, and validation/build evidence. The official package is not a direct output directory for the skill.
Available starters
| ID | Original project site | Default |
|---|---|---|
| caddy | Caddy architectural automatic-HTTPS landing page | no |
| marktext | MarkText midnight Art Deco editorial landing page | no |
| minimal | RepoChan single-screen editorial Hero | yes |
| redis | Redis kinetic real-time signal-relay landing page | no |
