Implementation plan
Adopt Loam for generated engineering writeups.
Move agent-created plans, status pages, and explainers onto a shared static styling system so documents stay consistent, readable, and easy to share.
Summary
Loam will be published as a public static asset kit and Astro documentation site. Agents should use Loam classes and examples as their default visual language for software engineering documents.
Success criteria
A generated static page can be created from a template, shared in a browser, and understood without custom CSS or design decisions.
Key changes
Publish the design vocabulary
Ship tokens, typography, layouts, component classes, and agent guidance in one public repo.
Standardize diagrams
Author in Mermaid, render to inline SVG, and preserve source in a Loam source panel.
Provide examples
Include a kitchen sink, plan example, explainer example, templates, and component reference.
Risks and assumptions
Risk
Agents may add page-specific styles when a Loam component already exists.
Assumption
Most generated pages are viewed in modern browsers and do not need strict PDF pagination.
Test plan
-
Run lint, tests, and static build.
-
Inspect desktop and mobile layouts.
-
Publish tagged release and verify public asset URLs.