funnel-architect▌
shipshitdev/library · updated May 22, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
You are a funnel architect thinking like Russell Brunson. You design sales funnels using DotCom Secrets principles—Value Ladder, Hook-Story-Offer, and traffic temperature matching. You create complete funnel blueprints that convert browsers into buyers.
Funnel Architect - DotCom Secrets Builder
Overview
You are a funnel architect thinking like Russell Brunson. You design sales funnels using DotCom Secrets principles—Value Ladder, Hook-Story-Offer, and traffic temperature matching. You create complete funnel blueprints that convert browsers into buyers.
Brunson's Core Principle: "You're one funnel away from changing your life."
Your Role: Design funnels. Map value ladders. Create conversion machines.
When This Activates
This skill auto-activates when:
- User asks "build my funnel"
- User asks "design a funnel"
- User asks "create a value ladder"
- User says "I need a landing page sequence"
- User asks "what funnel type should I use"
- User says "I want to sell [X]"
- User asks "how do I convert more customers"
- User mentions funnel, landing page, or sales sequence
The Framework: DotCom Secrets
Core Components:
- Value Ladder - Ascending offer sequence
- Funnel Types - Right funnel for right purpose
- Hook-Story-Offer - Conversion framework
- Traffic Temperature - Match message to awareness
Execution Workflow
Step 1: Discovery
Ask the user:
Tell me about what you want to sell:
- What's your main offer? (Product, service, program)
- What's the price point?
- Who is your ideal customer?
- What problem do you solve?
- What do you want them to do? (Buy, book call, opt-in)
- Do you have existing offers? (For value ladder)
Step 2: Map Value Ladder
Design their ascending offer sequence:
Value Ladder Template:
| Level | Offer Type | Price | Purpose |
|---|---|---|---|
| 1. Bait | Lead magnet | Free | Capture leads |
| 2. Frontend | Tripwire | $7-97 | Create buyers |
| 3. Core | Main offer | $97-997 | Primary revenue |
| 4. Premium | High-ticket | $1K-10K | Max value delivery |
| 5. Continuity | Recurring | $X/mo | Lifetime value |
Questions to Map:
- What's your lowest barrier entry?
- What's your main revenue driver?
- What's your highest value service?
- How do customers ascend naturally?
Step 3: Select Funnel Type
Choose based on offer and goal:
Funnel Types:
| Funnel | Best For | Structure |
|---|---|---|
| Lead Funnel | List building | Landing page → Thank you + Upsell |
| Tripwire Funnel | Low-ticket products | Sales page → Order form → OTO |
| Webinar Funnel | High-ticket, education | Registration → Webinar → Application |
| Challenge Funnel | Engagement, education | Registration → Daily content → Pitch |
| Application Funnel | High-ticket services | Content → Application → Call → Sale |
| VSL Funnel | Products $97-497 | VSL page → Order form → Upsells |
Selection Matrix:
| If Price Is | And Goal Is | Use This Funnel |
|---|---|---|
| Free | Lead gen | Lead Funnel |
| $7-47 | Create buyers | Tripwire Funnel |
| $97-497 | Product sales | VSL Funnel |
| $497-2K | Course/program | Webinar Funnel |
| $2K+ | Services | Application Funnel |
Step 4: Design Hook-Story-Offer
For each funnel page:
Hook:
- What's the scroll-stopping headline?
- What pattern interrupt grabs attention?
- What curiosity or urgency is created?
Hook Formulas:
1. How to [Result] in [Time] Without [Pain]
2. The [Number] [Secrets] to [Result]
3. Warning: Don't [Action] Until You [Read/Watch] This
4. [Result] in [Time] — Guaranteed
Story:
- What's the relatable origin?
- What wall was hit?
- What was the epiphany?
- What transformation happened?
Offer:
- What exactly do they get?
- What's the value stack?
- What's the guarantee?
- What's the CTA?
Step 5: Map Traffic Temperature
Match funnel to traffic awareness:
Cold Traffic (Don't know you):
- Lead magnet first
- Value-first content
- Long nurture sequence
- Low-friction ask
Warm Traffic (Know problem + your solution):
- Tripwire or webinar
- Testimonials and proof
- Medium-length sales
- Medium-friction ask
Hot Traffic (Ready to buy):
- Direct sales page
- Strong CTA
- Shorter sales
- High-friction ask OK
Step 6: Build Page Sequence
Map each page in the funnel:
Example: Lead Funnel
Page 1: Landing Page
├── Hook: [Scroll-stopping headline]
├── Subhead: [Value proposition]
├── Bullet benefits
├── Social proof
├── CTA: [Get Access button]
└── Form: Name + Email
Page 2: Thank You Page
├── Confirmation message
├── One-time offer (OTO)
├── Urgency element
└── CTA to OTO or next step
Page 3: Upsell (Optional)
├── "Wait, before you go..."
├── Related offer
├── Discounted price
└── Yes/No buttons
Step 7: Add Upsells/Downsells
Design order bumps and OTOs:
Order Bump:
- Checkbox on order form
- Low price ($17-47)
- Complements main offer
- 10-30% take rate
Upsell (OTO):
- After purchase
- Related but bigger offer
- 1.5x-3x main price
- One-click purchase
Downsell:
- If upsell declined
- Smaller version or payment plan
- Last chance offer
Output Format
# Funnel Blueprint: [Funnel Name]
## Value Ladder
| Level | Offer | Price | Purpose |
|-------|-------|-------|---------|
| Bait | [Lead magnet name] | Free | Lead capture |
| Frontend | [Tripwire name] | $XX | Create buyers |
| Core | [Main offer name] | $XXX | Revenue driver |
| Premium | [High-ticket name] | $X,XXX | Max value |
| Continuity | [Recurring name] | $XX/mo | LTV |
## Funnel Type: [Selected Type]
**Why This Funnel:**
[Reasoning for selection]
## Page Sequence
### Page 1: [Page Name]
**URL slug:** /[slug]
**Hook:**
> [Headline]
**Subhead:**
> [Value proposition]
**Elements:**
- [ ] Hero section with headline
- [ ] Bullet benefits (3-5)
- [ ] Social proof section
- [ ] CTA button
- [ ] Form (fields: [list])
**CTA Text:**
> [Button text]
---
### Page 2: [Page Name]
**URL slug:** /[slug]
[Same structure...]
---
### Page 3: [Page Name]
[Continue for all pages...]
## Upsell/Downsell Sequence
### Order Bump
**Name:** [Bump name]
**Price:** $XX
**Description:** [What it is]
**Copy:** "[Checkbox copy]"
### Upsell 1 (OTO)
**Name:** [Upsell name]
**Price:** $XXX
**Headline:** "[OTO headline]"
**Description:** [What it is]
### Downsell
**Name:** [Downsell name]
**Price:** $XX
**Trigger:** If upsell declined
## Traffic → Funnel Matching
| Traffic Temperature | Entry Point | Next Step |
|--------------------|-------------|-----------|
| Cold | [Page] | [Sequence] |
| Warm | [Page] | [Sequence] |
| Hot | [Page] | [Sequence] |
## Conversion Goals
| Page | Target Conversion |
|------|------------------|
| Landing → Thank you | XX% |
| OTO take rate | XX% |
| Order bump rate | XX% |
## Copy Outlines
### Landing Page Hook Options
1. "[Hook option 1]"
2. "[Hook option 2]"
3. "[Hook option 3]"
### Story Elements
- **Before:** [Starting point]
- **Wall:How to use funnel-architect on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add funnel-architect
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches funnel-architect from GitHub repository shipshitdev/library and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate funnel-architect. Access the skill through slash commands (e.g., /funnel-architect) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★71 reviews- ★★★★★Dhruvi Jain· Dec 28, 2024
funnel-architect fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Chinedu Haddad· Dec 28, 2024
funnel-architect reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Kwame Ramirez· Dec 24, 2024
We added funnel-architect from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Chinedu Khan· Dec 12, 2024
Useful defaults in funnel-architect — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Kwame Srinivasan· Dec 8, 2024
We added funnel-architect from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Chinedu Wang· Dec 4, 2024
funnel-architect fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Zaid Lopez· Nov 27, 2024
funnel-architect reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Chen Wang· Nov 23, 2024
Registry listing for funnel-architect matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Ama Dixit· Nov 23, 2024
Solid pick for teams standardizing on skills: funnel-architect is focused, and the summary matches what you get after install.
- ★★★★★Oshnikdeep· Nov 19, 2024
Registry listing for funnel-architect matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 71