Write stories for React Native components using @storybook/react-native v10 and Component Story Format (CSF).
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionwriting-react-native-storybook-storiesExecute the skills CLI command in your project's root directory to begin installation:
Fetches writing-react-native-storybook-stories from storybookjs/react-native and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate writing-react-native-storybook-stories. Access via /writing-react-native-storybook-stories in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
1.3K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
1.3K
stars
Write stories for React Native components using @storybook/react-native v10 and Component Story Format (CSF).
Minimal story file:
import type { Meta, StoryObj } from '@storybook/react-native';
import { MyComponent } from './MyComponent';
const meta = {
component: MyComponent,
} satisfies Meta<typeof MyComponent>;
export default meta;
type Story = StoryObj<typeof meta>;
export const Basic: Story = {
args: {
label: 'Hello',
},
};
ComponentName.stories.tsx colocated with the componentMeta and StoryObj from @storybook/react-nativemeta object with satisfies Meta<typeof Component>StoryObj<typeof meta>args for props, argTypes for control config, parameters for addon configrender for custom render functions, decorators for wrappersexport const Primary: Story = {
args: { variant: 'primary', title: 'Click me' },
};
export const Secondary: Story = {
args: { ...Primary.args, variant: 'secondary' },
};
export const WithScrollView: Story = {
render: (args) => (
<ScrollView>
<MyComponent {...args} />
</ScrollView>
),
};
export const Interactive: Story = {
render: function InteractiveRender() {
const [count, setCount] = useReducer((s) => s + 1, 0);
return <Counter count={count} onPress={setCount} />;
},
};
import { fn } from 'storybook/test';
const meta = {
component: Button,
args: { onPress: fn() },
} satisfies Meta<typeof Button>;
Or via argTypes:
argTypes: { onPress: { action: 'pressed' } },
export const MyStory: Story = {
storyName: 'Custom Display Name',
args: { label: 'Hello' },
};
const meta = {
title: 'NestingExample/Message/Bubble',
component: MyComponent,
} satisfies Meta<typeof MyComponent>;
For the full control type reference, see references/controls.md.
Common patterns:
const meta = {
component: MyComponent,
argTypes: {
// Select dropdown
size: {
options: ['small', 'medium', 'large'],
control: { type: 'select' },
},
// Range slider
opacity: {
control: { type: 'range', min: 0, max: 1, step: 0.1 },
},
// Color picker
color: { control: { type: 'color' } },
// Conditional control (shows only when `advanced` arg is true)
padding: { control: 'number', if: { arg: 'advanced' } },
},
} satisfies Meta<typeof MyComponent>;
Auto-detection: TypeScript prop types are automatically mapped to controls (string -> text, boolean -> boolean, union types -> select, number -> number).
parameters: {
// Markdown docs in the Notes addon tab
notes: `# MyComponent\nUsage: \`<MyComponent label="hi" />\``,
// Background options for Backgrounds addon
backgrounds: {
default: 'dark',
values: [
{ name: 'light', value: 'white' },
{ name: 'dark', value: '#333' },
],
},
},
| Parameter | Type | Description |
|---|---|---|
noSafeArea |
boolean |
Remove top safe area padding. When using this, the component itself must handle safe areas since Storybook will no longer provide safe area padding. Prefer useSafeAreaInsets() over SafeAreaView — apply insets as paddingTop/paddingBottom on the container, and for scrollable content use contentContainerStyle padding instead of wrapping in SafeAreaView. |
storybookUIVisibility |
'visible' | 'hidden' |
Initial UI visibility |
hideFullScreenButton |
boolean |
Hide fullscreen toggle |
layout |
'padded' | 'centered' | 'fullscreen' |
Story container layout |
Parameters can be set at story, meta (component), or global (preview.tsx) level.
Wrap stories in providers, layouts, or context:
const meta = {
component: MyComponent,
decorators: [
(Story) => (
<View style={{ alignItemsImplementation Guide
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Steps
- 1Install skill using provided installation command
- 2Test with simple use case relevant to your work
- 3Evaluate output quality and relevance
- 4Iterate on prompts to improve results
- 5Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Related Skills
react-vite-best-practices
55asyrafhussin/agent-skills
Frontendtag: reactml-paper-writing
75davila7/claude-code-templates
AI/MLtag: writingfrontend-design
633anthropics/claude-code
Frontendsame categoryui-animation
230mblode/agent-skills
Frontendsame categorypremium-frontend-ui
228github/awesome-copilot
Frontendsame categoryhigh-end-visual-design
183leonxlnx/taste-skill
Frontendsame categoryReviews
4.7★★★★★31 reviews- LLiam Torres★★★★★Dec 4, 2024
writing-react-native-storybook-stories fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- SSakshi Patil★★★★★Sep 17, 2024
writing-react-native-storybook-stories is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- HHiroshi Mehta★★★★★Sep 5, 2024
Keeps context tight: writing-react-native-storybook-stories is the kind of skill you can hand to a new teammate without a long onboarding doc.
- IIsabella Gonzalez★★★★★Sep 1, 2024
writing-react-native-storybook-stories is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- AAdvait Perez★★★★★Aug 24, 2024
writing-react-native-storybook-stories is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- RRen Kapoor★★★★★Aug 20, 2024
Keeps context tight: writing-react-native-storybook-stories is the kind of skill you can hand to a new teammate without a long onboarding doc.
- CChaitanya Patil★★★★★Aug 8, 2024
Keeps context tight: writing-react-native-storybook-stories is the kind of skill you can hand to a new teammate without a long onboarding doc.
- PPiyush G★★★★★Jul 27, 2024
Registry listing for writing-react-native-storybook-stories matched our evaluation — installs cleanly and behaves as described in the markdown.
- AAdvait Farah★★★★★Jul 15, 2024
writing-react-native-storybook-stories reduced setup friction for our internal harness; good balance of opinion and flexibility.
- RRen Johnson★★★★★Jul 11, 2024
Registry listing for writing-react-native-storybook-stories matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 31
1 / 4Discussion
Comments — not star reviews- No comments yet — start the thread.