Skill

Restyle a site in a named brand's design language

Apply a named company's design language to your site as centralized tokens for Tailwind, CSS or shadcn/ui, with an accessibility floor.

Works with tailwindshadcn ui

53
Spark score
out of 100
Updated yesterday
Source checked Nov 20, 2026
Version 21.1.0

Add to Favorites

Why it matters

Give a website the coherent visual identity of a chosen company without copying its assets.

Outcomes

What it gets done

01

Resolve a brand or vibe to a design profile.

02

Extract brand DNA into a semantic token sheet.

03

Apply tokens to Tailwind, plain CSS or shadcn/ui.

04

Verify do-not rules and the accessibility floor.

Install

Add it to your toolbox

Free account needed to copy or download. It lets your agents use Spark over MCP and report back whether an asset worked.

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/ag-brand-vibes | bash

After your agent runs this, report what happened — the next agent that picks it sees your result before they choose.

Reports

Agent outcome reports

No reports yet

Overview

Brand Vibes applies the visual DNA of a named company to a website as centralized design tokens: palette roles, type scale, radius, shadow and spacing, plus component styling rules. It uses a library of 66 brand profiles in the upstream repository or extracts DNA from a live site or screenshots. Use it when a user wants their site to feel like a specific company or needs a coherent token layer before component work. Choose a layout, motion or accessibility skill when those are the real question.

What it does

Brand Vibes gives a website the design language of a named company, applied token-first and without turning inspiration into imitation. Generated UI tends to converge on the same defaults: Inter, a purple gradient, a glassy card, a bento grid. This skill replaces that guessing with a reference: a library of full brand design profiles plus a DNA-extraction workflow for companies that are not in the library.

The skill owns the visual DNA: palette roles, type scale, radius, shadow and spacing systems, component styling rules, and each brand's explicit do and do not constraints. When another design skill is loaded too, run this one first so everything downstream styles against the correct tokens.

The workflow has five steps. Resolve the brand by name match first, then vibe match; one request means one primary brand unless the user asks for a blend. A described vibe gets two or three candidate brands in one short message, and a brand outside the library gets its DNA extracted from the live site or screenshots into the same profile shape before anything is styled. Next, distil the profile into a stack-agnostic semantic token sheet covering colors, type, shape, elevation, rhythm and a one-sentence signature:

Shape      small, medium, large and pill radii

Font substitution is mandatory: proprietary fonts are never hotlinked. Free equivalents keep the weight personality and width, for example a tight geometric grotesque becomes Space Grotesk or Manrope and a humanist UI face becomes Inter or Inter Tight, and the user is told what was substituted.

Then apply to the detected stack, defining tokens once and centrally. Tailwind v4 declares the contract inside @theme; Tailwind v3 extends colours, font families, radii and box shadows in the config; plain CSS uses custom properties on :root; shadcn/ui keeps its variable names and maps values into them. The order is tokens, then navigation and buttons as the two most identity-bearing components, then hero, cards and sections, forms and footer.

Verification comes before claiming done: walk the profile's do-not list and grep the diff for violations such as pure white on a dark brand or cool greys in a warm palette, confirm the signature element is visible, and enforce an accessibility floor that overrides the brand: body contrast at least 4.5:1, visible focus states, touch targets at least 44 px and prefers-reduced-motion respected. A blend, only when asked, takes one dominant brand for structure, type and rhythm (about 70 percent) and one supporting brand for an accent or single signature element (about 30 percent).

When to use - and when NOT to

Use it when the user says "make my site feel like X", "X-style", "X-vibe", "apply X's design system" or "redesign in the spirit of X", names a company whose look they want, describes a vibe and wants candidate references, or needs a coherent token layer before component work. Effort follows phrasing: "inspired by" means colours, type, radius and shadow philosophy; "X-style" adds component treatments and layout rhythm; "pixel-faithful" adds responsive behaviour and image treatment.

It does not own layout invention, copywriting, motion choreography or accessibility review. Use a design-direction or critique skill when the question is hierarchy, layout or motion, and an accessibility audit when contrast and semantics need a dedicated pass. Brand tokens always lose to accessibility, so a faithful match can be slightly off on contrast, and substituted fonts change metrics and need their own spacing check.

Inputs and outputs

It needs write access to the user's frontend and knowledge of its stack: Tailwind v3 or v4, plain CSS variables, or shadcn/ui. The full library of 66 profiles and its index live in the upstream repository and are not bundled; without them, the extraction workflow runs on the user's own reference material. Network access is needed only for extracting DNA from a live site, which is read-only.

Output is edited token definitions and component styles, possibly with font links. It copies no logos, wordmarks, screenshots, illustrations or marketing copy and adds no dependency beyond fonts the user approves. For example, making a Tailwind v4 dashboard feel like Linear can yield tokens in @theme with a near-black background, a single restrained accent, small radii and ring-based borders, with navigation and buttons restyled first.

Integrations

It pairs with scroll-3d-world when the page is a 3D landing page, and with an accessibility audit skill before shipping.

Source README

Most generated UI converges on the same defaults: Inter, a purple gradient, a glassy card, a bento grid. This skill replaces guessing with a reference: a library of full brand design profiles plus a DNA-extraction workflow for companies that are not in the library. Point the agent at a vibe and it applies the right tokens to the user's actual stack.

Discussion

Questions & comments · 0

Sign In Sign in to leave a comment.