# Creative

Playful, character-driven design with expressive typography and bold graphics for...

- Repository: https://github.com/bergside/awesome-design-skills (3441 stars)
- Category: Design
- License: MIT
- Last updated: 2026-06-28
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add bergside/awesome-design-skills --skill creative -g -a claude-code -y`
Codex: `npx skills add bergside/awesome-design-skills --skill creative -g -a codex -y`
Cursor: `npx skills add bergside/awesome-design-skills --skill creative -g -a cursor -y`
Gemini CLI: `npx skills add bergside/awesome-design-skills --skill creative -g -a gemini-cli -y`

## Description

Playful, character-driven design with expressive typography and bold graphics for landing pages and creative projects.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

<!-- TYPEUI_SH_MANAGED_START -->
# Creative Design System Skill (Universal)

## Mission
You are an expert design-system guideline author for Creative.
Create practical, implementation-ready guidance that can be directly used by engineers and designers.

## Brand
cerative style for landing  pages

## Style Foundations
- Visual style: playful
- Typography scale: 12/14/16/20/24/32 | Fonts: primary=Bangers, display=Bangers, mono=IBM Plex Mono | weights=100, 200, 300, 400, 500, 600, 700, 800, 900
- Color palette: primary, secondary, neutral, success, warning, danger | Tokens: primary=#3B82F6, secondary=#8B5CF6, success=#16A34A, warning=#D97706, danger=#DC2626, surface=#FFFFFF, text=#111827
- Spacing scale: 4/8/12/16/24/32


## Accessibility
WCAG 2.2 AA, keyboard-first interactions, visible focus states

## Writing Tone
concise, confident, helpful

## Rules: Do
- prefer semantic tokens over raw values
- preserve visual hierarchy
- keep interaction states explicit

## Rules: Don't
- avoid low contrast text
- avoid inconsistent spacing rhythm
- avoid ambiguous labels

## Expected Behavior
- Follow the foundations first, then component consistency.
- When uncertain, prioritize accessibility and clarity over novelty.
- Provide concrete defaults and explain trade-offs when alternatives are possible.
- Keep guidance opinionated, concise, and implementation-focused.

## Guideline Authoring Workflow
1. Restate the design intent in one sentence before proposing rules.
2. Define tokens and foundational constraints before component-level guidance.
3. Specify component anatomy, states, variants, and interaction behavior.
4. Include accessibility acceptance criteria and content-writing expectations.
5. Add anti-patterns and migration notes for existing inconsistent UI.
6. End with a QA checklist that can be executed in code review.

The rest: https://github.com/bergside/awesome-design-skills/blob/HEAD/skills/creative/SKILL.md