agentic-storybook-development
Develop, bundle, build, or troubleshoot the agentic-components Storybook app in apps/storybook on macOS, Windows, or Win32, including app catalog configuration, Metro, CocoaPods, native projects, and renderer builds. Not for configuring or running desktop tests or changing desktop package source.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 1.4k
- Forks
- 179
01 前言 Front Matter
- name
- agentic-storybook-development
- license
- MIT
- description
- Develop, bundle, build, or troubleshoot the agentic-components Storybook app in apps/storybook on macOS, Windows, or Win32, including app catalog configuration, Metro, CocoaPods, native projects, and renderer builds. Not for configuring or running desktop tests or changing desktop package source.
03 SKILL.md 正文
Agentic Storybook app development
This workflow covers the apps/storybook consumer and its native toolchain.
For the shared Storybook integration API and CLI use
storybook-desktop references;
for app identity, discovery, and diagnostics use the app's
agent-map.yaml and
AGENTS.md.
- Inspect
desktop.config.mtsand the app's declared scripts; do not invent aliases or direct native runner commands. - Use the package's platform recipes for prep, bundle, build, smoke, and diagnostics. Treat Pods, workspaces, generated solutions, build directories, and DerivedData as disposable. Fix the owning hand-authored source.
- Reinstall/regenerate affected native dependency sources and use a clean build after dependency or workaround changes.
- Validate the JavaScript bundle and affected native build. Run the app's format/lint and root validation when shared manifests or references change.
- Finish code/configuration changes with
yarn clean-lage-cachethenyarn lage buildci(R-VALID-003).
For test configuration, helper provisioning, test runs, smoke reports, or CI
lanes, use desktop-testing. For package source changes, use
maintain-desktop-testing. Component API and assertion work stays with
agentic-component-authoring.
The Storybook desktop CLI supports shared --reporter modes; see its
command reference
when choosing between a bounded JSON result and streamed NDJSON progress.
04 同仓库更多 Skills
review-component
Review component code or changes of any generation (v0, v1, agentic, primitive, or native-backed) without editing files. Classifies each changed surface, applies the matching checklists and native overlay, and reports evidence-backed findings with validation status.
maintain-v0-v1-component
Fix or maintain existing v0 (foundation-compose) or v1 (framework compose/compressible) components, including their platform variants. Classifies the generation first and loads only its recipe. Not for new components, agentic components, read-only reviews, or native-only changes.
maintain-desktop-testing
Change, review, or plan source changes to desktop-driver, desktop-test, storybook-desktop, or storybook-desktop-runtime, including native helpers. Applies package invariants, documentation, native and consumer validation, and changesets.
implement-native-component
Implement or change native components, TurboModules, native services, codegen specs, or native-backed platform wrappers (Swift, Objective-C, C++/WinRT, podspecs, Windows projects). Also supplies the native overlay checklist for v0, v1, and agentic work. Not for Storybook toolchain failures.
fix-security-issues
Audit and remediate dependency security advisories while respecting package age policy, removing unused vulnerable capabilities, deduplicating Yarn resolutions, and validating affected tooling.
desktop-testing
Configure, run, or troubleshoot native desktop tests using desktop-test, desktop-driver, and storybook-desktop, including app targets and suites, helpers, permissions, WDIO suites, Storybook story tests and smoke runs, reports, and CI. Not for package source changes or the Storybook app build toolchain.