Menu
Pick a brand name, color palette, or typography for a Sui product. Use when the user wants to name or brand a Sui project.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Build an AI agent that signs Sui transactions or runs onchain actions. Use when the user wants an AI agent on Sui.
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.
Build a mobile Sui app with React Native or the Sui Mobile SDK. Use when the user wants iOS, Android, or mobile Sui flows.
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.
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.
Integrate Cetus AMM on Sui (swaps, liquidity, concentrated pools). Use when the user mentions Cetus.
| 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. |
# 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.
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.
If you activated this and the user actually wants something else, consult skills/SKILL_ROUTER.md and hand off.
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>
Pull positioning
.suiperpower/idea-context.md if present. If not, ask one sentence on what the product does and for whom.Name
Color palette
Typography
Anti-generic check
references/anti-generic-checklist.md. If three or more "looks generic" markers fire, redo.Writeback
.suiperpower/brand.md..suiperpower/build-context.md so frontend skills pick it up.Before reporting done:
If any answer is no, the skill iterates.
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).claude "/suiper:brand-design <your message>"codex "/brand-design <your message>"grok, then /brand-design <your message> in the session~/.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.