generate-component-story

Generate UI component story examples using section! blocks and existing patterns.

62|1|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/zerx-lab/rmx --skill generate-component-story
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: generate-component-story
Source: https://github.com/zerx-lab/rmx/tree/main/.opencode/skills/generate-component-story
Command: npx skills add https://github.com/zerx-lab/rmx --skill generate-component-story

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the creation of story examples for UI components, helping teams document usage, test interactions, and showcase design system patterns with consistent stories.

Core Features & Use Cases

  • Generate stories following established patterns in crates/story/src/stories (e.g., tabs_story.rs, group_box_story.rs).
  • Organize stories with section! blocks for each major part (Basic usage, Variants, Interactive examples, Edge cases).
  • Provide ready-to-run stories that can be integrated into docs, tests, and design-system demos.

Quick Start

Use the generate-component-story skill to create stories for a sample component, following the patterns in crates/story/src/stories and organizing content with section! blocks.

Frequently Asked Questions about generate-component-story

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate UI component stories for Rust documentation?

You generate UI component stories by applying this skill to automate example creation, adhering to existing patterns in crates/story/src/stories and using section! blocks to organize basic usage, variants, and edge cases.

What is the best way to document design-system component variants in Rust?

Documenting design-system variants is best handled by generating structured story examples using section! blocks, which organize component demonstrations across basic usage, interactive examples, and edge cases consistently.

How do I structure a Rust UI component story for tests and tutorials?

Structuring a Rust UI component story involves using section! blocks to divide content into major parts, providing ready-to-run examples that integrate seamlessly into documentation, tests, and design-system demos.

Does the generated component story follow existing demo file patterns?

Yes, the generated component story follows established demo file patterns, matching the structure of existing files like tabs_story.rs and group_box_story.rs within the crates/story/src/stories directory.

What edge cases should I include when writing UI component stories?

When writing UI component stories, include edge cases alongside basic usage, variants, and interactive examples to ensure comprehensive coverage for documentation, testing, and tutorials.