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

brand-design

Generate brand guidelines, design systems with design tokens (W3C format), creative direction (SCAMPER, Design Thinking, TRIZ), and design briefs with scope and success criteria.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md11.6 KB

SKILL.md(原文)

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

Brand Design Skill v3.0

Brand identity, design systems, creative direction, and project briefs.


Workflow: Brand / Design System Creation

Follow this numbered process. Do not skip steps.

StepActionOutput
1Gather inputs: brand story, competitors, audience research, technical constraintsBrief document
2Define brand strategy: positioning, personality (3-5 adjectives), tone of voiceBrand strategy doc
3Build color system: primary, neutral, semantic palettes + WCAG AA checksColor tokens + palette
4Select typography: headline/body pairing, scale, line-height, responsive sizingTypography tokens
5Define spacing, radius, shadow, motion tokens (W3C format)Design tokens JSON
6Create logo variations + usage guidelinesLogo guidelines
7Apply to 3+ touchpoints: web, print, social, or environmentalApplication mockups
8Run design system audit (see checklist below)Audit report
9Document anti-patterns and error statesError + anti-pattern docs
10Stakeholder review + alignment sign-offApproved design system v1.0

Error Handling

ErrorCauseFix
Color contrast fails WCAG AALuminance ratio < 4.5:1 for textDarken or lighten until ratio passes. Use contrastRatio in tokens.
Token mismatch across platformsFigma tokens != code tokensSingle source of truth: W3C JSON. Export from design tool.
Typography scale gapsMissing intermediate sizesBuild scale with modular scale (1.25 or 1.333 ratio).
Logo illegible at min sizeToo much detail in iconUse simplified lockup or separate wordmark + icon variants.
Design brief scope creepUnclear out-of-scope listExplicit "what's NOT included" section. Reference during reviews.
Stakeholder disagreementNo clear decision authorityIdentify single approver in brief. Escalate to DRI.
Campaign fails originality axisCliché or derivative ideaForce 5+ directions. Run through SCAMPER/TRIZ. Reference culture, not competitors.

Brand Guidelines

A complete brand system has 9 sections: brand story, logo, color, typography, spacing, imagery, voice, application, anti-patterns.

Color Palette

Primary (2-4 colors, 60%+ of touchpoints):

RoleHexUsage
Primary#1B365DHeadlines, primary buttons
Accent#F5BD47CTAs, highlights

Neutral (grays for UI):

NameHexUsage
Dark#080808Headings
Mid#666666Body text
Light#E0E0E0Borders
Surface#F5F5F5Backgrounds

Semantic: Success #2ECC71, Warning #F39C12, Error #E74C3C, Info #3498DB

Design Tokens (W3C Format)

{
  "color": {
    "primary": { "$value": "#1B365D", "$type": "color" },
    "accent": { "$value": "#F5BD47", "$type": "color" },
    "surface": { "$value": "#F5F5F5", "$type": "color" }
  },
  "spacing": {
    "xs": { "$value": "4px", "$type": "dimension" },
    "sm": { "$value": "8px", "$type": "dimension" },
    "md": { "$value": "16px", "$type": "dimension" },
    "lg": { "$value": "32px", "$type": "dimension" }
  },
  "borderRadius": {
    "sm": { "$value": "4px", "$type": "dimension" },
    "md": { "$value": "8px", "$type": "dimension" },
    "full": { "$value": "9999px", "$type": "dimension" }
  }
}

Typography

ElementWeightSizeLine Height
Display H1Boldclamp(2.5rem,5vw,4.5rem)1.1
H2Boldclamp(1.75rem,3vw,2.5rem)1.2
H3Semiboldclamp(1.25rem,2vw,1.75rem)1.25
BodyRegular1rem (16px)1.6
CaptionRegular0.75rem1.4

Body text minimum 16px. Line length 45-75 chars. Contrast min 4.5:1 (WCAG AA).

Font Pairing Examples:

StyleHeadlineBody
Premium editorialPlayfair DisplaySource Sans Pro
Modern SaaSInterInter
Creative agencySynePlus Jakarta Sans
LuxuryCormorant GaramondProxima Nova

Logo Guidelines

  • Variations: primary, secondary, icon (32x32), wordmark
  • Clear space = height of "H" on all sides
  • Min size: 80px digital, 1.5in print
  • Never stretch, recolor, rotate, add effects, or use on low-contrast backgrounds

Tone of Voice

DimensionRule
Personality3-5 adjectives (e.g. confident, warm, precise)
VocabularyUse "we/you". Avoid "one/our users"
FormalityCasual for social, formal for investor comms
HumorIn social/email. Never in legal, support, or crisis

Design System Audit Checklist

  • All colors have hex/RGB/HSL values and usage guidelines
  • Typography scale covers 6+ sizes with line-height
  • Spacing scale (4/8/16/24/32/48/64px)
  • Component library matches design tokens
  • Dark mode variants defined
  • Accessibility: all color combos pass WCAG AA 4.5:1
  • Icons: consistent stroke width, corner radius, size grid
  • Shadow/elevation system defined
  • Motion: duration, easing, reduced-motion alternative
  • Form elements: all states (default, hover, focus, error, disabled)
  • Breakpoints match design tool
  • Figma component properties mapped to code props

Production Checklist

Before shipping any design system or brand guidelines:

CheckCriteriaOwner
Color parityHex values match exactly between Figma + code + docsDesign + Dev
Token exportW3C JSON exported and imported into codebaseDesign
Font licensingAll typefaces have valid web + print licensesProd Mgr
Logo rasterizationVector + PNG + favicon exported at all required sizesDesign
Accessibility auditAutomated + manual passes (axe, color contrast, keyboard nav)QA
Dark modeAll colors have dark mode variants, no hardcoded valuesDesign
Responsive breakpointsLayout tested at mobile, tablet, desktopDev
Motion reducedprefers-reduced-motion respected for all animationsDev
Component statesAll interactive elements defined: default, hover, focus, active, error, disabledDesign
Figma dev handoffComponents published with props, variants, and descriptionsDesign

Creative Direction

Ideation Methodologies

MethodologyBest for
SCAMPERProduct innovation, rebranding
Design ThinkingHuman-centered problem solving
TRIZ (40 principles)Technical problem solving
BisociationConnecting two unrelated frameworks
Synectics (analogies)Creative campaigns
SITInnovation with constraints
Blue Ocean StrategyMarket differentiation

Campaign Architecture

LevelTimeframeWhat
Brand platform3-5 yearsPositioning
Campaign themeAnnualWhat we say this year
Creative executionsPer assetHow we bring it to life
Tactical adaptationsPer channelHow it works in this medium

Campaign Idea Evaluation (5-axis)

AxisPassingFail
Originality (1-10)7+Below 5
Relevance (1-10)8+Below 6
Impact (1-10)7+Below 5
Feasibility (1-10)6+Below 4
Durability (1-10)6+Below 4

Score min 3 axes at 7+ to proceed.


Design Brief

Structure

  1. Project overview: what and why (2-3 sentences)
  2. Problem statement: "[User] cannot [goal] because [barrier]"
  3. Objectives: SMART
  4. Target audience: demographics, behaviors, goals, pain points, anti-audience
  5. Scope: what's in and explicitly out
  6. Deliverables: format, quantity, specs, revision rounds
  7. Timeline: phases, milestones, review points, buffer
  8. Success criteria: testable, with metrics and targets
  9. Constraints: budget, technology, brand, legal, timeline

Stakeholder Alignment Questions

  1. Who has final approval?
  2. What's the single most important metric?
  3. What can we deprioritize if scope shrinks?
  4. Who are we NOT designing for?
  5. What are the non-negotiables (legal, brand, technical)?

Anti-Patterns

Anti-PatternWhy It FailsFix
No single-minded propositionMessage dilutes, audience confusedForce one idea. Kill the rest.
Problem stated as solutionBrief prescribes fix instead of framing the real issueDescribe the problem, not the fix
Vague success criteriaCannot measure success or failureDefine specific, testable criteria with targets
No constraints givenDesign that looks great but can't be built or shippedAdd budget, tech, timeline constraints upfront
Too many stakeholdersDesign by committee produces mediocrityIdentify single DRI per decision type
Skipping audience insightDesign solves wrong problemResearch first. Find a non-obvious truth.
Chasing trendsLooks dated in 6 months, no differentiationReference culture, not competitors
Falling in love with first ideaBiased evaluation, better solutions missedForce 5+ directions before selecting
Designing for yourselfEnd-user needs subordinated to designer preferencesUser test with real audience segments
No error states definedUI breaks silently, bad UXDefine error, empty, loading states for every component

Design Token Architecture

{
  "color": {
    "primary": { "value": "#1B365D", "type": "color" },
    "primary-light": { "value": "#2D5A8A", "type": "color" }
  },
  "spacing": {
    "xs": { "value": "4px", "type": "spacing" },
    "sm": { "value": "8px" }, "md": { "value": "16px" }, "lg": { "value": "24px" }
  },
  "typography": {
    "heading": { "value": { "fontFamily": "Charter", "fontWeight": 500, "fontSize": "clamp(32px,5vw,56px)" } }
  }
}

Export as W3C Design Token format for Figma Tokens plugin, Style Dictionary, or token-transformer.

Figma-to-Code Handoff

  1. Dev Mode: inspect spacing (8px grid), colors (variables), typography (named styles)
  2. Export assets: SVG for icons, PNG @2x for raster
  3. Component mapping: FigmaComponent → ReactComponent documented before build
  4. Responsive: Figma frames at 375px (mobile), 768px (tablet), 1440px (desktop)

Sources

  • Pentagram — brand identity project standards
  • NASA Graphics Standards Manual
  • Stripe Brand Guidelines
  • W3C Design Tokens Format
  • IDEO design thinking methodology
  • Ogilvy "On Advertising"
  • Design Council UK "Double Diamond"
  • NN Group "How to Write a Design Brief"
  • Figma Design Tokens plugin

Checklist

  • Skill loads without errors in the AI agent
  • YAML frontmatter is valid (description, compatibility, audience)
  • Workflow section provides clear step-by-step instructions
  • Error handling section covers common failure modes
  • All referenced files (references/, scripts/, assets/) exist
  • Skill triggers correctly for intended use cases
  • No broken links or missing resources

レビュー

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

同じリポジトリのスキル

概要と使いどころ

Apply professional, premium UI/UX design standards when building or styling web interfaces. Use this skill when the user asks to create a website, landing page, web app, dashboard, UI component, or any visual interface — or when they ask to make something look better, more professional, or more beautiful. Covers visual hierarchy, typography, color systems, layout, spacing, motion, dark mode, responsive design, and conversion patterns. Activate even when the user doesn't say "design" — if they're building a web frontend, these standards apply.

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

EliasOulkadi/shokunin1142026年10月5日 更新

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.

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

EliasOulkadi/shokunin1142026年10月5日 更新

Run 150+ AI apps via inference.sh CLI - image generation, video creation, LLMs, search, 3D, Twitter automation. Models: FLUX, Veo, Gemini, Grok, Claude, Seedance, OmniHuman, Tavily, Exa, OpenRouter, and many more. Use when running AI apps, generating images/videos, calling LLMs, web search, or automating Twitter. Triggers: inference.sh, infsh, ai model, run ai, serverless ai, ai api, flux, veo, claude api, image generation, video generation, openrouter, tavily, exa search, twitter api, grok

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

EliasOulkadi/shokunin1142026年10月5日 更新

api-forge

無料

Design REST/GraphQL APIs with OpenAPI 3.1, error handling, pagination, rate limiting, webhooks, and idempotency. Use when user asks to design an API, create endpoints, define REST/GraphQL schema, or generate OpenAPI spec. Do NOT use for database schema design, frontend API integration, or non-HTTP protocols (gRPC, WebSocket, MQTT).

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

EliasOulkadi/shokunin1142026年10月5日 更新

Implement authentication and authorization with OWASP Top 10 standards, OAuth 2.0 + OIDC, WebAuthn/Passkeys, session management, and RBAC/ABAC. Use when user asks to implement login, signup, authentication, authorization, JWT, OAuth, SSO, passkeys, MFA, or role-based access. Do NOT use for API key management (use api-forge), encryption at rest, or network-level security (firewalls, WAF).

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

EliasOulkadi/shokunin1142026年10月5日 更新

Generate sales outreach sequences, proposals, SOWs, investor pitch decks, and RFP responses. Covers cold email sequences, proposal structure, pricing tiers (Good-Better-Best), scope of work with exclusions, and 10-slide pitch deck.

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

EliasOulkadi/shokunin1142026年10月5日 更新

EliasOulkadi のスキルをすべて見る

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