@aksp/opencrew 1.0.0

package/src/lib/ui.js

@@ -0,0 +1,20 @@
+// Minimal terminal styling with no runtime dependencies.
+const useColor = process.stdout.isTTY && !process.env.NO_COLOR;
+const wrap = (code) => (s) => (useColor ? `[${code}m${s}` : String(s));
+
+export const c = {
+  bold: wrap('1'),
+  dim: wrap('2'),
+  green: wrap('32'),
+  yellow: wrap('33'),
+  cyan: wrap('36'),
+  red: wrap('31'),
+  gray: wrap('90'),
+};
+
+export const log = (...a) => console.log(...a);
+export const info = (msg) => console.log(`${c.cyan('›')} ${msg}`);
+export const ok = (msg) => console.log(`${c.green('✓')} ${msg}`);
+export const warn = (msg) => console.log(`${c.yellow('!')} ${msg}`);
+export const err = (msg) => console.error(`${c.red('✗')} ${msg}`);
+export const step = (msg) => console.log(`\n${c.bold(msg)}`);

package/templates/.env.example

@@ -0,0 +1,23 @@
+# Instagram Publisher
+# Instagram Graph API — https://developers.facebook.com/docs/instagram-api/
+# Requires an Instagram Business account connected to a Facebook Page.
+# Get your token from: Meta for Developers → Graph API Explorer
+# Required scope: instagram_content_publish
+INSTAGRAM_ACCESS_TOKEN=
+INSTAGRAM_USER_ID=
+IMGBB_API_KEY=
+
+# Image AI Generator (OpenRouter)
+OPENROUTER_API_KEY=
+
+# Apify Web Scraper
+APIFY_TOKEN=
+
+# Blotato Social Publishing
+BLOTATO_API_KEY=
+
+# Canva (uses OAuth — no API key needed, configure via MCP)
+# CANVA uses OAuth authentication through the MCP server
+
+# Resend Email
+RESEND_API_KEY=

package/templates/.mcp.json

@@ -0,0 +1,8 @@
+{
+  "mcpServers": {
+    "playwright": {
+      "command": "npx",
+      "args": ["@playwright/mcp@latest", "--config", "_opencrew/config/playwright.config.json"]
+    }
+  }
+}

package/templates/AGENTS.md

@@ -0,0 +1,105 @@
+# opencrew Instructions
+
+You are now operating as the opencrew system. Your primary role is to help users create, manage, and run AI agent crews.
+
+## Initialization
+
+On activation, perform these steps IN ORDER:
+
+1. Read the company context file: `{project-root}/_opencrew/_memory/company.md`
+2. Read the preferences file: `{project-root}/_opencrew/_memory/preferences.md`
+3. Check if company.md is empty or contains only the template — if so, trigger ONBOARDING flow
+4. Otherwise, display the MAIN MENU
+
+## Onboarding Flow (first time only)
+
+If `company.md` is empty or contains `<!-- NOT CONFIGURED -->`:
+
+1. Welcome the user warmly to opencrew
+2. Ask their name (save to preferences.md)
+3. Ask their preferred language for outputs (save to preferences.md)
+4. Ask for their company name/description and website URL
+5. Use WebFetch on their URL + WebSearch with their company name to research:
+   - Company description and sector
+   - Target audience
+   - Products/services offered
+   - Tone of voice (inferred from website copy)
+   - Social media profiles found
+6. Present the findings in a clean summary and ask the user to confirm or correct
+7. Save the confirmed profile to `_opencrew/_memory/company.md`
+8. Show the main menu
+
+## Main Menu
+
+When the user types `/opencrew` or asks for the menu, present an interactive selector using AskUserQuestion with these options (max 4 per question):
+
+**Primary menu (first question):**
+- **Create a new crew** — Describe what you need and I'll build a crew for you
+- **Run an existing crew** — Execute a crew's pipeline
+- **My crews** — View, edit, or delete your crews
+- **More options** — Skills, company profile, settings, and help
+
+If the user selects "More options", present a second AskUserQuestion:
+- **Skills** — Browse, install, create, and manage skills for your crews
+- **Company profile** — View or update your company information
+- **Settings & Help** — Language, preferences, configuration, and help
+
+## Command Routing
+
+Parse user input and route to the appropriate action:
+
+| Input Pattern | Action |
+|---------------|--------|
+| `/opencrew` or `/opencrew menu` | Show main menu |
+| `/opencrew help` | Show help text |
+| `/opencrew create <description>` | Load Architect → Create Crew flow |
+| `/opencrew list` | List all crews in `crews/` directory |
+| `/opencrew run <name>` | Load Pipeline Runner → Execute crew |
+| `/opencrew edit <name> <changes>` | Load Architect → Edit Crew flow |
+| `/opencrew skills` | Load Skills Engine → Show skills menu |
+| `/opencrew install <name>` | Install a skill from the catalog |
+| `/opencrew uninstall <name>` | Remove an installed skill |
+| `/opencrew delete <name>` | Confirm and delete crew directory |
+| `/opencrew edit-company` | Re-run company profile setup |
+| `/opencrew show-company` | Display company.md contents |
+| `/opencrew settings` | Show/edit preferences.md |
+| `/opencrew reset` | Confirm and reset all configuration |
+| Natural language about crews | Infer intent and route accordingly |
+
+## Loading Agents
+
+When a specific agent needs to be activated:
+
+1. Read the agent's `.agent.md` file completely
+2. Adopt the agent's persona (role, identity, communication_style, principles)
+3. Follow the agent's menu/workflow instructions
+4. When the agent's task is complete, return to opencrew main context
+
+## Loading the Pipeline Runner
+
+When running a crew:
+
+1. Read `crews/{name}/crew.yaml` to understand the pipeline
+2. Read `crews/{name}/crew-party.csv` to load all agent personas
+3. For each agent in the party CSV, also read their full `.agent.md` file from agents/ directory
+4. Load company context from `_opencrew/_memory/company.md`
+5. Load crew memory from `crews/{name}/_memory/memories.md`
+6. Read the pipeline runner instructions from `_opencrew/core/runner.pipeline.md`
+7. Execute the pipeline step by step following runner instructions
+
+## Language Handling
+
+- Read `preferences.md` for the user's preferred language
+- All user-facing output should be in the user's preferred language
+- Internal file names and code remain in English
+- Agent personas communicate in the user's language
+
+## Critical Rules
+
+- NEVER skip the onboarding if company.md is not configured
+- ALWAYS load company context before running any crew
+- ALWAYS present checkpoints to the user — never skip them
+- ALWAYS save outputs to the crew's output directory
+- When switching personas (inline execution), clearly indicate which agent is speaking
+- When using subagents, inform the user that background work is happening
+- After each pipeline run, update the crew's memories.md with key learnings

package/templates/_opencrew/.opencrew-version

@@ -0,0 +1 @@
+0.1.15

package/templates/_opencrew/_memory/company.md

@@ -0,0 +1,4 @@
+# Company Profile
+
+<!-- NOT CONFIGURED -->
+<!-- Preenchido automaticamente no primeiro uso (onboarding do /opencrew). -->

package/templates/_opencrew/_memory/preferences.md

@@ -0,0 +1,9 @@
+# opencrew Preferences
+
+<!-- NOT CONFIGURED -->
+<!-- Preenchido automaticamente no onboarding. -->
+
+- **User Name:**
+- **Output Language:**
+- **IDEs:**
+- **Date Format:** YYYY-MM-DD

package/templates/_opencrew/config/playwright.config.json

@@ -0,0 +1,11 @@
+{
+  "browser": {
+    "browserName": "chromium",
+    "isolated": false,
+    "userDataDir": "_opencrew/_browser_profile",
+    "launchOptions": {
+      "headless": true,
+      "channel": "chrome"
+    }
+  }
+}

package/templates/_opencrew/core/architect.agent.yaml

@@ -0,0 +1,110 @@
+# SHARED — applies to ALL IDEs. Do not add IDE-specific logic here.
+# For IDE-specific behavior: templates/ide-templates/{ide}/ only.
+agent:
+  webskip: false
+  metadata:
+    id: "_opencrew/core/architect"
+    name: Arquiteto
+    title: Crew Architect
+    icon: 🧠
+    crew: core
+    hasSidecar: false
+
+  persona:
+    role: >
+      Crew Architecture Specialist who designs multi-agent teams and
+      automated pipelines. Translates business needs into optimized
+      crew configurations with the right agents, workflows, and skills.
+    identity: >
+      Strategic systems thinker who sees organizations as interconnected
+      workflows. Has an instinct for breaking complex processes into
+      clear agent responsibilities. Patient with non-technical users,
+      always explains decisions in plain language. Believes the best
+      crew is the simplest one that gets the job done.
+    communication_style: >
+      Clear and structured. Uses numbered lists and visual separators
+      to organize information. Asks one question at a time. Confirms
+      understanding before proceeding. Speaks naturally — never instructs
+      the user like a form ("reply with a number", "type yes to confirm").
+      Just presents options and lets the user respond however they want.
+    principles:
+      - YAGNI — never create agents that aren't strictly necessary
+      - Each agent must have exactly one clear responsibility
+      - Pipelines must have checkpoints at every user decision point
+      - Default to the simplest pipeline that achieves the goal
+      - "Path safety: Never use Bash mkdir to create directories. Always use the Write tool to create files — it creates parent directories automatically and avoids Windows/Bash path separator conflicts (backslash vs forward slash)."
+
+  discussion: true
+
+  menu:
+    - trigger: CS or fuzzy match on create-crew or create
+      description: "[CS] Create a new crew from natural language description"
+      action: create-crew
+
+    - trigger: ES or fuzzy match on edit-crew or edit or modify
+      description: "[ES] Edit an existing crew"
+      action: edit-crew
+
+    - trigger: LS or fuzzy match on list-crews or list or my crews
+      description: "[LS] List all crews"
+      action: list-crews
+
+    - trigger: DS or fuzzy match on delete-crew or delete or remove
+      description: "[DS] Delete a crew"
+      action: delete-crew
+
+  workflows:
+    create-crew: |
+      ## Create Crew
+
+      The create flow is now handled by the phased orchestration system.
+      See the SKILL.md entry point for the full phased flow:
+      Discovery → Investigation → Design → Template Selection (optional) → Build
+
+      Each phase is a separate prompt in `_opencrew/core/prompts/`:
+      - `discovery.prompt.md` — Phase 1: Intelligent wizard
+      - `sherlock-*.md` — Phase 2: Investigation (optional)
+      - `design.prompt.md` — Phase 3: Crew architecture (includes optional Phase G.5: Template Selection)
+      - `build.prompt.md` — Phase 4: File generation + validation
+
+      The SKILL.md orchestrator dispatches each phase as a subagent.
+
+    edit-crew: |
+      ## Edit Crew Workflow
+
+      1. Ask which crew to edit (list available crews if not specified).
+         If only 1 crew exists, add "Cancel" as a second option. If 0 crews, inform user directly.
+      2. Read the crew's crew.yaml to understand current structure
+      3. Ask what changes the user wants
+      4. **If the user asks to edit/define/change the visual template or identity of a design agent:**
+         - Read and follow `skills/template-designer/SKILL.md`
+         - If `template-reference.html` and `visual-identity.md` already exist in the crew's `pipeline/data/`, load them as the starting point
+      5. Modify the relevant files (agent .md files, pipeline steps, crew.yaml)
+      6. Present summary of changes
+      7. Confirm with user
+
+    list-crews: |
+      ## List Crews Workflow
+
+      1. Read all directories in crews/
+      2. For each, read crew.yaml to get name, description, icon, agent count
+      3. Present as a formatted list:
+         ```
+         Your Crews:
+         ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+         📋 my-crew
+            My Crew Description
+            3 agents | Last run: never
+         ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+         ```
+      4. If no crews exist, suggest creating one
+
+    delete-crew: |
+      ## Delete Crew Workflow
+
+      1. Ask which crew to delete (list available if not specified).
+         If only 1 crew exists, add "Cancel" as a second option. If 0 crews, inform user directly.
+      2. Show crew details (name, agents, output count)
+      3. Confirm deletion with explicit "Are you sure?" presented as a numbered list (1. Yes, delete / 2. No, cancel)
+      4. If confirmed, delete the entire crews/{code}/ directory
+      5. Confirm deletion

package/templates/_opencrew/core/best-practices/_catalog.yaml

@@ -0,0 +1,116 @@
+# Best Practices Catalog
+# The Architect reads this file to discover which best-practices are available.
+# Read the full file only for best-practices relevant to the crew being created.
+
+catalog:
+  # === Discipline Best Practices ===
+  - id: copywriting
+    name: "Copywriting & Persuasive Writing"
+    whenToUse: "Creating agents that write persuasive copy, hooks, CTAs, social media captions, sales content, or viral angles."
+    file: copywriting.md
+
+  - id: researching
+    name: "Research & Data Collection"
+    whenToUse: "Creating agents that research topics, collect data from the web, verify facts, or produce structured research briefs."
+    file: researching.md
+
+  - id: review
+    name: "Content Review & Quality Control"
+    whenToUse: "Creating agents that evaluate content quality, score against criteria, or produce structured APPROVE/REJECT verdicts."
+    file: review.md
+
+  - id: image-design
+    name: "Visual Design & Image Creation"
+    whenToUse: "Creating agents that design graphics, carousel slides, social media visuals, or HTML/CSS templates for rendering."
+    file: image-design.md
+
+  - id: social-networks-publishing
+    name: "Social Networks Publishing"
+    whenToUse: "Creating agents that publish content to Instagram, LinkedIn, X/Twitter, YouTube, or other social platforms."
+    file: social-networks-publishing.md
+
+  - id: strategist
+    name: "Strategy & Editorial Planning"
+    whenToUse: "Creating agents that plan content strategy, editorial calendars, competitive positioning, or audience segmentation."
+    file: strategist.md
+
+  - id: technical-writing
+    name: "Technical & Long-Form Writing"
+    whenToUse: "Creating agents that write articles, blog posts, documentation, tutorials, white papers, or educational content."
+    file: technical-writing.md
+
+  - id: data-analysis
+    name: "Data Analysis & Interpretation"
+    whenToUse: "Creating agents that interpret metrics, extract insights, benchmark performance, or produce analytical reports."
+    file: data-analysis.md
+
+  # === Platform Best Practices ===
+  - id: instagram-feed
+    name: "Instagram Feed & Carousels"
+    whenToUse: "Creating agents that produce Instagram feed posts, carousels, or static image content for Instagram."
+    file: instagram-feed.md
+
+  - id: instagram-reels
+    name: "Instagram Reels"
+    whenToUse: "Creating agents that produce Instagram Reels or short-form vertical video for Instagram."
+    file: instagram-reels.md
+
+  - id: instagram-stories
+    name: "Instagram Stories"
+    whenToUse: "Creating agents that produce Instagram Stories or ephemeral 24-hour content."
+    file: instagram-stories.md
+
+  - id: linkedin-post
+    name: "LinkedIn Post"
+    whenToUse: "Creating agents that produce LinkedIn posts, text updates, or document carousels for LinkedIn."
+    file: linkedin-post.md
+
+  - id: linkedin-article
+    name: "LinkedIn Article"
+    whenToUse: "Creating agents that produce LinkedIn articles or long-form professional content."
+    file: linkedin-article.md
+
+  - id: twitter-post
+    name: "Twitter/X Post"
+    whenToUse: "Creating agents that produce tweets, quote tweets, or single posts for X/Twitter."
+    file: twitter-post.md
+
+  - id: twitter-thread
+    name: "Twitter/X Thread"
+    whenToUse: "Creating agents that produce Twitter/X threads or multi-tweet narratives."
+    file: twitter-thread.md
+
+  - id: youtube-script
+    name: "YouTube Video Script"
+    whenToUse: "Creating agents that produce YouTube video scripts or long-form video content."
+    file: youtube-script.md
+
+  - id: youtube-shorts
+    name: "YouTube Shorts"
+    whenToUse: "Creating agents that produce YouTube Shorts or short-form vertical video for YouTube."
+    file: youtube-shorts.md
+
+  - id: email-newsletter
+    name: "Email Newsletter"
+    whenToUse: "Creating agents that produce email newsletters or recurring subscriber content."
+    file: email-newsletter.md
+
+  - id: email-sales
+    name: "Sales Email"
+    whenToUse: "Creating agents that produce sales emails, cold outreach, or direct response email campaigns."
+    file: email-sales.md
+
+  - id: blog-post
+    name: "Blog Post"
+    whenToUse: "Creating agents that produce blog posts, articles, or long-form content marketing."
+    file: blog-post.md
+
+  - id: blog-seo
+    name: "Blog Post (SEO)"
+    whenToUse: "Creating agents that produce SEO-optimized blog posts or search-targeted content."
+    file: blog-seo.md
+
+  - id: whatsapp-broadcast
+    name: "WhatsApp Broadcast"
+    whenToUse: "Creating agents that produce WhatsApp broadcast messages or conversational marketing content."
+    file: whatsapp-broadcast.md

package/templates/_opencrew/core/best-practices/blog-post.md

@@ -0,0 +1,151 @@
+---
+name: "Blog Post"
+platform: "blog"
+content_type: "post"
+description: "Long-form blog posts optimized for readability, engagement, and clear value delivery with structured subheadings"
+whenToUse: |
+  Creating agents that produce blog posts, articles, or long-form content marketing.
+constraints:
+  optimal_word_count: "1500-2500"
+  title_max_chars: 70
+  meta_description_chars: 160
+  subheading_frequency: "every 200-300 words"
+version: "1.0.0"
+---
+
+## Compact Rules
+
+1. Keep blog posts between 1,500-2,500 words for optimal depth and retention.
+2. Structure for mobile readability with 3-4 line paragraphs maximum.
+3. Insert descriptive subheadings every 200-300 words for scannability.
+4. Include at least 3 internal links and 2 external links naturally.
+5. Add a visual break (image, callout, list) every 300 words.
+6. Keep titles under 70 characters, front-loading the key concept.
+7. Write 150-160 character meta descriptions summarizing the value proposition.
+8. Hook the reader in the first 2-3 sentences (no dictionary definitions).
+9. Use 3-6 H2 sections to break down major points.
+10. Bold key phrases and takeaways within paragraphs.
+11. Write in the second person ("you") to connect directly with the reader.
+12. Conclude with a specific, actionable CTA (not generic questions).
+13. Maintain a consistent publishing cadence of 1-2 posts per week.
+14. Never publish thin content under 800 words or unbroken walls of text.
+
+<!-- End Compact Rules. Full reference below. -->
+
+## Platform Rules
+
+- Average time on page is the strongest engagement signal. Blog posts that keep readers scrolling for 3-5 minutes outperform those that get abandoned in the first 30 seconds. Structure and readability directly determine this metric.
+- Posts between 1,500-2,500 words hit the optimal balance of depth and retention. Below 800 words, content is perceived as thin and struggles to rank. Above 3,000 words, completion rates drop unless the topic demands exhaustive coverage.
+- Mobile readability is non-negotiable. Over 60% of blog traffic comes from mobile devices. Long paragraphs, wide images, and dense formatting that work on desktop become unreadable walls on small screens.
+- Subheadings serve as a scannable table of contents. Studies show 73% of readers scan blog posts rather than reading word by word. If the subheadings alone do not convey the article's value, the structure needs reworking.
+- Internal linking keeps readers on site and distributes page authority. Posts with 3+ internal links to related content have higher average session duration and lower bounce rates.
+- External links to authoritative sources (research, industry leaders, official documentation) increase credibility and can positively impact search ranking when linking to genuinely relevant resources.
+- Publishing consistency builds audience expectation and return visits. A regular cadence (1-2 posts per week) outperforms sporadic publishing bursts followed by silence.
+- Visual breaks every 300 words prevent fatigue: images, callout boxes, bullet lists, or blockquotes. Unbroken text spanning more than 300 words causes readers to disengage.
+
+## Content Structure
+
+### Blog Post Architecture
+
+1. **Title** — Under 70 characters. Clearly communicates what the reader will learn or gain. Front-load the key topic. Avoid vague or overly clever titles that sacrifice clarity for creativity.
+2. **Meta description** — 150-160 characters. Summarizes the post's value proposition in one sentence. This appears in search results and social shares — it is a second headline.
+3. **Intro hook (2-3 sentences)** — Open with a surprising stat, bold claim, relatable problem, or a story that places the reader in a scenario. Then state exactly what the post will deliver.
+4. **Body sections (3-6 H2 sections)** — Each section covers one major point with its own H2 subheading. Sections are 200-300 words each with H3 sub-sections for deeper breakdowns.
+5. **Conclusion (3-5 sentences)** — Summarize the key takeaways in 1-2 sentences, then deliver a clear CTA: read a related post, download a resource, leave a comment, or try a specific action.
+
+### Section-Level Structure
+
+- **H2 subheading** — Descriptive, scannable, and self-contained. A reader should understand the section's value from the heading alone.
+- **Opening sentence** — State the section's key point immediately. Do not build up to the insight.
+- **Supporting content** — Evidence, examples, data, or step-by-step instructions. Use bullet points for lists of 3+ items.
+- **Transition** — Final sentence bridges to the next section or reinforces the section's takeaway.
+
+### Effective Post Formats
+
+- **How-to guide**: "How to [achieve X]: A Step-by-Step Guide"
+- **Listicle**: "7 [Things] That [Outcome] (and How to Use Them)"
+- **Problem/Solution**: "Why [Problem Exists] and What to Do About It"
+- **Lessons learned**: "What I Learned From [Experience]: [N] Key Takeaways"
+- **Comparison**: "[Option A] vs. [Option B]: Which Is Right for [Audience]?"
+
+## Writing Guidelines
+
+- **Hook the reader in the first 2-3 sentences or lose them.** Open with a stat, question, bold claim, or relatable scenario. Never start with a dictionary definition or generic background. "Content marketing is important" loses readers. "87% of blog posts get zero organic traffic" keeps them.
+- Write in short paragraphs: 3-4 lines maximum on desktop, which translates to 2-3 lines on mobile. Single-sentence paragraphs are powerful for emphasis.
+- Bold key phrases and takeaways within paragraphs so scanners can extract value without reading every word.
+- Use bullet points and numbered lists for any sequence of 3+ items. Lists are easier to scan than inline comma-separated items.
+- Subheadings every 200-300 words. Each H2 should read like a mini-headline that a scanner would click on if presented independently.
+- Write in second person ("you") to create direct connection with the reader. First person ("I/we") works for personal stories and experience-based authority.
+- Include at least one visual break (image, callout box, blockquote, or list) every 300 words. Continuous text blocks cause reader fatigue and increase bounce rate.
+- End with a specific, actionable CTA. "What do you think?" is weak. "Try implementing [technique] this week and comment below with your results" is strong.
+- Include 3+ internal links to related content on your site and 2+ external links to authoritative sources. Link naturally within context, not in a dumped list at the end.
+- Write the title last, after you know what the post delivers. Front-load the most important keyword or concept in the first 40 characters.
+
+## Output Format
+
+```
+=== TITLE ===
+[Under 70 characters — clear, specific, keyword front-loaded]
+
+=== META DESCRIPTION ===
+[150-160 characters — summarizes the post's value proposition in one sentence]
+
+=== INTRO ===
+[Hook — surprising stat, bold claim, relatable problem, or opening story. 1-2 sentences.]
+
+[Promise — exactly what the reader will learn or gain from this post. 1 sentence.]
+
+=== BODY ===
+## [H2 Section 1 Title]
+[200-300 words — one major point with evidence, examples, or steps. Include bullet points or visuals where appropriate.]
+
+## [H2 Section 2 Title]
+[200-300 words — one major point with evidence, examples, or steps.]
+
+### [H3 Subsection if needed]
+[Deeper breakdown of a specific aspect — 100-150 words.]
+
+## [H2 Section 3 Title]
+[200-300 words — one major point with evidence, examples, or steps.]
+
+## [H2 Section 4 Title]
+[200-300 words — one major point with evidence, examples, or steps.]
+
+[Continue for 3-6 H2 sections total]
+
+=== CONCLUSION ===
+[Key takeaway summary — 1-2 sentences.]
+
+[CTA — specific, actionable ask. 1-2 sentences.]
+
+=== POST NOTES ===
+Target word count: [1500-2500]
+Internal links needed: [3+ with suggested anchor text]
+External links needed: [2+ to authoritative sources]
+Visual breaks: [List of suggested image/callout placements]
+```
+
+## Quality Criteria
+
+- [ ] Title is under 70 characters and clearly communicates the post's value
+- [ ] Meta description is 150-160 characters and serves as a compelling second headline
+- [ ] Intro hooks the reader in the first 2-3 sentences with a stat, bold claim, or relatable scenario
+- [ ] Post contains 3-6 H2 sections, each covering one major point
+- [ ] Subheadings appear every 200-300 words and are scannable as a standalone outline
+- [ ] Paragraphs are 3-4 lines maximum with key phrases bolded
+- [ ] At least one visual break (image, callout, list, or blockquote) every 300 words
+- [ ] 3+ internal links and 2+ external links are included with natural anchor text
+- [ ] Total word count is between 1,500-2,500 words
+- [ ] Conclusion ends with a specific, actionable CTA (not generic "What do you think?")
+
+## Anti-Patterns
+
+- **Walls of text** — Paragraphs exceeding 5-6 lines on desktop become impenetrable on mobile. Readers bounce rather than parse dense blocks. Short paragraphs and visual breaks are not optional — they are structural requirements for retention.
+- **No subheadings** — A 2,000-word post without H2/H3 subheadings is functionally a wall of text. Scanners (73% of readers) cannot extract value and leave. Subheadings serve as both navigation and content promises.
+- **Clickbait titles that do not deliver** — "This One Trick Changed Everything" followed by generic advice destroys trust. The reader feels deceived, bounces quickly, and never returns. High bounce rates also signal low quality to search engines.
+- **Thin content under 800 words** — Short posts struggle to provide sufficient depth, rank poorly for competitive keywords, and signal low effort. If the topic can be covered in 500 words, it may be better as a social post than a blog article.
+- **No conclusion or CTA** — Posts that simply stop after the last body section feel incomplete. The reader has invested 3-5 minutes and receives no guidance on what to do next. Every post needs a clear ending and next step.
+- **Dictionary definition openings** — Starting with "[Topic] is defined as..." is the most common sign of filler content. It adds no value, wastes the most important real estate in the post, and signals that the writer has nothing original to say.
+- **Link dumping** — Placing all internal and external links in a list at the bottom of the post rather than weaving them naturally into the content. Contextual links are clicked more and provide more value to the reader.
+- **No visual breaks** — Continuous text for 500+ words without an image, list, callout, or blockquote causes reading fatigue. Even well-written content gets abandoned when it is visually monotonous.
+- **Writing for search engines instead of humans** — Unnaturally forcing keywords into every sentence makes content awkward and unpleasant to read. Write for clarity first; optimize for search second.