design-systems
Create, evolve, and govern design systems that enable consistent, scalable product interfaces across teams. Use when building component libraries, defining design tokens, establishing contribution models, or improving design-dev consistency.
- License 许可
- MIT
- 最近更新
- 2026-07-22
- Stars
- ★ 7
- Forks
- 1
01 前言 Front Matter
- name
- design-systems
- description
- Create, evolve, and govern design systems that enable consistent, scalable product interfaces across teams. Use when building component libraries, defining design tokens, establishing contribution models, or improving design-dev consistency.
03 SKILL.md 正文
Design Systems
Overview
A design system is a shared language of UI components, patterns, tokens, and guidelines. Done well, it speeds delivery and raises quality; done poorly, it becomes ignored documentation.
When to Use
- Creating or maturing a component library
- Aligning multiple product teams on UI consistency
- Defining design tokens (color, type, space, elevation)
- Establishing contribution and governance models
Core Elements
- Design tokens and foundations
- Reusable components with clear APIs
- Usage guidelines and do/don’t examples
- Accessibility standards baked in
- Versioning and change communication
- Contribution model for designers and engineers
Principles
- Optimize for adoption, not completeness on day one
- Document the “why,” not only the “what”
- Partner tightly with engineering on implementation quality
- Measure usage and pain points; evolve based on real product needs
- Avoid becoming a bottleneck — enable teams to extend safely
Verification
- [ ] Components are actually used in production
- [ ] Tokens and components stay in sync between design and code
- [ ] Teams know how to contribute and request changes
04 同仓库更多 Skills
compliance-monitoring
Design compliance monitoring and testing programs that verify controls work in practice and surface issues before regulators do. Use when building monitoring plans, compliance testing, or continuous control monitoring.
complaints-handling
Operate complaints-handling processes that meet regulatory standards — logging, timely resolution, root-cause analysis, and fair outcomes. Use when designing or improving regulated complaints frameworks or analyzing complaint themes for conduct risk.
aml-kyc-basics
Apply AML/KYC fundamentals — customer due diligence, monitoring, suspicious activity escalation, and recordkeeping — for financial crime compliance. Use when designing onboarding controls, transaction monitoring concepts, or AML program components in financial services.
ai-model-compliance
Apply compliance controls to AI and automated decision systems — transparency, fairness, human oversight, documentation, and regulatory alignment. Use when deploying AI in regulated processes (credit, fraud, customer decisions) or responding to AI governance expectations.
data-quality-management
Manage data quality end-to-end — dimensions, rules, remediation, and prevention — beyond one-off cleaning scripts. Use when building sustained data quality programs or fixing systemic accuracy, completeness, or consistency problems.
data-lineage
Capture and use data lineage — where data comes from, how it transforms, and what depends on it — for impact analysis, debugging, and trust. Use when tracing metric origins, assessing change impact, or diagnosing broken pipelines.