agentsclimarketplace
Sign in

Brand design

Skill pivyme/suiperpower/core/skills/build/brand-design

Pick a brand name, color palette, or typography for a Sui product. Use when the user wants to name or brand a Sui project.From its SKILL.md

Install
npx -y skills add pivyme/suiperpower --skill brand-design

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

  • 12 stars12 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.
  • runs commandsInstructs the agent to run 2 commands, including `suiperpower track brand-design build started` and 1 more.

SKILL.md

5.2 KB, ~1.3k tokens by cl100k_base, as published. Nobody here has run it

Preamble (run first)

# Suiperpower telemetry. Routes through the CLI so projects.json + Convex stay in sync.
# Silent on failure so the skill never blocks. Opt out: SUIPERPOWER_TELEMETRY=off.
#
# AGENT NOTE: when this skill finishes, run the matching completion command:
#   suiperpower track brand-design build completed
# Or use "failed" / "aborted" if it ended that way.
command -v suiperpower >/dev/null 2>&1 && suiperpower track brand-design build started >/dev/null 2>&1 &
true

If TEL_PROMPTED is no, before doing real work, ask the user:

Help suiperpower get better. We track which skills get used and how long they take. No code, no file paths, no PII. Change anytime in ~/.suiperpower/config.json.

A) Sure, anonymous B) No thanks

Write the answer to ~/.suiperpower/config.json telemetryTier field and create ~/.suiperpower/.telemetry-prompted. Then continue.

What this skill does

Helps the user pick three brand decisions: name, color palette, typography. The output is concrete enough to drop into Tailwind config and a logo brief, not a 30-page brand bible. It actively pushes back on the generic crypto look (purple gradients, neon glow, generic sans-serif) and helps the user develop a brand that does not look AI-generated.

When to use it

  • The product has no name, or a placeholder name the user wants to replace.
  • The frontend is being scaffolded and the team needs colors and a typeface.
  • An existing brand looks generic and the user wants a critique.

When NOT to use it

  • The user already has a brand they are happy with.
  • The user wants a marketing video or pitch deck, route to those skills.
  • The user is mid-build on Move logic, finish that first.

If you activated this and the user actually wants something else, consult skills/SKILL_ROUTER.md and hand off.

Inputs

  • The product's positioning in one sentence (what it does, for whom).
  • A target tone (serious / playful / technical / consumer).
  • Optional: existing logo, existing color usage, existing typography choices.

Outputs

A brand spec written to .suiperpower/brand.md:

## brand-design session, <timestamp>
- name: <chosen name>, rationale: <one sentence>
- color palette:
  - primary: <hex>
  - secondary: <hex>
  - background: <hex>
  - text: <hex>
  - accent / warning / success: <hex each>
- typography: <heading family>, <body family>, <mono if used>
- logo brief: <one paragraph for a designer>
- tone references: <2-3 brand examples to follow>
- anti-references: <2-3 brand examples to NOT look like>

Workflow

  1. Pull positioning

    • Read .suiperpower/idea-context.md if present. If not, ask one sentence on what the product does and for whom.

  2. Name

    • Generate 5 candidates, evaluate each on: pronounceable in 2 seconds, .com or .xyz available (best-effort), not already a Sui project (search the catalog), not a banned word.
    • Pick the top 1, present the user with all 5 to confirm.

  3. Color palette

    • Pick a primary that is NOT purple, NOT blue, NOT neon green by default. Generic crypto colors signal generic crypto product.
    • Use a 60-30-10 rule: 60% background, 30% surface, 10% accent.
    • Run the palette through a contrast checker (mentally or via reference). All text must hit 4.5:1 against its background.

  4. Typography

    • Headings: a serif or a distinctive sans (NOT default Inter, NOT default system-ui without intent).
    • Body: a high-readability sans at 16px or larger.
    • Mono: only if the product surfaces code or addresses to users; otherwise skip.

  5. Anti-generic check

    • Compare the chosen palette and type to references/anti-generic-checklist.md. If three or more "looks generic" markers fire, redo.

  6. Writeback

    • Write .suiperpower/brand.md.
    • Note the brand spec in .suiperpower/build-context.md so frontend skills pick it up.

Quality gate (anti-slop)

Before reporting done:

  • Does the name pass the "say it on a podcast" test (clear pronunciation, no spelling-out)?
  • Does the palette avoid the default crypto-purple-gradient look?
  • Does the type pairing have actual contrast in voice (not two near-identical sans-serifs)?
  • Does the brand spec name 2-3 anti-references the brand should NOT look like?
  • Did the user confirm, or did the skill assume?

If any answer is no, the skill iterates.

References

On-demand references (load when relevant to the user's question):

  • references/anti-generic-checklist.md: Markers that signal a generic crypto brand.
  • references/palette-recipes.md: Starting palettes by tone (serious, playful, technical, consumer).

Use in your agent

  • Claude Code: claude "/suiper:brand-design <your message>"
  • Codex: codex "/brand-design <your message>"
  • Grok Build: run grok, then /brand-design <your message> in the session
  • Cursor: paste a chat message that includes a phrase like "pick brand colors", or load ~/.cursor/rules/brand-design.mdc and reference it.

If you activated this and the user actually wants something else, consult skills/SKILL_ROUTER.md and hand off.

What ships with it: 3 files

4.5 KB alongside SKILL.md

agents/

references/

Gives 0 of the 12 instructions most marketing audience skills give in ~1.3k tokens

Counted across 690 of the 894 authors here whose files we hold, read 2026-08-07

  • Apply Poppins font to headingsin 41 of 690, across 6 files
  • Apply Lora font to body textin 41 of 690, across 6 files
  • Use Arial fallback for headingsin 39 of 690, across 4 files
  • Use Georgia fallback for body textin 39 of 690, across 4 files
  • Maintain text hierarchy and formattingin 39 of 690, across 4 files
  • Use accent colors for non-text shapesin 38 of 690, across 3 files
  • Use RGB values for precise color matchingin 38 of 690, across 3 files
  • Use brand colors for primary text and backgroundsin 36 of 690, across 1 file
  • Read product marketing context file before asking questions, starting, or auditingin 35 of 690, across 23 files
  • Use active voice instead of passive voicein 26 of 690, across 10 files
  • Implement or generate appropriate JSON-LD structured datain 24 of 690, across 17 files
  • Prioritize clarity over clevernessin 22 of 690, across 8 files

Said here and by no other author read

  • ask one sentence on product positioning
  • generate five name candidates
  • pick a non-default primary color
  • apply a 60-30-10 color rule
  • verify all text meets 4.5:1 contrast
  • choose distinctive typography pairings

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.