write-ui-module-readme

Generate module READMEs for UI primitives under packages/ui/src/lib.

33.3k|2.8k|Updated Oct 26, 2020
One-click install
npx skills add https://github.com/remix-run/remix --skill write-ui-module-readme
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-ui-module-readme
Source: https://github.com/remix-run/remix/tree/main/.agents/skills/write-ui-module-readme
Command: npx skills add https://github.com/remix-run/remix --skill write-ui-module-readme

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This task produces concise, agent-friendly module READMEs for UI primitives, enabling rapid adoption and correct usage without exposing implementation details.

Core Features & Use Cases

  • Generate focused, module-level READMEs for UI primitives found under packages/ui/src/lib/*.
  • Explain each exported value briefly, include a practical usage example, and capture important behavior guarantees.
  • Produce a ready-to-publish README structure suitable for documentation tooling and onboarding new contributors.

Quick Start

Provide a short canonical summary of the module exports and a minimal usage example as a ready-to-copy template.

Frequently Asked Questions about write-ui-module-readme

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

FAQPage Schema
How do I generate a README for UI primitives to speed up developer onboarding?

Generate concise UI module READMEs by analyzing source files and tests to document public exports, minimal usage examples, and behavior guarantees for first-party UI helpers, ensuring rapid adoption and correct usage without exposing implementation details.

What should be included in a frontend module README for documentation tooling?

A frontend module README should include a brief explanation of each exported value, a practical minimal usage example, and important behavior notes, creating a ready-to-publish structure suitable for documentation tooling and onboarding new contributors.

Can I automatically document UI module exports and usage patterns from source code?

Yes, you can document UI module exports by analyzing the module source and nearby tests to verify public exports and real-world usage patterns, producing an agent-friendly README that captures a canonical summary of the module's API.

What is the best way to document behavior guarantees for UI helper modules?

The best way to document behavior guarantees for UI helper modules is to analyze the module source and nearby tests, capturing important behavior guarantees in a concise README structure that explains each exported value briefly.

Does generating module READMEs for UI primitives require exposing internal implementation details?

No, generating module READMEs for UI primitives focuses on enabling rapid adoption and correct usage without exposing implementation details, relying instead on analyzing source and tests to verify public exports and real-world usage patterns.