Brand system builder

Skill nahiddotai/operator-powers/plugins/operator-powers/skills/brand-system-builder

AI skills to operate and grow. Twenty-eight practical powers for non-technical operators.

Install

npx -y skills add nahiddotai/operator-powers --skill brand-system-builder

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

19 days oldThe repository was created 19 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Build a reusable visual identity from goals and references, with practical rules for colour, type, spacing, imagery, layout, components, and applications.

SKILL.md

3.0 KB, as published. Nobody here has run it

Brand System Builder

Turn visual taste into reusable decisions that different people and tools can apply consistently.

Job contract

Owns: visual identity rules and reusable design decisions.
Does not own: written voice (voice-dna) or production of one asset (instagram-carousel-maker, html-slideshow).
Finished deliverable: brand foundation, tokens, usage rules, component patterns, and examples.

Starting Material

Use whatever the user can provide. Do not require professional brand assets.

Existing brand: logos, colours, fonts, pages, or guidelines.
Reference-led: screenshots, websites, packaging, posts, or examples they like or dislike.
Description-led: plain-language descriptions such as “warm but credible,” the audience, and where the brand will appear.
Open exploration: no visual material yet. Ask for the audience, desired feeling, priority applications, and anything to avoid, then propose two or three clearly different directions. Recommend one when the user wants you to decide.

Label existing facts separately from proposed choices. A lack of assets is a reason to create a starting system, not to stop.

Workflow

Collect any available assets, screenshots, examples, descriptions, audience, applications, and accessibility constraints.
Select the closest starting-material route. When evidence is thin, create proposed directions instead of inventing an established brand.
Define the chosen visual character in three to five concrete traits and explain how each affects design decisions.
Set usable colour roles and values, typography hierarchy and fallbacks, spacing, shape, imagery, icon, and motion rules.
Check contrast, readability, mobile use, print use when relevant, and light/dark behaviour.
Build repeatable components and at least two application examples for the user's priority surfaces.
Produce a compact specification, token set, and examples an agent, non-designer, or designer can apply without interpretation.

Output

# Brand System

## Foundation
[Audience, positioning, visual traits]

## Visual Tokens
[Colours with roles and values, typography, spacing, radius, borders]

## Imagery And Graphic Language
[Photography, illustration, icon, texture, chart rules]

## Layout Rules
[Grid, hierarchy, whitespace, responsive behaviour]

## Components
[Buttons, cards, callouts, covers, slide/page patterns]

## Do And Avoid
[Concrete examples]

## Application Examples
[How the rules apply to the user's priority surfaces]

## Status
[Existing decisions, new proposals, and choices still open]

Guardrails

Never infer a brand fact from a single accidental screenshot.
Never treat a proposed direction as something the user already chose.
Check legibility and contrast before aesthetic preference.
Do not copy another brand's protected assets or distinctive trade dress.