AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Applying Visual Identity

skill-luccapinto-agentic-data-kit-applying-visual-identity · by luccapinto

Use when the user wants output to follow a company's brand / visual identity, or asks to set one up — "use our brand", "make it on-brand", "here's our identity", "create a DESIGN.md". Reads and applies a DESIGN.md (Google Labs open spec): brand tokens for colors, typography, spacing, radius, shadows, and components, so decks, sites, and docs come out consistently on-brand. Scaffolds a DESIGN.md w…

↗ Repository
— No reviews yet
0 installs
17 views
0.0% view→install

Install

$ agentstack add skill-luccapinto-agentic-data-kit-applying-visual-identity

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-luccapinto-agentic-data-kit-applying-visual-identity)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● 28d ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Applying Visual Identity? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Skill: applying-visual-identity

A company's visual identity lives in a DESIGN.md at the project root — the open spec from Google Labs (Apache-2.0, 2026). It pairs machine-readable design tokens (YAML frontmatter) with human-readable rationale (prose), so any AI tool renders the brand the same way across sessions. This skill reads that file and applies it; if none exists, it scaffolds one.

Workflow

  1. Locate. Look for DESIGN.md in the project root. If found, parse the frontmatter tokens

— they are the normative values; the prose is guidance.

  1. Apply. Map tokens to the target medium:
  • HTML/reveal.js/Marp → CSS custom properties on :root (--brand-primary, --font-heading, …).
  • Markdown/docs → headings, callouts, accent usage per the Do's/Don'ts.
  • Resolve token references like {colors.primary} before output.
  1. Stay in-spec. Use only defined tokens; don't introduce off-palette colors or fonts. If a

needed token is missing, ask or pick the closest defined one and note it.

  1. Scaffold when absent. If there's no DESIGN.md, offer to create one from

templates/DESIGN.md — ask for (or extract from a provided logo/site) the primary color, font, and tone. Never silently invent a brand; fall back to a neutral theme until confirmed.

The DESIGN.md format (Google Labs spec)

YAML frontmatter holds the tokens; the body documents intent in fixed sections.

Frontmatter token groups: colors, typography (objects: fontFamily, fontSize, fontWeight, lineHeight, letterSpacing), spacing, rounded, shadows, components (per-component token refs). Colors accept hex / rgb / hsl / oklch(). Dimensions carry units (px, rem). References use braces: {colors.primary}, {typography.h1}.

Body sections (in order): Overview · Colors · Typography · Layout & Spacing · Elevation & Depth · Shapes · Components · Do's and Don'ts.

See templates/DESIGN.md for a complete, fillable example.

Rules

  • Tokens are normative — match them exactly; the prose only explains why.
  • Keep DESIGN.md in the project root so every tool and agent finds it.
  • One source of truth: when the brand changes, edit DESIGN.md, not individual decks.
  • This skill defines the look; building-html-presentations defines the structure.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Developer Tools