Agent skill
shared-brand
Brand identity, design tokens, and anti-pattern philosophy shared across all platforms.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/shared-brand
SKILL.md
Purpose
Define brand identity once. Platform styleguides reference this for colors, typography philosophy, design direction, and anti-patterns — then add platform-specific details.
Design direction
- Aesthetic: premium consumer with selective immersive moments
- Tone: confident, intentional, restrained
- "Wow" is used sparingly and purposefully
If a screen could belong to any generic product, it does not meet the bar.
Brand colors
Core palette
brand.orange= #FF5E1Aneutral.white= #FFFFFFneutral.lightGray= #DAD9D9neutral.darkGray= #282828neutral.black= #000000
Usage rules
- Raw hex values must not appear in components or views
- All color usage must reference semantic tokens
- Contrast must meet WCAG 2.1 AA in both light and dark modes
- See platform styleguide references for token implementations
Typography
Banned as primary/sole font: Inter, Roboto, Open Sans, Lato, Montserrat, Poppins, Nunito, Source Sans, IBM Plex Sans
Typography must contribute voice, not just legibility. No single neutral sans-serif everywhere.
Anti-patterns (avoid)
Cards
- Don't wrap everything in cards
- Don't nest cards inside cards
- Prefer whitespace and scale over borders
Effects
- No decorative animation — motion must communicate state or causality
- Glass is a material, not decoration — must convey depth or focus
- No overly neutral palettes — brand accent used decisively
General
- Template layouts shipped unchanged do not meet the bar
- Perfect symmetry without intent
- Unchanged framework defaults (shadcn, PrimeNG, SwiftUI)
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?