@miranda0808/maya-codex 0.1.0

package/payload/.agents/skills/pricing-strategy/references/tier-structure.md

@@ -0,0 +1,232 @@
+# Tier Structure and Packaging
+
+## Contents
+- How Many Tiers?
+- Good-Better-Best Framework
+- Tier Differentiation Strategies
+- Example Tier Structure
+- Packaging for Personas (Identifying Pricing Personas, Persona-Based Packaging)
+- Freemium vs. Free Trial (When to Use Freemium, When to Use Free Trial, Hybrid Approaches)
+- Enterprise Pricing (When to Add Custom Pricing, Enterprise Tier Elements, Enterprise Pricing Strategies)
+
+## How Many Tiers?
+
+**2 tiers:** Simple, clear choice
+- Works for: Clear SMB vs. Enterprise split
+- Risk: May leave money on table
+
+**3 tiers:** Industry standard
+- Good tier = Entry point
+- Better tier = Recommended (anchor to best)
+- Best tier = High-value customers
+
+**4+ tiers:** More granularity
+- Works for: Wide range of customer sizes
+- Risk: Decision paralysis, complexity
+
+---
+
+## Good-Better-Best Framework
+
+**Good tier (Entry):**
+- Purpose: Remove barriers to entry
+- Includes: Core features, limited usage
+- Price: Low, accessible
+- Target: Small teams, try before you buy
+
+**Better tier (Recommended):**
+- Purpose: Where most customers land
+- Includes: Full features, reasonable limits
+- Price: Your "anchor" price
+- Target: Growing teams, serious users
+
+**Best tier (Premium):**
+- Purpose: Capture high-value customers
+- Includes: Everything, advanced features, higher limits
+- Price: Premium (often 2-3x "Better")
+- Target: Larger teams, power users, enterprises
+
+---
+
+## Tier Differentiation Strategies
+
+**Feature gating:**
+- Basic features in all tiers
+- Advanced features in higher tiers
+- Works when features have clear value differences
+
+**Usage limits:**
+- Same features, different limits
+- More users, storage, API calls at higher tiers
+- Works when value scales with usage
+
+**Support level:**
+- Email support → Priority support → Dedicated success
+- Works for products with implementation complexity
+
+**Access and customization:**
+- API access, SSO, custom branding
+- Works for enterprise differentiation
+
+---
+
+## Example Tier Structure
+
+```
+┌────────────────┬─────────────────┬─────────────────┬─────────────────┐
+│                │ Starter         │ Pro             │ Business        │
+│                │ $29/mo          │ $79/mo          │ $199/mo         │
+├────────────────┼─────────────────┼─────────────────┼─────────────────┤
+│ Users          │ Up to 5         │ Up to 20        │ Unlimited       │
+│ Projects       │ 10              │ Unlimited       │ Unlimited       │
+│ Storage        │ 5 GB            │ 50 GB           │ 500 GB          │
+│ Integrations   │ 3               │ 10              │ Unlimited       │
+│ Analytics      │ Basic           │ Advanced        │ Custom          │
+│ Support        │ Email           │ Priority        │ Dedicated       │
+│ API Access     │ ✗               │ ✓               │ ✓               │
+│ SSO            │ ✗               │ ✗               │ ✓               │
+│ Audit logs     │ ✗               │ ✗               │ ✓               │
+└────────────────┴─────────────────┴─────────────────┴─────────────────┘
+```
+
+---
+
+## Packaging for Personas
+
+### Identifying Pricing Personas
+
+Different customers have different:
+- Willingness to pay
+- Feature needs
+- Buying processes
+- Value perception
+
+**Segment by:**
+- Company size (solopreneur → SMB → enterprise)
+- Use case (marketing vs. sales vs. support)
+- Sophistication (beginner → power user)
+- Industry (different budget norms)
+
+### Persona-Based Packaging
+
+**Step 1: Define personas**
+
+| Persona | Size | Needs | WTP | Example |
+|---------|------|-------|-----|---------|
+| Freelancer | 1 person | Basic features | Low | $19/mo |
+| Small Team | 2-10 | Collaboration | Medium | $49/mo |
+| Growing Co | 10-50 | Scale, integrations | Higher | $149/mo |
+| Enterprise | 50+ | Security, support | High | Custom |
+
+**Step 2: Map features to personas**
+
+| Feature | Freelancer | Small Team | Growing | Enterprise |
+|---------|------------|------------|---------|------------|
+| Core features | ✓ | ✓ | ✓ | ✓ |
+| Collaboration | — | ✓ | ✓ | ✓ |
+| Integrations | — | Limited | Full | Full |
+| API access | — | — | ✓ | ✓ |
+| SSO/SAML | — | — | — | ✓ |
+| Audit logs | — | — | — | ✓ |
+| Custom contract | — | — | — | ✓ |
+
+**Step 3: Price to value for each persona**
+- Research willingness to pay per segment
+- Set prices that capture value without blocking adoption
+- Consider segment-specific landing pages
+
+---
+
+## Freemium vs. Free Trial
+
+### When to Use Freemium
+
+**Freemium works when:**
+- Product has viral/network effects
+- Free users provide value (content, data, referrals)
+- Large market where % conversion drives volume
+- Low marginal cost to serve free users
+- Clear feature/usage limits for upgrade trigger
+
+**Freemium risks:**
+- Free users may never convert
+- Devalues product perception
+- Support costs for non-paying users
+- Harder to raise prices later
+
+### When to Use Free Trial
+
+**Free trial works when:**
+- Product needs time to demonstrate value
+- Onboarding/setup investment required
+- B2B with buying committees
+- Higher price points
+- Product is "sticky" once configured
+
+**Trial best practices:**
+- 7-14 days for simple products
+- 14-30 days for complex products
+- Full access (not feature-limited)
+- Clear countdown and reminders
+- Credit card optional vs. required trade-off
+
+**Credit card upfront:**
+- Higher trial-to-paid conversion (40-50% vs. 15-25%)
+- Lower trial volume
+- Better qualified leads
+
+### Hybrid Approaches
+
+**Freemium + Trial:**
+- Free tier with limited features
+- Trial of premium features
+- Example: Zoom (free 40-min, trial of Pro)
+
+**Reverse trial:**
+- Start with full access
+- After trial, downgrade to free tier
+- Example: See premium value, live with limitations until ready
+
+---
+
+## Enterprise Pricing
+
+### When to Add Custom Pricing
+
+Add "Contact Sales" when:
+- Deal sizes exceed $10k+ ARR
+- Customers need custom contracts
+- Implementation/onboarding required
+- Security/compliance requirements
+- Procurement processes involved
+
+### Enterprise Tier Elements
+
+**Table stakes:**
+- SSO/SAML
+- Audit logs
+- Admin controls
+- Uptime SLA
+- Security certifications
+
+**Value-adds:**
+- Dedicated support/success
+- Custom onboarding
+- Training sessions
+- Custom integrations
+- Priority roadmap input
+
+### Enterprise Pricing Strategies
+
+**Per-seat at scale:**
+- Volume discounts for large teams
+- Example: $15/user (standard) → $10/user (100+)
+
+**Platform fee + usage:**
+- Base fee for access
+- Usage-based above thresholds
+- Example: $500/mo base + $0.01 per API call
+
+**Value-based contracts:**
+- Price tied to customer's revenue/outcomes
+- Example: % of transactions, revenue share

package/payload/.agents/skills/product-marketing-context/SKILL.md

@@ -0,0 +1,27 @@
+---
+name: product-marketing-context
+description: Use when a user asks for the retired product-marketing-context workflow and needs to be redirected to Maya's PRODUCT.md contract.
+metadata:
+  version: 2.0.0
+---
+
+# Product Marketing Context (Retired)
+
+This skill is retired for Maya.
+
+Maya no longer uses `.agents/product-marketing-context.md` as a context contract. `PRODUCT.md` is Maya's only canonical brand and product context source.
+
+## Redirect Behavior
+
+When a user asks for the old product-marketing-context workflow:
+1. Explain that Maya retired `.agents/product-marketing-context.md`.
+2. Explain that `PRODUCT.md` now holds the canonical product and brand context.
+3. Point them to `/product` if they want to create or update that context.
+4. Do not create a compatibility copy under `.agents/`.
+
+## Current Maya Rules
+
+- In consult-style usage, Maya may read `PRODUCT.md` directly when it is present.
+- In Maya task workflows, specialists stay packet-first and use approved `TASK-PACKET.md` inputs and listed brand sections before any direct file read.
+- If `PRODUCT.md` is missing, do not imply the work is fully brand-calibrated.
+- If the user wants old-file migration help, explain the retirement and redirect them to the current `PRODUCT.md` contract instead of reviving the deprecated file.

package/payload/.agents/skills/product-marketing-context/evals/evals.json

@@ -0,0 +1,40 @@
+{
+  "skill_name": "product-marketing-context",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "I want to set up my product marketing context. We're a B2B SaaS company that sells a customer feedback platform to product teams.",
+      "expected_output": "Should explain that Maya retired the old product-marketing-context workflow. Should say PRODUCT.md is now the canonical brand and product context document. Should redirect the user to /product for creation or updates. Should not offer to create .agents/product-marketing-context.md or any compatibility bridge.",
+      "assertions": [
+        "Explains the old workflow is retired",
+        "Says PRODUCT.md is the canonical context source",
+        "Redirects the user to /product",
+        "Does not recreate .agents/product-marketing-context.md"
+      ],
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "Update our product marketing context. We just added a new enterprise tier and our target audience has expanded to include VP of Engineering, not just Product Managers.",
+      "expected_output": "Should explain that Maya no longer updates .agents/product-marketing-context.md. Should direct the user to refresh PRODUCT.md through /product. Should make clear that Maya's current context contract centers PRODUCT.md instead of the retired file path.",
+      "assertions": [
+        "Explains .agents/product-marketing-context.md is no longer Maya's context file",
+        "Redirects the update request to /product",
+        "Explains the PRODUCT.md contract"
+      ],
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "Do we have a product marketing context set up? I want to make sure the other marketing skills have context about our product.",
+      "expected_output": "Should explain that Maya now looks to PRODUCT.md for canonical brand and product context. Should not claim the old product-marketing-context file is still the active contract. Should explain that consult workflows may read PRODUCT.md directly, while Maya task workflows keep specialists packet-first.",
+      "assertions": [
+        "Explains PRODUCT.md is the canonical context source",
+        "Does not describe the old file as active",
+        "Explains consult direct reads",
+        "Explains task-mode packet-first specialist behavior"
+      ],
+      "files": []
+    }
+  ]
+}

package/payload/.agents/skills/programmatic-seo/SKILL.md

@@ -0,0 +1,238 @@
+---
+name: programmatic-seo
+description: When the user wants to create SEO-driven pages at scale using templates and data. Also use when the user mentions "programmatic SEO," "template pages," "pages at scale," "directory pages," "location pages," "[keyword] + [city] pages," "comparison pages," "integration pages," "building many pages for SEO," "pSEO," "generate 100 pages," "data-driven pages," or "templated landing pages." Use this whenever someone wants to create many similar pages targeting different keywords or locations. For auditing existing SEO issues, see seo-audit. For content strategy planning, see content-strategy.
+metadata:
+  version: 1.1.0
+---
+
+# Programmatic SEO
+
+You are an expert in programmatic SEO—building SEO-optimized pages at scale using templates and data. Your goal is to create pages that rank, provide value, and avoid thin content penalties.
+
+## Initial Assessment
+
+**Use approved context inputs first:**
+In Maya task workflows, start with the approved `TASK-PACKET.md` inputs and listed brand sections. If `PRODUCT.md` is explicitly provided or the work is being done in consult-style standalone usage, read `PRODUCT.md` before asking questions. If `PRODUCT.md` is missing, do not pretend the output is fully brand-calibrated.
+
+Before designing a programmatic SEO strategy, understand:
+
+1. **Business Context**
+   - What's the product/service?
+   - Who is the target audience?
+   - What's the conversion goal for these pages?
+
+2. **Opportunity Assessment**
+   - What search patterns exist?
+   - How many potential pages?
+   - What's the search volume distribution?
+
+3. **Competitive Landscape**
+   - Who ranks for these terms now?
+   - What do their pages look like?
+   - Can you realistically compete?
+
+---
+
+## Core Principles
+
+### 1. Unique Value Per Page
+- Every page must provide value specific to that page
+- Not just swapped variables in a template
+- Maximize unique content—the more differentiated, the better
+
+### 2. Proprietary Data Wins
+Hierarchy of data defensibility:
+1. Proprietary (you created it)
+2. Product-derived (from your users)
+3. User-generated (your community)
+4. Licensed (exclusive access)
+5. Public (anyone can use—weakest)
+
+### 3. Clean URL Structure
+**Use subfolders, not subdomains** — subfolders consolidate domain authority while subdomains split it:
+- Good: `yoursite.com/templates/resume/`
+- Bad: `templates.yoursite.com/resume/`
+
+### 4. Genuine Search Intent Match
+Pages must actually answer what people are searching for.
+
+### 5. Quality Over Quantity
+Better to have 100 great pages than 10,000 thin ones.
+
+### 6. Avoid Google Penalties
+- No doorway pages
+- No keyword stuffing
+- No duplicate content
+- Genuine utility for users
+
+---
+
+## The 12 Playbooks (Overview)
+
+| Playbook | Pattern | Example |
+|----------|---------|---------|
+| Templates | "[Type] template" | "resume template" |
+| Curation | "best [category]" | "best website builders" |
+| Conversions | "[X] to [Y]" | "$10 USD to GBP" |
+| Comparisons | "[X] vs [Y]" | "webflow vs wordpress" |
+| Examples | "[type] examples" | "landing page examples" |
+| Locations | "[service] in [location]" | "dentists in austin" |
+| Personas | "[product] for [audience]" | "crm for real estate" |
+| Integrations | "[product A] [product B] integration" | "slack asana integration" |
+| Glossary | "what is [term]" | "what is pSEO" |
+| Translations | Content in multiple languages | Localized content |
+| Directory | "[category] tools" | "ai copywriting tools" |
+| Profiles | "[entity name]" | "stripe ceo" |
+
+**For detailed playbook implementation**: See [references/playbooks.md](references/playbooks.md)
+
+---
+
+## Choosing Your Playbook
+
+| If you have... | Consider... |
+|----------------|-------------|
+| Proprietary data | Directories, Profiles |
+| Product with integrations | Integrations |
+| Design/creative product | Templates, Examples |
+| Multi-segment audience | Personas |
+| Local presence | Locations |
+| Tool or utility product | Conversions |
+| Content/expertise | Glossary, Curation |
+| Competitor landscape | Comparisons |
+
+You can layer multiple playbooks (e.g., "Best coworking spaces in San Diego").
+
+---
+
+## Implementation Framework
+
+### 1. Keyword Pattern Research
+
+**Identify the pattern:**
+- What's the repeating structure?
+- What are the variables?
+- How many unique combinations exist?
+
+**Validate demand:**
+- Aggregate search volume
+- Volume distribution (head vs. long tail)
+- Trend direction
+
+### 2. Data Requirements
+
+**Identify data sources:**
+- What data populates each page?
+- Is it first-party, scraped, licensed, public?
+- How is it updated?
+
+### 3. Template Design
+
+**Page structure:**
+- Header with target keyword
+- Unique intro (not just variables swapped)
+- Data-driven sections
+- Related pages / internal links
+- CTAs appropriate to intent
+
+**Ensuring uniqueness:**
+- Each page needs unique value
+- Conditional content based on data
+- Original insights/analysis per page
+
+### 4. Internal Linking Architecture
+
+**Hub and spoke model:**
+- Hub: Main category page
+- Spokes: Individual programmatic pages
+- Cross-links between related spokes
+
+**Avoid orphan pages:**
+- Every page reachable from main site
+- XML sitemap for all pages
+- Breadcrumbs with structured data
+
+### 5. Indexation Strategy
+
+- Prioritize high-volume patterns
+- Noindex very thin variations
+- Manage crawl budget thoughtfully
+- Separate sitemaps by page type
+
+---
+
+## Quality Checks
+
+### Pre-Launch Checklist
+
+**Content quality:**
+- [ ] Each page provides unique value
+- [ ] Answers search intent
+- [ ] Readable and useful
+
+**Technical SEO:**
+- [ ] Unique titles and meta descriptions
+- [ ] Proper heading structure
+- [ ] Schema markup implemented
+- [ ] Page speed acceptable
+
+**Internal linking:**
+- [ ] Connected to site architecture
+- [ ] Related pages linked
+- [ ] No orphan pages
+
+**Indexation:**
+- [ ] In XML sitemap
+- [ ] Crawlable
+- [ ] No conflicting noindex
+
+### Post-Launch Monitoring
+
+Track: Indexation rate, Rankings, Traffic, Engagement, Conversion
+
+Watch for: Thin content warnings, Ranking drops, Manual actions, Crawl errors
+
+---
+
+## Common Mistakes
+
+- **Thin content**: Just swapping city names in identical content
+- **Keyword cannibalization**: Multiple pages targeting same keyword
+- **Over-generation**: Creating pages with no search demand
+- **Poor data quality**: Outdated or incorrect information
+- **Ignoring UX**: Pages exist for Google, not users
+
+---
+
+## Output Format
+
+### Strategy Document
+- Opportunity analysis
+- Implementation plan
+- Content guidelines
+
+### Page Template
+- URL structure
+- Title/meta templates
+- Content outline
+- Schema markup
+
+---
+
+## Task-Specific Questions
+
+1. What keyword patterns are you targeting?
+2. What data do you have (or can acquire)?
+3. How many pages are you planning?
+4. What does your site authority look like?
+5. Who currently ranks for these terms?
+6. What's your technical stack?
+
+---
+
+## Related Skills
+
+- **seo-audit**: For auditing programmatic pages after launch
+- **schema-markup**: For adding structured data
+- **site-architecture**: For page hierarchy, URL structure, and internal linking
+- **competitor-alternatives**: For comparison page frameworks

package/payload/.agents/skills/programmatic-seo/evals/evals.json

@@ -0,0 +1,94 @@
+{
+  "skill_name": "programmatic-seo",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "We want to create programmatic SEO pages for our CRM. We're thinking of 'CRM for [industry]' pages — like 'CRM for Real Estate,' 'CRM for Healthcare,' etc. How should we approach this?",
+      "expected_output": "Should use approved TASK-PACKET.md inputs first in Maya task workflows, and read PRODUCT.md directly when it is explicitly provided or when the work is consult-style standalone. Should identify this as the Personas playbook (industry-specific pages). Should apply the core principles: unique value per page (not just swapping the industry name), proprietary data or insights per industry, clean URL structure. Should recommend the implementation framework: keyword research for each industry variation, data requirements (what industry-specific content makes each page unique), template design, internal linking strategy between industry pages and main pages, and indexation strategy. Should warn against thin content (just template + keyword swap).",
+      "assertions": [
+        "Uses approved TASK-PACKET.md inputs or PRODUCT.md context first",
+        "Identifies as Personas playbook",
+        "Applies core principles (unique value, proprietary data, clean URLs)",
+        "Recommends keyword research per variation",
+        "Addresses data requirements for unique content",
+        "Provides template design guidance",
+        "Includes internal linking strategy",
+        "Warns against thin content"
+      ],
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "Create a comparison page strategy. We want pages like 'Notion vs Asana', 'Notion vs Monday', etc. for all our competitors. We have 15 competitors.",
+      "expected_output": "Should identify this as the Comparisons playbook. Should apply the programmatic approach for competitor comparison pages at scale. Should recommend: template structure for comparison pages, unique data per comparison (not just the same template with names swapped), keyword research for each '[competitor A] vs [competitor B]' variation, URL structure (/compare/notion-vs-asana), internal linking between comparison pages, and quality checks. Should cross-reference the competitor-alternatives skill for page content structure.",
+      "assertions": [
+        "Identifies as Comparisons playbook",
+        "Recommends template structure for scale",
+        "Addresses unique data per comparison",
+        "Includes keyword research for variations",
+        "Provides URL structure recommendation",
+        "Includes internal linking strategy",
+        "Cross-references competitor-alternatives skill",
+        "Applies quality checks"
+      ],
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "we want to rank for '[tool name] integration' keywords. we integrate with 50+ tools and want a page for each. like 'Slack integration', 'Salesforce integration' etc.",
+      "expected_output": "Should trigger on casual phrasing. Should identify this as the Integrations playbook. Should recommend: template design for integration pages (what it does, how to set up, use cases), unique content per integration (specific workflows, screenshots, setup steps), keyword research for '[tool] + [your product] integration', URL structure (/integrations/slack), hub page linking to all integration pages, and schema markup considerations. Should emphasize that each page needs genuine unique value, not just 'we integrate with [tool].'",
+      "assertions": [
+        "Triggers on casual phrasing",
+        "Identifies as Integrations playbook",
+        "Recommends template with unique content per integration",
+        "Includes setup steps and use cases per page",
+        "Provides URL structure recommendation",
+        "Recommends hub page for all integrations",
+        "Emphasizes genuine unique value per page"
+      ],
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "We built 500 programmatic pages but Google isn't indexing most of them. Only 80 are in the index. What's going wrong?",
+      "expected_output": "Should diagnose the indexation problem. Should apply the quality checks and indexation strategy guidance. Should investigate: thin content (are pages providing unique value or just template + keyword?), crawl budget (500 pages may be fine but depends on site authority), internal linking (are the pages discoverable?), XML sitemap inclusion, duplicate/near-duplicate content issues. Should recommend specific fixes: improve content uniqueness, strengthen internal linking, submit sitemap, check robots.txt, use Search Console for indexation requests. Should warn that Google may choose not to index thin pages regardless.",
+      "assertions": [
+        "Diagnoses indexation problem",
+        "Investigates thin content as likely cause",
+        "Checks crawl budget considerations",
+        "Checks internal linking to programmatic pages",
+        "Checks XML sitemap and robots.txt",
+        "Recommends specific fixes for indexation",
+        "Warns about Google's thin content policies"
+      ],
+      "files": []
+    },
+    {
+      "id": 5,
+      "prompt": "Help me create a glossary section for our marketing automation platform. We want to define 200+ marketing terms and rank for '[term] definition' keywords.",
+      "expected_output": "Should identify this as the Glossary playbook. Should apply the template design: term definition page template (definition, examples, related terms, how it applies to the user's product), hub/index page linking to all terms, URL structure (/glossary/[term]), alphabetical and categorical navigation. Should address quality: each definition should provide genuine value beyond a dictionary definition. Should include internal linking strategy and schema markup (DefinedTerm schema). Should recommend starting with highest-volume terms.",
+      "assertions": [
+        "Identifies as Glossary playbook",
+        "Provides template design for term pages",
+        "Recommends hub/index page",
+        "Provides URL structure",
+        "Addresses content quality beyond dictionary definitions",
+        "Includes internal linking strategy",
+        "Recommends starting with highest-volume terms"
+      ],
+      "files": []
+    },
+    {
+      "id": 6,
+      "prompt": "Can you audit our existing programmatic SEO pages for technical issues? We have crawl errors and some pages return 404s.",
+      "expected_output": "Should recognize this is a technical SEO audit task, not a programmatic SEO strategy task. Should defer to or cross-reference the seo-audit skill, which handles crawlability, indexation, and technical SEO issues. Programmatic-seo focuses on strategy, template design, and content planning for scaled pages.",
+      "assertions": [
+        "Recognizes this as technical SEO audit task",
+        "References or defers to seo-audit skill",
+        "Explains that programmatic-seo is for strategy and template design",
+        "Does not attempt full technical SEO audit"
+      ],
+      "files": []
+    }
+  ]
+}