Curated skills for Claude Code

Model a visual CMS as a Shopify OS 2.0-style theme contract — a ThemeBundle of primitive settings, JSON templates, and section instances, normalized on every read, in a zero-dependency package both the editor and the public renderer import. Trigger when building or extending a page builder, theme engine, or customizer, or when deciding what lives in the bundle versus beside it.

Drive a CMS theme editor as a three-pane customizer over a live cross-origin preview — query-marker preview (not a cookie), a theme-scoped token, load-bearing data-section-id hooks, and both render paths sharing every resolver. Trigger when building or extending a theme editor, visual customizer, or in-canvas section inspector.

Turn a customer design (Figma, HTML, a Claude Design export) into an editable CMS section that is DATA, not code — a tag-allowlisted template tree, CSS scoped on write, types namespaced custom:<id>, snapshotted at publish. Trigger when importing a design into a page builder, building a section importer, or deciding how user-authored sections render.

Split CMS pages from the theme — a page is a workspace-scoped row (Content) and the theme supplies only the layout it renders through (Theme), with variant fallback to default so a theme swap never 404s a live URL. Trigger when adding pages, templates, or handles to a page builder, or when deciding whether something belongs in the bundle.

Publish a CMS theme as an append-only snapshot and serve the public site over a bearer-gated read seam the renderer caches per HOST — the site never touches the database, and a shared cache key is a cross-tenant leak. Trigger when adding publish, rollback, ISR, preview tokens, or a public renderer to a page builder.

Declare every first-party CMS section as four artifacts — a manifest, a React component, a registry entry, and a preset — with settings, blocks, CTAs, and spacing generated from the manifest. Trigger when adding or editing a section in a page builder, or when mapping a design onto a section contract.

Tenant a multi-tenant CMS by resolving a workspace you own — membership is yours (Clerk authenticates a person and nothing else), resolution never creates a workspace, the active-workspace cookie is a hint, and billing gates on the write. Trigger when adding workspaces, domains, seats, Stripe, or host routing to a page builder.