wizz-method 2.17.2 → 2.19.0

package/src/skills-lib/wizz-launch-readiness/references/03-seo-descoberta.md

@@ -1,16 +1,16 @@
 # Area 03 · SEO / Discoverability
 
-Checks whether the product CAN be found on launch day. This is not a ranking, traffic, or Core Web Vitals diagnosis (that's `wizz-seo-audit`), and when the surface is a SITE, it doesn't repeat the execution rounds (that's `site-launch-kit`, rounds 08 to 13): here it only confirms whether basic indexability exists.
+Checks whether the product CAN be found on launch day. This is not a ranking, traffic, or Core Web Vitals diagnosis (that's `wizz-seo-audit`), and when the surface is a SITE, it doesn't repeat the execution rounds (that's `wizz-site-launch-kit`, rounds 08 to 13): here it only confirms whether basic indexability exists.
 
 If the project has no indexable public web surface (e.g., mobile-only app, internal tool), respond `ITEM DOES NOT APPLY` with a 1-line justification and stop.
 
 ## Objective checks
 
-1. **`robots.txt` present and not blocking everything.** Missing is 🟠; present but blocking `Disallow: /` in production by mistake is 🔴. Point to `site-launch-kit` (round 13) as the fixer.
+1. **`robots.txt` present and not blocking everything.** Missing is 🟠; present but blocking `Disallow: /` in production by mistake is 🔴. Point to `wizz-site-launch-kit` (round 13) as the fixer.
 2. **Sitemap present and referenced in `robots.txt`.** Missing is 🟠.
-3. **Unique title and meta description on the main public pages.** A default/repeated title (e.g., the same title on every page) is 🟠. Point to `site-launch-kit` (round 08).
-4. **Open Graph configured.** Without `og:title`/`og:image`/`og:description`, the share preview (WhatsApp, social) comes out broken. It's 🟡, but escalates to 🟠 if the launch's main acquisition channel is social/WhatsApp. Point to `site-launch-kit` (round 09).
-5. **Basic structured business data.** Absence isn't a standalone blocker, but if the business depends on appearing in Google local/rich snippets, it's 🟡. Point to `site-launch-kit` (round 12) or `wizz-schema-markup`.
+3. **Unique title and meta description on the main public pages.** A default/repeated title (e.g., the same title on every page) is 🟠. Point to `wizz-site-launch-kit` (round 08).
+4. **Open Graph configured.** Without `og:title`/`og:image`/`og:description`, the share preview (WhatsApp, social) comes out broken. It's 🟡, but escalates to 🟠 if the launch's main acquisition channel is social/WhatsApp. Point to `wizz-site-launch-kit` (round 09).
+5. **Basic structured business data.** Absence isn't a standalone blocker, but if the business depends on appearing in Google local/rich snippets, it's 🟡. Point to `wizz-site-launch-kit` (round 12) or `wizz-schema-markup`.
 6. **Canonical and non-duplicated indexing.** Multiple URLs serving the same content without `rel=canonical` is 🟡.
 7. **Domain/DNS resolving to the right production environment.** A domain configured but pointing to the staging/preview environment is 🔴 (also an infra finding, see area 07; log only the discoverability part here: whether the search engine has already indexed the wrong domain).
 

package/src/skills-lib/wizz-launch-readiness/references/04-analytics-medicao.md

@@ -6,7 +6,7 @@ Checks whether the team will be able to KNOW if the launch worked. A launch with
 
 1. **Analytics tool installed and firing.** No GA4/pixel/equivalent tool loading on the public pages at all is 🔴 if the launch depends on measuring acquisition; 🟠 otherwise.
 2. **Main conversion event configured.** The event that represents the launch's goal (signup, purchase, lead, download) not firing or not existing is 🔴.
-3. **Thank-you/confirmation page event.** A post-conversion page with no "confirmed conversion" event (distinct from just "visited the page") is 🟠. Overlaps with `site-launch-kit` round 15 when the surface is a site.
+3. **Thank-you/confirmation page event.** A post-conversion page with no "confirmed conversion" event (distinct from just "visited the page") is 🟠. Overlaps with `wizz-site-launch-kit` round 15 when the surface is a site.
 4. **Trackable traffic source/UTM.** Launch campaigns without standardized UTM is 🟡: it measures what happened, but not where it came from.
 5. **Production error monitoring (Sentry or equivalent).** A project that already uses an error tool but it's not active in the production environment is 🟠. A project that never adopted one at all is 🟡 (not a recommendation to adopt Sentry now, just logging a gap: the adoption decision belongs to the team).
 6. **Downtime/uptime alert.** No alert configured for when the product goes down on launch day (when traffic is most sensitive) is 🟠.

package/src/skills-lib/wizz-launch-readiness/references/05-conteudo-prova-social.md

@@ -1,20 +1,20 @@
 # Area 05 · Content / Copy / Social Proof
 
-Checks whether what is written and shown is REAL and ready — not whether the copy is good (that's `wizz-copywriting`/`wizz-copy-editing`). Central rule, inherited from `site-launch-kit`: no invented business data passes as compliant. Whatever is missing becomes a PENDING ITEM, never a guess filled in by estimation.
+Checks whether what is written and shown is REAL and ready — not whether the copy is good (that's `wizz-copywriting`/`wizz-copy-editing`). Central rule, inherited from `wizz-site-launch-kit`: no invented business data passes as compliant. Whatever is missing becomes a PENDING ITEM, never a guess filled in by estimation.
 
 ## Objective checks
 
 1. **Placeholder text in production.** `Lorem ipsum`, `TODO`, `[insert here]`, `{{LIKE THIS}}`, or any visible marker on a page/screen that's going live is 🔴.
-2. **Real social proof.** A testimonial, rating, or client logo without a verifiable source (a generic name like "Satisfied customer", a rating with no origin, a company logo that isn't actually a client) is 🔴: fake social proof is a reputational and sometimes legal risk. Point to `site-launch-kit` (round 04) when the surface is a site.
+2. **Real social proof.** A testimonial, rating, or client logo without a verifiable source (a generic name like "Satisfied customer", a rating with no origin, a company logo that isn't actually a client) is 🔴: fake social proof is a reputational and sometimes legal risk. Point to `wizz-site-launch-kit` (round 04) when the surface is a site.
 3. **Current price, timeline, contact info.** A price/plan/phone/email/hours that diverges from what the business actually does is 🔴. Don't validate this "by estimate": if you have no way to confirm the real data, mark it PENDING and ask — never accept what's already written as correct by default.
-4. **Real image vs. generic stock.** A generic stock photo in a context that should be authentic (team, product, location) is 🟡, escalating to 🟠 if the sector depends on visual trust (health, in-person service, financial). Point to `site-launch-kit` (round 06).
+4. **Real image vs. generic stock.** A generic stock photo in a context that should be authentic (team, product, location) is 🟡, escalating to 🟠 if the sector depends on visual trust (health, in-person service, financial). Point to `wizz-site-launch-kit` (round 06).
 5. **Product/brand name consistency.** The product name spelled differently across pages (e.g., "MeJu" vs. "Me Ju" vs. "meju") is 🟡.
-6. **Main CTA and message present and clear.** No main CTA above the fold on the landing page is 🔴 when the launch's goal depends on direct conversion. Point to `site-launch-kit` (round 01).
-7. **FAQ or objection-handling content ready for expected volume.** No FAQ when the product has a known recurring objection is 🟡. Point to `site-launch-kit` (round 05) or `wizz-copywriting`.
+6. **Main CTA and message present and clear.** No main CTA above the fold on the landing page is 🔴 when the launch's goal depends on direct conversion. Point to `wizz-site-launch-kit` (round 01).
+7. **FAQ or objection-handling content ready for expected volume.** No FAQ when the product has a known recurring objection is 🟡. Point to `wizz-site-launch-kit` (round 05) or `wizz-copywriting`.
 
 ## Cutoff rule
 
-Never fill in missing business data "to unblock the diagnosis". If it can't be confirmed (price, testimonial, address, timeline), the item becomes PENDING with "who to get it from / how to get it", same as `site-launch-kit`. Marking 🟢 without checking the real content is worse than marking PENDING.
+Never fill in missing business data "to unblock the diagnosis". If it can't be confirmed (price, testimonial, address, timeline), the item becomes PENDING with "who to get it from / how to get it", same as `wizz-site-launch-kit`. Marking 🟢 without checking the real content is worse than marking PENDING.
 
 ## Output format
 

package/src/skills-lib/wizz-launch-readiness/references/06-legal-lgpd.md

@@ -4,7 +4,7 @@ Checks basic legal exposure before launch. This isn't a legal opinion (that requ
 
 ## Objective checks
 
-1. **Privacy policy exists and is accessible.** Total absence, in a product that collects personal data (signup, form, analytics cookie), is 🔴. Point to `site-launch-kit` (round 14) when the surface is a site.
+1. **Privacy policy exists and is accessible.** Total absence, in a product that collects personal data (signup, form, analytics cookie), is 🔴. Point to `wizz-site-launch-kit` (round 14) when the surface is a site.
 2. **Privacy policy matches what the product actually does.** A generic copied document that doesn't reflect the real app (e.g., mentions data that isn't collected, or omits data that is) is 🔴: an incorrect policy is worse than none, because it creates a false legal commitment. Read the content, don't just confirm the file exists.
 3. **Terms of use present when there's a transaction or user account.** Absence is 🟠.
 4. **Cookie/tracking consent implemented when there's a non-essential cookie.** Analytics/pixel firing with no cookie notice at all is 🟠.

package/src/skills-lib/wizz-launch-readiness/references/08-fusao-priorizacao.md

@@ -7,7 +7,7 @@ Takes the 7 tables from the areas (01 to 07) and merges them into a single diagn
 1. **Paste the 7 tables** (or whichever ran, if any was marked `ITEM DOES NOT APPLY`).
 2. **Dedup by cross-origin.** The same problem can show up in two areas (e.g., a domain pointing to the wrong environment appears in area 03 and area 07). Keep a single row, citing both source areas.
 3. **Sort by severity first** (🔴 at the top, 🟢 at the bottom), and within the same severity, by estimated fix effort (lowest effort first): resolve first whatever is closest to go-live.
-4. **Group by fix owner.** Several 🔴 findings going to the same owner (e.g., 3 findings for `site-launch-kit`) form a single block in the delivery, to become a single dispatch.
+4. **Group by fix owner.** Several 🔴 findings going to the same owner (e.g., 3 findings for `wizz-site-launch-kit`) form a single block in the delivery, to become a single dispatch.
 5. **Count pending items separately.** MANUAL VERIFICATION PENDING is not a severity: it's "can't be known yet". List it separately, with what's needed to turn it into a real verdict.
 
 ## Final table

package/src/skills-lib/wizz-offer-forge/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wizz-offer-forge
-description: Forges irresistible direct-response and info-product offers by integrating a unique mechanism, offer thesis, value stacking, reverse guarantee, price anchoring, and a creative matrix for paid traffic. Use when the user wants to create a new offer from scratch, restructure an existing offer that isn't converting, stack high-perception bonuses, define an aggressive guarantee, or translate audience research (Piva/VoC) into a sales machine. Do NOT use for raw audience research (use pesquisa-de-publico-do-piva) or final page copywriting (use wizz-copywriting).
+description: Forges irresistible direct-response and info-product offers by integrating a unique mechanism, offer thesis, value stacking, reverse guarantee, price anchoring, and a creative matrix for paid traffic. Use when the user wants to create a new offer from scratch, restructure an existing offer that isn't converting, stack high-perception bonuses, define an aggressive guarantee, or translate audience research (Piva/VoC) into a sales machine. Do NOT use for raw audience research (use wizz-pesquisa-de-publico-do-piva) or final page copywriting (use wizz-copywriting).
 ---
 
 # Wizz Offer Forge
@@ -31,10 +31,10 @@ A master artifact `OFFER-SPEC.md` containing:
 
 **Before asking anything, read what already exists.** A good offer is born from the result of the previous one, not from a blank page.
 
-If the `cerebro` skill is installed, run `/cerebro ver` for the project and grep by theme in `_decisions/`. Look specifically for: a previous offer to the same audience, a price already tested, a guarantee already used, and any logged decision that forbids a certain path. Bring back what you found as input and state in your reply where it came from. Without the skill installed, skip this block and proceed with the questions below.
+If the `wizz-cerebro` skill is installed, run `/wizz-cerebro ver` for the project and grep by theme in `_decisions/`. Look specifically for: a previous offer to the same audience, a price already tested, a guarantee already used, and any logged decision that forbids a certain path. Bring back what you found as input and state in your reply where it came from. Without the skill installed, skip this block and proceed with the questions below.
 
 Then, consult existing context or ask the user:
-1. **Prior Audience Research:** Is there a report from the `pesquisa-de-publico-do-piva` skill or VoC notes? If so, import it as primary input. If not, define the Avatar, Latent Pain, and initial Awareness Level.
+1. **Prior Audience Research:** Is there a report from the `wizz-pesquisa-de-publico-do-piva` skill or VoC notes? If so, import it as primary input. If not, define the Avatar, Latent Pain, and initial Awareness Level.
 2. **Business Model:** Low-ticket (R$ 10 to R$ 97), Mid front-end (R$ 197 to R$ 497), or High-ticket / Mentorship (R$ 1,000 to R$ 10,000+)?
 3. **Delivery Vehicle:** Recorded course, community, templates/tools, live mentorship, SaaS, or hybrid?
 

package/src/skills-lib/{pesquisa-de-publico-do-piva → wizz-pesquisa-de-publico-do-piva}/README.md

@@ -42,7 +42,7 @@ Unzip the `pesquisa-de-publico-do-piva/` folder into `~/.claude/skills/` (to use
 Open a conversation, attach your offer document (`.docx`, `.pdf`, `.md` or `.txt`) and write:
 
 ```
-/pesquisa-de-publico-do-piva
+/wizz-pesquisa-de-publico-do-piva
 ```
 
 Or, without the slash, anything in that spirit:

package/src/skills-lib/{pesquisa-de-publico-do-piva → wizz-pesquisa-de-publico-do-piva}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: pesquisa-de-publico-do-piva
+name: wizz-pesquisa-de-publico-do-piva
 description: Generates a complete audience research arsenal for an infoproduct offer and paid traffic, from an offer document (.docx/.md/.txt/.pdf). Produces six chained reports — VoC, Schwartz Psychographic Profile, Levels of Awareness, Trend Report, Angle Matrix and Lexicon — compiled into a tab-navigable HTML dashboard. Use when the user sends an offer and asks for audience research, VoC, voice of customer, angle matrix, audience lexicon, persona pain points, or a copy arsenal for direct traffic. Do NOT use for technical research on libraries/code (use context7), broad B2B market research (use deep-research), or visual UI research (use wizz-premium-landing-ui-researcher). Methodology by @soupiva.
 ---
 

package/src/skills-lib/wizz-router/SKILL.md

@@ -20,7 +20,7 @@ You are the **Director / entry point** — not the orchestrator (that's `wizz-ma
 
 **Installation scope note:** this is the only skill in the catalog where **global** installation (`~/.claude/skills/wizz-router`) is the operationally correct default, not an exception to the "prefer local" rule (`skills-registry.yaml`, Installation Doctrine, rule 1) — its reason for existing is to route even outside a Wizz project. It stays in sync with the global `wizz-router-enforce.js` hook via `npm run sync:global`.
 
-**Token economy:** the `rtk-rewrite.sh` hook already handles RTK automatically (don't run `rtk --version` on every routing). Before reading raw files, prefer `/cerebro ver` or a specific `grep`.
+**Token economy:** the `rtk-rewrite.sh` hook already handles RTK automatically (don't run `rtk --version` on every routing). Before reading raw files, prefer `/wizz-cerebro ver` or a specific `grep`.
 
 ## Triage and delegation (the Director's core job)
 
@@ -72,7 +72,7 @@ This gate does NOT fire for an open-scope request. "My site is bad, sort it out"
 
 **The counterpart, and this is what is left for the maestro:** a request **of open scope, which the request itself does not delimit** — "how do I improve the signup conversion rate", "the sales page gets plenty of visits and almost nobody buys", "my sales page converts badly, improve it". There the scope has to be discovered before anything is delivered, and discovering scope is the Manager's work. The deciding difference is not the size of the request, it is whether **the request already states what the delivery is**.
 
-**And the counterpart has one exception: a single entry already delimits the scope.** If the whole outcome being asked for fits the `when:` of ONE catalogue entry, and what leaves at the end is that entry's own deliverable — a plan, a recommendation, an audit — then the scope is not open, the catalogue delimited it, and the request goes to that entry's area. "A plan to reduce churn" is `wizz-churn-prevention`; "I want ChatGPT and Perplexity to cite us" is `wizz-ai-seo`; "what to check before going live" is `site-launch-kit`. It stops being the exception the moment delivering the outcome means changing what other areas own: "improve the signup conversion rate" ends up in copy, UI and code, so it comes back to the maestro through the area clause. Ask which single entry would deliver it whole — if it takes two, the scope really is open. (Owner's decision, 2026-09-18.)
+**And the counterpart has one exception: a single entry already delimits the scope.** If the whole outcome being asked for fits the `when:` of ONE catalogue entry, and what leaves at the end is that entry's own deliverable — a plan, a recommendation, an audit — then the scope is not open, the catalogue delimited it, and the request goes to that entry's area. "A plan to reduce churn" is `wizz-churn-prevention`; "I want ChatGPT and Perplexity to cite us" is `wizz-ai-seo`; "what to check before going live" is `wizz-site-launch-kit`. It stops being the exception the moment delivering the outcome means changing what other areas own: "improve the signup conversion rate" ends up in copy, UI and code, so it comes back to the maestro through the area clause. Ask which single entry would deliver it whole — if it takes two, the scope really is open. (Owner's decision, 2026-09-18.)
 
 **Changing the product's code is `dev`, even when the subject is visual.** "Adjust the secondary button's colour", "fix the mobile spacing": the delivery is a commit, so it is the dev area — `designer` decides what the look should be, it does not ship the change. Ask which artifact leaves at the end: a file in the repo → dev; a decision, a spec or a piece of art → the area that owns it. **Exception: new or rebuilt screens.** When the request asks to BUILD screens in code (a new app, page, dashboard or panel, or a whole screen rebuilt in the product), the visual decision has not been made yet, so `designer` comes first and the sequence is design → dev (2 areas → maestro): the designer runs its research gate before any screen is coded. A tweak to an existing screen (a price, a label, a spacing) stays dev, and redesigning a section with no build asked for (a hero, a card) stays designer.
 
@@ -105,4 +105,4 @@ When detecting "auditoria completa / revisa tudo / 360 / análise geral", follow
 
 ## Memory Duty (at the end)
 
-After non-obvious bugs, architecture decisions, gotchas, or user corrections: record them in the project's `CLAUDE.md` ("Learnings" section) and in Cerebro (`/cerebro decisao` or `/cerebro salvar`). Remind the user if relevant.
+After non-obvious bugs, architecture decisions, gotchas, or user corrections: record them in the project's `CLAUDE.md` ("Learnings" section) and in Cerebro (`/wizz-cerebro decisao` or `/wizz-cerebro salvar`). Remind the user if relevant.

package/src/skills-lib/wizz-router/references/routing-table-flat.md

@@ -2,7 +2,7 @@
 
 Use this table to map skills/CLIs/MCPs directly **outside a Wizz project** (no `_wizz/`) — there the router fires the skill on its own. **Inside a Wizz project** it can also be consulted as a CAPABILITY INDEX, to discover a relevant capability the user didn't name (e.g. "I want a carousel" → `wizz-canvas-design`); but delegation still happens through the normal SKILL.md dispatch (area agent / maestro) — the table never fires a skill directly inside a Wizz project.
 
-**Existence check:** before offering any skill, confirm it exists in the environment (the session's skill catalog or `ls ~/.claude/skills`); if it doesn't exist, don't offer it: use the missing-skill protocol (`find-skills`).
+**Existence check:** before offering any skill, confirm it exists in the environment (the session's skill catalog or `ls ~/.claude/skills`); if it doesn't exist, don't offer it: use the missing-skill protocol (`wizz-find-skills`).
 
 ## Technical Area — Backend / Data / Infra
 
@@ -15,8 +15,8 @@ Use this table to map skills/CLIs/MCPs directly **outside a Wizz project** (no `
 | Auth, secrets, tokens, OAuth, JWT, Clerk, permissions | `wizz-auth-and-secrets` + `wizz-web-security` | 1 |
 | Dependencies, packages, vulnerabilities, npm audit | `wizz-database-and-deps` | 2 |
 | Security, XSS, CSRF, SQLi, IDOR, OWASP, rate limit, CORS, clickjacking, PII in the response, user enumeration, headers | `wizz-web-security` + `wizz-auth-and-secrets` | 1 |
-| Full-app security audit/pentest, "audit security", "pentest", "find vulnerabilities", pre-release scan | `security-audit-pentest` | 1 |
-| **Autonomous, offensive** pentest that actually runs the app and proves each finding with a real PoC | CLI `strix` (qa registry). CONDITIONAL, never the default: only on an app the user owns/is authorized to test, and only when they ask for validated exploitation rather than a review. Start from `security-audit-pentest` | 2 |
+| Full-app security audit/pentest, "audit security", "pentest", "find vulnerabilities", pre-release scan | `wizz-security-audit-pentest` | 1 |
+| **Autonomous, offensive** pentest that actually runs the app and proves each finding with a real PoC | CLI `strix` (qa registry). CONDITIONAL, never the default: only on an app the user owns/is authorized to test, and only when they ask for validated exploitation rather than a review. Start from `wizz-security-audit-pentest` | 2 |
 | Error monitoring, crash/exception triage, releases and source maps in Sentry | CLI `sentry-cli` (architect registry). CONDITIONAL: only if the project ALREADY uses Sentry (`SENTRY_DSN` in env, `sentry.properties`, or `@sentry/` in package.json) and it's at production stage — never propose adopting Sentry from this row | 2 |
 | Launch-readiness audit, "is it ready to launch?", broad release checklist (technical, security, SEO, analytics, content, legal, infra), "what's missing before going to production" | `wizz-launch-readiness` | 1 |
 | Desktop, Electron, contextIsolation, code signing | `wizz-desktop-security` | 2 |
@@ -54,8 +54,8 @@ Use this table to map skills/CLIs/MCPs directly **outside a Wizz project** (no `
 | Generate an image via code: carousel, quote card, infographic (editable PNG/PDF), generative hero background/texture | `wizz-canvas-design` + `wizz-algorithmic-art` | 2 |
 | **Video with audio, narration, SFX, or synced captions** (film assembly) | `wizz-remotion-best-practices` (Remotion assembles; frame timing). Pipeline rule: HyperFrames draws the mute screens, Remotion assembles the film — don't use hyperframes to position audio/captions (~2.76s drift and CSS leaking between screens in production) | 1 |
 | Draw a video SCREEN/scene in HTML/CSS, mute visual (app mockup, animated chart, title, loop; HTML→MP4) | CLI `hyperframes` (designer registry; `npx skills add heygen-com/hyperframes`) — mute screens only; assembly with audio goes to Remotion (line above) | 2 |
-| Word-by-word timestamps for TTS narration (sync captions/cuts/animation with speech) | `ctc-align` (designer registry; single source of timing, replaces Whisper) | 2 |
-| Which short-video STYLE to copy, from the inventory of the material (real person, voice only, B-roll, screens, product), with the recipe measured on 99 real shorts; "edit it in the style of", "the video looks amateur" | `wizz-video-styles` (designer registry; picks the style before voice, timing, effects and assembly) | 2 |
+| Word-by-word timestamps for TTS narration (sync captions/cuts/animation with speech) | `wizz-ctc-align` (designer registry; single source of timing, replaces Whisper) | 2 |
+| Which short-video STYLE to copy, from the inventory of the material (real person, voice only, B-roll, screens, product), with the recipe measured on 110 real videos (lyric video, kinetic typography and the UI-only app video "ui-morph" included); "a video of my app moving", "edit it in the style of", "the video looks amateur" | `wizz-video-styles` (designer registry; picks the style before voice, timing, effects and assembly) | 2 |
 | Effects and sound of a short vertical video (ad or Reels): which effect goes where and when not, which SFX for each event and at what level, ducking, master loudness, safe-zone/density/excess/rhythm gates | `wizz-video-effects` (designer registry; decides the effects, Remotion assembles them) | 2 |
 | **Find B-roll / inserts / cutaways / supporting footage** for a video or Reel (real footage of the fact, person, product, news item or screen the script names; YouTube/Instagram/TikTok/Pexels/Pixabay/Commons/NASA) | CLI `get-brolls` (designer registry; **macOS**, global `skills add` + its own `install.sh`; needs ffmpeg with drawtext, Node 22+, Python 3.11+). Ends in a Storyboard the HUMAN approves — the agent never self-approves. Stock only when the user explicitly asks for stock | 1 |
 | **Edit/cut video** (cuts, selects, roughcut) | CLI `buttercut` (designer registry; **Apple Silicon only**, clone-and-run in the project, heavy deps) | 1 |
@@ -72,7 +72,7 @@ Use this table to map skills/CLIs/MCPs directly **outside a Wizz project** (no `
 | Paid ads, ads, Google Ads, Meta Ads, TikTok Ads, paid media | `wizz-paid-ads` + `wizz-ad-creative` + `wizz-analytics-tracking` | 1 |
 | Wrong pixel/UTM/attribution, "sales don't match the ads manager", "where is the funnel leaking", inflated organic traffic, checking tracking before launching a campaign | `wizz-tracking-audit` (+ `wizz-analytics-tracking` if it's a SaaS/product) | 1 |
 | Feature launch, product launch, go-to-market | `wizz-launch-strategy` + `wizz-social-content` + `wizz-email-sequence` | 1 |
-| Site ready to go live, SITE pre-launch, "review before deploy", go-live checklist, or a specific pre-launch item (og:image/link preview, FAQ with schema, robots.txt, LGPD, alt text) | `site-launch-kit` | 1 |
+| Site ready to go live, SITE pre-launch, "review before deploy", go-live checklist, or a specific pre-launch item (og:image/link preview, FAQ with schema, robots.txt, LGPD, alt text) | `wizz-site-launch-kit` | 1 |
 | Price, plans, pricing, monetization | `wizz-pricing-strategy` + `wizz-paywall-upgrade-cro` | 1 |
 | Churn, retention, cancellation, NPS | `wizz-churn-prevention` + `wizz-revops` | 1 |
 | Page conversion, CRO, funnel optimization | `wizz-page-cro` + `wizz-copywriting` + `wizz-form-cro` | 1 |
@@ -84,6 +84,8 @@ Use this table to map skills/CLIs/MCPs directly **outside a Wizz project** (no `
 | EXECUTE the SEO distribution: publish articles, build backlinks through the Distribb network, connect Search Console, autopublish news | CLI `distribb` (seo registry) — the doing half; the strategy half is the SEO row above | 2 |
 | Competitor comparison, alternatives page, war room | `wizz-competitor-alternatives` | 2 |
 | Content, social media, newsletter, threads | `wizz-content-strategy` + `wizz-social-content` + `wizz-copy-editing` | 2 |
+| Tear down ONE viral Instagram post (Reel, carousel, caption) from its link: why it worked, which hook, a mould to do one like it | `wizz-hook-extractor` (social registry; reads the post itself) | 2 |
+| Audit and rewrite an Instagram PROFILE: bio, search NAME, link, highlights, pinned posts | `wizz-ig-profile-optimizer` (social registry) | 2 |
 | Actually PUBLISH/schedule to social networks (Instagram, TikTok, YouTube, LinkedIn and more), not write it | CLI `buffer` (social registry; needs `BUFFER_API_KEY`; media must be a public HTTPS URL). Separates "generate" (Wizz skills above) from "publish" | 2 |
 | Cold email, B2B outbound, prospecting | `wizz-cold-email` | 2 |
 | Referral, referrals, affiliate program | `wizz-referral-program` | 2 |
@@ -91,7 +93,7 @@ Use this table to map skills/CLIs/MCPs directly **outside a Wizz project** (no `
 | Free lead-capture tool | `wizz-free-tool-strategy` | 2 |
 | A/B test, variations, conversion experiments | `wizz-ab-test-setup` + `wizz-analytics-tracking` | 2 |
 | Copywriting, copy, persuasion, sales text | `wizz-copywriting` + `wizz-humanizer` | 1 |
-| Offer audience research, VoC, angle matrix, info-product lexicon | `pesquisa-de-publico-do-piva` | 1 |
+| Offer audience research, VoC, angle matrix, info-product lexicon | `wizz-pesquisa-de-publico-do-piva` | 1 |
 | Forge an offer, create an irresistible offer, unique mechanism, bonus, guarantee | `wizz-offer-forge` + `wizz-pricing-strategy` | 1 |
 | Market research, competitive intelligence | `deep-research` (external plugin — only if installed) | 2 |
 | Scrape/crawl the web for market research, lead prospecting or competitive intel (anti-bot bypass, adaptive parsing) | MCP `scrapling` (growth registry) — the collection layer under the research rows above | 2 |
@@ -100,7 +102,7 @@ Use this table to map skills/CLIs/MCPs directly **outside a Wizz project** (no `
 
 | Intent / keywords | Skills to offer | Priority |
 |---|---|---|
-| What was decided, past context, learnings, history | `cerebro` (/ver or /dia) | 1 |
+| What was decided, past context, learnings, history | `wizz-cerebro` (/ver or /dia) | 1 |
 
 ---
 
@@ -108,7 +110,7 @@ Use this table to map skills/CLIs/MCPs directly **outside a Wizz project** (no `
 
 When no installed skill/MCP covers the request, **classify what's missing** (skill = knowledge/flow; MCP = real access to a tool/API):
 
-**Missing a SKILL:** inform → invoke `find-skills` → `npx skills find "<term>"` → present 2-3 candidates with source → propose `npx skills add <pkg>` with confirmation → route again. Sources: anthropics/skills, superpowers-marketplace, skill-codex, claude-mem, skills.sh. **Review the SKILL.md and any `scripts/` before installing; prefer known owners.**
+**Missing a SKILL:** inform → invoke `wizz-find-skills` → `npx skills find "<term>"` → present 2-3 candidates with source → propose `npx skills add <pkg>` with confirmation → route again. Sources: anthropics/skills, superpowers-marketplace, skill-codex, claude-mem, skills.sh. **Review the SKILL.md and any `scripts/` before installing; prefer known owners.**
 
 **Missing an MCP:** inform → `claude mcp list` → check `skills-registry.yaml` (`mcps:`/`mcp_utility:`, with a ready `server`) → propose `claude mcp add <id> [-e VAR=$VAR] -- <command> [args]`. Secrets always via env/placeholder, never a real token.
 

package/src/skills-lib/{security-audit-pentest → wizz-security-audit-pentest}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: security-audit-pentest
+name: wizz-security-audit-pentest
 description: >
   Adversarial 5-stage security audit with standardized output (markdown table, cutoff ruler,
   concrete payload per finding). Use when the request is to audit/pentest an entire app, review security

package/src/skills-lib/{site-launch-kit → wizz-site-launch-kit}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: site-launch-kit
+name: wizz-site-launch-kit
 description: "Operational pre-launch website checklist in 15 corrective rounds: main CTA above the fold, mobile sticky bar, response-time promise, real social proof, decision-focused FAQ with FAQPage, real images (not stock), address and directions, unique titles, Open Graph, breadcrumbs, alt text, local business schema, robots/sitemap, LGPD privacy policy and terms, event measurement. Use when the site is ready or nearly ready to go live: 'vamos lançar', 'subir o site', 'revisar antes do deploy', 'checklist de lançamento', 'pré-go-live', 'o site tá pronto?', or when the request is one of the individual items (e.g. 'arruma a prévia do WhatsApp', 'coloca FAQ com schema', 'confere robots.txt antes de subir'). Runs AFTER the site is built and BEFORE deploy. Central rule: no invented business data goes into the site; whatever is missing becomes a placeholder and goes into PENDING ITEMS."
 ---
 

package/src/skills-lib/wizz-video-effects/SKILL.md

@@ -9,7 +9,8 @@ A catalogue of effects is easy. What makes a video look professional is the **re
 
 ## Where it sits in the video pipeline
 
-1. Script and narration exist; `ctc-align` gave word-by-word timestamps.
+1. Script and narration exist; `wizz-ctc-align` gave word-by-word timestamps.
+   On a music-driven piece (lyric video over a song) the song is the narration: `scenes[]` start on the downbeats from `wizz-video-styles/scripts/beat_grid.py`, and the song's own hits count as the SFX budget already spent.
 2. Screens were drawn silent (HyperFrames) or footage was sourced.
 3. **This skill:** events → SFX and levels → effects anchored on breaths → budget → timeline JSON → (render in Remotion) → gates on the final MP4.
 4. Remotion assembles from the timeline JSON. For the `<Audio>` and `<Sequence>` API, invoke the `wizz-remotion-best-practices` skill.
@@ -38,7 +39,7 @@ Requires Python 3 (stdlib only) and ffmpeg/ffprobe.
 
 ## Per piece
 
-1. **Timeline.** Write the piece's timeline JSON ([references/data-contract.md](references/data-contract.md)): `words[]` from ctc-align, `scenes[]`, `elements[]`, and the safe-zone profile (`ad` or `organic`).
+1. **Timeline.** Write the piece's timeline JSON ([references/data-contract.md](references/data-contract.md)): `words[]` from wizz-ctc-align, `scenes[]`, `elements[]`, and the safe-zone profile (`ad` or `organic`).
 2. **Events to sounds.** List what happens in the narration as semantic events with their times, from the words: a price appears, a verdict lands, a message arrives. Map them with `res = sound.map_requests([(5.4, "verdict"), (7.1, "element_in")], cfg)` from `scripts/sound.py`; it returns the shots (file and `vol` from the config) plus the refusals, with the reason. Write the accepted shots into `sfx[]` with their `event`. Events that trigger an effect (a `verdict` triggers `shake`): pass `sound.effect_candidates(res)` through `budget.select(...)` from `scripts/budget.py` and write the accepted ones into `shakes[]`; no other step writes them.
 3. **Effects on breaths.** `python3 scripts/fill_breaths.py TIMELINE --narration NARRATION.mp3 --visual LAYOUT_RENDER.mp4 --write` anchors punches and flashes on real speech breaths, runs every candidate through the budget, and sets scene transitions and cut sounds by speech pace. Without `--write` it only reports.
    - `--narration` is required in practice: ctc-align words touch each other (each ends where the next starts), so `words[]` alone yields almost no breaths.
@@ -80,6 +81,6 @@ Full table, what each gate cannot see, and escape hatches: [references/gates.md]
 
 - Assembling the film, captions layout, `<Audio>` API: `wizz-remotion-best-practices`.
 - Drawing screens: HyperFrames.
-- Word timestamps: `ctc-align`.
+- Word timestamps: `wizz-ctc-align`.
 - Script, hook wording and CTA wording: the copy or social area.
 - Launch films with music and art direction: `wizz-huashu-design`.

package/src/skills-lib/wizz-video-effects/references/data-contract.md

@@ -1,6 +1,6 @@
 # Timeline data contract
 
-The scripts in `scripts/` read and write one JSON object per piece: the **timeline**. It is the hand-off between whoever plans the edit (HyperFrames screens, `ctc-align` timing) and whoever renders the audio and effects (Remotion). Times are always **seconds from the start of the piece**, as floats. Every list is optional: an absent list is an empty list, never an error.
+The scripts in `scripts/` read and write one JSON object per piece: the **timeline**. It is the hand-off between whoever plans the edit (HyperFrames screens, `wizz-ctc-align` timing) and whoever renders the audio and effects (Remotion). Times are always **seconds from the start of the piece**, as floats. Every list is optional: an absent list is an empty list, never an error.
 
 Numbers that decide anything (gaps, ceilings, depths) are never in the timeline: they live in `effects.config.json` and are cited by key.
 
@@ -11,7 +11,7 @@ Numbers that decide anything (gaps, ceilings, depths) are never in the timeline:
 | `fps` | int | `sound.py duck` | planner | render fps; default `frame.fps` of the config |
 | `duration` | float | every check | planner | piece length; if absent, derived from the largest scene end (reports say so) |
 | `safe_zone_profile` | string | `check_safe_zone.py`, `measure_density.py`, `fill_breaths.py` | planner | `organic` or `ad` (any key of `safe_zones`); overrides the config default for this piece |
-| `words[]` | list | `sound.py duck`, `fill_breaths.py` | `ctc-align` | spoken words |
+| `words[]` | list | `sound.py duck`, `fill_breaths.py` | `wizz-ctc-align` | spoken words |
 | `scenes[]` | list | `check_excess.py`, `check_rhythm.py`, `fill_breaths.py` | planner, `fill_breaths.py` | screens |
 | `sfx[]` | list | `sound.py duck`, `fill_breaths.py` | planner, `fill_breaths.py` | point sounds |
 | `punches[]` | list | `check_excess.py`, `check_rhythm.py` | planner, `fill_breaths.py` | zoom punches |
@@ -40,7 +40,7 @@ Only `start` and `end` are required. Breaths are the gaps between words at least
 }
 ```
 
-- `transition`: `cut`, `whip`, `zoom` or any name the renderer knows. Anything other than `""` or `cut` counts as a `transition` event in the budget.
+- `transition`: `cut`, `whip`, `zoom` or any name the renderer knows. Anything other than `""` or `cut` counts as a `transition` event in the budget. `fill_breaths.py` only fills scenes without a real transition (absent, `""` or `cut`); a transition the author declared is kept, and its `sfx` too when already set.
 - `sfx` (optional): the cut sound, played at `start`. Same shape as an `sfx[]` entry without `at`.
 
 ### `sfx[]`

package/src/skills-lib/wizz-video-effects/scripts/fill_breaths.py

@@ -199,13 +199,27 @@ def pace_profile(index: int, wps: float, cfg: Config) -> str:
     return "fast" if wps >= cfg.breaths.fast_speech_wps else "slow"
 
 
+def declared_transition(scene: dict) -> bool:
+    """True when the author chose a real transition (anything but absent, "" or
+    'cut', the same rule timeline.transitions uses). Those are kept."""
+    return scene.get("transition") not in (None, "", "cut")
+
+
 def scene_updates(scenes: list[dict], words: list[dict], cfg: Config) -> list[tuple[dict, float]]:
-    """(new scene dict, words per second) with transition and cut sound by pace."""
+    """(new scene dict, words per second) with transition and cut sound by pace.
+    A transition the author declared stays, and so does a cut sound already set:
+    pace only fills what is missing."""
     out = []
     for i, sc in enumerate(scenes):
         start = float(sc["start"])
         wps = words_per_second(words, start, start + float(sc.get("dur", 0.0)))
         prof = cfg.breaths.pace_profiles[pace_profile(i, wps, cfg)]
+        if declared_transition(sc):
+            sfx = sc.get("sfx") or {"event": prof.sound_event,
+                                    "src": cfg.sound.src(prof.sound_event),
+                                    "vol": cfg.sound.event(prof.sound_event).vol}
+            out.append(({**sc, "sfx": sfx}, round(wps, 2)))
+            continue
         ev = cfg.sound.event(prof.sound_event)
         out.append(({**sc, "transition": prof.transition,
                     "sfx": {"event": prof.sound_event, "src": cfg.sound.src(prof.sound_event),

package/src/skills-lib/wizz-video-effects/scripts/test_fill_breaths.py

@@ -168,6 +168,26 @@ class TestPlan(unittest.TestCase):
         self.assertTrue(out["punches"])
         self.assertTrue(all("event" in s for s in out["sfx"]))
 
+    def test_declared_transition_is_kept(self):
+        whoosh = {"event": "block_cut", "src": "sfx/mine.mp3", "vol": 0.3}
+        data = {**self.DATA, "scenes": [
+            {"start": 0.0, "dur": 10.0, "transition": "zoom", "sfx": whoosh},
+            {"start": 10.0, "dur": 10.0, "transition": "whip"}]}
+        out = FB.apply(data, FB.plan(data, CFG, [], {}))
+        self.assertEqual([s["transition"] for s in out["scenes"]], ["zoom", "whip"])
+        self.assertEqual(out["scenes"][0]["sfx"], whoosh)
+        self.assertIn("sfx", out["scenes"][1])
+
+    def test_default_transition_is_filled(self):
+        for default in ("", "cut", None):
+            scene = {"start": 0.0, "dur": 10.0}
+            if default is not None:
+                scene["transition"] = default
+            data = {**self.DATA, "scenes": [scene]}
+            out = FB.apply(data, FB.plan(data, CFG, [], {}))
+            self.assertEqual(out["scenes"][0]["transition"],
+                             CFG.breaths.pace_profiles["first"].transition)
+
     def test_pace_profile(self):
         f = CFG.breaths.fast_speech_wps
         self.assertEqual(FB.pace_profile(0, 99.0, CFG), "first")

package/src/skills-lib/wizz-video-styles/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wizz-video-styles
-description: Catalogue of short vertical video styles (Reels, Shorts, TikTok) measured on real high-reach videos, for any niche. Takes an inventory of the material the project actually has (a real person on camera, voice only, b-roll, app screens, a physical product), crosses it with niche and goal, picks the style to copy and hands over its recipe - rhythm, captions, palette, typography, motion vocabulary, music and SFX rules - plus a Remotion template when one exists and a licensed audio kit. Use when a video is about to be edited or planned and nobody has decided what it should look like, when someone says a video "looks amateur" or asks to copy a creator's style, or before wizz-video-effects and Remotion take over. Triggers - estilo do vídeo, editar no estilo de, copiar a edição de, que estilo usar no reel, referência de edição, catálogo de estilos, o vídeo ficou amador. Does not decide per-event SFX or gates (that is wizz-video-effects) and does not assemble the film (that is Remotion).
+description: Catalogue of short vertical video styles (Reels, Shorts, TikTok) measured on real high-reach videos, for any niche. Takes an inventory of the material the project actually has (a real person on camera, voice only, b-roll, app screens, a physical product), crosses it with niche and goal, picks the style to copy and hands over its recipe - rhythm, captions, palette, typography, motion vocabulary, music and SFX rules - plus a Remotion template when one exists and a licensed audio kit. Use when a video is about to be edited or planned and nobody has decided what it should look like, when someone says a video "looks amateur" or asks to copy a creator's style, or before wizz-video-effects and Remotion take over. Triggers - estilo do vídeo, editar no estilo de, copiar a edição de, que estilo usar no reel, referência de edição, catálogo de estilos, o vídeo ficou amador, vídeo do app mexendo, anima o app num vídeo. Does not decide per-event SFX or gates (that is wizz-video-effects) and does not assemble the film (that is Remotion).
 ---
 
 # wizz-video-styles: which style to copy, and its recipe
@@ -11,7 +11,7 @@ Every number in this skill was measured on a real public short ([references/rese
 
 1. Script exists (social area, `wizz-social-content`).
 2. **This skill:** inventory of the material, then style, then recipe.
-3. Narration and word timing (the person's own recording or TTS, then `ctc-align`).
+3. Narration and word timing (the person's own recording or TTS, then `wizz-ctc-align`).
 4. Footage and screens: `get-brolls` for b-roll, HyperFrames for silent screens, real screenshots for app screens.
 5. Effects and sound per event, plus gates: `wizz-video-effects`. Pass it this style's SFX density ceiling and music level.
 6. Assembly in Remotion: invoke `wizz-remotion-best-practices`; copy the style's template from `assets/remotion/` when it has one.
@@ -20,6 +20,8 @@ It can also run at step 1, so the script is written for the style (room for b-ro
 
 ## Per piece
 
+Scripts live in this skill's `scripts/`; run them from the project root (the history file is written in the current directory, or in `--project <dir>`).
+
 1. **Inventory first, always.** Ask or read from the plan, one line each:
    - Is a real person on camera? Which shots exist (face to camera, podcast, stage, street, hands only)?
    - Voice: the person's own recording, a podcast/interview track, TTS, or none?
@@ -27,16 +29,17 @@ It can also run at step 1, so the script is written for the style (room for b-ro
    - B-roll or stock, a physical product, food, a place?
    - Niche, goal of the piece (follow, comment, save, click), duration.
    Never pick a style the material cannot feed. "Talking head" needs a person on camera; "motion editorial" needs nothing but a voice; "macro / ASMR" needs a physical product filmed close.
-2. **Pick the style** with [references/style-picker.md](references/style-picker.md): material decides which styles are possible, niche and goal rank them. Mixed is allowed and common: person on camera for the hook and the CTA, another style in the middle.
+2. **Pick the style** with [references/style-picker.md](references/style-picker.md): material decides which styles are possible, niche and goal rank them. Mixed is allowed and common: person on camera for the hook and the CTA, another style in the middle. Before deciding, run `node scripts/references.mjs history` in the project: if the last two pieces used the same style, do not pick it a third time unless the user wants a series; choose another style the material allows, or keep it only for the hook and CTA.
 3. **Open the style card** in `references/styles/` and follow it: rhythm, captions, palette, typography, motion, music, SFX, hook, CTA, and its "do not" list.
-4. **Watch two of its references** (links in the card) before editing. Reading a card is not watching a video.
+4. **Get fresh references and watch two** before editing: `node scripts/references.mjs pick --style <key>` returns measured references plus, for styles generated in code, current viral videos from the awesome-opus5-5-videos list, skipping everything this project already used. Reading a card is not watching a video. For how those generated videos were briefed, see [references/generated-prompts.md](references/generated-prompts.md).
 5. **Audio:** music and SFX choices from [references/audio.md](references/audio.md); the redistributable kit is in `assets/audio/` (credits in `assets/audio/CREDITS.md`).
 6. **Hand over** to `wizz-video-effects` with the card's SFX ceiling and music level, then to Remotion.
 7. **Look at the final file**: extract frames and compare them side by side with a contact sheet of one reference.
+8. **Record the piece**: `node scripts/references.mjs record --style <key> --piece <slug> --refs <ids watched>`. It writes `_wizz-output/video-styles/historico.json`, which is what keeps the next piece from repeating the same references and look.
 
 ## What the measurements say across every style
 
-- **SFX are rare.** Across 99 measured shorts, sound effects landed on a cut in a small minority of cuts (per-style counts in each card). Putting a sound on every cut is the most common amateur tell.
+- **SFX are rare.** Across 104 measured shorts, sound effects landed on a cut in a small minority of cuts (per-style counts in each card). Putting a sound on every cut is the most common amateur tell.
 - **Music bed: style-dependent.** Fast montage, animated explainers and travel POV carry a continuous bed; talking heads and podcast clips mostly have none or a faint one.
 - **Captions** in reach-heavy styles are 1 to 3 words at a time, bold, lower-centre, with one keyword in an accent colour; editorial and explainer styles keep them small or drop them.
 - **Rhythm is a style property, not a virtue.** The highest-reach videos in the set range from single takes with no detected cut to a cut every second.
@@ -53,7 +56,10 @@ Details and the per-style table: [references/measured-patterns.md](references/me
 | [references/audio.md](references/audio.md) | music and SFX per style, the kit, libraries and licences |
 | [references/research-method.md](references/research-method.md) | how the catalogue was measured, its limits, how to add a niche or a style |
 | `data/references.json` | every measured short: link, channel, views, niche, style, metrics |
+| [references/generated-prompts.md](references/generated-prompts.md) | prompts of viral code-generated videos, grouped by style, and how they run here |
 | `scripts/analyze.sh` | measures one short (cuts, music bed, SFX heuristics, loudness, contact sheet) |
+| `scripts/references.mjs` | fresh references per style without repeats, and the project's history of styles used |
+| `scripts/beat_grid.py` | BPM, beats and downbeats of a song, so cuts snap to the music (lyric video, kinetic typography) |
 | `assets/remotion/editorial/` | Remotion template of the motion editorial style |
 | `assets/audio/` | licensed music beds and SFX that may ship with a project |
 

package/src/skills-lib/wizz-video-styles/data/recipes.json

@@ -7,7 +7,8 @@
   "e": "health / fitness / nutrition",
   "f": "food / recipes / lifestyle / travel",
   "g": "beauty / fashion / local services (clinic, salon, architecture, real estate)",
-  "h": "education / science / comedy"
+  "h": "education / science / comedy",
+  "i": "music / artists / lyric videos"
  },
  "styles": {
   "motion-editorial": {
@@ -336,6 +337,68 @@
    "dont": [
     "Setup longer than 3 s before the first joke."
    ]
+  },
+  "tipografia-cinetica": {
+   "title": "Kinetic typography and lyric video (mexicat P(doom), PixelValet, Ninh Truong)",
+   "needs": "An audio track with words: a song with its lyrics, or a voice-over with its script. Nobody on camera, no footage. Everything is generated (HyperFrames, three.js, canvas). Word timing from ctc-align; a beat grid when there is music.",
+   "fits": "Music releases and lyric videos, manifestos, a strong opinion read aloud, brand promos built on a slogan, poetry. Shares and rewatches; weak for teaching step by step.",
+   "look": [
+    "The words ARE the image: one keyword huge in the frame, the rest of the line small. No caption strip at the bottom.",
+    "Plain background (black, or a flat colour that changes per section) or one generated world the camera travels through (a map, a grid in perspective, a 3D object the line wraps around).",
+    "Each word is animated by what it means: PAIN breaks, CHEERFUL bounces, LIGHT lights up, a word curves around the object it names.",
+    "Code-rendered pieces add film treatment: bloom, halation, grain, a thin HUD in mono."
+   ],
+   "palette": "Dark base (#0A0A0A or a deep teal #0F3B3A) plus ONE glowing accent (orange #FF6A1A in P(doom), coral in Maps) and off-white text. Flat-colour variant: one saturated background per word or section, text in white or ink.",
+   "type": "Two or three families with high contrast: a heavy grotesk or condensed caps for the keyword (Archivo Black, Bebas Neue), a mono for small lines and HUD (IBM Plex Mono), optionally a serif italic for a soft word (Cormorant Garamond). Mix weights inside the same line.",
+   "motion": [
+    "Words enter on the syllable they are sung or spoken (forced alignment, never guessed); the keyword lands on the beat.",
+    "Scene changes snap to the downbeat. P(doom) changes every ~0.3 s at peaks; the calm variant is a single continuous camera move for a whole verse.",
+    "The camera moves through the type (push, orbit, travel across a map) instead of the text sliding over a still frame.",
+    "Hold the last word of a line a beat longer before it leaves."
+   ],
+   "captions": "None separate: the type is the caption. Keep the full line readable somewhere (small, mono, corner) when the keyword alone would lose the sense.",
+   "hook": "The first sung or spoken word, huge, in the accent colour, landing on the first downbeat (0 to 1 s). No logo intro.",
+   "cta": "The title or slogan locked up big and still for 1 to 2 s, the accent lit; one small line (artist, handle, link) under it.",
+   "music": "The track itself is the whole soundtrack. Lyric videos: song at full level, no extra bed. Voice-over promos: a beat-driven bed under the voice.",
+   "sfx": "Song-driven pieces: almost none (5 of 56 cuts in P(doom), 0 of 2 in Maps). Promo variant: hits on every word change (9/13 and 16/20 cuts), which the heuristic partly confuses with the kick. Never add whooshes over a song.",
+   "dont": [
+    "Karaoke subtitles at the bottom over a static background: that is a lyric 'overlay', not this style.",
+    "Guessing word timing by ear; align it (ctc-align) and snap scenes to the beat grid.",
+    "More than one accent colour, or a different font for every word.",
+    "Shipping 16:9: every measured reference is horizontal; recompose for 9:16 with the keyword in the upper-middle and nothing in the bottom 20%."
+   ],
+   "template": null
+  },
+  "ui-morph": {
+   "title": "UI morph: one shape, many UI states (twoclipping, verbove, AnnaCher)",
+   "needs": "The product's real screens or a list of 8 to 12 UI states that tell its story (button, loader, player, slider, toggle, tabs, chart, ⌘K, toast), one accent colour and a track around 120 BPM. Nobody on camera, no footage: everything is drawn in code (HyperFrames).",
+   "fits": "App and SaaS launches, a feature announcement, a product promo for the site or the store page, a portfolio piece. Strong on X and LinkedIn with a product audience; it shows the product working instead of describing it. Weak for teaching step by step or for anything that needs a face.",
+   "look": [
+    "One shape on screen the whole time, never cut: it becomes button, loader, player, slider, toggle, tabs, chart, ⌘K and toast, changing size, corners and colour (the same language as the iPhone Dynamic Island).",
+    "Warm light grey canvas (#EDEBE6), components in black and white, at most one accent colour; a dark variant (navy with one yellow) for a product film.",
+    "Real UI and real data: the product's own labels and numbers, never lorem ipsum or generic components.",
+    "A cursor drives every change with real clicks and drags; the camera zooms so each state fills the frame."
+   ],
+   "palette": "Warm grey #EDEBE6 or beige #E6E2DA, black #111, white, plus ONE accent (orange, peach or yellow) used only where the eye must go. Dark variant: #0B1020 base, one yellow accent.",
+   "type": "One UI sans (Inter, Geist or the product's own font) in regular and semibold; mono only for a URL or a code line. No display fonts.",
+   "motion": [
+    "Every state grows out of the previous one by a spring (size, corner radius, colour), with at most one small overshoot; content swaps with a short blur.",
+    "Something happens on every beat; the state changes land on the downbeats of the beat grid (scripts/beat_grid.py), not on a hand-counted 120 BPM.",
+    "Build it as a pure function of time (seek(t)): closed-form springs, no CSS transitions or timers, so every frame renders the same. HyperFrames does this natively.",
+    "The last frame equals the first, so the piece loops."
+   ],
+   "captions": "None. The text is the interface's own (button labels, track title, chart numbers). A single short line at most, in the UI font, when the product needs one sentence.",
+   "hook": "The first state already on screen at 0 s (a button or the brand pill) and the cursor arriving on the first beat. No logo intro, no title card.",
+   "cta": "The shape returns to the first state or closes on the brand pill with the URL in small mono under it, held 1 to 2 s.",
+   "music": "The track is the whole soundtrack: a continuous bed in 4 of 6 measured pieces, around -14 LUFS. Pick an electronic or lo-fi track with a clear kick so the beat grid is reliable.",
+   "sfx": "Sparse and tied to UI events: a soft click on a press, a low tick on a snap. The measured pieces range from none to a hit on most state changes; never whooshes on every move.",
+   "dont": [
+    "Cutting between screens: the moment it cuts it becomes a screen recording, not this style.",
+    "Bouncy easing, particles, glow, gradients on the UI chrome, icons with uneven stroke, dead time, template look.",
+    "Generic components instead of the product's real UI and numbers.",
+    "Shipping square or 16:9: every measured piece is 1:1 or 16:9; recompose for 9:16 with the shape in the upper-middle and nothing in the bottom 20 %."
+   ],
+   "template": null
   }
  }
-}
+}