القائمة
Define how a design system evolves: ownership models, contribution lifecycle, semantic versioning as a contract, deprecation policy, and quality gates.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Catalogue navigator for design-agent-skills. Lists available design skill stubs, matches user intent to the right stub, and routes to install and invoke. Use when the user wants to browse or find the right design skill.
Domain navigator for UI craft, visual design, brand, color, typography, mobile design, and interactive design engineering skills. Routes to skills for taste-driven UI, platform design (iOS/Android), components, color science, and the full visual design stack.
Create programmatic videos with React. Official Remotion skill package — compose video sequences using React components, animate with spring physics, and render to MP4/GIF. Ideal for product demos, explainers, and data-driven videos.
SwiftUI visual design skill for distinctive iOS/macOS interfaces that avoid generic AI-slop patterns. Covers design direction, layout systems, typography, color, spacing, brand integration, and design review.
6 web quality skills from Google Chrome's Addy Osmani: accessibility (WCAG), web quality audit (Lighthouse-style), Core Web Vitals (LCP/INP/CLS), performance, SEO, and security best practices.
Validates animation durations, enforces typography scale, checks component accessibility, and prevents layout anti-patterns in Tailwind CSS. Ensures UI work meets baseline quality standards before shipping.
استنادا إلى تصنيف SOC المهني
| name | design-system-governance |
| description | Define how a design system evolves: ownership models, contribution lifecycle, semantic versioning as a contract, deprecation policy, and quality gates. |
| triggers | ["design system governance","design system contribution model","component versioning policy","design system deprecation"] |
| das | {"type":"skill","category":"design-systems","upstream":"https://github.com/Owl-Listener/designer-skills","upstream_path":"design-systems/skills/design-system-governance/SKILL.md","version":"latest"} |
Catalogue stub — full skill: Owl-Listener/designer-skills
Is the full skill already installed?
grep -q "^das:" ~/.agents/skills/design-system-governance/SKILL.md 2>/dev/null && echo "pointer" || echo "installed"grep -q "^das:" .agents/skills/design-system-governance/SKILL.md 2>/dev/null && echo "pointer" || echo "installed"das: block → full skill installed, invoke and proceeddas: block present → go to step 2Detect scope, then install:
[ -e ~/.agents/skills/design-system-governance ] && echo "global" || echo "project"
Global:
npx skills add Owl-Listener/designer-skills --skill design-system-governance -g -y
Project:
npx skills add Owl-Listener/designer-skills --skill design-system-governance -y
Claude Code: send either command as a chat message starting with
!to run it without leaving the conversation.
Owls design-system-governance skill: the three ownership models (centralized / federated / hybrid) with trade-offs, the contribution lifecycle (request → triage → design → review → build → release → communicate), semver as a consumer contract, a deprecation process with migration guidance, and the quality bar a component must clear to enter the system. Public alternatives omit the ownership-model analysis.
design-tokens-skill