design-systems▌
mindrally/skills · updated Apr 8, 2026
You are an expert in UI and UX design principles for software development. Apply these guidelines when creating or maintaining design systems.
Design Systems Best Practices
You are an expert in UI and UX design principles for software development. Apply these guidelines when creating or maintaining design systems.
Foundation Elements
Color System
- Define primary, secondary, and accent colors
- Include semantic colors for success, warning, error, info states
- Ensure all color combinations meet WCAG contrast requirements
- Document color usage guidelines and contexts
- Provide light and dark mode variants
Typography
- Establish a type scale with consistent ratios
- Define font families for headings and body text
- Set line heights and letter spacing standards
- Document font weights and their usage
- Ensure readability across screen sizes
Spacing System
- Define consistent spacing scale (4px, 8px, 16px, 24px, etc.)
- Create layout primitives for common patterns
- Document margin and padding conventions
- Ensure responsive spacing behavior
- Use CSS custom properties for maintainability
Icons and Imagery
- Maintain consistent icon style and sizing
- Define icon grid and stroke weights
- Document icon naming conventions
- Optimize assets for web performance
- Provide multiple formats when needed (SVG, PNG)
Component Architecture
Component Structure
- Create atomic, reusable components
- Define clear component APIs (props/attributes)
- Document variants and states
- Ensure components are accessible by default
- Provide clear naming conventions
Component States
- Default state
- Hover state
- Focus state (keyboard navigation)
- Active/pressed state
- Disabled state
- Loading state
- Error state
Component Variants
- Size variants (small, medium, large)
- Color/theme variants
- Layout variants
- Contextual variants
Accessibility Requirements
- Follow WCAG 2.1 AA guidelines minimum
- Use semantic HTML elements
- Provide ARIA labels where needed
- Ensure keyboard navigation
- Test with screen readers
- Maintain color contrast ratios
- Support reduced motion preferences
Documentation Standards
Component Documentation
- Purpose and use cases
- Props/API reference
- Code examples
- Do's and don'ts
- Accessibility notes
- Related components
Pattern Documentation
- When to use
- Anatomy breakdown
- Behavior specifications
- Responsive considerations
- Edge cases
Implementation Guidelines
CSS Architecture
- Use CSS custom properties for tokens
- Implement utility classes for common patterns
- Follow BEM or similar naming convention
- Ensure specificity is manageable
- Support theming and customization
Component Libraries
- Framework-agnostic when possible
- Tree-shakeable exports
- TypeScript support
- Comprehensive test coverage
- Storybook integration
Governance
Contribution Guidelines
- How to propose new components
- Review and approval process
- Versioning strategy
- Breaking change policy
- Deprecation process
Maintenance
- Regular accessibility audits
- Performance monitoring
- Browser compatibility testing
- Documentation updates
- Community feedback incorporation
Design Tokens
Token Categories
- Colors
- Typography (font sizes, weights, line heights)
- Spacing
- Border radius
- Shadows
- Breakpoints
- Animation durations
- Z-index values
Token Implementation
:root {
/* Colors */
--color-primary-500: #0066cc;
--color-neutral-100: #f5f5f5;
/* Spacing */
--space-1: 4px;
--space-2: 8px;
--space-4: 16px;
/* Typography */
--font-size-sm: 0.875rem;
--font-size-base: 1rem;
--font-size-lg: 1.125rem;
/* Shadows */
--shadow-sm: 0 1px 2px rgba(0, 0, 0, 0.05);
--shadow-md: 0 4px 6px rgba(0, 0, 0, 0.1);
}
Quality Assurance
- Visual regression testing
- Accessibility automated testing
- Cross-browser testing
- Performance benchmarking
- Component unit testing
- Integration testing
Stay current with design system practices and industry standards.
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.8★★★★★46 reviews- ★★★★★Shikha Mishra· Dec 28, 2024
design-systems has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Isabella Smith· Dec 28, 2024
We added design-systems from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Fatima Iyer· Dec 28, 2024
Keeps context tight: design-systems is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Rahul Santra· Nov 19, 2024
design-systems reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Chen Mehta· Nov 19, 2024
design-systems fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Nikhil Liu· Nov 19, 2024
design-systems is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Pratham Ware· Oct 10, 2024
We added design-systems from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Chen Smith· Oct 10, 2024
design-systems has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Henry Ndlovu· Oct 10, 2024
Solid pick for teams standardizing on skills: design-systems is focused, and the summary matches what you get after install.
- ★★★★★Naina Diallo· Sep 21, 2024
Useful defaults in design-systems — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 46