arkaos 4.26.0 → 4.27.0

package/config/evals/landing.yaml

@@ -0,0 +1,927 @@
+# --- BEGIN imported (marketing-skills, MIT) — regenerated by scripts/tools/evals_import.py ---
+- id: landing-copy-framework-01
+  department: landing
+  prompt: Write homepage copy for a SaaS tool that automates employee onboarding. Target audience
+    is HR directors at mid-size companies (200-2000 employees). Main differentiator is that
+    it integrates with all major HRIS systems and cuts onboarding time from 2 weeks to 2 days.
+  expected_properties:
+  - Checks for product-marketing.md
+  - Writes full page copy organized by section
+  - Includes Headline, Subheadline, and CTA above the fold
+  - Includes Social Proof, Problem/Pain, Solution/Benefits, How It Works sections
+  - Uses the '2 weeks to 2 days' specificity in copy
+  - CTAs are action-oriented, not generic
+  - Provides 2-3 headline alternatives with rationale
+  - Includes annotations explaining copy choices
+  - Includes meta content (SEO title and meta description)
+  rubric: 'Should check for product-marketing.md first. Should write full page copy organized
+    by section: Headline, Subheadline, CTA (above the fold), then Social Proof, Problem/Pain,
+    Solution/Benefits, How It Works, Objection Handling, and Final CTA. Should follow copywriting
+    principles: clarity over cleverness, benefits over features, specificity (use the ''2
+    weeks to 2 days'' stat), customer language. Headline should communicate core value proposition.
+    CTAs should be action-oriented (''Start Free Trial'' not ''Submit''). Should provide 2-3
+    headline alternatives with rationale. Should include annotations explaining key copy choices.
+    Should include meta content (SEO page title and meta description).'
+  tags:
+  - copy-framework
+  - imported
+- id: landing-copy-framework-02
+  department: landing
+  prompt: 'Rewrite this headline: ''An Innovative AI-Powered Platform for Streamlined Business
+    Operations'' — it''s for a B2B SaaS tool that helps small businesses manage invoicing
+    and payments.'
+  expected_properties:
+  - Identifies jargon in original headline
+  - Identifies vagueness as a problem
+  - Identifies company language vs customer language issue
+  - Provides 2-3 alternative headlines
+  - Alternatives use headline formulas from the skill
+  - Each alternative includes rationale
+  - Suggests a subheadline
+  rubric: 'Should identify problems: jargon (''innovative,'' ''AI-powered,'' ''streamlined,''
+    ''business operations''), too vague, company language not customer language. Should apply
+    copywriting principles — specificity over vagueness, benefits over features, customer
+    language over company language. Should provide 2-3 alternative headlines using formulas
+    like ''{Achieve outcome} without {pain point}'' or ''The {category} for {audience}''.
+    Each alternative should include rationale. Should also suggest a subheadline that adds
+    specificity.'
+  tags:
+  - copy-framework
+  - imported
+- id: landing-copy-framework-03
+  department: landing
+  prompt: 'i need copy for my pricing page. we have three plans: starter ($29/mo), pro ($79/mo),
+    business ($199/mo). it''s a social media scheduling tool for marketers'
+  expected_properties:
+  - Triggers on casual phrasing
+  - Applies Pricing Page guidance
+  - Addresses 'which plan is right for me' anxiety
+  - Makes recommended plan obvious
+  - Writes benefit-oriented feature copy, not just feature names
+  - Includes page headline
+  - CTAs are specific per plan
+  - Includes FAQ or objection handling copy
+  - Provides alternatives for key elements
+  rubric: 'Should trigger on the casual phrasing. Should ask or infer audience context. Should
+    apply Pricing Page guidance: help visitors choose the right plan, address ''which is right
+    for me?'' anxiety, make recommended plan obvious. Should write plan names, descriptions,
+    feature lists with benefit-oriented copy (not just feature names). Should include a page
+    headline that addresses the pricing decision. CTAs should be specific per plan. Should
+    handle objection handling (FAQ copy). Should provide alternatives for key elements.'
+  tags:
+  - copy-framework
+  - imported
+- id: landing-copy-framework-04
+  department: landing
+  prompt: Write copy for our About page. We're a 3-person startup that built a developer tool
+    for database migrations. Founded because we kept losing data during migrations at our
+    last jobs. Tone should be professional but human.
+  expected_properties:
+  - Applies About Page guidance
+  - Tells the story of why the company exists
+  - Connects mission to customer benefit
+  - Includes a CTA
+  - Adapts tone to professional but human
+  - Uses the founder origin story
+  - Connects personal pain to customer pain
+  - Uses active voice
+  - Avoids corporate jargon
+  rubric: 'Should apply About Page guidance: tell the story of why you exist, connect mission
+    to customer benefit, still include a CTA. Should adapt voice and tone to ''professional
+    but human'' as specified. Should tell the founder origin story authentically. Should connect
+    the personal pain to the customer''s pain. Should include a CTA even on the About page.
+    Copy should follow style rules: active voice, confident, specific. Should NOT be overly
+    corporate or generic.'
+  tags:
+  - copy-framework
+  - imported
+- id: landing-copy-framework-05
+  department: landing
+  prompt: Can you improve this CTA? We currently have 'Learn More' on our feature page for
+    our analytics dashboard product.
+  expected_properties:
+  - Identifies 'Learn More' as a weak CTA
+  - Applies the CTA formula from the skill
+  - Provides 2-3 strong alternatives
+  - Each alternative includes rationale
+  - Considers CTA hierarchy (primary vs secondary)
+  - Suggests complementary CTAs
+  rubric: 'Should immediately identify ''Learn More'' as a weak CTA per the guidelines. Should
+    apply the CTA formula: [Action Verb] + [What They Get] + [Qualifier]. Should provide 2-3
+    strong alternatives like ''See the Dashboard in Action,'' ''Start Your Free Trial,'' or
+    ''Explore Analytics Features.'' Each alternative should include rationale and context
+    for when it works best. Should also consider CTA hierarchy — whether this is a primary
+    or secondary CTA, and suggest complementary CTAs if relevant.'
+  tags:
+  - copy-framework
+  - imported
+- id: landing-copy-framework-06
+  department: landing
+  prompt: Write me a 5-email welcome sequence for new trial users of our project management
+    tool.
+  expected_properties:
+  - Recognizes this as email sequence work
+  - References or defers to emails skill
+  - Does not attempt to write a full email sequence using page copywriting patterns
+  rubric: Should recognize this is an email copywriting task, not page copywriting. Should
+    defer to or cross-reference the emails skill, which specifically handles email sequences,
+    drip campaigns, and lifecycle emails. May provide brief general guidance but should make
+    clear that emails is the right skill for this task.
+  tags:
+  - copy-framework
+  - imported
+- id: landing-copy-framework-07
+  department: landing
+  prompt: 'Review this copy and tell me what''s wrong: ''We are extremely excited to announce
+    our revolutionary, cutting-edge platform that will totally transform how businesses optimize
+    their workflows! Sign up now!!'''
+  expected_properties:
+  - Identifies exclamation point overuse
+  - Identifies marketing buzzwords without substance
+  - Identifies vague language
+  - Applies writing style rules
+  - Rewrites the copy following principles
+  - Provides alternatives
+  - Result is specific, clear, and jargon-free
+  rubric: 'Should apply the Quick Quality Check. Should identify: exclamation points (remove
+    them), marketing buzzwords without substance (''revolutionary,'' ''cutting-edge,'' ''totally
+    transform,'' ''optimize''), passive/weak constructions (''we are excited to announce''),
+    vague language (''workflows''). Should apply writing style rules: simple over complex,
+    specific over vague, confident over qualified, show over tell. Should rewrite the copy
+    following these principles. Should provide 2-3 alternatives.'
+  tags:
+  - copy-framework
+  - imported
+- id: landing-optimize-page-01
+  department: landing
+  prompt: 'Here''s my SaaS landing page: https://example.com/product. We get about 5,000 visitors/month
+    from Google Ads but only 1.2% convert to free trial signups. Can you help me figure out
+    what''s wrong?'
+  expected_properties:
+  - Checks for product-marketing.md
+  - Identifies page type as landing page
+  - Identifies conversion goal as free trial signup
+  - Analyzes value proposition clarity
+  - Analyzes CTA placement and copy
+  - Notes message match between ads and landing page
+  - Output has Quick Wins section
+  - Output has High-Impact Changes section
+  - Output has Test Ideas section
+  - Provides 2-3 headline or CTA alternatives
+  rubric: 'Should check for product-marketing.md first. Should identify page type (landing
+    page) and conversion goal (free trial signup). Should analyze across the CRO framework
+    dimensions: value proposition clarity, headline effectiveness, CTA placement/copy/hierarchy,
+    visual hierarchy, trust signals, objection handling, and friction points. Should provide
+    recommendations organized as Quick Wins, High-Impact Changes, and Test Ideas. Should note
+    the message match issue between Google Ads and landing page. Should provide 2-3 headline
+    and CTA copy alternatives with rationale.'
+  tags:
+  - optimize-page
+  - imported
+- id: landing-optimize-page-02
+  department: landing
+  prompt: Our pricing page has three tiers but nobody picks the middle one. 60% choose the
+    cheapest plan and 30% bounce entirely. What should we change?
+  expected_properties:
+  - Applies Pricing Page CRO framework
+  - Addresses recommended plan indication
+  - Addresses 'which plan is right for me' anxiety
+  - Analyzes middle tier differentiation
+  - Suggests specific experiments
+  - Output has Quick Wins section
+  - Output has High-Impact Changes section
+  - Output has Test Ideas section
+  rubric: Should apply the Pricing Page CRO framework. Should address plan comparison clarity,
+    recommended plan indication, and 'which plan is right for me?' anxiety. Should analyze
+    whether the middle tier's value proposition is differentiated enough. Should recommend
+    trust signals and social proof near pricing. Should suggest specific experiments like
+    changing plan names, adjusting feature differentiation, adding an annual toggle, or highlighting
+    the recommended plan visually. Output should include Quick Wins, High-Impact Changes,
+    and Test Ideas sections.
+  tags:
+  - optimize-page
+  - imported
+- id: landing-optimize-page-03
+  department: landing
+  prompt: this page isn't converting. can you take a look? it's our homepage for a B2B project
+    management tool
+  expected_properties:
+  - Triggers on casual phrasing
+  - Identifies as Homepage CRO
+  - Asks about current conversion rate
+  - Asks about traffic sources
+  - Applies CRO Analysis Framework
+  - Addresses serving multiple audiences
+  - Addresses clear paths for different visitor intents
+  - Output has structured sections
+  rubric: 'Should trigger on the casual ''this page isn''t converting'' phrasing. Should identify
+    this as a Homepage CRO analysis. Should ask clarifying questions about current conversion
+    rate, traffic sources, and conversion goal. Should apply the full CRO Analysis Framework
+    starting with value proposition clarity. Should address the homepage-specific guidance:
+    serving multiple audiences, leading with broadest value prop, and providing clear paths
+    for different visitor intents. Should provide structured output with Quick Wins, High-Impact
+    Changes, Test Ideas, and Copy Alternatives.'
+  tags:
+  - optimize-page
+  - imported
+- id: landing-optimize-page-04
+  department: landing
+  prompt: We have a blog that gets 20k organic visits/month but almost nobody clicks through
+    to our product. How do we get more conversions from blog readers?
+  expected_properties:
+  - Applies Blog Post CRO framework
+  - Recommends contextual CTAs matching content
+  - Recommends inline CTAs at natural stopping points
+  - Suggests specific CTA placements
+  - Suggests testing different CTA formats
+  - Cross-references copywriting or related skill
+  rubric: 'Should apply the Blog Post CRO framework. Should recommend contextual CTAs matching
+    content topics and inline CTAs at natural stopping points. Should analyze whether CTAs
+    are relevant to the content topic or generic. Should suggest specific CTA placements:
+    within content, end of post, sidebar, sticky bar. Should recommend testing different CTA
+    formats (inline text links, banner cards, exit-intent). Should cross-reference copywriting
+    skill for CTA copy improvement.'
+  tags:
+  - optimize-page
+  - imported
+- id: landing-optimize-page-05
+  department: landing
+  prompt: We redesigned our landing page and conversions dropped from 4.2% to 2.8%. Here's
+    the new page. What went wrong?
+  expected_properties:
+  - Approaches as diagnostic audit
+  - Checks for lost trust signals
+  - Checks for weakened value proposition
+  - Checks for CTA hierarchy changes
+  - Checks for added friction
+  - Checks for broken message match with traffic sources
+  - Provides fixes organized by impact
+  - Recommends reverting high-risk changes
+  rubric: 'Should approach this as a diagnostic CRO audit focused on what changed. Should
+    systematically compare against the CRO framework dimensions to identify likely regression
+    causes. Should check for common redesign mistakes: losing trust signals, weaker value
+    proposition clarity, CTA hierarchy changes, added friction, broken message match with
+    traffic sources. Should provide specific fixes organized by likely impact. Should recommend
+    reverting high-risk changes while testing others.'
+  tags:
+  - optimize-page
+  - imported
+- id: landing-optimize-page-06
+  department: landing
+  prompt: Our signup form has too many fields and people keep abandoning it halfway through.
+    Can you help optimize it?
+  expected_properties:
+  - Recognizes this as signup flow optimization
+  - References or defers to signup skill
+  - Does not attempt full cro analysis on a form
+  rubric: Should recognize this is about signup form optimization, not general page CRO. Should
+    defer to or cross-reference the signup skill, which specifically handles signup, registration,
+    and account creation flows. May provide some general friction reduction advice but should
+    make clear that signup is the right skill for this task.
+  tags:
+  - optimize-page
+  - imported
+- id: landing-optimize-page-07
+  department: landing
+  prompt: Review this feature page for our API monitoring tool. Most traffic comes from organic
+    search for 'API monitoring tools'. We want them to start a free trial.
+  expected_properties:
+  - Applies Feature Page CRO framework
+  - Connects features to benefits
+  - Suggests use cases and examples
+  - Provides clear path to try/buy
+  - Notes organic traffic source and search intent match
+  - Suggests specific experiment hypotheses
+  - Cross-references ab-testing skill
+  rubric: 'Should apply the Feature Page CRO framework: connect feature to benefit, show use
+    cases and examples, clear path to try/buy. Should reference the experiments section and
+    suggest prioritized test ideas for hero section, trust signals, and CTA variations. Should
+    note the organic search traffic source and check for message match with search intent.
+    Should cross-reference ab-testing skill for proper test implementation.'
+  tags:
+  - optimize-page
+  - imported
+- id: landing-lead-magnet-01
+  department: landing
+  prompt: We're a B2B SaaS selling project management software to marketing agencies. What
+    lead magnet should we create?
+  expected_properties:
+  - Checks for product-marketing.md
+  - Asks about buyer stage and goal
+  - Applies the 5 principles
+  - Recommends specific format with rationale
+  - Examples match the audience and product
+  - Outlines all 5 output sections (recommendation, content, gating, distribution, measurement)
+  rubric: 'Should check for product-marketing.md first. Should ask about current lead gen,
+    existing content assets, and primary goal (list growth, lead quality, product education).
+    Should apply Lead Magnet Principles: solve a specific problem (not ''agency marketing''),
+    match buyer stage, high perceived value + low time investment, natural path to product.
+    Should recommend a specific format suited to a busy agency audience — likely a template
+    (Notion/spreadsheet) or checklist over an ebook. Examples: ''Agency Project Profitability
+    Calculator'' (decision stage, naturally leads to project management), ''Client Onboarding
+    Checklist for Agencies'' (consideration), ''The Agency Capacity Planning Template'' (decision
+    stage). Should justify the choice by matching buyer stage and effort/value ratio. Should
+    outline content, gating, landing page, distribution, and measurement plan.'
+  tags:
+  - lead-magnet
+  - imported
+- id: landing-lead-magnet-02
+  department: landing
+  prompt: We have a 50-page ebook we spent 3 months writing. Conversion on the landing page
+    is only 4%. Should we keep iterating?
+  expected_properties:
+  - Diagnoses likely cause as length/effort mismatch
+  - Recommends format A/B test
+  - Suggests breaking into shorter formats
+  - Reviews landing page structure
+  - Asks about traffic source (cold vs warm)
+  - Cross-references cro or ab-testing skill
+  rubric: 'Should diagnose this as a likely mismatch on Lead Magnet Principles, especially
+    #3 (high perceived value, low time investment — consumable in under 30 minutes, ideally
+    under 10). Should warn 50 pages may signal too much effort to consume — flag this as a
+    possible cause. Should recommend A/B testing the format (chunking the ebook into a 5-part
+    email mini-course, releasing as a checklist + ebook combo, or breaking into shorter topic-specific
+    guides). Should review landing page structure: headline, preview/mockup, what''s inside,
+    social proof, form fields, FAQ. Should suggest testing partial gate (preview first 5 pages)
+    vs full gate. Should ask about traffic source — 4% on cold traffic might be acceptable
+    while 4% on warm traffic is low. Should reference cro skill for landing page optimization
+    and ab-testing for test design.'
+  tags:
+  - lead-magnet
+  - imported
+- id: landing-lead-magnet-03
+  department: landing
+  prompt: Our lead form asks for name, email, company, role, company size, and phone. We're
+    not getting enough signups. Could the form be the problem?
+  expected_properties:
+  - Flags form length as likely culprit
+  - Cites 5-10% per field rule
+  - Recommends reducing to email or email + name
+  - Asks what fields are actually used
+  - Suggests progressive profiling
+  - Cross-references cro skill
+  rubric: 'Should immediately flag form length as a likely culprit. Should cite the rule of
+    thumb: every extra field reduces conversion 5-10%. Should recommend reducing to the minimum
+    needed: ideally email only (highest conversion), or email + name if personalization matters.
+    Should explain when multi-field is justified (only for high-value offers like webinars
+    or demos). Should ask what information is actually used in follow-up — fields that aren''t
+    used should be removed. Should suggest progressive profiling: capture email now, ask for
+    more fields later via enrichment or follow-up forms. Should reference cro skill for form
+    optimization specifically.'
+  tags:
+  - lead-magnet
+  - imported
+- id: landing-lead-magnet-04
+  department: landing
+  prompt: What's the difference between a lead magnet and a free tool? Should I build one
+    or the other?
+  expected_properties:
+  - Distinguishes static content from interactive tool
+  - Compares effort to build
+  - Compares SEO and shareability characteristics
+  - Recommends based on speed vs investment trade-off
+  - Defers to free-tools skill
+  rubric: 'Should explain the distinction: lead magnets are static content offers (ebooks,
+    checklists, templates) while free tools are interactive (calculators, graders, quizzes).
+    Should explain when to build which. Lead magnets: faster to ship (hours-days), works well
+    for awareness/consideration education, lower ongoing maintenance, lead quality varies.
+    Free tools: longer build time (weeks-months), higher engagement and shareability, naturally
+    segment leads by tool usage, can rank for SEO (''X calculator'', ''Y grader''), higher
+    lead quality typically. Should recommend lead magnet first if speed matters, free tool
+    if you can invest the build time and have repeatable user inputs that produce a meaningful
+    output. Should defer to free-tools skill for tool strategy specifically.'
+  tags:
+  - lead-magnet
+  - imported
+- id: landing-lead-magnet-05
+  department: landing
+  prompt: We have a top-performing blog post on email subject lines. Can we use it as a lead
+    magnet?
+  expected_properties:
+  - Recommends content upgrade over gating the post
+  - Cites 2-5x improvement vs generic CTAs
+  - Suggests specific upgrade formats with rationale
+  - Keeps blog post ungated to preserve SEO
+  - Explains why upgrades convert better
+  rubric: 'Should recommend creating a content upgrade specific to the post rather than gating
+    the post itself (post-specific content upgrades convert 2-5x better than generic sidebar
+    CTAs). Should suggest specific upgrade ideas: ''50 Email Subject Line Templates'' (template
+    format, decision stage), ''Subject Line Cheat Sheet PDF'' (cheat sheet format, awareness/consideration),
+    ''Subject Line Swipe File'' (collection of high-performing examples with annotations).
+    Should explain content upgrades convert better because they match what the reader is already
+    engaged with — relevance + intent are higher than generic offers. Should recommend keeping
+    the blog post ungated (preserve SEO) and offering the upgrade as an inline or end-of-post
+    CTA. Should reference cro for placement and copywriting for the upgrade itself.'
+  tags:
+  - lead-magnet
+  - imported
+- id: landing-lead-magnet-06
+  department: landing
+  prompt: Our checklist gets a lot of downloads but very few of them ever sign up for a trial.
+    Is the lead magnet broken?
+  expected_properties:
+  - Diagnoses as lead quality / buyer stage mismatch
+  - Asks about ICP fit of leads
+  - References Lead Quality Signals
+  - Cross-references emails skill for nurture
+  - Suggests a decision-stage lead magnet alternative
+  - Mentions tracking time to conversion by source
+  rubric: 'Should diagnose this as a lead quality / buyer stage mismatch problem. Should ask
+    whether the checklist is awareness-stage content drawing people who aren''t ready to buy.
+    Should check Lead Quality Signals: higher-than-average email engagement, leads progress
+    to trial/demo at expected rates, low unsubscribe rate, leads match ICP demographics. Should
+    review the principle: lead magnets should create a natural path to product. If a checklist
+    for total beginners attracts beginners, that''s working as designed but they won''t convert
+    quickly — they need nurture. Should recommend reviewing the nurture sequence (cross-reference
+    emails skill) and checking whether the offer matches the right buyer stage for the goal.
+    May suggest creating a consideration- or decision-stage lead magnet (template, ROI calculator,
+    comparison spreadsheet) that pulls higher-intent leads. Should track time to conversion
+    by lead magnet source.'
+  tags:
+  - lead-magnet
+  - imported
+- id: landing-popup-design-01
+  department: landing
+  prompt: Help me create an exit-intent popup for our SaaS landing page. We want to capture
+    emails from visitors who are about to leave without signing up. Our product is a social
+    media scheduling tool.
+  expected_properties:
+  - Checks for product-marketing.md
+  - Identifies as exit-intent popup type
+  - Includes compelling headline
+  - Includes lead magnet or incentive
+  - Minimal form fields (email only)
+  - Applies copy formulas from the skill
+  - Addresses trigger configuration
+  - Recommends frequency rules
+  - Includes conversion benchmarks
+  rubric: 'Should check for product-marketing.md first. Should identify the popup type as
+    exit-intent email capture. Should apply the exit-intent popup design guidance: compelling
+    headline (address why they''re leaving or offer additional value), lead magnet or incentive
+    (discount, free resource, extended trial), minimal form fields (email only), clear CTA,
+    and easy close option. Should apply copy formulas from the skill. Should address trigger
+    configuration (exit intent detection). Should recommend frequency rules (don''t show again
+    if dismissed). Should include benchmarks (exit intent popups typically 3-10% conversion).'
+  tags:
+  - popup-design
+  - imported
+- id: landing-popup-design-02
+  department: landing
+  prompt: We want to offer a 10% discount to first-time visitors via a popup. When should
+    we show it and what should it say?
+  expected_properties:
+  - Identifies as discount popup type
+  - Recommends against immediate page load trigger
+  - Suggests better trigger alternatives (time, scroll, exit)
+  - Applies copy formula for discount popups
+  - Includes urgency element
+  - Addresses frequency capping
+  - Addresses compliance considerations
+  rubric: 'Should identify this as a discount/offer popup type. Should apply trigger strategy
+    guidance: recommend against showing immediately on page load (too aggressive). Should
+    suggest time-based delay (30-60 seconds), scroll-based trigger (50%+ page scroll), or
+    exit intent as better alternatives. Should apply the copy formula for discount popups:
+    headline that frames the value, clear offer terms, urgency element, email capture, and
+    CTA. Should address compliance (GDPR cookie consent if applicable). Should recommend frequency
+    capping.'
+  tags:
+  - popup-design
+  - imported
+- id: landing-popup-design-03
+  department: landing
+  prompt: our popups are annoying everyone. we keep getting complaints but we also get a lot
+    of email signups from them. how do we balance this?
+  expected_properties:
+  - Triggers on casual phrasing
+  - Applies frequency and rules guidance
+  - Addresses balance between conversions and UX
+  - Recommends frequency capping
+  - Suggests excluding existing subscribers
+  - Recommends less intrusive alternatives
+  - Suggests A/B testing to optimize
+  rubric: 'Should trigger on casual phrasing. Should apply the frequency and rules guidance.
+    Should address the balance: reduce annoyance while preserving conversions. Should recommend:
+    frequency capping (once per session or once per X days), don''t show to returning visitors
+    who already dismissed, don''t show to existing subscribers, respect ''close'' action,
+    consider less intrusive formats (slide-in instead of full modal, announcement bar instead
+    of overlay). Should address compliance and accessibility requirements. Should suggest
+    A/B testing different triggers and formats to find the best balance.'
+  tags:
+  - popup-design
+  - imported
+- id: landing-popup-design-04
+  department: landing
+  prompt: What types of popups should we use on our blog? We publish content about email marketing
+    and want to grow our email list.
+  expected_properties:
+  - Recommends blog-appropriate popup types
+  - Includes scroll-triggered and exit-intent
+  - Suggests less intrusive formats (slide-in)
+  - Recommends relevant lead magnets
+  - Addresses popup placement on blog pages
+  - Recommends behavior-based triggers for blog
+  - Applies copy formulas
+  rubric: 'Should recommend blog-appropriate popup types: scroll-triggered popup (show after
+    50-70% scroll indicating engagement), exit-intent popup, slide-in (less intrusive than
+    modal), and inline content upgrades. Should recommend lead magnets relevant to the blog
+    topic (email marketing templates, checklist, swipe file). Should address different popup
+    placements: mid-content, end of post, sidebar slide-in. Should recommend behavior-based
+    triggers over time-based for blog content. Should apply copy formulas with blog-specific
+    hooks.'
+  tags:
+  - popup-design
+  - imported
+- id: landing-popup-design-05
+  department: landing
+  prompt: Design an announcement banner for our new feature launch. We want it to show at
+    the top of the site for 2 weeks.
+  expected_properties:
+  - Identifies as announcement banner type
+  - Provides short, clear headline
+  - Includes brief benefit description and CTA
+  - Includes dismiss option
+  - Addresses banner positioning
+  - Recommends audience targeting
+  - Provides copy recommendations
+  rubric: 'Should identify this as an announcement banner popup type. Should apply banner
+    design guidance: short, clear headline announcing the feature, brief description of benefit,
+    CTA to learn more or try it, dismiss option. Should recommend banner positioning (top
+    of page, sticky or static). Should address duration (2 weeks as stated). Should recommend
+    targeting (show to existing users who''d benefit, not just everyone). Should provide copy
+    recommendations.'
+  tags:
+  - popup-design
+  - imported
+- id: landing-popup-design-06
+  department: landing
+  prompt: We need to optimize the lead capture form inside our popup. It currently asks for
+    name, email, company, and phone number. Too many fields?
+  expected_properties:
+  - Recognizes overlap with form optimization
+  - References or defers to cro skill
+  - Notes popups need minimal fields due to context
+  - Does not attempt detailed form redesign
+  rubric: Should recognize this overlaps with form optimization. Should defer to or cross-reference
+    the cro skill, which handles form field optimization, layout, and conversion. May provide
+    popup-specific context (popups need minimal fields due to fleeting attention) but should
+    make clear that cro is the right skill for detailed form optimization.
+  tags:
+  - popup-design
+  - imported
+- id: landing-affiliate-bridge-01
+  department: landing
+  prompt: Help me design a referral program for our SaaS product. We're a $49/month project
+    management tool with about 1,000 customers. We want to encourage word-of-mouth growth.
+  expected_properties:
+  - Checks for product-marketing.md
+  - Distinguishes referral from affiliate
+  - Designs the referral loop (trigger, share, convert, reward)
+  - Recommends double-sided incentive structure
+  - Suggests specific incentives for the price point
+  - Includes launch checklist
+  - Recommends tool integrations
+  rubric: 'Should check for product-marketing.md first. Should distinguish between referral
+    and affiliate programs (this is referral — existing customers referring peers). Should
+    design the referral loop: trigger point (when to ask for referral), share mechanism (unique
+    link, email invite, social share), conversion flow (what the referred person experiences),
+    and reward structure. Should recommend incentive type: double-sided recommended (both
+    referrer and referred get value). Should suggest specific incentives appropriate for $49/month
+    SaaS (e.g., free month for both). Should include the launch checklist. Should recommend
+    tool integrations (Rewardful, Tolt, etc.).'
+  tags:
+  - affiliate-bridge
+  - imported
+- id: landing-affiliate-bridge-02
+  department: landing
+  prompt: We have a referral program but only 5% of customers have ever referred someone.
+    How do we increase participation?
+  expected_properties:
+  - Applies program optimization guidance
+  - Diagnoses potential causes of low participation
+  - Checks awareness, timing, incentive, and friction
+  - Recommends optimization tactics
+  - Suggests timing referral asks at satisfaction moments
+  - Provides experiment ideas
+  rubric: 'Should apply the program optimization guidance. Should diagnose low participation:
+    are customers aware of the program? Is the trigger point well-timed? Is the incentive
+    compelling enough? Is sharing easy? Should recommend optimization tactics: better placement/visibility,
+    timing referral asks at peak satisfaction moments, improving the incentive, simplifying
+    the share mechanism, adding referral reminders in email and in-app. Should provide specific
+    experiment ideas to test improvements.'
+  tags:
+  - affiliate-bridge
+  - imported
+- id: landing-affiliate-bridge-03
+  department: landing
+  prompt: should we do referral or affiliate? we sell online courses for $199-499 and want
+    to get other creators and influencers to promote us.
+  expected_properties:
+  - Triggers on casual phrasing
+  - Clearly distinguishes referral from affiliate
+  - Recommends affiliate for this use case
+  - Provides commission structure guidance for courses
+  - Addresses cookie duration and payout terms
+  - Recommends appropriate affiliate platforms
+  rubric: 'Should trigger on casual phrasing. Should apply the referral vs affiliate distinction
+    clearly. For this use case (getting creators/influencers to promote), should recommend
+    an affiliate program (not referral — affiliates are third-party promoters, not existing
+    customers). Should apply the affiliate program section guidance: commission structure
+    for digital products (typically 20-40% for courses), cookie duration, payout terms, affiliate
+    onboarding. Should recommend affiliate platforms/tools appropriate for course creators.'
+  tags:
+  - affiliate-bridge
+  - imported
+- id: landing-affiliate-bridge-04
+  department: landing
+  prompt: What incentive structure works best? We've been offering $10 off for referrers but
+    it's not working. Our product is $29/month.
+  expected_properties:
+  - Evaluates current incentive structure
+  - Identifies as single-sided and recommends double-sided
+  - Discusses multiple incentive types
+  - Applies tiered incentive concept
+  - Provides specific alternatives to test
+  - Notes incentive may not be the only issue
+  rubric: 'Should evaluate the current incentive: $10 off on a $29/month product is significant
+    but only benefits the referrer (single-sided). Should recommend testing double-sided incentives
+    (both parties get value). Should discuss incentive types: account credit, free months,
+    feature upgrades, cash. Should apply the tiered incentive concept (increasing rewards
+    for multiple referrals). Should provide specific alternative incentive structures to test.
+    Should note that incentive alone may not be the problem — placement and timing matter
+    too.'
+  tags:
+  - affiliate-bridge
+  - imported
+- id: landing-affiliate-bridge-05
+  department: landing
+  prompt: How do we measure the success of our referral program? What metrics should we track?
+  expected_properties:
+  - Applies measuring success framework
+  - Defines participation rate, share rate, conversion rate
+  - Includes viral coefficient / k-factor
+  - Compares referral CAC to other channels
+  - Compares referred customer LTV to organic
+  - Recommends tracking approach
+  - Provides benchmark ranges
+  rubric: 'Should apply the measuring success framework. Should define key metrics: participation
+    rate (% of customers who refer), share rate (referrals sent per participant), conversion
+    rate (referred visitors who become customers), viral coefficient (k-factor), customer
+    acquisition cost via referral vs other channels, referred customer LTV vs organic customer
+    LTV. Should recommend tracking tools and dashboards. Should provide benchmark ranges for
+    each metric.'
+  tags:
+  - affiliate-bridge
+  - imported
+- id: landing-affiliate-bridge-06
+  department: landing
+  prompt: Can you write the referral invitation emails? I need the email that goes out when
+    someone shares their referral link.
+  expected_properties:
+  - Applies referral email section from the skill
+  - Provides referral invitation email guidance
+  - Cross-references emails for broader email work
+  - Provides specific referral email copy or template
+  rubric: Should recognize this overlaps with email writing. Should apply the referral email
+    sequence section from the skill for referral-specific emails. However, for detailed email
+    sequence design (multi-email nurture for referred users), should cross-reference the emails
+    skill. Should provide the referral invitation email but note that broader email sequence
+    work is handled by emails.
+  tags:
+  - affiliate-bridge
+  - imported
+- id: landing-signup-optimize-01
+  department: landing
+  prompt: 'Audit our signup flow. We have a 3-step process: Step 1 asks for email, password,
+    and full name. Step 2 asks for company name, company size, role, and industry. Step 3
+    asks for use case and how they heard about us. Current completion rate is 45%.'
+  expected_properties:
+  - Checks for product-marketing.md
+  - Identifies flow type
+  - Applies minimize required fields principle
+  - Evaluates each field for necessity
+  - Recommends deferring most Step 2 and all Step 3 fields
+  - Provides findings in structured format
+  - Includes Quick Wins, High-Impact Changes, Test Hypotheses
+  rubric: 'Should check for product-marketing.md first. Should identify the flow type (likely
+    B2B SaaS trial). Should apply the core principles: minimize required fields (which of
+    these are genuinely needed before they can use the product?). Should evaluate each step:
+    Step 1 is reasonable, Step 2 fields are mostly deferrable to progressive profiling, Step
+    3 is entirely deferrable. Should recommend cutting to Step 1 only or at most 2 steps.
+    Should provide audit findings in structured format (Issue, Impact, Fix, Priority). Should
+    include Quick Wins, High-Impact Changes, and Test Hypotheses.'
+  tags:
+  - signup-optimize
+  - imported
+- id: landing-signup-optimize-02
+  department: landing
+  prompt: Should we add Google and Microsoft SSO to our signup page? We're a B2B project management
+    tool and currently only have email/password signup.
+  expected_properties:
+  - Applies social auth options guidance
+  - Recommends Google and Microsoft for B2B
+  - Explains conversion benefits of SSO
+  - Recommends prominent placement
+  - Addresses visual separation from email signup
+  - Provides implementation recommendations
+  rubric: 'Should apply the social auth options guidance. For B2B, should recommend Google
+    and Microsoft as the primary SSO options (matching the B2B recommendation). Should explain
+    benefits: higher conversion (less friction), pre-verified email, faster onboarding. Should
+    recommend placing SSO prominently (often higher conversion than email). Should address
+    implementation considerations: clear visual separation from email signup, button copy
+    (''Sign up with Google'' not just Google icon), consider which option to emphasize based
+    on audience.'
+  tags:
+  - signup-optimize
+  - imported
+- id: landing-signup-optimize-03
+  department: landing
+  prompt: our signup form is just email and password but we still only get 35% of visitors
+    to complete it. what else could be wrong?
+  expected_properties:
+  - Triggers on casual phrasing
+  - Investigates beyond form fields
+  - Applies trust and friction reduction
+  - Checks for 'No credit card required' messaging
+  - Checks error handling and password UX
+  - Considers pre-form factors (value prop, page CRO)
+  - Provides diagnostic checklist
+  rubric: 'Should trigger on casual phrasing. Should investigate beyond just form fields since
+    the form is already minimal. Should apply trust and friction reduction guidance: is there
+    a ''No credit card required'' message? Privacy assurance? Testimonial near the form? Should
+    check form-level issues: error handling, password requirements clarity, submit button
+    copy. Should also look at pre-form factors: is the value proposition clear? Is the page
+    optimized? (cross-reference cro). Should provide diagnostic checklist and recommendations.'
+  tags:
+  - signup-optimize
+  - imported
+- id: landing-signup-optimize-04
+  department: landing
+  prompt: We require email verification before users can access the product. Is that hurting
+    our conversion? Should we change it?
+  expected_properties:
+  - Applies verification flows guidance
+  - Explains verification friction impact
+  - Recommends delaying verification
+  - Suggests letting users explore while pending
+  - Discusses when verification is required
+  - Provides improvements if verification is kept
+  rubric: 'Should apply the verification flows guidance. Should explain that requiring verification
+    before product access does create friction and likely reduces activation. Should recommend
+    alternatives: delay verification until needed (let users explore first), magic link as
+    alternative to password, let users start while verification is pending. Should discuss
+    when email verification IS required (compliance, preventing abuse). Should provide specific
+    recommendations for improving the verification experience if kept.'
+  tags:
+  - signup-optimize
+  - imported
+- id: landing-signup-optimize-05
+  department: landing
+  prompt: What experiments should we run on our signup page? We want to improve our trial
+    signup rate.
+  expected_properties:
+  - Applies experiment ideas section
+  - Covers form design experiments
+  - Covers copy and messaging experiments
+  - Covers trial and commitment experiments
+  - Prioritizes by likely impact
+  - Cross-references ab-testing skill
+  rubric: 'Should apply the experiment ideas section. Should provide experiments across categories:
+    form design experiments (layout, field count, SSO), copy and messaging experiments (headline,
+    CTA text, trust elements), trial and commitment experiments (credit card required vs not,
+    trial length), and post-submit experiments. Should prioritize experiments by likely impact.
+    Should cross-reference ab-testing for proper experiment design.'
+  tags:
+  - signup-optimize
+  - imported
+- id: landing-signup-optimize-06
+  department: landing
+  prompt: Users sign up fine but then never activate. Only 20% complete onboarding. What do
+    we do?
+  expected_properties:
+  - Recognizes this as post-signup onboarding, not signup flow
+  - References or defers to onboarding skill
+  - Explains signup covers the signup form, not post-signup
+  rubric: Should recognize this is a post-signup onboarding problem, not a signup flow problem.
+    Should defer to or cross-reference the onboarding skill, which handles post-signup activation
+    and onboarding optimization. Signup-flow-cro covers getting users through the signup form,
+    not what happens after.
+  tags:
+  - signup-optimize
+  - imported
+- id: landing-page-architect-01
+  department: landing
+  prompt: Help me plan the site architecture for our new SaaS marketing website. We have a
+    homepage, product page, pricing page, about page, blog, and want to add competitor comparison
+    pages and integration pages.
+  expected_properties:
+  - Checks for product-marketing.md
+  - Applies 3-click rule and flat vs deep principles
+  - Creates ASCII tree for site structure
+  - Organizes pages logically
+  - Recommends URL structure for each section
+  - Provides navigation design (4-7 header items)
+  - Includes internal linking strategy
+  - Provides hierarchy, URL map, and nav spec
+  rubric: 'Should check for product-marketing.md first. Should apply the page hierarchy design
+    principles (3-click rule, flat vs deep). Should create an ASCII tree showing the full
+    site structure. Should organize pages logically: main nav (Home, Product, Pricing, About,
+    Blog), comparison pages section, integrations hub. Should recommend URL structure patterns
+    for each section. Should provide navigation design recommendations (4-7 header items).
+    Should include internal linking strategy (hub-and-spoke for comparisons and integrations).
+    Should provide the full deliverable set: hierarchy, URL map, nav spec.'
+  tags:
+  - page-architect
+  - imported
+- id: landing-page-architect-02
+  department: landing
+  prompt: Our website has grown organically and the navigation is a mess. We have 50+ pages
+    and users can't find anything. Help us reorganize.
+  expected_properties:
+  - Recommends content inventory first
+  - Groups related pages logically
+  - Applies 3-click rule
+  - Redesigns navigation structure
+  - Provides ASCII tree or visual sitemap
+  - Addresses URL redirects for moved pages
+  - Reduces header navigation items
+  rubric: 'Should treat this as a site architecture audit and redesign. Should recommend starting
+    with a content inventory of all 50+ pages. Should apply the page hierarchy design to reorganize:
+    group related pages, establish clear parent-child relationships, apply the 3-click rule.
+    Should redesign the navigation (reduce header items, use mega-menu or dropdowns for deeper
+    pages). Should provide before/after ASCII tree structure. Should address URL redirects
+    for any pages that move. Should include a visual sitemap (Mermaid).'
+  tags:
+  - page-architect
+  - imported
+- id: landing-page-architect-03
+  department: landing
+  prompt: what should our url structure look like? we keep debating between /blog/post-name
+    vs /resources/blog/post-name and /product/feature vs /features/feature-name
+  expected_properties:
+  - Triggers on casual phrasing
+  - Applies URL structure patterns
+  - Recommends shorter, cleaner paths
+  - Provides recommendations for each section type
+  - Addresses SEO implications
+  - Provides URL map reference
+  rubric: 'Should trigger on casual phrasing. Should apply the URL structure patterns guidance.
+    Should recommend clean, descriptive URLs: prefer shorter paths (/blog/post-name over /resources/blog/post-name),
+    use consistent patterns, avoid unnecessary nesting. Should provide URL structure recommendations
+    for each section type (blog, features, comparisons, integrations). Should address SEO
+    implications of URL structure. Should provide a complete URL map as a reference.'
+  tags:
+  - page-architect
+  - imported
+- id: landing-page-architect-04
+  department: landing
+  prompt: We're adding programmatic SEO pages — 200 integration pages and 50 comparison pages.
+    How should these fit into our site architecture?
+  expected_properties:
+  - Recommends hub pages for each section
+  - Applies hub-and-spoke internal linking
+  - Keeps programmatic pages out of main nav
+  - Provides URL structure for both sections
+  - Addresses crawl budget for 250 pages
+  - Cross-references programmatic-seo skill
+  rubric: 'Should address how to integrate scaled content into the site architecture. Should
+    recommend hub pages for both sections (/integrations and /compare or /vs). Should apply
+    the hub-and-spoke internal linking model. Should address navigation: these shouldn''t
+    clutter the main nav, but should be accessible via hub pages. Should provide URL structure
+    for both sections. Should address crawl budget considerations for 250 new pages. Should
+    cross-reference programmatic-seo for the content strategy.'
+  tags:
+  - page-architect
+  - imported
+- id: landing-page-architect-05
+  department: landing
+  prompt: Can you create a visual sitemap for our site? We want something we can share with
+    our design team.
+  expected_properties:
+  - Provides visual sitemap in Mermaid format
+  - Shows hierarchical page relationships
+  - Includes all major sections
+  - Uses clear, readable format
+  - Suitable for sharing with design team
+  rubric: Should provide a visual sitemap using Mermaid diagram format. Should organize the
+    sitemap hierarchically showing page relationships. Should use the Mermaid graph syntax
+    that can be rendered by most tools. Should include all major sections and key pages. Should
+    be clear enough for a design team to use as a reference for navigation and wireframing.
+  tags:
+  - page-architect
+  - imported
+- id: landing-page-architect-06
+  department: landing
+  prompt: Our XML sitemap hasn't been updated in 6 months and we have crawl errors in Search
+    Console. Can you fix our technical SEO?
+  expected_properties:
+  - Recognizes this as technical SEO, not site architecture
+  - References or defers to seo-audit skill
+  - Explains site-architecture covers design, not technical SEO
+  rubric: Should recognize this is a technical SEO audit task, not a site architecture design
+    task. Should defer to or cross-reference the seo-audit skill, which handles XML sitemaps,
+    crawl errors, and technical SEO issues. Site-architecture focuses on page hierarchy, navigation,
+    and URL structure design — not technical SEO troubleshooting.
+  tags:
+  - page-architect
+  - imported
+# --- END imported ---