Component workbench
Browse documented components, switch examples in iframe previews, inspect generated API tables, and track the primitive backlog.
29 ready33 planned
- components
- playground
- api-reference
The docs site now dogfoods the shared component library for catalog browsing, theme review, and long-form handbook content while staying fully static and SSR-safe.
Brand
Color mode
Contrast
Core docs
7
Vision, stack choices, and architecture decisions stay versioned with the code.
Planning docs
3
Roadmaps, operating cadence, and backlog structure live in the same handbook.
Runbooks
7
Server, Docker, and bootstrap guides live alongside the code.
Prompts
2
Prompt patterns are versioned inside the monorepo.
The docs site now includes a live component workbench and a token explorer so the design system can be reviewed in the same product surface that documents it.
Browse documented components, switch examples in iframe previews, inspect generated API tables, and track the primitive backlog.
29 ready33 planned
Search the live token contract, inspect values across modes, and verify the component-level token model as the library grows.
System, brand, and component tokensTheme-aware
Search and filter every handbook and prompt entry from one responsive catalog. This is the first reusable foundation for a future CMS-backed DSM surface.
Collection
Showing all 19 catalog entries.
The major decisions already made in phase 1, along with their rationale and consequences.
Updated 2026-03-14Docs
Why Directus remains the preferred self-hosted CMS path over hosted options like Sanity for the Devsuite DSM.
Updated 2026-03-14Docs
How tokens, accessibility, theming, Storybook, and future Penpot alignment work together.
Updated 2026-03-14Docs
A self-hosted CMS-backed path for a future design system manager that dogfoods the Devsuite component library.
Updated 2026-03-14Docs
The monorepo layout, dependency flow, and how the major zones of the suite fit together.
Updated 2026-03-14Docs
The original brief, the north star, and the success criteria for Devsuite as a personal platform.
Updated 2026-03-14Docs
The current stack, why each major tool was chosen, and what tradeoffs come with it.
Updated 2026-03-14Docs
The seeded epics, spikes, tickets, and QA work that should guide the next iteration cycles.
Updated 2026-03-14Planning
The kanban workflow, work item taxonomy, and quality gates for day-to-day execution.
Updated 2026-03-14Planning
What phase 1 has already established and what the next product and platform slices should be.
Updated 2026-03-14Planning
Provision a fresh macOS machine, install the toolchain, and verify the main surfaces all run.
Updated 2026-03-14Runbooks
Stand up the local Directus-based CMS foundation and understand the first content model for the DSM path.
Updated 2026-03-14Runbooks
Bring up Postgres and MySQL locally, understand what they are for, and validate the default stack.
Updated 2026-03-14Runbooks
Build and deploy the static docs site to AWS using the same OIDC-backed pattern as Storybook.
Updated 2026-03-14Runbooks
Mirror the repo-native planning system into GitHub with labels, milestones, issues, and the right auth expectations.
Updated 2026-03-14Runbooks
The default verification flow for linting, testing, Storybook, e2e, and release readiness.
Updated 2026-03-14Runbooks
Build Storybook in GitHub Actions and deploy it to a private AWS-hosted review surface when the repo is ready.
Updated 2026-03-14Runbooks
Summarize architecture, rollout order, and operating checks for a new service.
Reusable prompt2 variables
Review a UI component against keyboard, focus, semantics, and motion expectations.
Reusable prompt1 variables