ddg-design-system
Skill274 starsChanged 10 days agoApache-2.0View on GitHub
Use when creating, changing or reviewing UI on iOS or macOS, including colors, macOS theme support, typography, icons, corner radii, shadows, spacing, button styles and other shared components from DesignResourcesKit (DRK), DesignResourcesKitIcons, UIComponents or DuckUI.
In this repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .maestro/AGENTS.mdAGENTS.md
- ddg-add-feature-flagSkill
- ddg-add-pixelSkill
- ddg-apple-feedback-reviewSkill
- ddg-diagnose-ci-failureSkill
- ddg-drk-add-iconSkill
- ddg-macos-add-promoSkill
- ddg-sentry-reportSkill
- ddg-xcode-add-fileSkill
- verify-iosSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 27
Use semantic colors (Color(designSystemColor:), UIColor(designSystemColor:), NSColor(designSystemColor:)) and keep the screen's palette …
- Distinctive: line 34
Prefer system components when they meet the design.
- Very specific: line 38
Use baseColor: initializers, hex or RGB literals, or new color assets in the apps.
- Distinctive: line 43
Add speculative abstractions.
- Distinctive: line 49
No existing token, icon or component matches the design.
- Distinctive: line 64
Check light and dark mode and any palette or theme variants.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Design system (DRK)
Figma defines the design intent. The code in SharedPackages/Infrastructure/DesignResourcesKit,
SharedPackages/Infrastructure/DesignResourcesKitIcons, SharedPackages/UIComponents and, on iOS,
iOS/LocalPackages/DuckUI defines what is available; read it rather than assuming an API exists.
Lookup order
For every color, font, icon or piece of repeated styling, stop at the first step that fits:
- A DRK semantic color or typography style, or a DRKIcons asset in the matching size.
- A common component, modifier or preset in UIComponents, a button style in DuckUI (iOS), or an existing usage nearby. Look before writing your own buttons, shadows, borders, corner radii or spacing.
- Nothing fits: ask the user what to do. Figma and a designer should resolve the doubt.
SingleUseColor is the fallback when no semantic color fits. When you use one, say so explicitly
to the user and recommend confirming with a designer that no semantic color applies.
Do
- Use semantic colors (
Color(designSystemColor:),UIColor(designSystemColor:),NSColor(designSystemColor:)) and keep the screen's palette wiring and light/dark behavior. - macOS: colors must follow live theme changes. Read
references/macos-theming.mdbefore touching colors. - iOS: use DRK typography (
UIFont.daxBodyRegular(),.daxTitle1()and similar) and keep Dynamic Type working; fix layouts for larger text rather than disabling it. macOS: DRK typography is iOS only, so follow the feature's existing conventions. - Prefer system components when they meet the design.
Don't
- Use
baseColor:initializers, hex or RGB literals, or new color assets in the apps. They bypass palettes and dark mode. - Duplicate a DRKIcons icon in app assets or swap it for a lookalike SF Symbol.
- Replace intentional platform, feature or branding differences with the nearest token just to remove literals, or restyle unrelated UI during a focused change.
- Add speculative abstractions. Extract shared code when a pattern actually repeats.
Stop and ask a designer
- Ownership of a component is unclear, or it is unclear whether a visual difference is intentional.
- No existing token, icon or component matches the design.
- The change touches a shared element. List its other usages and show how they are affected before finalizing.
Where new things go
- Figma atoms (colors, common typography): DRK, with purpose-based names (
textPrimary, notblack) and both light and dark values. - Icons: DRKIcons, added with the
ddg-drk-add-iconskill, which the user runs. - Reusable composed UI and components: UIComponents.
- Feature-specific styling that is not part of the design system: keep it local, with a short comment on why it differs.
Before finishing
- Check light and dark mode and any palette or theme variants.
- iOS: check Dynamic Type up to accessibility sizes.
- For a changed shared element, check its other consumers, not only the screen you worked on.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

