Starting points for Studio projects in Shell:B, the local-first AI workspace. Part of the family with Shell-B-Themes, Shell-B-Screensavers and Shell-B-Skills.
The Studio is where Shell:B builds websites, decks, dashboards, games, screensavers and full-stack apps with you, one
project at a time. A template is a project to start from instead of a blank page: real files with a real structure,
which the agent then reshapes to your brief. Each template is a folder with template.json, the project files, and
a preview.
In Shell:B open Studio → New project and pick a template under Start from a template. Shell:B creates a project
of the template's kind with a copy of its files and its brief in DESIGN.md, and opens it; from there it is yours.
Shell:B fetches this repository as a tarball at a pinned commit, so the list works offline once fetched.
The gallery below and index.json are generated by scripts/validate.py; don't edit them by hand.
![]() Operations dashboard · dashboard by Shell:B · MIT |
![]() Full-stack starter · fullstack by Shell:B · MIT |
![]() Launch page · website by Shell:B · MIT |
![]() Screensaver skeleton · screensaver by Shell:B · MIT |
![]() Slide deck · deck by Shell:B · MIT |
templates/launch-page/
template.json name, kind, blurb, brief, author, authorUrl, license, version, tags, credits
index.html the entry file for the kind (public/index.html for fullstack, README.md for code)
DESIGN.md optional: the brief and decisions, as the Studio keeps them
assets/ … anything else the project needs; relative paths only
preview.jpg a screenshot of the entry page, about 640 px wide, under 400 KB
template.json:
{
"name": "Launch page",
"kind": "website",
"blurb": "One or two sentences for the picker (≤ 200 characters).",
"brief": "The starting brief written into the new project's DESIGN.md.",
"author": "Your name",
"authorUrl": "https://github.com/you",
"license": "MIT",
"version": "1.0",
"tags": ["website", "landing"],
"credits": []
}Kinds: website, deck, print, mobile, dashboard, design-system, brand, social, email, motion,
screensaver, game, 3d, fullstack, music, illustration, blank, code.
What makes a template good: a deliberate structure and type scale the agent can keep while swapping the content;
palette and sizes as variables at the top; real copy that shows the intended tone (never lorem ipsum); no external
scripts (Shell:B's sandboxed previews serve only /vendor and the project's own files). Then:
python3 -I scripts/validate.py # rules, sizes, index.json, README gallery
scripts/preview.sh templates/<id> # headless Firefox screenshot → preview.jpgSee CONTRIBUTING.md for the pull request checklist.
Every template names its author, linked when authorUrl is given, in Shell:B's picker, the gallery above and
index.json; the git history keeps the pull request under your account. Third-party work goes in credits.
The scripts and this repository are MIT. Each template names its own license in template.json.
- Shell-B-Themes: interface themes (Settings → Appearance)
- Shell-B-Screensavers: screensavers (Settings → Appearance)
- Shell-B-Skills: agent skills (Community Hub)
- Shell-B-Agents: agent personas
- Shell-B-Translations: interface languages




