skills.rest
murphytrueman
murphytruemanCOMMUNITY
Explore all skills by this author →
Website𝕏@murphytruemanGitHub

usage-guidelines

Generate usage guidelines for design system components with anti-patterns and accessibility.

155|7|Updated Mar 9, 2026
Search Tags:#anti-patterns#accessibility#design system#component guidelines#developer documentation#usage documentation
One-click install
npx skills add https://github.com/murphytrueman/design-system-ops --skill usage-guidelines
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: usage-guidelines
Source: https://github.com/murphytrueman/design-system-ops/tree/main/skills/usage-guidelines
Command: npx skills add https://github.com/murphytrueman/design-system-ops --skill usage-guidelines

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps create clear, actionable usage guidelines for specific components, preventing misuse and ensuring consistent application across a design system.

Core Features & Use Cases

  • Component Guidance: Generates detailed instructions on when to use, when not to use, and how to correctly implement a component.
  • Anti-pattern Identification: Documents common mistakes and provides clear corrections.
  • Use Case: A developer needs to understand the correct way to use a new Tooltip component. They use this Skill to generate guidelines covering its purpose, when to use it instead of a Popover, and common anti-patterns like using it for critical information.

Quick Start

Write usage guidelines for the 'Avatar' component.

Frequently Asked Questions about usage-guidelines

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

FAQPage Schema
How do I write component usage guidelines for a design system?▼

To write component usage guidelines, generate prescriptive documentation detailing correct application, anti-patterns, and accessibility considerations for specific design system components.

What are design system anti-patterns and how do I document them?▼

Design system anti-patterns are common component implementation mistakes. Document them by generating usage guidelines that identify these errors and provide clear corrections to prevent misuse.

When should I create usage documentation for design system components?▼

Create usage documentation when you need to provide developers and designers with prescriptive guidance on component implementation, intent, and edge cases to ensure consistent application across the system.

Does usage documentation need to include accessibility considerations?▼

Yes, usage documentation should include accessibility considerations. Comprehensive component guidelines must address correct application, anti-patterns, and accessibility to ensure proper implementation.

What's the best way to document component variants and edge cases?▼

The best way to document component variants and edge cases is to generate guidelines that cover component-specific content principles, correct implementation, and when not to use the component.

Related Skills

Explore More Design & Creative Skills→
ilanf23ilanf23
1

component-spec

Generate structured component specifications with anatomy, variants, states, and accessibility.

Community
Intermediate
JongsixJongsix

moai-docs-generation

Generate technical documentation from source code and API definitions.

Community
Advanced
boomNDSboomNDS

visual-design-foundations

Create cohesive visual design systems with tokens, typography, color, spacing, and iconography.

Community
Intermediate
TheCardGoatTheCardGoat
14

audit

Audit frontend UIs for accessibility, performance, theming, responsive, and design anti-pattern issues.

Official
Intermediate