القائمة
Build the brand foundation — positioning, story, voice, naming, visual primitives — so every other launch asset (landing, content, outreach) sings the same song.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Slice a goal into the smallest feature slices that can each be PROVEN — every slice ships with a named eval and an end-to-end test, and a slice you can't evaluate or test doesn't get selected. Use after the goal is set and before the spec, so only provable features make the build.
Guided, stateful provisioning of a product's production stack — deep-links, key-format validation, a secrets backend (fnox recommended, or user-touched .env.local), a resumable ledger, CLI automation after signup, and a blocking A1–A10 live gate. Hands off to /security-check → /ship. The walked version of SETUP.md.
Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea.
Launch the factory's control plane — scaffold and fill FACTORY-ORDERS (weekly mandate + hard budget), STANDING-ORDERS (autonomous-program authority), HEARTBEAT (weekly pulse), and write lifecycle gates for every registered product. A deliberate one-time ritual (re-run to audit); invoke as /factory-launch, not auto-triggered.
One-shot a new product — folders, Next.js starter, product.config.json, CLAUDE.md, scope.md, PRD skeleton, SETUP.md checklist. The Lovable-like ignition.
Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.
استنادا إلى تصنيف SOC المهني
| name | brand-story-builder |
| description | Build the brand foundation — positioning, story, voice, naming, visual primitives — so every other launch asset (landing, content, outreach) sings the same song. |
| model_tier | opus |
Saved to products/<name>/launch/brand.md:
## Brand — <product>
### Positioning statement (the April Dunford structure)
For <target customer> who <statement of need>, <product name> is the <market category> that <key benefit>. Unlike <primary competitive alternative>, we <key differentiator>.
### Origin story (3 sentences)
<setup — the problem we kept seeing>
<turn — why no one was solving it well>
<commitment — what we're doing about it>
### Voice & tone
- We sound like: <3 adjectives> (e.g., direct, technical, irreverent)
- We don't sound like: <3 adjectives>
- Pet phrases we use: <list>
- Phrases we never use: <list of marketing-jargon we reject>
### Visual primitives
- Color palette: <primary + 2 accents + neutral>
- Typography: <heading font / body font, from `fontsource` or system stack>
- Logo direction: <wordmark | mark+wordmark | letter mark> + <one-line aesthetic>
- Imagery: <photo | illustration | abstract | none>
### Naming check
- Does the name pass: pronounceable, googleable, .com available, no trademark collision in adjacent space, doesn't mean something weird in 3+ languages
- Result: ✅ / ⚠️ / ❌
### Taglines (3 candidates ranked)
1. <tagline> — best for <where>
2. ...
3. ...
### Anti-positioning (what we are NOT)
3 things we explicitly say we don't do.
prd.md + scope.md + most-recent interview synthesis.brain/persona.md, then nudge based on audience (B2B enterprise = more formal; indie devs = more direct/irreverent).Per factory/playbooks/mvp-stage/agent-handoff-contracts.md:
products/<name>/launch/brand.md in the format above./competitor-research)./name-clearance before anything downstream uses the name.factory/playbooks/launch-stage/seo-content-strategy.md (for naming/SEO interaction)factory/playbooks/founders-wisdom/100k-arr-tactics.md