/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.
$ npx -y skills add pivyme/suiperpower --skill brand-design --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/brand-design
Context preview
The summary Claude sees to decide when to auto-load this skill.
Pick a brand name, color palette, or typography for a Sui product. Use when the user wants to name or brand a Sui project.
SKILL.md
brand-design.SKILL.mdname: brand-design
description: Pick a brand name, color palette, or typography for a Sui product. Use when the user wants to name or brand a Sui project.
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.
Read more
name: brand-design description: Pick a brand name, color palette, or typography for a Sui product. Use when the user wants to name or brand a Sui project.
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.
Build something meaningful, on Sui. A superpower for AI coding agents to ship real products on Sui. Your AI coding agent has never written Move before. Suiperpower fixes that.
Repo: pivyme/suiperpower
Other skills on suiperpower.
- /build-ai-agent
Build an AI agent that signs Sui transactions or runs onchain actions. Use when the user wants an AI agent on Sui.
Open skill - /build-data-pipeline
Build a Sui data indexer or analytics pipeline. Use when the user wants to index Sui events, build a pipeline, or query Sui RPC data.
Open skill - /build-mobile-sui
Build a mobile Sui app with React Native or the Sui Mobile SDK. Use when the user wants iOS, Android, or mobile Sui flows.
Open skill - /build-with-claude
Pair with a coding agent to build a Sui MVP step by step. Use when the user wants to build the MVP iteratively with an agent.
Open skill - /build-with-move
Author Sui Move modules and packages with a senior Move dev as your pair. Use when the user wants to write, build, author, add, or scaffold Move code, smart contracts, or Sui programs at the module or function level, in any phrasing.
Open skill - /cetus-swap
Integrate Cetus AMM on Sui (swaps, liquidity, concentrated pools). Use when the user mentions Cetus.
Open skill