Menu
Repo-wide docs lifecycle — plans, audits, research, README surfaces. Use when authoring or editing any docs/**, README, or other doc-bearing folder.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Alpine.js adapter for @stainless-code/alpine-layers; plugin magics, x-layer-outlet, layerStack data, and JS hooks for typed layer stacks
Angular adapter for @stainless-code/angular-layers (signals + DI + imperative renderStack); use when wiring provideLayerClient, renderStack/useStackHandles, useLayerGroup, useMutationFlow, or createStackHook
UI-agnostic layer stack engine for @stainless-code/layers. Use for opening layers imperatively from anywhere, ordered named stacks, typed await or fire-and-forget calls, lifecycle control, blockers, validation, singleton updates, serial or nested layers, multi-stack orchestration, or building a library/framework adapter.
Lit adapter for @stainless-code/lit-layers; open UI from anywhere and manage ordered, named stacks with typed or fire-and-forget `open` via Reactive Controllers and custom elements
Preact adapter for @stainless-code/preact-layers — use for awaitable confirm flows, singleton toasts, nested drawers, stack subscriptions, and custom layer hosts
React adapter for @stainless-code/react-layers; open UI from anywhere and manage ordered, named stacks with typed or fire-and-forget `open`
| name | docs-governance |
| description | Repo-wide docs lifecycle — plans, audits, research, README surfaces. Use when authoring or editing any docs/**, README, or other doc-bearing folder. |
Repo-wide Tier B surface (cross-cutting reference + lifecycle substrate). This is a small library: no per-feature docs/ subtrees, no ownership tables. Full blueprint: LIFECYCLE.md.
Full blueprint: LIFECYCLE.md — the shared spine (§1–6: lifecycle types → cross-reference preservation), README surfaces (the apps/docs docs site is canonical; package + root READMEs are npm landings only; docs label on site-touching PRs for FTP deploy), + Closing states (plans / audits / research). This is a small library — no per-feature docs/ subtrees, no ownership tables.
docs-lifecycle-sweep — the doc janitor; walks docs/ and produces a per-file action plan.docs-governance-priming — Tier 2 priming on doc edits.authoring-discipline — prose density.