code-ai-installer 1.5.6 → 2.0.1

package/domains/content/locales/en/.agents/skills/content-calendar/SKILL.md

@@ -0,0 +1,248 @@
+---
+name: content-calendar
+description: Complete content calendar — topics, personas, funnel, content mix, recurring pillars, deadlines, cross-posting, balance check
+---
+# Content Calendar
+
+## When to use
+- During **strategic planning** — weekly, monthly, quarterly, or for a campaign.
+- During **content scaling** — shifting from chaotic posting to a system.
+- During **strategy revision** — rebalancing after metrics analysis or shifting priorities.
+- After **`$audience-analysis`**, **`$platform-strategy`**, **`$competitor-content-analysis`** — the calendar aggregates their findings into an action plan.
+
+## Input
+
+| Field | Required | Description |
+|------|:-----------:|----------|
+| Planning horizon | ✅ | Week / month / quarter / campaign (with dates) |
+| TA Personas | ✅ | From `$audience-analysis` — for distribution across posts |
+| Platforms and frequency | ✅ | From `$platform-strategy` — where and how much to post |
+| Brand guidelines | ✅ | From `$brand-guidelines` — ToV, visual style |
+| Business goals for the period | ✅ | What the business expects from content (launch, leads, awareness) |
+| Newsjacks / events | ⬚ | Holidays, industry events, product launches, seasons |
+| Competitor analysis recommendations | ⬚ | From `$competitor-content-analysis` — gaps and opportunities |
+| `$trend-research` results | ⬚ | Current trends to embed |
+| Recurring pillars | ⬚ | If already defined — repeating formats |
+| Previous calendar + metrics | ⬚ | For iteration: what worked, what didn't |
+
+> If personas or platforms are not provided — **request them from the user** or direct them to `$audience-analysis` / `$platform-strategy`.
+
+## Key Definitions
+
+### Content Types (Content Mix)
+
+| Type | Description | Example |
+|-----|----------|--------|
+| Educational | How-to, tips, breakdowns, guides | "5 email-marketing mistakes" |
+| Sales | Offers, case studies, reviews, demos | "Client increased conversion by 40%" |
+| Entertainment | Memes, trends, interactive | Meme about deadlines + poll |
+| Image | Mission, team, behind the scenes | "How we run a retro" |
+| Community | UGC, Q&A, challenges | "Show us your workspace" |
+
+### Funnel Stages
+
+| Stage | Goal | KPI |
+|------|------|-----|
+| **TOFU** | Awareness — attract new audience | Reach, followers |
+| **MOFU** | Consideration — build trust | Engagement, saves, read time |
+| **BOFU** | Decision — convert | Clicks, leads, sales |
+
+## Protocol
+
+### Step 1 — Period Framework
+1. Record the **horizon** (start and end dates).
+2. Note the **period's key events**: holidays, industry events, launches, seasonal triggers.
+3. Define **business priorities**: what's most crucial (awareness / leads / sales).
+
+### Step 2 — Recurring Pillars
+1. Determine **recurring pillars** (if any are present or needed):
+   - Fixed day + format (e.g., Monday = Tip, Wednesday = Case, Friday = Meme).
+   - Series (e.g., "Industry Myths", "Tool of the Week").
+2. Pillars should fill ~40-60% of slots. The rest is situational content.
+
+### Step 3 — Topic Distribution
+For each slot in the calendar determine:
+1. **Topic** — a specific angle (not "marketing", but "why UTM tracking breaks in email").
+2. **Persona** — which persona from `$audience-analysis` this is for.
+3. **Funnel stage** — TOFU / MOFU / BOFU.
+4. **Content type** — educational / sales / entertainment / image / community.
+5. **Format** — post / carousel / reel / article / email / thread / stories.
+6. **Platform** — main channel.
+
+Topic sources:
+- Personas' pain points and triggers (from `$audience-analysis`).
+- Competitor gaps (from `$competitor-content-analysis`).
+- Trends (from `$trend-research`).
+- Period events.
+- Recurring pillars.
+
+### Step 4 — Cross-posting
+For each content unit, determine:
+1. Is it suitable for adaptation on other platforms?
+2. What changes are required (format, length, CTA, visuals)?
+3. Add cross-posting rows to the calendar (marked as `↳ adaptation`).
+
+### Step 5 — Production Deadlines
+For each content unit — a countdown from the publication date:
+
+| Stage | Offset | Responsible |
+|------|----------|---------------|
+| Brief ready | Publication − N days | Strategist |
+| Text ready | Publication − N days | Copywriter |
+| Visual ready | Publication − N days | Visual Concept |
+| Review passed| Publication − N days | Reviewer |
+| Ready to post| Publication − 1 day | — |
+
+> Specific offsets depend on volume and complexity. Agree with the user upon the first planning session, then use as a standard.
+
+### Step 6 — Balance Check
+Review the calendar across 4 axes:
+
+1. **Content Mix** — proportions by type:
+   - Recommended balance (adapt to business): Educational 30-40% · Sales 15-25% · Entertainment 15-20% · Image 10-15% · Community 10-15%.
+   - If > 40% sales — the calendar "pressures" the audience.
+
+2. **Funnel** — stage coverage:
+   - TOFU 40-50% · MOFU 30-35% · BOFU 15-25%.
+   - There shouldn't be a week without TOFU (no influx of new audience).
+
+3. **Personas** — even coverage:
+   - Priority persona → more content, but others shouldn't be abandoned.
+
+4. **Formats** — variety:
+   - No more than 50% of an identical format (all posts = text without visuals = boring).
+
+### Step 7 — ID Assignment
+Assign a unique ID to every content unit:
+```
+[Platform]-[YYYYMMDD]-[sequence number]
+Example: IG-20260415-01, TG-20260415-02
+```
+This ID is utilized in `$content-brief` to link the brief to the calendar unit.
+
+## Validation (Quality Gate)
+
+The calendar is considered ready if:
+
+- [ ] All slots are filled (no empty dates given the frequency from `$platform-strategy`)
+- [ ] Each unit has: topic, persona, funnel, type, format, platform
+- [ ] Each unit has a unique ID
+- [ ] Content mix sits within acceptable proportions (no skew > 40% of one type)
+- [ ] The funnel is balanced (there's TOFU + MOFU + BOFU every week)
+- [ ] All personas are covered (priority gets more, others not forgotten)
+- [ ] Key events are factored in (holidays, launches, seasons)
+- [ ] Cross-posting is marked (adaptations appropriately flagged)
+- [ ] Production deadlines are set
+- [ ] Balance check passed across all 4 axes
+- [ ] Approved by the user
+
+## Handoff
+
+| Outcome | Routing |
+|------|---------|
+| Calendar approved | → `$content-brief` for each content unit (by ID) |
+| Research needed before brief | → `$topic-research` / `$trend-research` → then `$content-brief` |
+| Strategy revision needed | → back to `$audience-analysis` / `$platform-strategy` |
+
+When handing off — use `$handoff` attaching the calendar and the balance summary.
+
+## Integration with other skills
+
+| Skill | Interaction |
+|------|----------------|
+| `$audience-analysis` | **Source:** personas, pain points, triggers → topics |
+| `$platform-strategy` | **Source:** platforms, frequency, formats, timing |
+| `$competitor-content-analysis` | **Source:** gaps → topics and formats |
+| `$trend-research` | **Source:** trends → situational content |
+| `$tone-of-voice` | **Source:** tone for each persona |
+| `$content-brief` | **Consumer:** each calendar unit → brief by ID |
+| `$board` | Update content production progress |
+
+## Anti-patterns
+
+| Error | Why it's bad | How to do it right |
+|--------|-------------|---------------|
+| Everything is sales | Audience gets tired, unfollows | Sales content ≤ 25% |
+| No TOFU | No new audience acquisition | TOFU 40-50% every week |
+| Topics without an angle | "SEO" is not a topic | A specific angle: "Why alt-tags beat meta titles" |
+| No persona attached | Content "for everyone" = for no one | Every post is for a specific persona |
+| Calendar without a buffer | One sick day breaks the chain | 1-2 slots a week = buffer / situational |
+| Forgotten holidays | Competitors celebrate, you fall silent | Jot down key events prior to planning |
+| No cross-posting | Content is made 1 time for 1 platform | One piece of content → 2-3 adaptations |
+| Identical formats | Everything is text zero visuals | Alternate formats, ≤ 50% of one type |
+| Missing deadlines | Content won't be ready for publish date | Backward countdown from publish date |
+
+## Output Template
+
+```
+### Content Calendar — [Period: date — date]
+
+**Horizon:** [week / month / quarter / campaign]
+**Business priority for the period:** [awareness / leads / sales / launch]
+**Platforms:** [list]
+**Personas:** [list from $audience-analysis]
+
+---
+
+#### Period Events
+| Date | Event | Type | Relevance |
+|------|-----------|-----|---------------|
+| [date] | [event] | [holiday / industry / product / season] | [high / medium] |
+
+#### Recurring Pillars
+| Day | Pillar | Format | Content type | Persona |
+|------|---------|--------|-------------|---------|
+| Mon | [pillar name] | [format] | [type] | [persona] |
+| Wed | [pillar name] | [format] | [type] | [persona] |
+| Fri | [pillar name] | [format] | [type] | [persona] |
+
+---
+
+#### Calendar
+
+| ID | Date | Day | Topic | Persona | Funnel | Type | Format | Platform | Cross-posting | Text Deadline | Visual Deadline | Status |
+|----|------|------|------|---------|---------|-----|--------|-----------|---------------|----------------|-----------------|--------|
+| IG-20260407-01 | 04/07 | Mon | [topic] | [persona] | TOFU | Educational | Carousel | Instagram | TG (adaptation) | 04/04 | 04/05 | [ ] |
+| TG-20260407-01 | 04/07 | Mon | ↳ adaptation IG-20260407-01 | [persona] | TOFU | Educational | Post | Telegram | — | 04/05 | — | [ ] |
+| IG-20260409-01 | 04/09 | Wed | [topic] | [persona] | MOFU | Sales | Reel | Instagram | — | 04/06 | 04/07 | [ ] |
+
+---
+
+#### Balance Summary
+
+**Content Mix:**
+| Type | Count | % | Norm | Status |
+|-----|-----------|---|-------|--------|
+| Educational | [N] | [%] | 30-40% | ✅/⚠️ |
+| Sales | [N] | [%] | 15-25% | ✅/⚠️ |
+| Entertainment | [N] | [%] | 15-20% | ✅/⚠️ |
+| Image | [N] | [%] | 10-15% | ✅/⚠️ |
+| Community | [N] | [%] | 10-15% | ✅/⚠️ |
+
+**Funnel:**
+| Stage | Count | % | Norm | Status |
+|------|-----------|---|-------|--------|
+| TOFU | [N] | [%] | 40-50% | ✅/⚠️ |
+| MOFU | [N] | [%] | 30-35% | ✅/⚠️ |
+| BOFU | [N] | [%] | 15-25% | ✅/⚠️ |
+
+**Personas:**
+| Persona | Count | % | Priority | Status |
+|---------|-----------|---|-----------|--------|
+| [Persona 1] | [N] | [%] | ⭐ Priority | ✅/⚠️ |
+| [Persona 2] | [N] | [%] | Secondary | ✅/⚠️ |
+
+**Formats:**
+| Format | Count | % | Status (≤50%) |
+|--------|-----------|---|---------------|
+| [format] | [N] | [%] | ✅/⚠️ |
+
+---
+
+**Total for the period:**
+- Publications: [N] (of which [M] cross-posting)
+- Platforms: [list]
+- Buffer slots: [N]
+
+**→ Next step:** create a `$content-brief` for each unit, beginning with the closest dates
+```

package/domains/content/locales/en/.agents/skills/content-release-gate/SKILL.md

@@ -0,0 +1,237 @@
+---
+name: content-release-gate
+description: Final gate prior to publication — artifact check, blocker/non-blocker checklist, publication package, rollback, post-publish
+---
+# Content Release Gate
+
+## When to use
+- After **passing all pipeline gates** (Reviewer yielded APPROVED).
+- Preceding the **final publication** of any content unit.
+- During **re-publication** after a HOLD — verifying that blockers have been resolved.
+
+## Input
+
+| Field | Required | Source |
+|------|:-----------:|----------|
+| Final text (APPROVED) | ✅ | Copywriter → Reviewer |
+| Visual brief / final visual | ✅ | Visual Concept → Reviewer |
+| AI-prompts for images | ⬚ | Visual Concept (if generated via AI) |
+| `$brand-compliance` result | ✅ | Reviewer — status COMPLIANT |
+| `$fact-checking` result | ✅ | Reviewer — status VERIFIED |
+| `$readability-scoring` result | ⬚ | Reviewer — if applicable to the format |
+| `$platform-compliance` result | ✅ | Reviewer — compliance with platform rules |
+| Content brief (ID) | ✅ | `$content-brief` — to verify goal, CTA, persona |
+| Publication date | ✅ | `$content-calendar` |
+
+> If any required artifact is missing or possesses a status other than APPROVED/COMPLIANT/VERIFIED — the Release Gate **cannot be initiated**. Return it to the appropriate gate.
+
+## Protocol
+
+### Step 1 — Artifact Collection and Verification
+1. Ensure **all mandatory artifacts** from the table above have been procured.
+2. Verify the **status of each**: APPROVED / COMPLIANT / VERIFIED.
+3. If anything is missing → mark it as a blocker, do not proceed.
+
+### Step 2 — Final Checklist
+Walk through all checklist items (see template). Every item carries a severity level:
+- **🔴 Blocker** — publication is impossible until amended.
+- **🟡 Warning** — publication is possible, but amendment is recommended.
+
+### Step 3 — Status Determination
+
+| Status | Condition |
+|--------|---------|
+| **READY TO PUBLISH** | 0 blockers · 0 or more warnings (logged, user is aware) |
+| **HOLD** | ≥ 1 blocker · publication is forbidden until resolved |
+
+### Step 4 — Formulating the Publication Package
+If `READY TO PUBLISH` — assemble the entire package (see template):
+1. Final text (copy-pasteable, in platform format).
+2. Hashtags (if applicable).
+3. Links with UTM trackers (if applicable).
+4. Visual — file or AI-prompt for generation.
+5. Platform settings — dimensions, alt-text, thumbnail.
+6. Schedule — exact publication time.
+
+### Step 5 — User Sign-Off
+Present to user:
+- The final checklist with results.
+- The publication package.
+- Anticipate an explicit **"Approved"**.
+
+### Step 6 — Post-publish Actions
+Upon receiving Approved and publishing:
+1. Update `$board` — Release Gate → `[✓] Finished`.
+2. Update `$content-calendar` — content unit → status `Done`.
+3. Log the outcome into the domain's `CONTEXT.md`.
+4. Schedule monitoring (if determined): tracking metrics after 24h / 48h / 7 days.
+
+## Rollback Protocol
+
+When in **HOLD** status — the rollback routing depends on the blocker type:
+
+| Blocker type | Return to | Action |
+|-------------|-------------|------------|
+| Text is not approved / errors in text | → Copywriter | Amend → repeat Reviewer |
+| Brand compliance NON-COMPLIANT | → Copywriter / Visual Concept | Resolve violations from `$brand-compliance` report |
+| Facts unverified | → Researcher | Double-check/replace facts → `$fact-checking` |
+| Visual non-compliant | → Visual Concept | Amend → repeat Reviewer |
+| Platform compliance violated | → Copywriter / Visual Concept | Adapt to the rules of the platform |
+| CTA mismatches brief | → Copywriter | Rework CTA taking `$content-brief` into account |
+| Legal blocker | → User | Escalation: disclaimer, copyright, permissions |
+
+Upon rollback:
+1. Update `$board` — current gate `[↩] Rollback`, target gate `[→] In progress`.
+2. Handoff via `$handoff` — explicitly indicating the blockers and what to amend.
+3. After amendment — **repeat Release Gate** (do not skip).
+
+## Validation (Quality Gate)
+
+A Release Gate is deemed successfully traversed if:
+
+- [ ] All mandatory artifacts are gathered and hold the requisite status
+- [ ] Checklist is processed completely — every item is marked ✅ or ❌ along with an explanation
+- [ ] No unresolved blockers exist (🔴 = 0)
+- [ ] Warnings are logged and the user has been notified
+- [ ] Publication package is thoroughly fashioned (text + visual + meta)
+- [ ] User sign-off acquired
+- [ ] Post-publish activities are complete (board, calendar, CONTEXT.md)
+
+## Integration with other skills
+
+| Skill | Interaction |
+|------|----------------|
+| `$brand-compliance` | **Input:** review result — COMPLIANT is mandatory |
+| `$fact-checking` | **Input:** result — VERIFIED is mandatory |
+| `$readability-scoring` | **Input:** result — if applicable to the format |
+| `$platform-compliance` | **Input:** adherence to platform rules |
+| `$content-brief` | **Input:** comparing CTA, goal, persona against the final content |
+| `$content-calendar` | **Input:** publication date · **Update:** status → Done |
+| `$board` | **Update:** gate → `[✓]` or `[↩]` |
+| `$handoff` | For rollback — handoff denoting blockers |
+| `$content-review-checklist` | Complementary: review checklist must be passed prior to Release Gate |
+
+## Anti-patterns
+
+| Error | Why it's bad | How to do it right |
+|--------|-------------|---------------|
+| Release Gate without Reviewer APPROVED | Unverified content gets published | Mandatory verification of Reviewer status |
+| Checklist items carry identical weight | A triviality blocks, a criticality passes | Blocker / Warning stratification |
+| HOLD without a rollback route | Unclear who amends what | Rollback table providing specific routing |
+| Package devoid of UTMs / hashtags | Analytics lost, brand disrupted | Complete package with metadata intact |
+| Publishing sans user sign-off | The user hasn't seen the final version | Always wait for explicit Approved |
+| Lack of post-publish updates | Board and calendar desync | Update board, calendar, CONTEXT.md |
+| Reiterating release minus repeating checklist | A blocker might endure | Full checklist executed during each pass |
+
+## Output Template
+
+```
+### Content Release Gate — [Content unit ID]
+
+**Publication Date:** [date from $content-calendar]
+**Platform:** [platform]
+**Format:** [format]
+**Persona:** [from $content-brief]
+**Responsible for publishing:** [who]
+**Repeat pass:** [No / Yes (iteration N — blockers from preceding: [list])]
+
+---
+
+#### 1. Artifact Verification
+
+| Artifact | Source | Status | Blocker? |
+|----------|----------|--------|----------|
+| Final text | Copywriter → Reviewer | ✅ APPROVED / ❌ | 🔴 |
+| Visual | Visual Concept → Reviewer | ✅ APPROVED / ❌ | 🔴 |
+| AI-prompts | Visual Concept | ✅ / N/A | — |
+| Brand compliance | `$brand-compliance` | ✅ COMPLIANT / ❌ | 🔴 |
+| Fact checking | `$fact-checking` | ✅ VERIFIED / ❌ | 🔴 |
+| Readability | `$readability-scoring` | ✅ / N/A | 🟡 |
+| Platform compliance | `$platform-compliance` | ✅ / ❌ | 🔴 |
+
+---
+
+#### 2. Final Checklist
+
+**Text:**
+- [ ] 🔴 Text conforms to the brief (topic, theses, persona) 
+- [ ] 🔴 CTA aligns with the brief and funnel stage
+- [ ] 🔴 ToV aligns with `$brand-guidelines`
+- [ ] 🔴 Free from grammatical / orthographic errors
+- [ ] 🟡 Readability score falls within permissible bounds
+
+**Visual:**
+- [ ] 🔴 Dimensions align with the platform
+- [ ] 🔴 Visual conforms to `$brand-guidelines`
+- [ ] 🟡 Alt-text is appended (for accessibility)
+
+**Meta and Links:**
+- [ ] 🔴 Links are functional (verified)
+- [ ] 🟡 UTM trackers appended (if any links exist)
+- [ ] 🟡 Brand hashtags deployed
+- [ ] 🔴 Disclaimer / © present (if mandated)
+
+**Platform:**
+- [ ] 🔴 Format meets platform requirements (character-count, dimensions, duration)
+- [ ] 🟡 Publication time is optimal (from `$platform-strategy`)
+- [ ] 🔴 Platform rules are not violated
+
+---
+
+#### 3. Result
+
+**Blockers (🔴):** [N] — [list, if any]
+**Warnings (🟡):** [N] — [list, if any]
+
+### Status: [ READY TO PUBLISH / HOLD ]
+
+**Rationale:** [reason for the status]
+
+---
+
+#### 4. Publication Package (if READY TO PUBLISH)
+
+**Text:**
+```
+[Final text — copy-pasteable]
+```
+
+**Hashtags:** [list]
+
+**Links:**
+| Link | UTM | Destination |
+|--------|-----|------------|
+| [URL] | [utm_source=...&utm_medium=...] | [where it leads] |
+
+**Visual:**
+- File / prompt: [link or AI-prompt]
+- Size: [WxH px]
+- Alt-text: [text]
+
+**Schedule:**
+- Date: [YYYY-MM-DD]
+- Time: [HH:MM] [time zone]
+- Platform: [platform]
+
+**Cross-posting:** [platforms + what's adapted / "No"]
+
+---
+
+#### 5. Routing (if HOLD)
+
+| Blocker | Type | Return to | What to amend |
+|--------|-----|-------------|---------------|
+| [blocker 1] | [text / visual / legal] | → [agent] | [specific action] |
+
+→ Put through a repeat Release Gate after amendment.
+
+---
+
+→ Awaiting final "Approved" for publication
+
+#### 6. Post-publish (after Approved)
+- [ ] `$board` — Release Gate → `[✓] Finished`
+- [ ] `$content-calendar` — ID [X] → status `Done`
+- [ ] `CONTEXT.md` — log publication 
+- [ ] Monitoring scheduled: [24h / 48h / 7 days — metrics from $content-brief]
+```