'%20d='M64%205c-3%2018-15%2026-13%2043-9-5-13-13-13-22C20%2043%2015%2062%2022%2082c7%2022%2023%2037%2042%2041%2022-4%2039-21%2043-43%203-17-3-32-18-45%202%2011%200%2018-6%2025C84%2036%2075%2019%2064%205Z'%20/%3e%3cpath%20fill='url(%23heat)'%20d='M64%2045c-2%2015-14%2022-13%2038-5-4-8-9-9-15-7%2010-8%2020-4%2030%205%2012%2014%2020%2026%2023%2013-3%2023-12%2027-25%203-11%200-20-8-29%200%207-2%2012-6%2016%201-16-5-27-13-38Z'%20/%3e%3c!--%20The%20glasses%20render%20as%20two%20stacked%20stroke%20groups:%20a%20pale%20warm%20casing%20under%20a%20dark%20warm-charcoal%20stroke.%20The%20casing%20keeps%20the%20dark%20strokes%20legible%20where%20they%20leave%20the%20flame%20body%20(temple%20tips,%20lower%20rims)%20on%20dark%20backgrounds,%20and%20reads%20as%20a%20rim%20light%20against%20the%20flame%20on%20light%20ones.%20--%3e%3cg%20fill='none'%20stroke='%23ffe3ae'%20stroke-opacity='0.85'%20stroke-linecap='round'%20stroke-linejoin='round'%3e%3cpath%20stroke-width='14'%20d='M7%2063c12-4%2027-5%2043-1M78%2062c16-4%2031-3%2043%201'/%3e%3crect%20x='12'%20y='58'%20width='46'%20height='35'%20rx='13'%20stroke-width='14'/%3e%3crect%20x='70'%20y='58'%20width='46'%20height='35'%20rx='13'%20stroke-width='14'/%3e%3cpath%20stroke-width='13'%20d='M57%2066c5-4%209-4%2014%200'/%3e%3c/g%3e%3cg%20fill='none'%20stroke='%2333221b'%20stroke-linecap='round'%20stroke-linejoin='round'%3e%3cpath%20stroke-width='8'%20d='M7%2063c12-4%2027-5%2043-1M78%2062c16-4%2031-3%2043%201'/%3e%3crect%20x='12'%20y='58'%20width='46'%20height='35'%20rx='13'%20stroke-width='8'/%3e%3crect%20x='70'%20y='58'%20width='46'%20height='35'%20rx='13'%20stroke-width='8'/%3e%3cpath%20stroke-width='7'%20d='M57%2066c5-4%209-4%2014%200'/%3e%3c/g%3e%3c/svg%3e){kind=small}
@happyvertical/smrt-planner
The s-m-r-t app planner as a mountable Svelte component with cookbooks, recipes, layout, theme, and export tabs, a typed command set, and a plan snapshot.
What it gives you
The s-m-r-t app planner as a mountable Svelte component with cookbooks, recipes, layout, theme, and export tabs, a typed command set, and a plan snapshot.
- 01Add recipes or whole packages and an app mock-up assembles around them: navigation, a list and record view with a form per model, and help pages
- 02Ready-made cookbooks for a bakery, a mechanic, a welder, a yoga studio, and other small businesses; the cookbook saves in the browser or is left to the host
- 03Commands are published as tool definitions, so an LLM or MCP server can drive the planner
Mount it in a host page
Planner and createPlannerController come from the package root, which is Svelte source and needs a Svelte-compiling bundler. Its props are all optional: controller, basePath, inference, layout, persistence, themeControls, advancedStylesHref, defaultTitle, tabs, backLink, and onready. The controller runs commands such as add_recipes, set_policy, apply_cookbook, and undo, and returns a snapshot and receipt or a typed error. A host that owns an AppShell mounts PlannerControls inside it with PLANNER_SHELL_EDGE_TOGGLES and PLANNER_SHELL_PANEL_DEFAULTS.
What the tabs cover
The tabs are cookbooks, recipes, features, layout, theme, settings, and export. The pencil in the header edits the menu and every section page in place, and each edit lands in the cookbook layout and overviews. Metric, records, and chart widgets read the in-browser sample data. Theme offers palettes, appearance, a brand color wheel, fonts, and an Advanced Styles CSS editor. Export shows what the cookbook holds, a prompt to copy for a coding agent, and the download.
Drive it from a model
commandTools from the commands subpath is every command as name, description, and inputSchema. The snapshot is a compact read-only plan of a few kilobytes, fit for a prompt. Passing inference switches the assistant on; without it the planner has no chat icon. A plain Node server uses the core subpath for the schemas, buildHostPrompt, parseHostReply, the cookbook library, and createHeadlessPlanner. It serves the prebuilt app from the app subpath. HostPlanner mounts the same planner inside a Kitchen host such as an MCP app or widget.
Mounted on this site as build-a-boilerplate
This site mounts the complete Planner on its build-a-boilerplate page with a backLink to the documentation. An on-device browser model is offered first; a bring-your-own endpoint, with any key held in memory for the tab, is the alternative. The page is the site name, passed as defaultTitle; the package keeps its own.
Open build-a-boilerplate →Released with the framework
The planner lives in the smrt monorepo and releases in lockstep with every other smrt package. Its catalog is a build output generated from the packages in the same release, so the published planner cannot drift from them.
Package UI
Components in this package
Import these public components directly. When the package also exports playground entries, the next tab renders its real components with package-owned example data.
Package previews
No playground module yet
This package does not currently export a ./playground module. Its component names and import path remain available in the Components tab.
Intentionally not registered
Generated interface
REST
The exact route set comes from each model's @smrt({ api }) policy
and the application manifest—not from a second controller definition.
A browser component with no models. It describes the REST routes, MCP tools, and CLI commands other packages generate; it generates none itself.
Generated interface
MCP
AI tools are generated from the methods you explicitly include. Their inputs are validated against the same model metadata used by REST and CLI.
A browser component with no models. It describes the REST routes, MCP tools, and CLI commands other packages generate; it generates none itself.
Browser-native agent interface
WebMCP
The generated web definitions carry the same tool names, descriptions, and JSON Schema
inputs as MCP. smrt-web registers them with document.modelContext.
A browser component with no models. It describes the REST routes, MCP tools, and CLI commands other packages generate; it generates none itself.
Generated interface
CLI
The app CLI turns manifest resources into predictable operator commands while keeping package-specific actions close to their models.
A browser component with no models. It describes the REST routes, MCP tools, and CLI commands other packages generate; it generates none itself.