shipshitdev/brand-architect
bundles/branding/skills/brand-architect/SKILL.md
Use this skill when users need to develop brand strategy, choose a company name, define brand positioning, create brand voice, or build brand identity from day one. Activates for "what should I name it," "brand strategy," "positioning," or identity questions.
$ install --global
skillsauthnpx skillsauth add shipshitdev/library brand-architectInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 22, 2026, 4:41 AM190.1s3 files scanned
SKILL.md
- name:
- brand-architect
- description:
- Use this skill when users need to develop brand strategy, choose a company name, define brand positioning, create brand voice, or build brand identity from day one. Activates for "what should I name it," "brand strategy," "positioning," or identity questions.
- version:
- 1.0.0
- tags:
- business, hexa, brand, naming, positioning, voice, identity
Brand Architect - Day-One Brand Strategy
Overview
Help indie founders build brands that scale using Hexa's "Branding from Day One" methodology. Execute strategic brand development by guiding users through naming, positioning, voice, and visual identity foundations.
Hexa's Core Principle: "The name of your business should reflect not only your initial point of entry in the market but also where you aim to be in the future."
When This Activates
- "What should I name it"
- Brand name questions
- Brand positioning
- Brand voice definition
- Logo, colors, visual identity
- "How do I differentiate"
- Trademark considerations
The Framework: Brand Architecture Stack
┌─────────────────────────────────────────┐
│ BRAND IDENTITY │
│ (Logo, Colors, Typography) │
├─────────────────────────────────────────┤
│ BRAND VOICE │
│ (Tone, Language, Personality) │
├─────────────────────────────────────────┤
│ BRAND POSITIONING │
│ (Who, What, Why Different) │
├─────────────────────────────────────────┤
│ BRAND NAME │
│ (The Foundation) │
└─────────────────────────────────────────┘
Build from bottom up: Name → Positioning → Voice → Identity.
Naming Strategies
| Strategy | Description | Examples | Best For | |----------|-------------|----------|----------| | Descriptive | Clear category | Salesforce | B2B, SaaS | | Evocative | Emotional resonance | Nike, Apple | Aspirational | | Invented | New words | Spotify, Xerox | Tech, premium | | Compound | Join words | Facebook, YouTube | Clear value prop | | Portmanteau | Blend two words | Pinterest, Instagram | Apps, social | | Misspelling | Creative respelling | Lyft, Flickr | Startups, apps | | Suffix Pattern | Brand suffixes | Shopify, Grammarly | SaaS, tools | | Founder | Personal name | Bloomberg | Personal brand |
Popular Suffixes: -ify, -ly, -io, -hub, -ment, -able
Popular Prefixes: get-, try-, go-, my-, super-
Name Evaluation
Brandability Score (1-10 each)
- Memorability: Shorter = better
- Pronounceability: Vowel ratio, consonant clusters
- Spellability: Common patterns, no confusion
- Uniqueness: Distinctiveness in market
- Domain Available: .com bonus
Viability Score (1-5 each)
- Easy to spell/pronounce
- Memorable
- Domain available
- Trademark-able
- Works at scale
- International friendly
Minimum viability score: 35/50
Validation Checklist
- [ ] Easy to spell when heard
- [ ] Easy to pronounce when read
- [ ] No trademark conflicts
- [ ] No negative connotations in target markets
- [ ] Domain available (preferred TLD)
- [ ] Social handles available
Name Generation Workflow
- Gather context (industry, keywords, constraints)
- Generate 20-30 candidates using multiple strategies
- Score brandability + viability
- Check domain availability
- Recommend top 3-5 with rationale
Positioning Statement Template
For [target customer]
who [problem/need],
[Product Name] is a [category]
that [primary benefit].
Unlike [primary alternative],
we [key differentiator].
Brand Voice Framework
| Dimension | Spectrum | |-----------|----------| | Formal ↔ Casual | [Position] | | Serious ↔ Playful | [Position] | | Expert ↔ Approachable | [Position] |
Integration
copywriter- Brand-consistent copystartup-icp-definer- Define audiencemicro-landing-builder- Brand-aligned pages
For complete naming evaluation matrices, positioning maps, voice definition frameworks, visual identity guidelines, color psychology reference, and output templates, see: references/full-guide.md
Related Skills
shipshitdev/worktree
development
VerifiedTrustedCommunity
Create an isolated git worktree from the correct base branch and check it out into a clean, gitignored directory. Use when the user asks to make a worktree, spin up a parallel/isolated workspace, work on something without disturbing the current checkout, branch off the current work, or run multiple agents on the same repo at once. Picks the base branch smartly — the current feature branch when you are on one, otherwise the develop integration branch — so worktrees continue your in-progress work by default instead of forking from the wrong place.
27SKILL.mdUpdated Jun 13, 2026
shipshitdev/release-cleanup
development
VerifiedTrustedCommunity
Verify a release was fully promoted through develop, staging, and master/main, then prune merged local and remote branches and stale git worktrees. Squash-merge aware — uses GitHub PR merge state as the merge oracle, not commit ancestry. Use when the user asks to clean up branches after a deploy, prune worktrees, remove merged branches, tidy up after promoting develop to staging to master, or confirm nothing stale was left behind before pruning.
27SKILL.mdUpdated Jun 13, 2026
shipshitdev/finishing-a-development-branch
development
VerifiedTrustedCommunity
Structured "done coding, now what?" workflow: verify tests pass, detect the repository environment (normal repo vs worktree, named branch vs detached HEAD), present exactly the right merge / PR / keep / discard options, and execute the chosen path including safe worktree cleanup. Use when implementation is complete and the branch needs to be integrated, published, or abandoned.
27SKILL.mdUpdated Jun 13, 2026
shipshitdev/feature-intake
tools
VerifiedTrustedCommunity
Capture a client or stakeholder feature request, turn it into a planner-ready PRD epic with scoped sub-issues, check for duplicate work, and place approved issues on a GitHub Projects kanban. Use when a user invokes feature intake, asks to turn a rough client requirement into GitHub issues, or wants an idea written as a PRD and pushed to a board.
27SKILL.mdUpdated Jun 13, 2026