bonus-stack-builder
Design exclusive bonus packages that make YOUR affiliate link the obvious choice. Triggers on: "create bonuses for", "bonus stack", "what bonuses should I offer", "bonus ideas for", "exclusive bonuses", "differentiate my affiliate link", "why buy through my link", "affiliate bonuses", "bonus package", "what can I offer as a bonus", "design bonuses", "build a bonus stack".
What this skill does
# Bonus Stack Builder
Design exclusive bonus packages that make YOUR affiliate link the only rational choice. The product is the same through every affiliate's link — your bonuses are what differentiate you. Creates specific, deliverable bonuses matched to your skills and audience needs.
## Stage
S4: Landing — Bonuses live on the landing page. They are the conversion differentiator between your link and every other affiliate promoting the same product.
## When to Use
- User promotes an affiliate product and wants to stand out from other affiliates
- User asks "why would someone buy through MY link?"
- User wants to increase conversion rates on existing promotions
- User says "bonus", "bonus stack", "exclusive offer", "differentiate"
- After running `grand-slam-offer` to flesh out the bonus suggestions
## Input Schema
```yaml
product: # REQUIRED — the affiliate product
name: string # Product name
description: string # What it does
pricing: string # Product price
url: string # Affiliate link
tags: string[] # e.g., ["ai", "video", "saas"]
your_skills: string[] # OPTIONAL — what you can create/offer
# e.g., ["writing", "design", "coding", "consulting"]
# Default: inferred from context
audience_pain_points: string[] # OPTIONAL — biggest struggles of your audience
# Default: inferred from product category
existing_bonuses: string[] # OPTIONAL — bonuses you already offer
# Default: none
```
**Chaining from S4 grand-slam-offer**: If `grand-slam-offer` was run, use `offer_stack.bonuses` as starting point and flesh them out.
## Workflow
### Step 1: Gather Context
1. If product data available from chain, use directly. Otherwise `web_search` for product details.
2. Identify the product's top 3 pain points it solves
3. Identify the product's top 3 gaps (things users struggle with after buying)
4. Research: `"[product] complaints" OR "[product] struggles" OR "[product] learning curve"` to find bonus opportunities
### Step 2: Design Bonus Stack
Read `shared/references/offer-frameworks.md` for bonus types and rules.
For each bonus, define:
1. **What it is** — specific deliverable, not vague
2. **What problem it solves** — maps to a pain point or product gap
3. **Format** — PDF, video, template, spreadsheet, community access, call
4. **Perceived value** — what you'd charge if sold separately
5. **Effort to create** — low/medium/high (helps user prioritize)
6. **Exclusivity** — why this is ONLY available through your link
Design 5-7 bonuses across these tiers:
- **Tier 1: Quick wins** (low effort to create, high perceived value) — templates, checklists, swipe files
- **Tier 2: Deep value** (medium effort, high impact) — mini-course, workshop recording, tool
- **Tier 3: Premium** (high effort, ultimate differentiator) — personal support, community, coaching
### Step 3: Calculate Stack Value
- Sum perceived values of all bonuses
- Compare to product price — bonus value should be 3-10x product price
- Identify the "hero bonus" — the one that does the most persuasive heavy lifting
### Step 4: Write Bonus Copy
For each bonus, write:
- **Name** — specific and benefit-driven (not "Bonus #1")
- **One-liner** — what it is + what it does for them
- **Value statement** — "$XX value — FREE with your purchase"
- **Delivery method** — how they get it after purchasing
### Step 5: Self-Validation
- [ ] Each bonus is specific and deliverable (not vague promises)
- [ ] At least one bonus addresses the product's biggest gap
- [ ] Total bonus value exceeds product price
- [ ] At least one "exclusive" bonus (only through your link)
- [ ] All bonuses are within your skills to actually create
- [ ] No income claims or unrealistic promises
## Output Schema
```yaml
output_schema_version: "1.0.0"
bonus_stack:
product_name: string
total_value: string # Total perceived value of all bonuses
product_price: string # For comparison
hero_bonus: string # The most compelling bonus name
bonuses:
- name: string
description: string
problem_solved: string
format: string # "pdf" | "video" | "template" | "community" | "call" | "tool"
perceived_value: string
effort_to_create: string # "low" | "medium" | "high"
exclusivity: string
delivery: string # How they receive it
chain_metadata:
skill_slug: "bonus-stack-builder"
stage: "landing"
timestamp: string
suggested_next:
- "landing-page-creator"
- "guarantee-generator"
- "email-drip-sequence"
```
## Output Format
```
## Bonus Stack: [Product Name]
### Stack Overview
- **Product price:** $XX/mo
- **Total bonus value:** $XXX
- **Hero bonus:** [name]
- **Message:** "Get $XXX in exclusive bonuses FREE when you start [product] through my link"
### Bonus 1: [Name] ($XX value)
**What:** [specific deliverable]
**Solves:** [pain point]
**Format:** [format]
**Delivery:** [how they get it]
**Why exclusive:** [only through your link because...]
[Repeat for each bonus]
### Bonus Copy (ready to paste)
✅ [Bonus 1 name] — [one-liner] ($XX value)
✅ [Bonus 2 name] — [one-liner] ($XX value)
...
**Total value: $XXX — yours FREE through my link**
### Creation Priority
1. [Easiest bonus to create first — get live fast]
2. [Next priority]
3. [Can create later — still mention on page]
```
## Error Handling
- **No product provided**: "I need a product to design bonuses for. Run `affiliate-program-search` first, or tell me the product."
- **No skills specified**: Suggest universal bonuses anyone can create: curated resource lists, setup checklists, comparison spreadsheets, email templates.
- **Product is free tier**: Focus bonuses on accelerating results (templates, guides) rather than adding financial value.
- **User can't deliver high-effort bonuses**: Prioritize Tier 1 (templates, checklists) — they have high perceived value with low creation effort.
## Examples
**Example 1:** "Design bonuses for HeyGen affiliate link"
→ Research HeyGen pain points (avatar creation, script writing, video editing), design bonuses: AI avatar setup guide, 50 video script templates, brand voice cheatsheet, private community access, 1-on-1 setup call.
**Example 2:** "What bonuses can I offer for Semrush? I'm a content writer."
→ Match writer skills to Semrush gaps: keyword research template, content calendar spreadsheet, SEO audit checklist, writing prompts for each content type, monthly strategy call.
**Example 3:** "Create bonuses for this product" (after grand-slam-offer)
→ Take bonus suggestions from grand-slam-offer output, flesh each out with specific deliverables, formats, perceived values, and creation timeline.
## Revenue & Action Plan
### Expected Outcomes
- **Revenue potential**: Bonus stacks increase affiliate conversion rates by 2-5x. If your current conversion rate is 1% with 500 monthly clicks = 5 sales × $50 commission = $250/month. With a bonus stack at 3% conversion = 15 sales = $750/month — a $500/month increase from the SAME traffic
- **Benchmark**: Affiliates with bonus stacks report 200-400% higher conversion rates vs naked affiliate links. The hero bonus alone can double conversions
- **Key metric to track**: Conversion rate (sales / clicks) with vs without bonus stack. A/B test by running traffic to both versions for 2 weeks
### Do This Right Now (15 min)
1. Create the **easiest Tier 1 bonus first** — a checklist, template, or swipe file takes 15-30 minutes to make
2. Add the bonus stack copy to your landing page (or create one with `landing-page-creator`)
3. Don't wait until ALL bonuses are ready — launch with 2-3 and add more over time
4. Send an email to your list announcing the exclusive bonuses
### Track Your Results
After 2 weeks: compare conversion rates with and without the bonus stack. If conversion didn't imRelated in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.