mirror of https://github.com/nextlevelbuilder/ui-ux-pro-max-skill.git synced 2026-08-01 19:06:14 +00:00

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

1.7 KiB

Raw Permalink Blame History

Messaging Framework

Framework Structure

Mission (Why we exist)
    ↓
Vision (Where we're going)
    ↓
Value Proposition (What we offer)
    ↓
Positioning Statement (How we're different)
    ↓
Key Messages (What we say)
    ↓
Proof Points (Why to believe)

Core Statements

Mission Statement

We [action] for [audience] by [method] so they can [outcome].

Vision Statement

A world where [aspiration/change we want to see].

Value Proposition

For [target customer] who [need/problem],
[Product/Brand] is a [category]
that [key benefit].
Unlike [competitors],
we [unique differentiator].

Positioning Statement

[Brand] is the [category] for [audience]
who want [desired outcome]
because [reason to believe].

Message Architecture

Primary Message

One sentence that captures your core value.

Supporting Messages (3-5)

Each addresses a different benefit or audience need.

Message	Audience Need	Proof Point
[Message 1]	[Need]	[Evidence]
[Message 2]	[Need]	[Evidence]
[Message 3]	[Need]	[Evidence]

Elevator Pitches

10-second: [One sentence that sparks interest]

30-second: [Problem + solution + differentiation]

60-second: [Full pitch with proof points]

Message by Audience

Audience	Pain Point	Key Message	CTA
[Segment 1]	[Pain]	[Message]	[Action]
[Segment 2]	[Pain]	[Message]	[Action]

Message Testing

Is it clear? (No jargon)
Is it differentiated? (Competitors can't say it)
Is it credible? (Can we prove it)
Is it compelling? (Does audience care)
Is it consistent? (Aligns with brand)

1.7 KiB Raw Permalink Blame History