DesignMD Brand Kit
Use this skill to turn a public website or provided DESIGN.md into practical design constraints for Codex UI work and client research.
Inputs
Accept any of:
- a public website URL or domain,
- a generated
DESIGN.md,
- screenshots plus notes,
- existing CSS/Tailwind tokens,
- a client/company name for research.
If only a company name is given, find the official site before analyzing current visual identity.
Workflow
- Gather brand evidence:
- Prefer an existing
DESIGN.md if provided.
- Otherwise use designmd.supply or a local
context-dot-dev/designmd-supply run when credentials are available.
- If unavailable, manually inspect the official site, screenshots, CSS, and page content.
- Extract constraints:
- brand name, positioning, tone,
- colors and semantic roles,
- typography scale and font families,
- spacing, radii, borders, elevation,
- layout patterns,
- component patterns,
- concrete do's and don'ts.
- Verify:
- Check the site/screenshot for obvious mismatches.
- Treat extracted tokens as evidence, not gospel.
- Flag uncertainty instead of inventing precise token values.
- Apply:
- Generate or update
DESIGN.md, Tailwind v4 theme tokens, CSS variables, or implementation notes as the task requires.
- Use the brand kit as constraints, not as a demand to clone the original site.
- For client research, summarize design implications without publishing, emailing, or changing external systems unless the user approves.
DESIGN.md Shape
Prefer this structure:
---
version: alpha
name:
description:
colors:
typography:
rounded:
spacing:
components:
---
## Overview
## Colors
## Typography
## Layout
## Elevation & Depth
## Shapes
## Components
## Do's and Don'ts
YAML values should be machine-usable. Markdown should explain when and how to apply them.
Token Rules
- Color values should be SRGB hex strings.
- Use semantic names:
primary, secondary, surface, on-surface, muted, border, accent, error.
- Typography tokens should include font family, size, weight, line-height, and intended use.
- Spacing/radii should map to a small usable scale, not every observed value.
- Component tokens should describe repeated patterns: buttons, nav, cards, forms, badges, tables, hero, footer.
- If a token is inferred, say so in prose, not in the token value.
Tailwind v4 Output
When asked for Tailwind v4, emit tokens in CSS-first form:
@theme {
--color-brand-primary: #000000;
--color-brand-surface: #ffffff;
--font-brand-sans: "Inter", sans-serif;
--radius-brand-md: 8px;
--spacing-brand-section: 4rem;
}
Only write these into a project after checking the existing Tailwind setup and naming conventions.
CSS Variables Output
When asked for CSS variables, prefer:
:root {
--brand-primary: #000000;
--brand-surface: #ffffff;
--brand-text: #111111;
--brand-muted: #666666;
--brand-radius-md: 8px;
}
For dark themes or alternate modes, use scoped selectors such as [data-theme="dark"].
Frontend Application Rules
- Use the brand kit to guide hierarchy, color, spacing, typography, and interaction states.
- Preserve the project's existing design system when one already exists; map brand tokens into local conventions.
- Do not copy a competitor's site one-to-one. Use compatible visual language, not imitation.
- Verify with browser screenshots when implementing UI.
- If generated UI conflicts with the brand kit, revise the UI or explain why the project context overrides the kit.
Client And Job Search Use
For potential clients or employers:
- Add a compact brand/design read to the company notes: visual positioning, maturity, inconsistencies, opportunities.
- Identify useful outreach angles from evidence: outdated UI, inconsistent tokens, unclear hierarchy, weak conversion path, accessibility issues, performance/design debt.
- Keep claims specific and non-accusatory.
- Draft messages only; sending, applying, posting, or changing public profiles requires user approval.
- Avoid storing screenshots, contacts, resumes, or private notes in reusable global skills.
Final Output
Report:
- source used: URL, provided
DESIGN.md, screenshot, or manual inspection,
- core brand constraints,
- files created or changed,
- verification performed,
- uncertainty and risks.
1---2name: designmd-brand-kit3description: Create, inspect, and apply DESIGN.md brand kits for brand-aware frontend work. Use when building or reviewing landing pages, frontend UI, pitch pages, redesigns, client audits, brand-matched prototypes, or researching a potential client/company where website identity, design tokens, typography, layout, components, or do/don't guidance should shape the output.4license: MIT5metadata:6 source: https://skillmd.com/skills/markoblogo/designmd-brand-kit7 abvx_status: experimental8 abvx_origin: adapted9---1011# DesignMD Brand Kit1213Use this skill to turn a public website or provided `DESIGN.md` into practical design constraints for Codex UI work and client research.1415## Inputs1617Accept any of:1819- a public website URL or domain,20- a generated `DESIGN.md`,21- screenshots plus notes,22- existing CSS/Tailwind tokens,23- a client/company name for research.2425If only a company name is given, find the official site before analyzing current visual identity.2627## Workflow28291. Gather brand evidence:30 - Prefer an existing `DESIGN.md` if provided.31 - Otherwise use [designmd.supply](https://www.designmd.supply/) or a local `context-dot-dev/designmd-supply` run when credentials are available.32 - If unavailable, manually inspect the official site, screenshots, CSS, and page content.332. Extract constraints:34 - brand name, positioning, tone,35 - colors and semantic roles,36 - typography scale and font families,37 - spacing, radii, borders, elevation,38 - layout patterns,39 - component patterns,40 - concrete do's and don'ts.413. Verify:42 - Check the site/screenshot for obvious mismatches.43 - Treat extracted tokens as evidence, not gospel.44 - Flag uncertainty instead of inventing precise token values.454. Apply:46 - Generate or update `DESIGN.md`, Tailwind v4 theme tokens, CSS variables, or implementation notes as the task requires.47 - Use the brand kit as constraints, not as a demand to clone the original site.485. For client research, summarize design implications without publishing, emailing, or changing external systems unless the user approves.4950## DESIGN.md Shape5152Prefer this structure:5354```markdown55---56version: alpha57name:58description:59colors:60typography:61rounded:62spacing:63components:64---6566## Overview67## Colors68## Typography69## Layout70## Elevation & Depth71## Shapes72## Components73## Do's and Don'ts74```7576YAML values should be machine-usable. Markdown should explain when and how to apply them.7778## Token Rules7980- Color values should be SRGB hex strings.81- Use semantic names: `primary`, `secondary`, `surface`, `on-surface`, `muted`, `border`, `accent`, `error`.82- Typography tokens should include font family, size, weight, line-height, and intended use.83- Spacing/radii should map to a small usable scale, not every observed value.84- Component tokens should describe repeated patterns: buttons, nav, cards, forms, badges, tables, hero, footer.85- If a token is inferred, say so in prose, not in the token value.8687## Tailwind v4 Output8889When asked for Tailwind v4, emit tokens in CSS-first form:9091```css92@theme {93 --color-brand-primary: #000000;94 --color-brand-surface: #ffffff;95 --font-brand-sans: "Inter", sans-serif;96 --radius-brand-md: 8px;97 --spacing-brand-section: 4rem;98}99```100101Only write these into a project after checking the existing Tailwind setup and naming conventions.102103## CSS Variables Output104105When asked for CSS variables, prefer:106107```css108:root {109 --brand-primary: #000000;110 --brand-surface: #ffffff;111 --brand-text: #111111;112 --brand-muted: #666666;113 --brand-radius-md: 8px;114}115```116117For dark themes or alternate modes, use scoped selectors such as `[data-theme="dark"]`.118119## Frontend Application Rules120121- Use the brand kit to guide hierarchy, color, spacing, typography, and interaction states.122- Preserve the project's existing design system when one already exists; map brand tokens into local conventions.123- Do not copy a competitor's site one-to-one. Use compatible visual language, not imitation.124- Verify with browser screenshots when implementing UI.125- If generated UI conflicts with the brand kit, revise the UI or explain why the project context overrides the kit.126127## Client And Job Search Use128129For potential clients or employers:130131- Add a compact brand/design read to the company notes: visual positioning, maturity, inconsistencies, opportunities.132- Identify useful outreach angles from evidence: outdated UI, inconsistent tokens, unclear hierarchy, weak conversion path, accessibility issues, performance/design debt.133- Keep claims specific and non-accusatory.134- Draft messages only; sending, applying, posting, or changing public profiles requires user approval.135- Avoid storing screenshots, contacts, resumes, or private notes in reusable global skills.136137## Final Output138139Report:140141- source used: URL, provided `DESIGN.md`, screenshot, or manual inspection,142- core brand constraints,143- files created or changed,144- verification performed,145- uncertainty and risks.