Alexander ef5f5ba0e6
fix(cli): install all 7 skills via uipro init, not just the orchestrator (#362) (#387)
* fix(cli): install all 7 skills via uipro init, not just the orchestrator

`uipro init` rendered only the orchestrator (ui-ux-pro-max) and never
delivered the 6 sibling skills (banner-design, brand, design,
design-system, slides, ui-styling), so users got 1 of 7 skills (#362).

- sync-assets.mjs: bundle the 6 sub-skills into cli/assets/skills/ as
  static copies (source of truth: .claude/skills/), with sync + check
  coverage. Excludes ui-styling/canvas-fonts (~5.8MB of TTF) and
  __pycache__/.pyc cruft — a skill registers from its SKILL.md, not its
  fonts — so the bundle adds ~0.9MB, not ~6.6MB.
- template.ts: after rendering the orchestrator, install each bundled
  sub-skill as a sibling. The skills parent is derived from the
  platform's skillPath (skills/ for most, prompts/ for copilot,
  steering/ for kiro) rather than hardcoded.
- uninstall.ts: remove the sub-skills too.

Verified: check:assets in sync, tsc passes, and a per-platform install
harness delivers all 7 skills to the correct parent dir with no fonts.

Closes #362

* fix(cli): filter excluded files from target side of check:assets

check:assets filtered sourceFiles with isExcludedAssetFile but not
targetFiles, so a stray cli/assets/scripts/__pycache__/*.pyc (generated
by a local Python run) was reported as an "extra asset file" and failed
the gate. Apply the same predicate to targetFiles in both the
dirsToSync and sub-skill loops.

Verified: check:assets now passes with __pycache__/*.pyc present in the
target tree; typecheck passes.

* fix(cli): uninstall from each platform's real skills dir, not hardcoded skills/

removeSkillDir() hardcoded <folder>/skills/<name>, but the installer
places skills under each platform config's skillPath parent — copilot in
.github/prompts/, kiro in .kiro/steering/. So uninstall left those
platforms' skills (orchestrator + sub-skills) behind.

Derive the install parent from loadPlatformConfig(aiType).folderStructure
(same source the installer uses), and keep the legacy <folder>/skills/
cleanup (incl. .shared/) for older installs. Deduped via a Set.

Verified: typecheck passes; an install+uninstall harness removes all 7
skills with zero leftovers for claude (.claude/skills), copilot
(.github/prompts) and kiro (.kiro/steering).

* fix(cli): re-sync bundled sub-skills after #385 stripped ckm- names

#385 merged to main and removed the ckm- prefix from the six
.claude/skills/*/SKILL.md name fields. This branch's bundled copies
under cli/assets/skills/ still carried the old ckm- names, so after the
PR merges with main the source no longer matched the bundle and the
check-asset-sync CI gate failed (stale asset file: skills/*/SKILL.md).

Merge main and regenerate the bundle so cli/assets/skills matches the
current .claude/skills source of truth. check:assets and typecheck pass.
2026-06-25 17:33:23 +07:00

2.0 KiB

Brand Voice Framework

Voice vs. Tone

Voice = Brand's personality (consistent) Tone = How voice adapts to context (variable)

Example: A friendly brand (voice) might be celebratory in a win announcement but empathetic in a support response (tone).

Voice Dimensions

Tone Spectrum

Formal ←――――――――――――――→ Casual
[Legal docs]     [Social media]

Language Spectrum

Simple ←――――――――――――――→ Complex
[Consumer]       [Technical B2B]

Character Spectrum

Serious ←――――――――――――――→ Playful
[Finance]        [Entertainment]

Emotion Spectrum

Reserved ←――――――――――――――→ Expressive
[Corporate]      [Lifestyle brand]

Voice Development Process

Step 1: Define Personality Traits

Choose 3-5 traits that describe your brand:

  • Confident, not arrogant
  • Friendly, not unprofessional
  • Knowledgeable, not condescending
  • Innovative, not gimmicky
  • Authentic, not casual

Step 2: Create Voice Chart

Trait Description Do Don't
[Trait] [Meaning] [Example] [Example]

Step 3: Context Adaptation

Context Tone Shift Example
Social media More casual "Hey there!"
Support More empathetic "We understand..."
Legal More formal "In accordance with..."
Sales More confident "You'll see results..."

Voice Testing

Ask these questions:

  1. Does this sound like our brand?
  2. Would a competitor say this?
  3. Does it resonate with our audience?
  4. Is it consistent with our values?

Voice Guide Template

## [Brand] Voice Guide

### We Are
- [Trait 1]: [Description]
- [Trait 2]: [Description]
- [Trait 3]: [Description]

### We Sound Like
[Example phrases]

### We Don't Sound Like
[Anti-examples]

### Sample Rewrites
Before: [Generic copy]
After: [Branded copy]