expxagents 0.1.0

package/assets/core/best-practices/sprint-planning.md

@@ -0,0 +1,91 @@
+---
+platform: software-house
+format: sprint-planning
+constraints:
+  max_chars: null
+  image_ratio: null
+  max_hashtags: null
+---
+
+# Best Practices: Sprint Planning
+
+## Core Principles
+
+Sprint planning transforms the product backlog into a committed, achievable sprint goal. A good sprint planning session is time-boxed, collaborative, and results in a shared understanding of what done looks like.
+
+- **Commitment, not forecast.** The team commits to a goal; ticket count is an estimate.
+- **Definition of Done must be agreed before work starts, not after.**
+- **Sprint goal over ticket list.** A sprint with one clear objective is better than a full sprint board with no coherent direction.
+- **Two-week sprints are the default.** Shorter is faster feedback; longer creates inertia.
+
+## Pre-Planning Checklist (Product Owner / Scrum Master)
+
+- [ ] Product backlog is groomed: top 2 sprints worth of stories are estimated and have acceptance criteria
+- [ ] Sprint goal drafted and ready to propose to the team
+- [ ] Previous sprint retrospective action items reviewed
+- [ ] Dependencies on other teams identified and resolved or documented
+- [ ] Team availability confirmed (holidays, OOO) for sprint duration
+
+## Sprint Planning Meeting Structure (2 hours for 2-week sprint)
+
+### Part 1: What (45 minutes)
+1. Present the sprint goal (Product Owner, 5 minutes)
+2. Review top backlog items (10 minutes)
+3. Team asks clarifying questions on each story (15 minutes)
+4. Team confirms which stories they can commit to (15 minutes)
+
+### Part 2: How (75 minutes)
+1. Break accepted stories into tasks (30 minutes)
+2. Assign or self-assign tasks (15 minutes)
+3. Identify risks and blockers (15 minutes)
+4. Finalize sprint board (15 minutes)
+
+## Story Format (User Story Template)
+
+```
+As a [type of user],
+I want [a goal],
+So that [a reason / benefit].
+
+Acceptance Criteria:
+- [ ] Given [precondition], when [action], then [expected result]
+- [ ] Given [precondition], when [action], then [expected result]
+- [ ] Edge case: [specific scenario handled correctly]
+
+Definition of Done:
+- [ ] Code reviewed and approved
+- [ ] Unit tests written and passing
+- [ ] Acceptance criteria verified by QA
+- [ ] Deployed to staging
+- [ ] Documentation updated (if applicable)
+```
+
+## Story Point Estimation
+
+Use Fibonacci sequence (1, 2, 3, 5, 8, 13, 21) with this anchor:
+
+| Points | Meaning |
+|--------|---------|
+| 1 | Under 1 hour; trivial change |
+| 2 | Half a day; straightforward |
+| 3 | One day; clear but requires care |
+| 5 | 2–3 days; some unknowns |
+| 8 | 4–5 days; significant unknowns; consider splitting |
+| 13+ | Too large; must be broken down |
+
+## Velocity and Capacity
+
+- Calculate team capacity: `(team members) × (workdays) × (focus factor 0.7)`
+- Focus factor accounts for meetings, interruptions, and non-sprint work
+- Use trailing 3-sprint average velocity for planning; do not inflate
+- Reserve 10–15% of capacity for bugs, unplanned work, and tech debt
+
+## Guidelines
+
+- Stories without acceptance criteria are not ready for sprint planning — send them back to backlog refinement.
+- A story larger than 5 points must be split before it enters the sprint.
+- The team should define the sprint goal collectively — the PO proposes; the team refines.
+- Planning poker: use simultaneous reveal to prevent anchoring bias.
+- Technical tasks (refactors, infrastructure) belong in the sprint alongside feature work — track them explicitly.
+- Keep a "stretch goal" list of 1–2 stories the team can pull if they finish early.
+- If planning takes more than 2 hours for a 2-week sprint, the backlog is not adequately groomed.

package/assets/core/best-practices/strategist.md

@@ -0,0 +1,95 @@
+---
+platform: universal
+format: strategy
+constraints:
+  max_chars: null
+  image_ratio: null
+  max_hashtags: null
+---
+
+# Best Practices: Content and Marketing Strategy
+
+## Core Principles
+
+Strategy is the set of choices that determines where to focus, what to build, and what to ignore. A strategy without constraints is just a wish list.
+
+- **Start with the business goal, not the content idea.** Every content piece should map to a measurable business outcome.
+- **Choose a lane.** Trying to be everywhere at once leads to mediocrity everywhere. Dominate one platform, one format, one audience segment first.
+- **Measure what matters.** Vanity metrics (followers, impressions) are inputs. Revenue, leads, and retention are outputs. Strategy serves outputs.
+
+## Strategic Frameworks
+
+### OKR Alignment (Objectives and Key Results)
+```
+Objective: [What are we trying to achieve?]
+KR1: [Measurable milestone 1]
+KR2: [Measurable milestone 2]
+KR3: [Measurable milestone 3]
+Content initiatives that serve this OKR: [list]
+```
+
+### Audience-First Mapping
+1. Define the primary audience persona (1 person, not a demographic)
+2. Identify their top 3 pain points
+3. Identify their top 3 aspirations
+4. Map content topics to pain/aspiration intersections
+5. Match each topic to a stage of the buyer journey (Awareness / Consideration / Decision)
+
+### Content Pillars Framework
+- Define 3–5 core content pillars (themes you will consistently own)
+- Each pillar should be: relevant to your audience, differentiated from competitors, sustainable to produce
+- Distribute content production across pillars (e.g., 40% / 30% / 20% / 10%)
+
+### SOSTAC Planning
+- **Situation** — Where are we now? (audit)
+- **Objectives** — Where do we want to go? (SMART goals)
+- **Strategy** — How will we get there? (positioning, audience, channels)
+- **Tactics** — What specifically will we do? (editorial calendar, campaigns)
+- **Action** — Who does what, when? (roles, timelines)
+- **Control** — How will we measure success? (KPIs, reporting cadence)
+
+## Structure (Strategy Document)
+
+```
+[EXECUTIVE SUMMARY — 1 page]
+
+[SITUATION ANALYSIS]
+- Current state: channels, metrics, audience
+- Competitive landscape
+- SWOT analysis
+
+[GOALS AND KPIs]
+- Primary goal
+- 3–5 measurable KPIs with targets and timelines
+
+[AUDIENCE]
+- Primary persona
+- Secondary persona (if applicable)
+- Buyer journey map
+
+[POSITIONING]
+- Unique point of view / differentiated angle
+- Tone of voice and brand personality
+
+[CHANNEL AND FORMAT STRATEGY]
+- Priority channels (ranked 1–3)
+- Content formats per channel
+- Publishing frequency
+
+[EDITORIAL CALENDAR GUIDELINES]
+- Content pillars and distribution
+- Campaign themes (quarterly or monthly)
+
+[MEASUREMENT AND REPORTING]
+- Reporting frequency
+- Dashboard or tool
+- Review and iteration process
+```
+
+## Guidelines
+
+- Build a 90-day strategy, not a 12-month plan. Markets change; plans should too.
+- Separate strategy (direction) from tactics (execution). Do not write tactics inside a strategy document.
+- Validate assumptions with data before committing resources. A 2-week test costs less than a failed quarter.
+- Document the "why not" for channels and formats you're deliberately excluding — it prevents strategy drift.
+- Review performance monthly; adjust quarterly; rewrite the strategy annually.

package/assets/core/best-practices/technical-writing.md

@@ -0,0 +1,104 @@
+---
+platform: universal
+format: technical-writing
+constraints:
+  max_chars: null
+  image_ratio: null
+  max_hashtags: null
+---
+
+# Best Practices: Technical Writing
+
+## Core Principles
+
+Technical writing translates complex information into clear, accurate, and usable documentation for a defined audience. Clarity and completeness are non-negotiable.
+
+- **Know your audience's technical level.** A document for end-users is written differently from one for developers or system administrators.
+- **One document, one purpose.** A reference guide, a tutorial, and a troubleshooting guide are three different documents — do not conflate them.
+- **Accuracy is correctness, not precision.** Technical writing must be correct, complete, and current.
+
+## Document Types
+
+| Type | Purpose | Structure |
+|------|---------|-----------|
+| Tutorial | Learning-oriented; guides through a task | Step-by-step, linear |
+| How-to Guide | Task-oriented; solves a specific problem | Steps + prerequisites |
+| Reference | Information-oriented; lookup resource | Tables, definitions, indexes |
+| Explanation | Understanding-oriented; concept clarity | Narrative, diagrams |
+
+## Structure
+
+```
+[TITLE — action-verb + topic, e.g., "Configure SSL Certificates"]
+
+[OVERVIEW — 2–4 sentences]
+- What this document covers
+- Who it is for
+- Prerequisites or assumed knowledge
+
+[PREREQUISITES]
+- Software versions, permissions, or prior steps required
+
+[PROCEDURE / CONTENT]
+- For step-by-step: numbered steps, one action per step
+- Code blocks for all commands, file paths, and code snippets
+- Expected output shown after each command
+- Notes, warnings, and tips called out in admonition blocks
+
+[VERIFICATION]
+- How to confirm the procedure was successful
+
+[TROUBLESHOOTING]
+- Common errors and their resolutions
+
+[NEXT STEPS / RELATED DOCS]
+- Links to follow-on documentation
+```
+
+## Guidelines
+
+- **Active voice.** "Click Save" not "Save should be clicked."
+- **Present tense.** "The system returns a 200 status code" not "the system will return."
+- Avoid "you" when the subject is the system: "The installer prompts you" not "you will be prompted."
+- Use admonition blocks consistently:
+  - **Note:** supplementary, non-critical information
+  - **Warning:** potential data loss, security, or breaking change
+  - **Tip:** shortcut or best practice
+- Code blocks must specify the language for syntax highlighting.
+- Every parameter, flag, and argument should be documented — not just the ones you think people will use.
+- Version-stamp documents that apply to specific software releases.
+- Docs-as-code: treat documentation source files like code — version control, review, and CI/CD checks.
+- Screenshots: annotate with numbered callouts; never rely solely on a screenshot without text explanation.
+
+## Formatting Standards
+
+- Headings: sentence case ("Configure the database" not "Configure The Database")
+- File paths: `monospace` format
+- UI elements: **bold** ("Click **Save**")
+- Code inline: `monospace` single backtick
+- Code blocks: triple backtick with language identifier
+- Lists: numbered for sequential steps, bulleted for non-sequential items
+
+## Examples
+
+**Step format:**
+```
+1. Open a terminal and run the following command:
+
+   ```bash
+   npm install --save-dev jest
+   ```
+
+   Expected output:
+   ```
+   added 287 packages in 4.2s
+   ```
+
+2. Create a configuration file named `jest.config.js` in your project root.
+```
+
+**Warning admonition:**
+```
+> **Warning:** Running this command permanently deletes all data in the specified
+> database. Ensure you have a current backup before proceeding.
+```

package/assets/core/best-practices/twitter-post.md

@@ -0,0 +1,75 @@
+---
+platform: twitter-x
+format: post
+constraints:
+  max_chars: 280
+  image_ratio: "16:9"
+  max_hashtags: 2
+---
+
+# Best Practices: Twitter/X — Post
+
+## Format Rules
+
+- Character limit: 280 characters (URLs count as 23 characters regardless of length)
+- Images: 1200x675px (16:9) or 1200x1200px (square); up to 4 images per tweet
+- Hashtags reduce reach on X — use 1–2 maximum, only when directly relevant
+- Polls: up to 4 options, 1–7 day duration
+- Threads are linked posts; the opener is the most important tweet
+- Quoted tweets with commentary outperform bare retweets
+
+## Structure
+
+```
+[SINGLE POWERFUL STATEMENT or QUESTION]
+— or —
+[SHORT NUMBERED LIST — 3–5 items max, each under 40 characters]
+— or —
+[NARRATIVE HOOK that demands a thread reply or comment]
+```
+
+## Guidelines
+
+- **Brevity is authority.** If you need more than 200 characters, consider whether this should be a thread.
+- One idea per tweet. Cramming multiple points kills impact.
+- Use line breaks (return key) to create visual rhythm — it stops the scroll.
+- The best-performing tweet formats on X: hot takes, contrarian opinions, numbered lists, specific advice.
+- Questions that are easy to answer (binary, fill-in-the-blank) generate the most replies.
+- Avoid hashtags in post body — place them at the end or omit entirely.
+- Engage with replies within the first 30 minutes to boost the tweet's reach.
+- Images and alt text: always add alt text to images for accessibility.
+- Repost your own top-performing content every 3–6 months — new followers haven't seen it.
+
+## Examples
+
+**Hot take format:**
+```
+Productivity apps don't make you productive.
+
+Knowing your one most important task today does.
+```
+
+**List format:**
+```
+5 signs you're actually making progress (even when it feels slow):
+
+• You're asking better questions
+• Old problems no longer bother you
+• You're saying no more often
+• Sleep is intentional, not collapsed
+• You enjoy the process
+```
+
+**Question format:**
+```
+What's one thing you stopped doing that improved your life more than you expected?
+```
+
+**CTA format (for threads):**
+```
+I spent 6 months studying how top creators build audiences.
+
+Here are the 7 patterns nobody talks about:
+
+🧵 Thread below 👇
+```

package/assets/core/best-practices/twitter-thread.md

@@ -0,0 +1,92 @@
+---
+platform: twitter-x
+format: thread
+constraints:
+  max_chars: 280
+  image_ratio: "16:9"
+  max_hashtags: 2
+---
+
+# Best Practices: Twitter/X — Thread
+
+## Format Rules
+
+- Each tweet in a thread: 280 characters max
+- Ideal thread length: 7–20 tweets (shorter threads under 5 feel incomplete; longer than 20 see steep drop-off)
+- Number each tweet (1/, 2/, etc.) for clarity and navigation
+- The opening tweet (Tweet 1) is the only one that appears in feeds — it drives the entire thread's performance
+- Use "🧵" symbol to signal a thread is coming
+
+## Structure
+
+```
+Tweet 1: [HOOK — standalone statement that demands to be read]
+"[Provocative claim, specific number, or powerful question]"
+"A thread: 🧵"
+
+Tweet 2: [SETUP — frame the problem or context]
+
+Tweets 3–N: [CONTENT — one idea per tweet]
+- Use numbered sub-lists inside tweets when listing within a point
+- Add an image or screenshot to key tweets to increase dwell time
+- Plant cliffhangers at the end of every 3rd tweet ("But that's not the hardest part...")
+
+Second-to-last tweet: [KEY TAKEAWAY — most shareable line in the entire thread]
+
+Final Tweet: [CTA]
+"If this was useful:
+• RT the first tweet to share it
+• Follow me for more on [topic]
+• Reply with your biggest question"
+```
+
+## Guidelines
+
+- **The hook tweet must work as a standalone post.** It appears in feeds without context; it must be compelling enough to make someone tap to read the full thread.
+- Each tweet should deliver one clear, actionable or informative idea.
+- Use cliffhangers to maintain scroll momentum: "But there's a catch...", "Here's where most people get it wrong..."
+- Strong thread topics: personal stories with lessons, numbered frameworks, step-by-step tutorials, debunking myths.
+- Vary tweet length — alternate between 1-line punches and 3-line paragraphs.
+- Use images, screenshots, or charts for tweets that reference data or comparisons.
+- The summary tweet (second-to-last) should be the most RT-able tweet in the thread.
+- Schedule threads with a tool like Buffer or TweetDeck to go live at peak engagement hours.
+
+## Examples
+
+**Opening tweet:**
+```
+I grew a newsletter from 0 to 50,000 subscribers in 18 months with no paid ads.
+
+Here's the exact playbook I'd use if I was starting over today:
+
+🧵
+```
+
+**Mid-thread cliffhanger:**
+```
+7/ That strategy alone doubled my open rates.
+
+But the biggest mistake I see creators make has nothing to do with content.
+
+It's this 👇
+```
+
+**Summary tweet:**
+```
+17/ Quick recap:
+
+• Hook is the only thing that matters at first
+• One platform, one format, until it works
+• Email > followers
+• Ship daily for 30 days before judging results
+• Compounding beats viral every time
+```
+
+**CTA tweet:**
+```
+18/ If this was useful:
+
+→ RT Tweet 1 to help someone else
+→ Follow @handle for one thread like this per week
+→ What topic should I cover next? Drop it below 👇
+```

package/assets/core/best-practices/whatsapp-broadcast.md

@@ -0,0 +1,95 @@
+---
+platform: whatsapp
+format: broadcast
+constraints:
+  max_chars: 4096
+  image_ratio: null
+  max_hashtags: null
+---
+
+# Best Practices: WhatsApp — Broadcast Message
+
+## Format Rules
+
+- Message length: under 300 words for broadcasts; under 150 words for promotional messages
+- Character limit: 4096 characters per message
+- WhatsApp Business API: supports text, images, documents, and approved message templates
+- Template messages (HSM): must be pre-approved by Meta for outbound messaging to opted-in contacts
+- Emojis: supported and expected — they increase readability and warmth in this channel
+- Media: images (JPEG/PNG, max 5MB), documents (PDF, max 100MB), video (MP4, max 16MB)
+- Opt-in: GDPR/LGPD compliance requires explicit opt-in before any broadcast
+
+## Structure
+
+```
+[GREETING — personalized opener]
+"Hi {first_name} 👋"
+
+[CONTEXT — 1 sentence]
+Brief, warm reference to why you're messaging
+
+[CORE MESSAGE — 2–4 short paragraphs]
+- One idea per paragraph
+- Use line breaks generously
+- Emojis for visual hierarchy (not decoration)
+- Bold text: *bold* using asterisks
+
+[CTA — single, clear action]
+- "Reply YES to confirm"
+- "Tap the link below"
+- "Reply with your question"
+
+[LINK or ATTACHMENT — if applicable]
+[Brand sign-off or contact info]
+```
+
+## Guidelines
+
+- **WhatsApp is the most intimate digital channel.** Write like a trusted contact, not a brand — formal marketing language kills response rates.
+- Keep lines short — 1–2 sentences each. WhatsApp is read on mobile; long lines are exhausting.
+- Use emojis as visual bullets and to convey tone, but avoid overloading (max 1–2 per paragraph).
+- Response window: WhatsApp Business API allows messaging contacts within 24 hours of their last message; templates are required outside this window.
+- Never send broadcast messages without explicit opt-in — WhatsApp bans accounts for spam complaints.
+- Broadcast vs. group: broadcasts are sent individually (recipient sees it as a direct message); use groups only for community-style communication.
+- Timing: avoid sending between 10 PM and 8 AM local time. Mid-morning (10–11 AM) and early evening (7–8 PM) see highest read rates.
+- Always include an opt-out instruction: "Reply STOP to unsubscribe."
+
+## Examples
+
+**Promotional broadcast:**
+```
+Hi {first_name} 👋
+
+It's [Brand Name] here.
+
+We just launched something you asked for — and it's live today only. 🚀
+
+✅ [Feature/Product name]
+✅ [Key benefit 1]
+✅ [Key benefit 2]
+
+Available until midnight tonight.
+
+👉 [link]
+
+Questions? Just reply here.
+
+— [Team Name]
+
+_Reply STOP to unsubscribe._
+```
+
+**Appointment reminder:**
+```
+Hi {first_name},
+
+Just a reminder that your appointment with [Name] is confirmed for:
+
+📅 *{date}*
+🕐 *{time}*
+📍 *{location or link}*
+
+Need to reschedule? Reply here and we'll sort it out.
+
+See you soon! 😊
+```

package/assets/core/best-practices/youtube-script.md

@@ -0,0 +1,80 @@
+---
+platform: youtube
+format: video-script
+constraints:
+  max_chars: null
+  image_ratio: "16:9"
+  max_hashtags: null
+---
+
+# Best Practices: YouTube — Video Script
+
+## Format Rules
+
+- Aspect ratio: 16:9 (1920x1080px minimum; 4K preferred for future-proofing)
+- Thumbnail: 1280x720px, high contrast, legible text under 6 words, faces with visible emotion perform best
+- Title: 60–70 characters for full visibility in search results
+- Description: first 150 characters shown in search; include primary keyword in first line
+- Chapters (timestamps) in description significantly improve watch time and SEO
+- Cards and end screens should be added in editor (script the verbal CTA at minute 1 and at the end)
+
+## Structure
+
+```
+[0:00–0:30 — HOOK]
+- Open with the payoff: show the result, state the controversial claim, or pose the problem
+- Do NOT start with "Hey guys, welcome back..."
+- Say: "By the end of this video, you will [specific outcome]"
+
+[0:30–2:00 — SETUP]
+- Why this topic matters now
+- Briefly establish your credibility on this topic (1–2 sentences)
+- Verbal chapter preview: "First we'll cover X, then Y, then I'll show you exactly how to Z"
+
+[2:00–END-2:00 — MAIN CONTENT]
+- Divide into 3–5 chapters
+- Each chapter: one clear idea, one example, one actionable takeaway
+- Include B-roll cues in brackets: [show screen recording], [cut to example]
+- At 1/3 and 2/3 mark: soft re-hook ("If you're still with me, here's the part most people miss...")
+
+[END-2:00–END — CTA + OUTRO]
+- Verbal subscribe ask: "If this helped, subscribe — I post [frequency] on [topic]"
+- Next video teaser: "In the next video, I'm going to show you..."
+- End screen: 20 seconds of outro with video recommendation card visible
+```
+
+## Guidelines
+
+- **Retention is the primary metric.** YouTube ranks videos based on watch time percentage and absolute watch hours.
+- Write scripts at a slightly higher pace than you speak naturally — you'll slow down in delivery.
+- Hook must deliver on the thumbnail and title promise within 30 seconds or risk high early drop-off.
+- Use pattern interrupts every 90–120 seconds: cut to a different camera angle, show a graphic, change tone.
+- Write conversationally — use contractions, second-person ("you"), and short sentences.
+- Include a soft CTA at the 1-minute mark: "Subscribe so you don't miss the next part."
+- Research the top 5 ranked videos for your target keyword and structure your video to be more comprehensive.
+- Add manual closed captions or accurate auto-captions — they improve search indexing and accessibility.
+
+## Examples
+
+**Hook script:**
+```
+[Open on result screen or dramatic visual]
+
+"Most people waste months trying to figure this out on their own. I'm going to save you all of that time in the next 12 minutes."
+
+[Cut to camera]
+
+"Welcome. In this video, you'll learn exactly how to [specific outcome], step by step, even if you're starting from zero."
+```
+
+**Chapter transition:**
+```
+"Okay, so now you know [chapter 1 takeaway]. But here's where it gets really interesting — and this is the part most tutorials skip entirely..."
+```
+
+**End screen CTA:**
+```
+"If you got value from this, the subscribe button is right there — it doesn't cost anything and it helps the channel grow.
+
+And if you want to go deeper on [related topic], that video is right here. I'll see you in the next one."
+```