@jaimevalasek/aioson 1.8.0 → 1.9.0

package/template/CLAUDE.md

@@ -1,97 +1,98 @@
-# AIOSON
-
-You operate as AIOSON.
-
-## Mandatory first action
-1. Read `.aioson/config.md`
-2. Check whether `.aioson/context/project.context.md` exists
-   - If missing: run `/setup`
-   - If present: read it before any action
-3. If `.aioson/rules/` contains `.md` files, note silently that project rules are active — each agent will load applicable rules automatically via its "Project rules, docs & design docs" section. Do not alarm if the directory is absent or empty.
-
-## Agents
-- /setup -> `.aioson/agents/setup.md`
-- /discovery-design-doc -> `.aioson/agents/discovery-design-doc.md`
-- /analyst -> `.aioson/agents/analyst.md`
-- /architect -> `.aioson/agents/architect.md`
-- /ux-ui (UI/UX) -> `.aioson/agents/ux-ui.md`
-- /product -> `.aioson/agents/product.md`
-- /sheldon -> `.aioson/agents/sheldon.md`
-- /deyvin -> `.aioson/agents/deyvin.md`
-- /pair -> `.aioson/agents/deyvin.md` (compatibility alias)
-- /pm -> `.aioson/agents/pm.md`
-- /dev -> `.aioson/agents/dev.md`
-- /qa -> `.aioson/agents/qa.md`
-- /validator -> `.aioson/agents/validator.md`
-- /tester -> `.aioson/agents/tester.md`
-- /neo -> `.aioson/agents/neo.md`
-- /orchestrator -> `.aioson/agents/orchestrator.md`
-- /squad -> `.aioson/agents/squad.md`
-- /committer -> `.aioson/agents/committer.md`
-- /copywriter -> `.aioson/agents/copywriter.md`
-- /cypher -> `.aioson/agents/cypher.md`
-- /orache -> `.aioson/agents/orache.md`
-- /genome -> `.aioson/agents/genome.md`
-- /profiler-researcher -> `.aioson/agents/profiler-researcher.md`
-- /profiler-enricher -> `.aioson/agents/profiler-enricher.md`
-- /profiler-forge -> `.aioson/agents/profiler-forge.md`
-- /design-hybrid-forge -> `.aioson/agents/design-hybrid-forge.md`
-- /site-forge -> `.aioson/agents/site-forge.md`
-- /discover -> `.aioson/agents/discover.md`
-
-## Spec-Driven Development framework
-
-AIOSON follows a Spec-Driven Development (SDD) methodology. Key governance files:
-
-- **`.aioson/constitution.md`** — 6 governing principles all agents must respect
-- **`.aioson/context/project-pulse.md`** — global project state; read at session start, update at session end
-- **`.aioson/skills/process/aioson-spec-driven/SKILL.md`** — process methodology; agents load this automatically
-
-The process depth scales with project classification:
-- **MICRO** (0-1): lightweight — @product → @dev
-- **SMALL** (2-3): standard — @product → @analyst → @dev
-- **MEDIUM** (4-6): full — all agents, all gates, all artifacts
-
-Classification is determined by @analyst during discovery. See `aioson-spec-driven` skill for details.
-
-## Workflow enforcement
-
-When AIOSON manages the session via `aioson workflow:next`, the CLI controls all routing, state, and event emission. The lifecycle instructions are injected into the agent prompt automatically — follow them exactly.
-
-When running Claude Code directly (without `aioson workflow:next`), these rules apply:
-
-**Hard constraints — no exceptions:**
-- You MUST NEVER implement code, produce UI specs, write PRDs, or answer technical tasks outside an activated agent.
-- If the user explicitly activates `/deyvin` or `/pair`, it may act directly only for continuity on existing known context and a small validated slice. If the request is a new project, greenfield build, new feature, broad redesign, vague or contradictory, or mixes product + UX + implementation scope, `/deyvin` must hand off immediately and must not code first.
-- Between agent handoffs, your ONLY valid output is: which agent is next and why. Do not continue into that agent's work.
-- If the user sends an implementation request before setup is complete: do not implement. Tell them to activate `/setup` first.
-- If the user insists on bypassing an agent stage: refuse and redirect. Urgency or complexity do not override this rule.
-
-**Tracked execution in external clients:**
-- Runtime telemetry belongs to the AIOSON gateway, not to ad-hoc shell snippets inside the prompt.
-- Use `aioson workflow:next . --tool=claude` for tracked workflow sessions.
-- Use `aioson agent:prompt <agent> . --tool=claude` when you want a tracked direct handoff before continuing in Claude Code.
-- Use `aioson live:start . --tool=claude --agent=deyvin --no-launch` when you want an explicit tracked continuity session envelope before Claude Code starts working.
-- Inside an active live session, emit milestones via `aioson runtime:emit . --agent=<agent> --type=<event> --summary="..."` instead of opening a parallel `runtime:session:*` session.
-- Use `aioson runtime:emit . --agent=<agent> --type=plan_checkpoint --plan-step=<step>` when the session is attached to an explicit plan and a step has just been completed.
-- Use `aioson live:handoff . --agent=<agent> --to=<next-agent> --reason="..."` when the active agent must transfer the same live session to another AIOSON agent.
-- Monitor active live sessions with `aioson live:status . --agent=<agent> --watch=2` and close them with `aioson live:close . --agent=<agent> --summary="..."`.
-- Plain slash-command activation registers in the dashboard automatically via `aioson agent:done` at the end of each agent session — each agent file has the call in its "Observability" section.
-- Do not call `aioson runtime-log` directly from inside the session — use `aioson agent:done` instead, which is safe in both direct and live-session contexts.
-
-## Shared research cache: researchs/
-
-All agents may read from and write to `researchs/` (project root). Before running any web search, check if `researchs/{slug}/summary.md` exists and was created within the last 7 days — use the cached result instead. After searching, save results there for reuse by other agents. `@product`, `@sheldon`, and `@squad` should also extract short keyword phrases and scout this cache before finalizing substantial output. See AGENTS.md for the full convention.
-
-## Local overrides
-
-Create `CLAUDE.local.md` (not committed) for machine-specific settings:
-- Local tool paths and environment variables
-- Personal preferences that should not affect other team members
-- Dev environment overrides
-
-`CLAUDE.local.md` is loaded after `CLAUDE.md` and takes precedence.
-Add it to `.gitignore` to keep it out of version control.
-
-## Golden rule
-Small project, small solution.
+# AIOSON
+
+You operate as AIOSON.
+
+## Mandatory first action
+1. Read `.aioson/config.md`
+2. Check whether `.aioson/context/project.context.md` exists
+   - If missing: run `/setup`
+   - If present: read it before any action
+3. If `.aioson/rules/` contains `.md` files, note silently that project rules are active — each agent will load applicable rules automatically via its "Project rules, docs & design docs" section. Do not alarm if the directory is absent or empty.
+
+## Agents
+- /setup -> `.aioson/agents/setup.md`
+- /discovery-design-doc -> `.aioson/agents/discovery-design-doc.md`
+- /analyst -> `.aioson/agents/analyst.md`
+- /architect -> `.aioson/agents/architect.md`
+- /ux-ui (UI/UX) -> `.aioson/agents/ux-ui.md`
+- /product -> `.aioson/agents/product.md`
+- /sheldon -> `.aioson/agents/sheldon.md`
+- /deyvin -> `.aioson/agents/deyvin.md`
+- /pair -> `.aioson/agents/deyvin.md` (compatibility alias)
+- /pm -> `.aioson/agents/pm.md`
+- /dev -> `.aioson/agents/dev.md`
+- /qa -> `.aioson/agents/qa.md`
+- /validator -> `.aioson/agents/validator.md`
+- /tester -> `.aioson/agents/tester.md`
+- /pentester -> `.aioson/agents/pentester.md`
+- /neo -> `.aioson/agents/neo.md`
+- /orchestrator -> `.aioson/agents/orchestrator.md`
+- /squad -> `.aioson/agents/squad.md`
+- /committer -> `.aioson/agents/committer.md`
+- /copywriter -> `.aioson/agents/copywriter.md`
+- /briefing -> `.aioson/agents/briefing.md`
+- /orache -> `.aioson/agents/orache.md`
+- /genome -> `.aioson/agents/genome.md`
+- /profiler-researcher -> `.aioson/agents/profiler-researcher.md`
+- /profiler-enricher -> `.aioson/agents/profiler-enricher.md`
+- /profiler-forge -> `.aioson/agents/profiler-forge.md`
+- /design-hybrid-forge -> `.aioson/agents/design-hybrid-forge.md`
+- /site-forge -> `.aioson/agents/site-forge.md`
+- /discover -> `.aioson/agents/discover.md`
+
+## Spec-Driven Development framework
+
+AIOSON follows a Spec-Driven Development (SDD) methodology. Key governance files:
+
+- **`.aioson/constitution.md`** — 6 governing principles all agents must respect
+- **`.aioson/context/project-pulse.md`** — global project state; read at session start, update at session end
+- **`.aioson/skills/process/aioson-spec-driven/SKILL.md`** — process methodology; agents load this automatically
+
+The process depth scales with project classification:
+- **MICRO** (0-1): lightweight — @product → @dev
+- **SMALL** (2-3): standard — @product → @analyst → @dev
+- **MEDIUM** (4-6): full — all agents, all gates, all artifacts
+
+Classification is determined by @analyst during discovery. See `aioson-spec-driven` skill for details.
+
+## Workflow enforcement
+
+When AIOSON manages the session via `aioson workflow:next`, the CLI controls all routing, state, and event emission. The lifecycle instructions are injected into the agent prompt automatically — follow them exactly.
+
+When running Claude Code directly (without `aioson workflow:next`), these rules apply:
+
+**Hard constraints — no exceptions:**
+- You MUST NEVER implement code, produce UI specs, write PRDs, or answer technical tasks outside an activated agent.
+- If the user explicitly activates `/deyvin` or `/pair`, it may act directly only for continuity on existing known context and a small validated slice. If the request is a new project, greenfield build, new feature, broad redesign, vague or contradictory, or mixes product + UX + implementation scope, `/deyvin` must hand off immediately and must not code first.
+- Between agent handoffs, your ONLY valid output is: which agent is next and why. Do not continue into that agent's work.
+- If the user sends an implementation request before setup is complete: do not implement. Tell them to activate `/setup` first.
+- If the user insists on bypassing an agent stage: refuse and redirect. Urgency or complexity do not override this rule.
+
+**Tracked execution in external clients:**
+- Runtime telemetry belongs to the AIOSON gateway, not to ad-hoc shell snippets inside the prompt.
+- Use `aioson workflow:next . --tool=claude` for tracked workflow sessions.
+- Use `aioson agent:prompt <agent> . --tool=claude` when you want a tracked direct handoff before continuing in Claude Code.
+- Use `aioson live:start . --tool=claude --agent=deyvin --no-launch` when you want an explicit tracked continuity session envelope before Claude Code starts working.
+- Inside an active live session, emit milestones via `aioson runtime:emit . --agent=<agent> --type=<event> --summary="..."` instead of opening a parallel `runtime:session:*` session.
+- Use `aioson runtime:emit . --agent=<agent> --type=plan_checkpoint --plan-step=<step>` when the session is attached to an explicit plan and a step has just been completed.
+- Use `aioson live:handoff . --agent=<agent> --to=<next-agent> --reason="..."` when the active agent must transfer the same live session to another AIOSON agent.
+- Monitor active live sessions with `aioson live:status . --agent=<agent> --watch=2` and close them with `aioson live:close . --agent=<agent> --summary="..."`.
+- Plain slash-command activation registers in the dashboard automatically via `aioson agent:done` at the end of each agent session — each agent file has the call in its "Observability" section.
+- Do not call `aioson runtime-log` directly from inside the session — use `aioson agent:done` instead, which is safe in both direct and live-session contexts.
+
+## Shared research cache: researchs/
+
+All agents may read from and write to `researchs/` (project root). Before running any web search, check if `researchs/{slug}/summary.md` exists and was created within the last 7 days — use the cached result instead. After searching, save results there for reuse by other agents. `@product`, `@sheldon`, and `@squad` should also extract short keyword phrases and scout this cache before finalizing substantial output. See AGENTS.md for the full convention.
+
+## Local overrides
+
+Create `CLAUDE.local.md` (not committed) for machine-specific settings:
+- Local tool paths and environment variables
+- Personal preferences that should not affect other team members
+- Dev environment overrides
+
+`CLAUDE.local.md` is loaded after `CLAUDE.md` and takes precedence.
+Add it to `.gitignore` to keep it out of version control.
+
+## Golden rule
+Small project, small solution.

package/template/OPENCODE.md

@@ -1,34 +1,35 @@
-# AIOSON - OpenCode
-
-## Boot
-1. Read `.aioson/config.md`
-2. Check `.aioson/context/project.context.md`
-3. If missing, start with `setup`
-
-## Available agents
-- setup -> `.aioson/agents/setup.md`
-- discovery-design-doc -> `.aioson/agents/discovery-design-doc.md`
-- analyst -> `.aioson/agents/analyst.md`
-- architect -> `.aioson/agents/architect.md`
-- ux-ui (UI/UX) -> `.aioson/agents/ux-ui.md`
-- product -> `.aioson/agents/product.md`
-- sheldon -> `.aioson/agents/sheldon.md`
-- deyvin -> `.aioson/agents/deyvin.md`
-- pair -> `.aioson/agents/deyvin.md` (compatibility alias)
-- pm -> `.aioson/agents/pm.md`
-- dev -> `.aioson/agents/dev.md`
-- qa -> `.aioson/agents/qa.md`
-- tester -> `.aioson/agents/tester.md`
-- neo -> `.aioson/agents/neo.md`
-- orchestrator -> `.aioson/agents/orchestrator.md`
-- squad -> `.aioson/agents/squad.md`
-- genome -> `.aioson/agents/genome.md`
-- profiler-researcher -> `.aioson/agents/profiler-researcher.md`
-- profiler-enricher -> `.aioson/agents/profiler-enricher.md`
-- profiler-forge -> `.aioson/agents/profiler-forge.md`
-- orache -> `.aioson/agents/orache.md`
-- design-hybrid-forge -> `.aioson/agents/design-hybrid-forge.md`
-- site-forge -> `.aioson/agents/site-forge.md`
-
-## Rule
-Do not duplicate rules outside `.aioson/`.
+# AIOSON - OpenCode
+
+## Boot
+1. Read `.aioson/config.md`
+2. Check `.aioson/context/project.context.md`
+3. If missing, start with `setup`
+
+## Available agents
+- setup -> `.aioson/agents/setup.md`
+- discovery-design-doc -> `.aioson/agents/discovery-design-doc.md`
+- discover -> `.aioson/agents/discover.md`
+- analyst -> `.aioson/agents/analyst.md`
+- architect -> `.aioson/agents/architect.md`
+- ux-ui (UI/UX) -> `.aioson/agents/ux-ui.md`
+- product -> `.aioson/agents/product.md`
+- sheldon -> `.aioson/agents/sheldon.md`
+- deyvin -> `.aioson/agents/deyvin.md`
+- pair -> `.aioson/agents/deyvin.md` (compatibility alias)
+- pm -> `.aioson/agents/pm.md`
+- dev -> `.aioson/agents/dev.md`
+- qa -> `.aioson/agents/qa.md`
+- tester -> `.aioson/agents/tester.md`
+- neo -> `.aioson/agents/neo.md`
+- orchestrator -> `.aioson/agents/orchestrator.md`
+- squad -> `.aioson/agents/squad.md`
+- genome -> `.aioson/agents/genome.md`
+- profiler-researcher -> `.aioson/agents/profiler-researcher.md`
+- profiler-enricher -> `.aioson/agents/profiler-enricher.md`
+- profiler-forge -> `.aioson/agents/profiler-forge.md`
+- orache -> `.aioson/agents/orache.md`
+- design-hybrid-forge -> `.aioson/agents/design-hybrid-forge.md`
+- site-forge -> `.aioson/agents/site-forge.md`
+
+## Rule
+Do not duplicate rules outside `.aioson/`.

package/template/aioson-models.json

@@ -1,40 +1,40 @@
-{
-  "_comment": "aioson model config — copy this file, fill in your keys, keep it gitignored",
-  "preferred_scan_provider": "deepseek",
-  "providers": {
-    "deepseek": {
-      "api_key": "YOUR_DEEPSEEK_API_KEY",
-      "model": "deepseek-chat",
-      "base_url": "https://api.deepseek.com/v1"
-    },
-    "gemini": {
-      "api_key": "YOUR_GEMINI_API_KEY",
-      "model": "gemini-2.0-flash",
-      "base_url": "https://generativelanguage.googleapis.com/v1beta/openai"
-    },
-    "openai": {
-      "api_key": "YOUR_OPENAI_API_KEY",
-      "model": "gpt-4o-mini",
-      "base_url": "https://api.openai.com/v1"
-    },
-    "anthropic": {
-      "api_key": "YOUR_ANTHROPIC_API_KEY",
-      "model": "claude-haiku-4-5-20251001"
-    },
-    "groq": {
-      "api_key": "YOUR_GROQ_API_KEY",
-      "model": "llama-3.3-70b-versatile",
-      "base_url": "https://api.groq.com/openai/v1"
-    },
-    "together": {
-      "api_key": "YOUR_TOGETHER_API_KEY",
-      "model": "meta-llama/Llama-3.3-70B-Instruct-Turbo",
-      "base_url": "https://api.together.xyz/v1"
-    },
-    "mistral": {
-      "api_key": "YOUR_MISTRAL_API_KEY",
-      "model": "mistral-small-latest",
-      "base_url": "https://api.mistral.ai/v1"
-    }
-  }
-}
+{
+  "_comment": "aioson model config — copy this file, fill in your keys, keep it gitignored",
+  "preferred_scan_provider": "deepseek",
+  "providers": {
+    "deepseek": {
+      "api_key": "YOUR_DEEPSEEK_API_KEY",
+      "model": "deepseek-chat",
+      "base_url": "https://api.deepseek.com/v1"
+    },
+    "gemini": {
+      "api_key": "YOUR_GEMINI_API_KEY",
+      "model": "gemini-2.0-flash",
+      "base_url": "https://generativelanguage.googleapis.com/v1beta/openai"
+    },
+    "openai": {
+      "api_key": "YOUR_OPENAI_API_KEY",
+      "model": "gpt-4o-mini",
+      "base_url": "https://api.openai.com/v1"
+    },
+    "anthropic": {
+      "api_key": "YOUR_ANTHROPIC_API_KEY",
+      "model": "claude-haiku-4-5-20251001"
+    },
+    "groq": {
+      "api_key": "YOUR_GROQ_API_KEY",
+      "model": "llama-3.3-70b-versatile",
+      "base_url": "https://api.groq.com/openai/v1"
+    },
+    "together": {
+      "api_key": "YOUR_TOGETHER_API_KEY",
+      "model": "meta-llama/Llama-3.3-70B-Instruct-Turbo",
+      "base_url": "https://api.together.xyz/v1"
+    },
+    "mistral": {
+      "api_key": "YOUR_MISTRAL_API_KEY",
+      "model": "mistral-small-latest",
+      "base_url": "https://api.mistral.ai/v1"
+    }
+  }
+}

package/template/.aioson/genomes/copywriting.md

@@ -1,204 +0,0 @@
----
-name: copywriting
-description: Generic direct response copywriting genome — mental models, frameworks, heuristics and methodologies for high-converting copy in any niche.
-type: function
-domain: copywriting
----
-
-# Genome: Copywriting (Direct Response)
-
-## Identity
-
-This genome encodes the thinking patterns of direct response copywriting — the discipline of writing words that produce measurable action. It is niche-agnostic: the principles work for health, finance, education, SaaS, e-commerce, and any domain where conversion matters.
-
----
-
-## Filosofias
-
-### 1. Copy is salesmanship in print
-Copy is not creative writing. It's a salesperson who works 24/7 without breaks, sick days, or mood swings. Every sentence must advance the sale or be cut.
-
-### 2. The prospect is the hero, not the product
-The product is a vehicle. The prospect is the protagonist. The copy's job is to show them a path from their current painful state to their desired future state — and the product is the bridge.
-
-### 3. Nothing is created, everything is modeled
-Original copy comes from structured research, not imagination. Study what works (swipe files, competitor analysis, audience language), then adapt the structure, angle, and psychology to the specific product and audience.
-
-### 4. There is no long copy, only boring copy
-Length doesn't kill conversion — boredom does. A 5,000-word sales page that maintains curiosity and relevance outperforms a 500-word page that's generic. Every paragraph must earn the next paragraph.
-
-### 5. The market dictates the message
-You don't choose what to say — the market does. Research (PMS, competitor analysis, audience language) reveals what the prospect needs to hear. Your job is to organize and present it, not to invent it.
-
-### 6. Data beats opinion
-If an element is converting, don't change it because it looks "ugly" or doesn't match your taste. Conversion data is the only judge. Aesthetic improvements that reduce conversion are failures, not improvements.
-
----
-
-## Modelos mentais
-
-### The One Belief Model
-Every page/VSL must establish one central belief:
-> "Doing [New Opportunity] is the key to [Primary Benefit], and this is only possible through [Unique Mechanism]."
-
-All copy elements serve this single thesis. If a section doesn't build the belief, it weakens it.
-
-**Reference:** `.aioson/skills/marketing/references/one-belief.md`
-
-### The 5-Act Narrative Arc
-Sales content follows a dramatic structure, not a flat feature list:
-1. **Lead** — hook attention, create curiosity
-2. **Background** — build authority and emotional connection
-3. **Mechanism** — explain WHY (problem cause + solution logic)
-4. **Offer** — present the product as the vehicle
-5. **Close** — manage emotions, drive action
-
-**Reference:** `.aioson/skills/marketing/references/five-acts.md`
-
-### PMS (Problems, Myths, Dreams)
-Before writing, map:
-- **P** — Problems the audience faces (in their words)
-- **M** — Myths/Lies they believe that keep them stuck
-- **S** — Dreams they have (specific, emotional, visualizable)
-
-Copy that mirrors PMS back to the prospect in their vocabulary converts.
-
-**Reference:** `.aioson/skills/marketing/references/pms-research.md`
-
-### Market Sophistication Levels
-Eugene Schwartz's 5 levels determine HOW to write:
-
-| Level | State | Strategy |
-|---|---|---|
-| 1 | Unaware of the problem | Lead with problem discovery |
-| 2 | Problem-aware, no solutions tried | Simple promise + mechanism |
-| 3 | Solution-aware, tried things that failed | Invalidate old solutions first |
-| 4 | Product-aware, knows your type exists | Hyper-specific unique mechanism |
-| 5 | Most sophisticated, skeptical | Lead with proof, reverse-engineer belief |
-
-### The Awareness Spectrum
-Where the prospect is determines the page structure:
-
-- **Cold traffic** (never heard of you) → Full 5-act structure, longer copy, more proof needed
-- **Warm traffic** (follows you, knows you) → Can shorten Acts 1-2, focus on mechanism + offer
-- **Hot traffic** (ready to buy, needs the push) → Lead with offer + guarantee + urgency
-
----
-
-## Heurísticas
-
-### H1: Headline decides 80% of the page's performance
-If the headline doesn't stop the scroll, nothing else matters. Spend 40% of your writing time on the headline and subheadline.
-
-### H2: Every section must do one of three things
-1. Build the belief (One Belief)
-2. Prove the belief (social proof, mechanism, demonstration)
-3. Drive the action (CTA, urgency, guarantee)
-
-If a section doesn't do any of these, cut it.
-
-### H3: The prospect's vocabulary is always better than yours
-"I'm tired of the yo-yo cycle" > "Achieve sustainable weight management."
-Use the words they use. Research gives you those words.
-
-### H4: Specificity creates credibility
-"14,237 patients" > "thousands of patients"
-"R$47M in combined revenue" > "millions in revenue"
-"In 21 days" > "quickly"
-The more specific the claim, the more believable it is.
-
-### H5: One CTA per decision point
-Never give the prospect 5 things to click. One primary action. One secondary (lower commitment) if needed. That's it.
-
-### H6: Objections not addressed are objections that win
-Every prospect has reasons to say no. Name them. Address them. Prove them wrong. Unaddressed objections compound into a silent "no."
-
-### H7: The guarantee is a conversion multiplier, not a risk
-Strong guarantees increase conversion more than they increase refunds. A 30-day unconditional guarantee can increase sales by 20-30% while refund rates typically stay under 5%.
-
-### H8: Features are proof, not headlines
-Features belong in supporting sections as evidence that the benefit is real. They never lead. Benefits lead, features support.
-
-### H9: Price is always relative
-R$97 is expensive for a PDF. R$97 is cheap for solving a problem that costs R$5,000/year. The copy must frame the price against the alternative cost.
-
-### H10: Urgency must be real or absent
-Fake urgency destroys trust faster than no urgency destroys conversion. If there's no real deadline, don't invent one. Use the Two Paths technique instead (emotional urgency, not manufactured scarcity).
-
----
-
-## Frameworks
-
-### Framework 1: AIDA (classic)
-**A**ttention → **I**nterest → **D**esire → **A**ction
-Best for: short copy, email sequences, ad scripts.
-
-### Framework 2: PAS (Problem-Agitate-Solve)
-**P**roblem (name it) → **A**gitate (make it feel urgent) → **S**olve (present the solution)
-Best for: email subject lines, ad hooks, section openers.
-
-### Framework 3: BAB (Before-After-Bridge)
-**B**efore (current painful state) → **A**fter (desired future state) → **B**ridge (the product connects them)
-Best for: testimonial sections, hero copy, case studies.
-
-### Framework 4: The Two Paths (close technique)
-Present two futures:
-- **Path 1:** Stay the same (paint the pain of inaction with specific consequences)
-- **Path 2:** Take the new opportunity (paint the dream outcome with specific details)
-
-Best for: Act 5 (close), email sequences, retargeting pages.
-
-### Framework 5: The Irresistible Offer Stack
-Value anchoring → Component stacking → Bonuses with purpose → Reason why → Guarantee → CTA
-Best for: Act 4 (offer section).
-
-**Reference:** `.aioson/skills/marketing/references/offer-structure.md`
-
----
-
-## Metodologias
-
-### M1: Research before writing (always)
-1. PMS mapping (Problems, Myths, Dreams)
-2. Competitive scan (ads, pages, gaps)
-3. Audience language capture (exact quotes)
-4. Trend validation (Google Trends, social)
-
-**Reference:** `.aioson/skills/marketing/references/market-intelligence.md`
-
-### M2: Write in blocks, not linearly
-Write the headline LAST (after you know the mechanism and offer).
-Write the mechanism FIRST (it determines the headline angle).
-Order: Mechanism → Offer → Lead → Background → Close → Headline.
-
-### M3: Validate against anti-patterns
-After writing, run every section through the anti-pattern checklist.
-**Reference:** `.aioson/skills/marketing/references/anti-patterns.md`
-
-### M4: Test before perfecting
-For VSLs: test with an "ugly" version (slides, text on screen) before investing in production.
-For pages: test the headline and CTA before designing the full page.
-Data validates — opinion guesses.
-
----
-
-## Conditional reference loading
-
-This genome references detailed files in `.aioson/skills/marketing/references/`. Load them on demand:
-
-| When writing... | Load these references |
-|---|---|
-| Any marketing/sales page | `patterns.md` + `anti-patterns.md` |
-| Offer/pricing section | `offer-structure.md` + `fascinations.md` |
-| Research phase | `pms-research.md` + `market-intelligence.md` |
-| Narrative structure | `five-acts.md` + `one-belief.md` |
-| VSL script | All references + `.aioson/skills/marketing/vsl-craft.md` |
-
----
-
-## What this genome does NOT cover
-
-- **Brand-specific voice:** Use a `brand-voice-{slug}.md` genome for client-specific tone
-- **Domain-specific knowledge:** Use domain genomes for industry-specific mental models
-- **Visual design:** @ux-ui handles visual implementation — this genome handles the words
-- **SEO/technical implementation:** `landing-page-forge.md` skill handles technical production

package/template/.aioson/genomes/copywriting.meta.json

@@ -1,48 +0,0 @@
-{
-  "genome": "copywriting",
-  "schemaVersion": 2,
-  "slug": "copywriting",
-  "domain": "Copywriting (Direct Response)",
-  "type": "function",
-  "version": 2,
-  "format": "genome-v2",
-  "language": "en",
-  "depth": "deep",
-  "evidenceMode": "inferred",
-  "sourceCount": 0,
-  "counts": {
-    "knowledgeNodes": 0,
-    "philosophies": 6,
-    "mentalModels": 4,
-    "heuristics": 10,
-    "frameworks": 5,
-    "methodologies": 4,
-    "mentes": 0,
-    "skills": 0,
-    "cognitiveProfile": 0,
-    "communicationStyle": 0,
-    "biases": 0,
-    "conflictResolution": 0,
-    "evidence": 0,
-    "applicationNotes": 0
-  },
-  "dependencies": {
-    "skills": ["marketing"],
-    "genomes": []
-  },
-  "origin": {
-    "mode": "llm",
-    "sourceFiles": [],
-    "sourceUrls": []
-  },
-  "compat": {
-    "legacyMarkdownCompatible": true,
-    "synthesizedFromLegacy": false
-  },
-  "bindings": {
-    "squads": [],
-    "agents": []
-  },
-  "createdAt": "2026-03-01T00:00:00.000Z",
-  "updatedAt": "2026-04-07T00:00:00.000Z"
-}