@jaimevalasek/aioson 1.7.2 → 1.9.0

package/template/.aioson/skills/squad/formats/social/twitter-thread.md

@@ -1,39 +1,39 @@
-# Format: Twitter/X Thread
-
-> Platform: Twitter/X
-> Version: 1.0.0
-> Updated: 2026-03-24
-> Category: social
-
-## Specs
-- **Tweet length:** 280 characters per tweet
-- **Thread length:** 5-15 tweets ideal
-- **Media:** Images/GIFs boost engagement 2-3x
-
-## Structure
-
-### Tweet 1 (Hook)
-Bold claim or curiosity gap. End with "A thread:" or equivalent to signal more value coming.
-
-### Body tweets (2 to N-1)
-One idea per tweet. Use numbering (1/, 2/) for scanability. Mix text-only with visual tweets.
-
-### Final tweet
-Summary + CTA (follow, retweet, bookmark). Link to relevant resource.
-
-## Best Practices
-1. Tweet 1 determines 80% of the thread's reach — optimize ruthlessly
-2. Each tweet should stand alone (people land mid-thread)
-3. Include images or examples every 3-4 tweets to break monotony
-4. Self-retweet the thread after 8-12 hours
-
-## Anti-patterns
-1. Threads that could be one tweet (don't stretch thin content)
-2. Every tweet starting with the same structure
-3. Burying the value in tweet 8+ without enough hooks
-
-## Quality Checklist
-- [ ] Tweet 1 is a standalone hook
-- [ ] Each tweet delivers one clear idea
-- [ ] Thread has visual variety (images, examples)
-- [ ] Final tweet has CTA and summary
+# Format: Twitter/X Thread
+
+> Platform: Twitter/X
+> Version: 1.0.0
+> Updated: 2026-03-24
+> Category: social
+
+## Specs
+- **Tweet length:** 280 characters per tweet
+- **Thread length:** 5-15 tweets ideal
+- **Media:** Images/GIFs boost engagement 2-3x
+
+## Structure
+
+### Tweet 1 (Hook)
+Bold claim or curiosity gap. End with "A thread:" or equivalent to signal more value coming.
+
+### Body tweets (2 to N-1)
+One idea per tweet. Use numbering (1/, 2/) for scanability. Mix text-only with visual tweets.
+
+### Final tweet
+Summary + CTA (follow, retweet, bookmark). Link to relevant resource.
+
+## Best Practices
+1. Tweet 1 determines 80% of the thread's reach — optimize ruthlessly
+2. Each tweet should stand alone (people land mid-thread)
+3. Include images or examples every 3-4 tweets to break monotony
+4. Self-retweet the thread after 8-12 hours
+
+## Anti-patterns
+1. Threads that could be one tweet (don't stretch thin content)
+2. Every tweet starting with the same structure
+3. Burying the value in tweet 8+ without enough hooks
+
+## Quality Checklist
+- [ ] Tweet 1 is a standalone hook
+- [ ] Each tweet delivers one clear idea
+- [ ] Thread has visual variety (images, examples)
+- [ ] Final tweet has CTA and summary

package/template/.aioson/skills/squad/formats/social/youtube-long.md

@@ -1,47 +1,47 @@
-# Format: YouTube Long-form Video
-
-> Platform: YouTube
-> Version: 1.0.0
-> Updated: 2026-03-24
-> Category: social
-
-## Specs
-- **Duration:** 8-20 minutes (sweet spot for monetization + retention)
-- **Title:** Max 100 chars, ideal 50-70
-- **Description:** First 150 chars visible, max 5,000
-- **Thumbnail:** 1280x720px, max 2MB
-
-## Structure
-
-### Hook (0-3s)
-Pattern interrupt, curiosity gap, or bold claim. The viewer decides to stay or leave in 3 seconds.
-
-### Context Bridge (3-15s)
-Why the viewer should stay. Establish credibility and promise of value.
-
-### Value Delivery (main body)
-Chapters with mini-hooks at transitions to prevent drop-off. Each chapter delivers on a specific promise.
-
-### CTA
-Subscribe, like, comment prompt integrated naturally (not forced). Best placed after a value moment.
-
-### End Screen (last 20s)
-Teaser for the next video. Visual end screen elements.
-
-## Best Practices
-1. Script the first 30 seconds word-for-word
-2. Use chapters (timestamps) for SEO and navigation
-3. Thumbnail: one focal point, max 3-4 words, readable at 120px width
-4. Title creates curiosity without misleading (clickbait kills trust)
-
-## Anti-patterns
-1. "Hey guys, welcome back to my channel..." (instant drop-off)
-2. Intros longer than 15 seconds
-3. Thumbnails with cluttered text or low contrast
-
-## Quality Checklist
-- [ ] Hook is scripted and compelling (first 3 seconds)
-- [ ] Title creates genuine curiosity
-- [ ] Thumbnail is readable at mobile size
-- [ ] Chapters/timestamps are defined
-- [ ] Description includes keywords and links
+# Format: YouTube Long-form Video
+
+> Platform: YouTube
+> Version: 1.0.0
+> Updated: 2026-03-24
+> Category: social
+
+## Specs
+- **Duration:** 8-20 minutes (sweet spot for monetization + retention)
+- **Title:** Max 100 chars, ideal 50-70
+- **Description:** First 150 chars visible, max 5,000
+- **Thumbnail:** 1280x720px, max 2MB
+
+## Structure
+
+### Hook (0-3s)
+Pattern interrupt, curiosity gap, or bold claim. The viewer decides to stay or leave in 3 seconds.
+
+### Context Bridge (3-15s)
+Why the viewer should stay. Establish credibility and promise of value.
+
+### Value Delivery (main body)
+Chapters with mini-hooks at transitions to prevent drop-off. Each chapter delivers on a specific promise.
+
+### CTA
+Subscribe, like, comment prompt integrated naturally (not forced). Best placed after a value moment.
+
+### End Screen (last 20s)
+Teaser for the next video. Visual end screen elements.
+
+## Best Practices
+1. Script the first 30 seconds word-for-word
+2. Use chapters (timestamps) for SEO and navigation
+3. Thumbnail: one focal point, max 3-4 words, readable at 120px width
+4. Title creates curiosity without misleading (clickbait kills trust)
+
+## Anti-patterns
+1. "Hey guys, welcome back to my channel..." (instant drop-off)
+2. Intros longer than 15 seconds
+3. Thumbnails with cluttered text or low contrast
+
+## Quality Checklist
+- [ ] Hook is scripted and compelling (first 3 seconds)
+- [ ] Title creates genuine curiosity
+- [ ] Thumbnail is readable at mobile size
+- [ ] Chapters/timestamps are defined
+- [ ] Description includes keywords and links

package/template/.aioson/skills/squad/formats/social/youtube-shorts.md

@@ -1,39 +1,39 @@
-# Format: YouTube Shorts
-
-> Platform: YouTube
-> Version: 1.0.0
-> Updated: 2026-03-24
-> Category: social
-
-## Specs
-- **Duration:** Max 60 seconds, ideal 15-45s
-- **Aspect ratio:** 9:16 (vertical)
-- **Title:** Short, hashtag-friendly
-
-## Structure
-
-### Hook (0-1s)
-Immediate visual or verbal hook. No intro, no greeting — start with the payoff or the tension.
-
-### Core (1-45s)
-One idea, one message. Fast pacing, cuts every 2-3 seconds. Text overlays for silent viewers.
-
-### Loop Point
-End connects visually or thematically to the beginning to encourage re-watches.
-
-## Best Practices
-1. Start mid-action or mid-sentence
-2. Text on screen for accessibility and silent viewing
-3. Trending sounds boost discoverability
-4. #Shorts in title or description
-
-## Anti-patterns
-1. Slow starts or countdowns
-2. Horizontal content cropped to vertical
-3. Asking to subscribe before delivering value
-
-## Quality Checklist
-- [ ] Opens with immediate hook (no greeting)
-- [ ] Single clear message
-- [ ] Viewable without audio (text overlays)
-- [ ] Under 60 seconds
+# Format: YouTube Shorts
+
+> Platform: YouTube
+> Version: 1.0.0
+> Updated: 2026-03-24
+> Category: social
+
+## Specs
+- **Duration:** Max 60 seconds, ideal 15-45s
+- **Aspect ratio:** 9:16 (vertical)
+- **Title:** Short, hashtag-friendly
+
+## Structure
+
+### Hook (0-1s)
+Immediate visual or verbal hook. No intro, no greeting — start with the payoff or the tension.
+
+### Core (1-45s)
+One idea, one message. Fast pacing, cuts every 2-3 seconds. Text overlays for silent viewers.
+
+### Loop Point
+End connects visually or thematically to the beginning to encourage re-watches.
+
+## Best Practices
+1. Start mid-action or mid-sentence
+2. Text on screen for accessibility and silent viewing
+3. Trending sounds boost discoverability
+4. #Shorts in title or description
+
+## Anti-patterns
+1. Slow starts or countdowns
+2. Horizontal content cropped to vertical
+3. Asking to subscribe before delivering value
+
+## Quality Checklist
+- [ ] Opens with immediate hook (no greeting)
+- [ ] Single clear message
+- [ ] Viewable without audio (text overlays)
+- [ ] Under 60 seconds

package/template/.aioson/skills/squad/patterns/multi-platform-pattern.md

@@ -1,108 +1,108 @@
----
-name: multi-platform-pattern
-description: How to create squads that produce content for multiple platforms simultaneously
-version: 1.0.0
----
-
-# Multi-Platform Pattern
-
-A multi-platform squad produces content adapted for 2+ platforms from a single
-creative brief. The key challenge is platform-specific adaptation without
-losing message coherence.
-
-## When to use
-
-- Content squads targeting Instagram + YouTube + TikTok (or any combination)
-- Marketing squads with omnichannel campaigns
-- Brand squads maintaining consistent voice across platforms
-
-## Structure
-
-### Option A: Single creator + platform adapters
-
-```
-core-creator → platform-adapter-instagram
-             → platform-adapter-youtube
-             → platform-adapter-tiktok
-```
-
-Best when: one strong creative vision needs platform-specific formatting.
-
-### Option B: Platform specialists
-
-```
-briefer → instagram-specialist
-        → youtube-specialist
-        → tiktok-specialist
-        → brand-reviewer (cross-platform consistency check)
-```
-
-Best when: each platform requires deeply different approaches.
-
-### Option C: Hybrid (recommended for most cases)
-
-```
-strategist → core-creator → platform-specialists (parallel)
-                           → cross-platform-reviewer
-```
-
-## Executor recommendations
-
-| Role | Type | Model tier | Purpose |
-|---|---|---|---|
-| strategist | agent | powerful | Defines the creative brief and core message |
-| core-creator | agent | powerful | Creates the primary content piece |
-| platform-adapter | agent | balanced | Adapts content per platform specs |
-| brand-reviewer | agent | balanced | Ensures cross-platform consistency |
-| format-checker | worker | none | Validates platform constraints (char limits, dimensions) |
-
-## Format loading
-
-Load format templates from `formats/` only for platforms the squad targets:
-
-```
-formats/instagram-feed.md    → Instagram squads
-formats/youtube-long.md      → YouTube squads
-formats/tiktok.md            → TikTok squads
-formats/linkedin-post.md     → LinkedIn squads
-formats/twitter-thread.md    → Twitter/X squads
-```
-
-## Workflow template
-
-```json
-{
-  "slug": "multi-platform-content",
-  "phases": [
-    { "id": "brief", "executor": "strategist" },
-    { "id": "core-draft", "executor": "core-creator" },
-    { "id": "adapt", "executors": ["ig-adapter", "yt-adapter", "tt-adapter"], "parallel": true },
-    { "id": "review", "executor": "brand-reviewer", "review": { "criteria": ["brand-consistency", "platform-fit"] } },
-    { "id": "validate", "executor": "format-checker" }
-  ]
-}
-```
-
-## Anti-patterns
-
-- **Copy-paste across platforms:** Each platform has unique audience behavior. Adaptation is mandatory.
-- **Ignoring platform constraints:** Character limits, video durations, image ratios differ per platform.
-- **One-size-fits-all CTA:** "Subscribe" on YouTube, "Follow" on Instagram, "Connect" on LinkedIn.
-- **Missing cross-platform review:** Without consistency checks, brand voice fragments.
-
-## Content blueprint suggestion
-
-```json
-{
-  "slug": "multi-platform-package",
-  "contentType": "multi-platform",
-  "layoutType": "tabs",
-  "sections": [
-    { "key": "brief", "label": "Creative Brief" },
-    { "key": "core-content", "label": "Core Content" },
-    { "key": "instagram", "label": "Instagram Version" },
-    { "key": "youtube", "label": "YouTube Version" },
-    { "key": "tiktok", "label": "TikTok Version" }
-  ]
-}
-```
+---
+name: multi-platform-pattern
+description: How to create squads that produce content for multiple platforms simultaneously
+version: 1.0.0
+---
+
+# Multi-Platform Pattern
+
+A multi-platform squad produces content adapted for 2+ platforms from a single
+creative brief. The key challenge is platform-specific adaptation without
+losing message coherence.
+
+## When to use
+
+- Content squads targeting Instagram + YouTube + TikTok (or any combination)
+- Marketing squads with omnichannel campaigns
+- Brand squads maintaining consistent voice across platforms
+
+## Structure
+
+### Option A: Single creator + platform adapters
+
+```
+core-creator → platform-adapter-instagram
+             → platform-adapter-youtube
+             → platform-adapter-tiktok
+```
+
+Best when: one strong creative vision needs platform-specific formatting.
+
+### Option B: Platform specialists
+
+```
+briefer → instagram-specialist
+        → youtube-specialist
+        → tiktok-specialist
+        → brand-reviewer (cross-platform consistency check)
+```
+
+Best when: each platform requires deeply different approaches.
+
+### Option C: Hybrid (recommended for most cases)
+
+```
+strategist → core-creator → platform-specialists (parallel)
+                           → cross-platform-reviewer
+```
+
+## Executor recommendations
+
+| Role | Type | Model tier | Purpose |
+|---|---|---|---|
+| strategist | agent | powerful | Defines the creative brief and core message |
+| core-creator | agent | powerful | Creates the primary content piece |
+| platform-adapter | agent | balanced | Adapts content per platform specs |
+| brand-reviewer | agent | balanced | Ensures cross-platform consistency |
+| format-checker | worker | none | Validates platform constraints (char limits, dimensions) |
+
+## Format loading
+
+Load format templates from `formats/` only for platforms the squad targets:
+
+```
+formats/instagram-feed.md    → Instagram squads
+formats/youtube-long.md      → YouTube squads
+formats/tiktok.md            → TikTok squads
+formats/linkedin-post.md     → LinkedIn squads
+formats/twitter-thread.md    → Twitter/X squads
+```
+
+## Workflow template
+
+```json
+{
+  "slug": "multi-platform-content",
+  "phases": [
+    { "id": "brief", "executor": "strategist" },
+    { "id": "core-draft", "executor": "core-creator" },
+    { "id": "adapt", "executors": ["ig-adapter", "yt-adapter", "tt-adapter"], "parallel": true },
+    { "id": "review", "executor": "brand-reviewer", "review": { "criteria": ["brand-consistency", "platform-fit"] } },
+    { "id": "validate", "executor": "format-checker" }
+  ]
+}
+```
+
+## Anti-patterns
+
+- **Copy-paste across platforms:** Each platform has unique audience behavior. Adaptation is mandatory.
+- **Ignoring platform constraints:** Character limits, video durations, image ratios differ per platform.
+- **One-size-fits-all CTA:** "Subscribe" on YouTube, "Follow" on Instagram, "Connect" on LinkedIn.
+- **Missing cross-platform review:** Without consistency checks, brand voice fragments.
+
+## Content blueprint suggestion
+
+```json
+{
+  "slug": "multi-platform-package",
+  "contentType": "multi-platform",
+  "layoutType": "tabs",
+  "sections": [
+    { "key": "brief", "label": "Creative Brief" },
+    { "key": "core-content", "label": "Core Content" },
+    { "key": "instagram", "label": "Instagram Version" },
+    { "key": "youtube", "label": "YouTube Version" },
+    { "key": "tiktok", "label": "TikTok Version" }
+  ]
+}
+```

package/template/.aioson/skills/squad/patterns/persona-based-pattern.md

@@ -1,98 +1,98 @@
----
-name: persona-based-pattern
-description: How to create squads driven by a specific person's voice, methodology, or brand
-version: 1.0.0
----
-
-# Persona-Based Pattern
-
-A persona-based squad produces content or work that reflects a specific person's
-voice, methodology, or cognitive style. This pattern uses the profiler pipeline
-to create a cognitive genome that informs creative executors.
-
-## When to use
-
-- Personal branding squads (content in someone's voice)
-- Methodology-based squads (applying a specific expert's framework)
-- Ghost-writing or content delegation squads
-- Squads where "sounding like the person" is a core requirement
-
-## Detection heuristics
-
-The squad agent should suggest profiling when:
-
-- The user mentions a specific person by name
-- The goal includes "in the style of", "like {person}", "based on {person}'s approach"
-- The domain is personal branding or creator content
-- The user references a specific methodology tied to a person
-
-## Profiler pipeline
-
-```
-@profiler-researcher → @profiler-enricher → @profiler-forge
-         ↓                     ↓                    ↓
-   evidence gathering    pattern analysis      genome generation
-```
-
-### Step 1: Check existing profile
-
-Before running the pipeline, check `.aioson/profiler-reports/{person-slug}/`.
-If a profile exists, reuse it.
-
-### Step 2: Run profiling (if needed)
-
-1. `@profiler-researcher` — collects public evidence about the person
-2. `@profiler-enricher` — analyzes patterns, voice, methodology
-3. `@profiler-forge` — generates the cognitive genome
-
-### Step 3: Apply genome selectively
-
-The genome should only be applied to executors that produce voice-sensitive output:
-
-| Executor type | Apply genome? | Reason |
-|---|---|---|
-| Copywriter/Scriptwriter | Yes | Needs the person's voice |
-| Editor/Reviewer | Yes | Needs to judge voice fidelity |
-| Researcher/Analyst | No | Research should be objective |
-| Orchestrator | No | Coordination doesn't need voice |
-| Worker (no LLM) | No | Deterministic, no voice needed |
-
-### Step 4: Register in blueprint
-
-```json
-{
-  "profiling": {
-    "person": "Person Name",
-    "genomePath": ".aioson/profiler-reports/person-slug/genome.json",
-    "genomeSlug": "person-slug",
-    "evidenceMode": "verified",
-    "profiledAt": "2026-03-24T00:00:00Z"
-  }
-}
-```
-
-## Executor recommendations
-
-| Role | Type | Model tier | Genome? |
-|---|---|---|---|
-| researcher | agent | balanced | No |
-| scriptwriter | agent | powerful | Yes |
-| copywriter | agent | powerful | Yes |
-| editor | agent | balanced | Yes |
-| brand-guardian | agent | balanced | Yes |
-| publisher | worker | none | No |
-
-## Anti-patterns
-
-- **Applying genome to all executors:** Research and orchestration don't need persona voice.
-- **Profiling without consent:** Always ask the user before running the profiler pipeline.
-- **Stale genome:** If the person's style has evolved, the genome may need refreshing.
-- **Over-reliance on genome:** The genome calibrates voice, it doesn't replace creative judgment.
-- **Copying vs. calibrating:** The goal is to capture methodology and voice patterns, not to clone or impersonate.
-
-## Quality gates for persona fidelity
-
-- Voice consistency: Does the output sound like the person across all pieces?
-- Methodology alignment: Does the approach follow the person's known frameworks?
-- Authenticity check: Would the person recognize this as something they might produce?
-- Originality: Is it inspired by the person, not a copy of their specific works?
+---
+name: persona-based-pattern
+description: How to create squads driven by a specific person's voice, methodology, or brand
+version: 1.0.0
+---
+
+# Persona-Based Pattern
+
+A persona-based squad produces content or work that reflects a specific person's
+voice, methodology, or cognitive style. This pattern uses the profiler pipeline
+to create a cognitive genome that informs creative executors.
+
+## When to use
+
+- Personal branding squads (content in someone's voice)
+- Methodology-based squads (applying a specific expert's framework)
+- Ghost-writing or content delegation squads
+- Squads where "sounding like the person" is a core requirement
+
+## Detection heuristics
+
+The squad agent should suggest profiling when:
+
+- The user mentions a specific person by name
+- The goal includes "in the style of", "like {person}", "based on {person}'s approach"
+- The domain is personal branding or creator content
+- The user references a specific methodology tied to a person
+
+## Profiler pipeline
+
+```
+@profiler-researcher → @profiler-enricher → @profiler-forge
+         ↓                     ↓                    ↓
+   evidence gathering    pattern analysis      genome generation
+```
+
+### Step 1: Check existing profile
+
+Before running the pipeline, check `.aioson/profiler-reports/{person-slug}/`.
+If a profile exists, reuse it.
+
+### Step 2: Run profiling (if needed)
+
+1. `@profiler-researcher` — collects public evidence about the person
+2. `@profiler-enricher` — analyzes patterns, voice, methodology
+3. `@profiler-forge` — generates the cognitive genome
+
+### Step 3: Apply genome selectively
+
+The genome should only be applied to executors that produce voice-sensitive output:
+
+| Executor type | Apply genome? | Reason |
+|---|---|---|
+| Copywriter/Scriptwriter | Yes | Needs the person's voice |
+| Editor/Reviewer | Yes | Needs to judge voice fidelity |
+| Researcher/Analyst | No | Research should be objective |
+| Orchestrator | No | Coordination doesn't need voice |
+| Worker (no LLM) | No | Deterministic, no voice needed |
+
+### Step 4: Register in blueprint
+
+```json
+{
+  "profiling": {
+    "person": "Person Name",
+    "genomePath": ".aioson/profiler-reports/person-slug/genome.json",
+    "genomeSlug": "person-slug",
+    "evidenceMode": "verified",
+    "profiledAt": "2026-03-24T00:00:00Z"
+  }
+}
+```
+
+## Executor recommendations
+
+| Role | Type | Model tier | Genome? |
+|---|---|---|---|
+| researcher | agent | balanced | No |
+| scriptwriter | agent | powerful | Yes |
+| copywriter | agent | powerful | Yes |
+| editor | agent | balanced | Yes |
+| brand-guardian | agent | balanced | Yes |
+| publisher | worker | none | No |
+
+## Anti-patterns
+
+- **Applying genome to all executors:** Research and orchestration don't need persona voice.
+- **Profiling without consent:** Always ask the user before running the profiler pipeline.
+- **Stale genome:** If the person's style has evolved, the genome may need refreshing.
+- **Over-reliance on genome:** The genome calibrates voice, it doesn't replace creative judgment.
+- **Copying vs. calibrating:** The goal is to capture methodology and voice patterns, not to clone or impersonate.
+
+## Quality gates for persona fidelity
+
+- Voice consistency: Does the output sound like the person across all pieces?
+- Methodology alignment: Does the approach follow the person's known frameworks?
+- Authenticity check: Would the person recognize this as something they might produce?
+- Originality: Is it inspired by the person, not a copy of their specific works?