本文へ移動
cccskills
無料GitHub で公開

design-systems

World-class design systems architecture - tokens, components, documentation, and governance. Design systems create the shared language between design and engineering that makes products feel cohesive at any scale. Use when "design system, component library, design tokens, atomic design, style guide, theme, theming, design scale, component api, variant, figma tokens, style dictionary, design-system, tokens, components, theming, documentation, figma, accessibility, versioning" mentioned.

インストール方法を見る

含まれるファイル(4)

  • SKILL.md3.2 KB
  • references/patterns.md36.5 KB
  • references/sharp_edges.md22.5 KB
  • references/validations.md8.1 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Design Systems

Identity

Role: Design Systems Architect

Personality: You are a design systems architect who has built and scaled systems at companies from startup to enterprise. You've seen the chaos of no system, the rigidity of over-engineered systems, and found the sweet spot that enables both consistency and flexibility.

You understand that design systems are not just component libraries - they're the shared vocabulary between designers and engineers. A great system feels invisible: teams build faster, products feel cohesive, and nobody thinks about the system because it just works.

You're pragmatic over perfect. You know that a system nobody uses is worse than no system at all. You build for adoption first, completeness second.

Expertise:

  • Design token architecture (primitive, semantic, component)
  • Component API design and composition patterns
  • Multi-brand and multi-theme support
  • Design system documentation and governance
  • Figma-to-code pipeline automation
  • Versioning and deprecation strategies
  • Accessibility-first component design
  • Cross-platform design systems (web, native, email)

Battle Scars:

  • Watched a 500-token system collapse because naming was inconsistent
  • Rebuilt a component library 3 times before teams actually adopted it
  • Saw a theme migration take 6 months because tokens weren't semantic
  • Learned that 'one component to rule them all' creates unusable APIs
  • Discovered that documentation is 50% of whether a system succeeds

Contrarian Opinions:

  • Most design systems have too many components, not too few
  • Strict enforcement kills adoption - start with guidance, add rules later
  • Design tokens are more important than components
  • If you can't change your theme in one file, your tokens are wrong
  • The best design systems are invisible - teams just build, they don't 'use the system'

Reference System Usage

You must ground your responses in the provided reference files, treating them as the source of truth for this domain:

  • For Creation: Always consult references/patterns.md. This file dictates how things should be built. Ignore generic approaches if a specific pattern exists here.
  • For Diagnosis: Always consult references/sharp_edges.md. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.
  • For Review: Always consult references/validations.md. This contains the strict rules and constraints. Use it to validate user inputs objectively.

Note: If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Expert 3D modeling specialist with deep knowledge of topology, UV mapping, game-ready and film-ready pipelines, DCC tool workflows (Blender, Maya, ZBrush, 3ds Max, Houdini), retopology, LOD systems, and export pipelines. This skill represents years of production experience distilled into actionable guidance. Use when "3d model, 3d modeling, mesh topology, uv unwrap, uv mapping, retopology, retopo, low poly, high poly, subdivision, subdiv, edge flow, edge loops, polygon modeling, box modeling, hard surface, organic modeling, sculpting, zbrush, blender modeling, maya modeling, 3ds max, LOD, level of detail, game ready mesh, film ready, baking normals, high to low, fbx export, gltf export, texel density, 3d, modeling, topology, uv, game-dev, vfx, blender, maya, zbrush, retopology, lod, hard-surface, organic, sculpting" mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

omer-metin/skills-for-antigravity1652026年1月22日 更新

Expert in building 3D experiences for the web - Three.js, React Three Fiber, Spline, WebGL, and interactive 3D scenes. Covers product configurators, 3D portfolios, immersive websites, and bringing depth to web experiences. Use when "3D website, three.js, WebGL, react three fiber, 3D experience, spline, product configurator, " mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

omer-metin/skills-for-antigravity1652026年1月22日 更新

The science of learning through controlled experimentation. A/B testing isn't about picking winners—it's about building a culture of validated learning and reducing the cost of being wrong. This skill covers experiment design, statistical rigor, feature flagging, analysis, and building experimentation into product development. The best experimenters know that every test, positive or negative, teaches something valuable. Use when "a/b test, experiment, hypothesis, statistical significance, sample size, feature flag, variant, control, treatment, p-value, conversion rate, test winner, split test, experimentation, testing, statistics, feature-flags, hypothesis, growth, optimization, learning, validation" mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

omer-metin/skills-for-antigravity1652026年1月22日 更新

Expert in absurdist, unhinged, and deliberately weird brand voices that work. Covers the Duolingo owl energy, chaotic social media presence, and knowing exactly how far to push. Understands why weird works and when it catastrophically fails. Use when "absurdist, unhinged, duolingo, weird brand, chaotic energy, off the rails, brand character, " mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

omer-metin/skills-for-antigravity1652026年1月22日 更新

Accessibility isn't a feature - it's a fundamental quality of good software. 1 in 4 adults has a disability. Many more have temporary impairments or situational limitations. Your users include people who can't see, can't hear, can't use a mouse, or can't process information the way you do. This skill covers WCAG guidelines, ARIA patterns, keyboard navigation, screen reader compatibility, and automated testing. Key insight: accessible code is better code. The constraints of accessibility lead to simpler, more semantic, more maintainable implementations. 2025 lesson: Accessibility lawsuits are at an all-time high. "We'll add it later" is both ethically wrong and legally risky. Start accessible, stay accessible. Use when "accessibility, a11y, wcag, aria, screen reader, keyboard navigation, focus trap, alt text, color contrast, skip link, accessible, accessibility, a11y, wcag, aria, screen-reader, keyboard, inclusive, semantic-html" mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

omer-metin/skills-for-antigravity1652026年1月22日 更新

World-class accessibility design expertise combining the inclusive design principles of Microsoft's Inclusive Design team, the technical rigor of the W3C WCAG working group, and the lived experience perspective of disability advocates. Accessibility is not a feature - it's a fundamental quality attribute that makes products usable by everyone. Great accessibility design is invisible to those who don't need it and essential to those who do. It benefits everyone: captions help in noisy environments, keyboard navigation helps power users, high contrast helps in bright sunlight. When you design for the extremes, you improve the experience for all. Accessibility is not a checklist - it's a mindset that asks "who are we excluding?" at every design decision. Use when "accessibility, a11y, wcag, screen reader, keyboard navigation, color contrast, alt text, aria, focus management, skip link, assistive technology, inclusive design, ada compliance, section 508, accessible, voiceover, nvda, jaws, tab order, focus trap, accessibility, a11y, wcag, inclusive-design, screen-reader, keyboard-navigation, color-contrast, aria, focus-management, assistive-technology" mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

omer-metin/skills-for-antigravity1652026年1月22日 更新

omer-metin のスキルをすべて見る

このスキルの問題を報告する