agents in

This commit is contained in:
2026-03-27 22:34:12 -05:00
commit a682231f73
44 changed files with 2274 additions and 0 deletions

View File

@@ -0,0 +1,45 @@
# Content Strategy and SEO
## Purpose
Create durable content plans and search-aligned messaging that compound over time instead of only supporting one launch moment.
## When to use
- Planning evergreen content around a product area
- Improving discoverability for technical or product topics
- Aligning content to audience intent and search behavior
- Deciding which topics deserve durable written assets
## Inputs to gather
- Audience segments and their recurring questions
- Product strengths, proof points, and topic authority
- Existing content library and content gaps
- Desired business outcome: discovery, education, conversion, or retention
## How to work
- Start from audience intent and recurring problems, not isolated keywords alone.
- Organize content into durable themes that the product can support credibly.
- Align titles, structure, and calls to action with user intent.
- Avoid search-driven copy that weakens clarity or trust.
- Prefer content that stays useful as the product evolves.
## Output expectations
- Content strategy, topic map, or SEO-aware draft direction
- Prioritized content opportunities with rationale
- Notes on how content connects to product positioning and documentation
## Quality checklist
- Recommendations reflect real audience needs.
- Content ideas support durable value, not shallow traffic grabs.
- Search alignment does not distort message clarity.
- The strategy can inform multiple future assets.
## Handoff notes
- Note which assumptions are based on audience reasoning versus actual search data.
- Pair with messaging/positioning and technical docs for strong, credible long-tail content.

View File

@@ -0,0 +1,45 @@
# Marketing Content
## Purpose
Create external-facing content that explains, promotes, or launches product capabilities in a way that is accurate, audience-aware, and compelling.
## When to use
- Drafting launch posts, emails, feature pages, announcements, or social content
- Turning product or engineering work into outward-facing communication
- Adapting one core message into multiple channels
- Creating content tied to a release or campaign
## Inputs to gather
- Audience, channel, and desired action
- The actual product change or offer being communicated
- Supporting proof points, examples, and differentiators
- Voice, tone, and length constraints
## How to work
- Lead with why the audience should care.
- Ground claims in the real product and its benefits.
- Structure content so it is easy to scan and repurpose.
- Tailor tone and density to the channel instead of reusing the same draft everywhere.
- Keep technical explanations accurate while translating them into audience-relevant outcomes.
## Output expectations
- A polished draft for the requested channel
- Supporting variations or headline options when useful
- Clear call to action where appropriate
## Quality checklist
- The content is audience-centered, not feature-dump centered.
- Claims are specific and defensible.
- The narrative is easy to scan and follow.
- The output matches the requested medium and length.
## Handoff notes
- State which audience and channel the draft targets.
- Pair with messaging/positioning when the strategic framing is not yet settled.

View File

@@ -0,0 +1,45 @@
# Messaging and Positioning
## Purpose
Clarify who the product or feature is for, what value it provides, why it matters now, and how it differs from alternatives.
## When to use
- Defining or refining product narrative
- Preparing launches, landing pages, or feature announcements
- Choosing how to frame a new capability for a target audience
- Aligning product, UX, and marketing language around one story
## Inputs to gather
- Target audience and their pain points
- Product capability, strengths, and evidence
- Competitive or alternative solutions
- Business goal of the messaging effort
## How to work
- Start with audience pain or desired outcome, then connect the product to that need.
- Distinguish core value, supporting proof, and differentiators.
- Avoid vague slogans unless they are backed by a concrete explanation.
- Stress-test the message against realistic alternatives and skeptical readers.
- Produce a tight core narrative that other copy can inherit.
## Output expectations
- Clear positioning statement or message framework
- Defined audience, value proposition, and differentiators
- Candidate headlines, pillars, or narrative directions when useful
## Quality checklist
- The message is specific about audience and value.
- Differentiation is real, not generic category language.
- Claims are supportable by the product.
- The narrative can guide product copy and campaign content consistently.
## Handoff notes
- Note open questions about audience, market, or product maturity if they limit confidence.
- Pair with product copy or marketing content to turn the narrative into shipped assets.

View File

@@ -0,0 +1,45 @@
# Product Copy
## Purpose
Write concise, user-facing product language that is clear, useful, on-brand, and matched to the immediate interface or conversion context.
## When to use
- Naming buttons, labels, helper text, empty states, and error messages
- Tightening landing page or feature page copy
- Improving clarity and persuasion in product-adjacent text
- Rewriting awkward or confusing interface wording
## Inputs to gather
- Audience, goal, and context of the text
- Current product voice and terminology
- UI constraints such as length, hierarchy, and surrounding elements
- Desired action or decision the copy should support
## How to work
- Optimize for clarity first, persuasion second, cleverness last.
- Use the words users expect based on the product and task.
- Match the level of confidence and urgency to the action being requested.
- Keep text tight and scannable, especially in UI contexts.
- Offer alternatives when tone or positioning is uncertain.
## Output expectations
- Final copy or strong candidate options
- Brief rationale when choosing between meaningful directions
- Notes on character, tone, or placement constraints when relevant
## Quality checklist
- Copy is clear on first read.
- The wording fits the user's moment and intent.
- Claims are credible and specific.
- Text length is appropriate to the surface.
## Handoff notes
- Note if final selection depends on brand voice or product strategy not yet defined.
- Pair with UX review for interface clarity and with messaging/positioning for strategic alignment.