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

brand-guidelines

Create and maintain brand style guides for consistent visual identity. Use when a user asks to create brand guidelines, build a style guide, define a brand identity, create a design system document, establish brand colors and typography, or produce any brand standards documentation.

インストール方法を見る

含まれるファイル(2)

  • SKILL.md8.1 KB
  • _scores.json1.6 KB

SKILL.md(原文)

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

Brand Guidelines

Overview

Create and maintain brand style guides that ensure consistent visual identity across all touchpoints. Covers logo usage, color palettes, typography, spacing, tone of voice, imagery, and component styling. Produces actionable documentation that designers and developers can follow to keep a brand cohesive.

Instructions

When a user asks you to create brand guidelines, follow these steps:

Step 1: Understand the brand foundation

Gather information about:

ElementQuestions
MissionWhat does the company do and why?
AudienceWho are the primary users/customers?
PersonalityIf the brand were a person, how would they behave?
CompetitorsWho are the main competitors? How to differentiate?
Existing assetsAny logos, colors, or fonts already in use?

Define 3-5 brand personality traits:

Examples: Bold & Confident, Friendly & Approachable, Clean & Minimal,
Technical & Precise, Playful & Creative, Premium & Elegant

Step 2: Define the color system

Primary palette (1-2 colors):

Primary:     The main brand color (used for CTAs, links, key UI elements)
Secondary:   Supporting color (used for accents and secondary actions)

Neutral palette:

Gray-950:    Headings, primary text
Gray-700:    Body text
Gray-500:    Secondary text, placeholders
Gray-300:    Borders, dividers
Gray-100:    Backgrounds, hover states
White:       Cards, content areas

Semantic palette:

Success:     Green for confirmations, positive states
Warning:     Amber/yellow for cautions and alerts
Error:       Red for errors and destructive actions
Info:        Blue for informational messages

Color usage rules:

  • Document exact hex, RGB, and HSL values
  • Specify minimum contrast ratios (WCAG AA: 4.5:1 for text)
  • Show approved color combinations and forbidden pairings
  • Define tint/shade variants (100-900 scale) for each brand color

Step 3: Define typography

## Font Families

**Headings:** [Font name] — Bold, confident, used for all headlines
**Body:** [Font name] — Clean, readable, used for paragraphs and UI text
**Code/Mono:** [Font name] — Used for code snippets and technical content

## Type Scale

| Name | Size | Weight | Line Height | Use |
|------|------|--------|-------------|-----|
| Display | 48-64px | Bold | 1.1 | Hero headlines |
| H1 | 36px | Bold | 1.2 | Page titles |
| H2 | 28px | Semibold | 1.3 | Section headers |
| H3 | 22px | Semibold | 1.3 | Subsection headers |
| H4 | 18px | Medium | 1.4 | Card titles |
| Body Large | 18px | Regular | 1.6 | Lead paragraphs |
| Body | 16px | Regular | 1.6 | Default text |
| Body Small | 14px | Regular | 1.5 | Secondary text |
| Caption | 12px | Medium | 1.4 | Labels, metadata |

Step 4: Define logo usage

## Logo Variants
- Full logo (icon + wordmark): Primary use
- Icon only: Favicons, app icons, small spaces
- Wordmark only: When icon context is clear

## Clear Space
- Minimum padding around logo: equal to the height of the logo icon
- Never crowd the logo with other elements

## Incorrect Usage (document these explicitly)
- Do not stretch or distort
- Do not change colors outside approved palette
- Do not add effects (shadows, gradients, outlines)
- Do not place on busy backgrounds without contrast
- Do not rotate or flip

Step 5: Define voice and tone

## Brand Voice (consistent across all content)
- [Trait 1]: We are [description]. Example: "We are direct. We say
  what we mean without jargon or filler."
- [Trait 2]: We are [description].
- [Trait 3]: We are [description].

## Tone Variations (adapts to context)
| Context | Tone | Example |
|---------|------|---------|
| Marketing | Confident, inspiring | "Build something remarkable." |
| Documentation | Clear, helpful | "To get started, install the CLI." |
| Error messages | Empathetic, actionable | "That didn't work. Try again." |
| Social media | Casual, engaging | "New feature just dropped." |

## Writing Rules
- Use active voice
- Keep sentences under 25 words
- Avoid jargon unless audience is technical
- Use contractions (we're, it's, you'll)
- Capitalize only proper nouns and sentence starts

Step 6: Compile the guide

Organize the complete guide with these sections:

  1. Brand Overview (mission, values, personality)
  2. Logo (variants, clear space, usage rules)
  3. Color Palette (primary, neutral, semantic, usage)
  4. Typography (fonts, scale, pairing rules)
  5. Voice & Tone (personality, writing rules, examples)
  6. Imagery (photography style, illustration style, iconography)
  7. Components (buttons, cards, forms — if applicable)
  8. Do's and Don'ts (visual examples of correct and incorrect usage)

Examples

Example 1: Startup brand guidelines

User request: "Create brand guidelines for a fintech startup called Ledger"

Output structure:

# Ledger Brand Guidelines

## Brand Personality
Professional, trustworthy, modern. We make finance feel simple.

## Colors
- Primary: Deep Navy (#1a2744) — Trust, stability
- Accent: Emerald (#10b981) — Growth, success
- Neutrals: Slate scale for text and UI

## Typography
- Headings: Inter (Bold/Semibold)
- Body: Inter (Regular/Medium)
- Monospace: JetBrains Mono (for numbers and data)

## Voice
Clear and confident. We explain complex finance in simple terms.
Never condescending. Never use unnecessary jargon.

## Logo
[Usage rules, clear space, variants]

## Do's and Don'ts
Do: Use plenty of whitespace, let data breathe
Don't: Use flashy gradients or animations on financial data

Example 2: Rebrand color system

User request: "Help me define a color palette for our developer tool brand"

Output:

## Color Palette

### Primary
- Brand Blue: #3b82f6 (rgb 59, 130, 246)
  - Use for: CTAs, links, active states, primary buttons
  - Tints: #dbeafe (bg), #93c5fd (hover), #2563eb (pressed)

### Neutrals (Zinc scale)
- zinc-950: #09090b — Primary headings
- zinc-800: #27272a — Body text
- zinc-500: #71717a — Secondary text
- zinc-300: #d4d4d8 — Borders
- zinc-100: #f4f4f5 — Subtle backgrounds
- white: #ffffff — Card backgrounds

### Semantic
- Success: #22c55e (green-500)
- Warning: #f59e0b (amber-500)
- Error: #ef4444 (red-500)
- Info: #3b82f6 (blue-500)

### Accessibility
All text colors meet WCAG AA contrast ratios:
- zinc-950 on white: 18.4:1 (AAA)
- zinc-800 on white: 12.6:1 (AAA)
- zinc-500 on white: 4.6:1 (AA)
- white on blue-500: 4.7:1 (AA)

Guidelines

  • Brand guidelines are useless if nobody follows them. Keep them concise, visual, and easy to reference.
  • Always include do's and don'ts with visual examples. Abstract rules are ignored; concrete examples are followed.
  • Provide exact values (hex codes, pixel sizes, font weights). "Use a nice blue" is not a guideline.
  • Test the color palette for accessibility before finalizing. Beautiful colors that fail contrast checks are not usable.
  • Include dark mode variants if the product supports it. Do not assume light mode only.
  • Update the guide as the brand evolves. Outdated guidelines are worse than none because they create confusion.
  • Distribute the guidelines where people work. A PDF nobody opens is not useful. A Figma file or living document is.
  • Less is more. A 5-page guide that people actually read beats a 50-page guide that collects dust.

レビュー

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

同じリポジトリのスキル

概要と使いどころ

Scripts and configures production rendering in Autodesk 3ds Max with the V-Ray and Corona renderers: output size and files, render elements, denoising, light mix, batch and command-line rendering, and network rendering. Use when a user asks to set up a production render, render several cameras in one batch, render from the command line or on a render farm, add render passes for compositing, or cut render time for archviz and product shots.

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

TerminalSkills/skills1652026年10月4日 更新

Covers scripting Autodesk 3ds Max, the 3D modeling and rendering application, with MAXScript and Python (pymxs): scene manipulation, object creation, material assignment, camera and light setup, batch operations, and file I/O. Use when tasks involve automating repetitive 3ds Max workflows, batch processing scenes, running scripts headless with 3dsmaxbatch, creating custom tools, or scripting scene setup for archviz, product visualization, or VFX.

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

TerminalSkills/skills1652026年10月4日 更新

3proxy

無料

3proxy is a small open-source proxy server that runs HTTP/HTTPS, SOCKS4/5, SNI and TCP/UDP port-mapping proxies from one config file. Use when a user asks to set up an HTTP or SOCKS5 proxy, add proxy users and passwords, write 3proxy access rules, chain or rotate upstream (parent) proxies, limit bandwidth, connections or monthly traffic per user, run 3proxy in Docker, or fix a 3proxy.cfg that will not start.

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

TerminalSkills/skills1652026年10月4日 更新

Builds Agent2Agent (A2A) servers and clients, the open protocol (originally from Google, now under the Linux Foundation) that lets AI agents from different frameworks call each other. Use when the user wants to create an A2A-compliant agent, build an Agent Card, implement task management, connect agents across frameworks, set up agent discovery, handle streaming responses, implement push notifications, or orchestrate multi-agent workflows. Trigger words: a2a, agent to agent, agent2agent, a2a protocol, a2a server, a2a client, agent card, agent interoperability, agent collaboration, multi-agent, agent discovery, a2a sdk, a2a task.

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

TerminalSkills/skills1652026年10月4日 更新

Plans a controlled experiment (A/B test) so its result can be trusted: writes the hypothesis, picks one primary metric and the guardrails, computes sample size and run time, specifies how visitors are assigned and when exposure is logged, and reads out the result with a confidence interval. Use when someone says "set up an A/B test", "split test this page", "how many visitors do I need", "how long should the experiment run", "is this result significant", "can I stop the test early", or wants to test a headline, price, layout or onboarding change against the current version.

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

TerminalSkills/skills1652026年10月4日 更新

ably

無料

Ably is a hosted realtime messaging service: clients publish and subscribe to named channels over WebSockets, see who is present, replay message history, and resume after a dropped connection. Use when a user asks to "add realtime updates", "push live notifications to the browser", "show who is online", "add a chat room with typing indicators", "publish from a serverless function", or "authenticate Ably clients without exposing the API key". Covers the ably 2.x JavaScript SDK (Realtime and REST), JWT token authentication, presence, history and rewind, batch publishing, and the @ably/chat 1.x SDK.

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

TerminalSkills/skills1652026年10月4日 更新

TerminalSkills のスキルをすべて見る

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