← ClaudeAtlas

yosegilisted

Build a screen mock or screen proposal (画面モック) out of the components already registered in a host project's Storybook, and deliver it as a Storybook Story (.stories.tsx) that can be reviewed before anything is implemented. On a host without Storybook, it delivers the same screen as a plain React component file instead. Also looks up what a host's components are actually called and what props they actually take, and turns an assembled mock Story into a real page implementation. Use it when asked to draft, propose, or mock up a screen from an existing design system, to make a new screen visible in Storybook first, or to convert a mock Story into an implementation.
yosegi-dev/yosegi · ★ 0 · Web & Frontend · score 60
Install: claude install-skill yosegi-dev/yosegi
# Yosegi — building screens from a host's own components > **Version: 2026-08-13.** An agent harness can load a stale copy of a skill without saying so. If > this date is older than the one in the repository's `skills/yosegi/SKILL.md`, you are reading an > out-of-date copy — re-install it before going further. Yosegi turns a host project's components into facts you can build a screen from, and emits the screen as a Story (CSF) for review before anything is implemented. It has neither a rendering environment nor a GUI of its own; you check how things look in the host's Storybook. On a host without Storybook, the deliverable becomes a plain React component file (`--target component`) — the step 1 branch below says how the procedure changes. This document is the procedure, and you are the one carrying it out. The CLI (and the equivalent MCP tools) are the instruments it reaches for. ## When to use it - Composing a screen proposal or UI mock from an existing design system, in a reviewable form. - Getting a first draft of a new screen visible in Storybook before it is implemented. - Looking up which components a host has, and what props they really take, before writing any UI. - Transcribing an approved mock Story into a real page. Do steps 1 and 2, then jump to step 5. Not for: one-off component changes. ## Where the value is The registry's job is narrow: it is the source of truth for a component's *props* — the real prop names, the real enum options, which are required,