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.
소스 정보
- 저장소
- microsoft/fluentui-react-native
- 최근 소스 활동
- 2026년 10월 23일 18:59
- 감지된 SKILL.md 언어
- 영어
- 스타
- 1,446
- 포크
- 179
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
SKILL.md 표시 중
SKILL.md
소스 지침 · 읽기 전용 미리보기- name
- agentic-storybook-development
- 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.
- license
- MIT
# 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](../../../packages/agentic/storybook-desktop/references/README.md);
for app identity, discovery, and diagnostics use the app's
[`agent-map.yaml`](../../../apps/storybook/agent-map.yaml) and
[`AGENTS.md`](../../../apps/storybook/AGENTS.md).
1. Inspect `desktop.config.mts` and the app's declared scripts; do not invent
aliases or direct native runner commands.
2. 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.
3. Reinstall/regenerate affected native dependency sources and use a clean
build after dependency or workaround changes.
4. Validate the JavaScript bundle and affected native build. Run the app's
format/lint and root validation when shared manifests or references change.
5. Finish code/configuration changes with `yarn clean-lage-cache` then
`yarn 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`.
GitHub에서 보기