Generate Storybook stories for components
Treat slash-command examples as skill names or user intents, not literal Codex command syntax. Treat $ARGUMENTS as the user's request text for the skill. Use Codex subagents only when the user explicitly asks for delegation, parallel agents, or team work; otherwise perform the workflow locally and use the playbooks in holophyte-agent-playbooks as references.
Generate Storybook stories for React components in the Holophyte project.
/storybook → Stories for components changed on current branch
/storybook TaskCard → Story for a specific component
/storybook --all → Stories for all unstorified components
Based on $ARGUMENTS:
git diff main...HEAD --name-only --diff-filter=AM | grep '\.tsx$' | grep -v '\.stories\.' | grep -v '\.test\.'
--all: Find all .tsx components without a corresponding .stories.tsx:
# List all component files, exclude those that already have stories
src/frontend/components/**/*.tsx and filter out files that have a sibling .stories.tsx.For each target component, use the storybook-writer subagent:
Generate a Storybook story for
<component-path>. Follow the project's story conventions — see the agent instructions for the exact pattern. If the component should be skipped (Convex-connected wrapper, WebSocket-dependent, etc.), explain why and skip it.
Run subagents in parallel for multiple components (max 4 concurrent).
After all stories are generated:
timeout 60s bun run build-storybook
If the build fails, read the error and fix the failing story. Max 2 retries.
Display: