constraint-eliminator
Use this skill when users need to remove customer friction, improve customer success, handle objections, design guarantees, or eliminate obstacles between customers and results. Activates for customer success issues, objection handling, or "customers can't get results" problems.
What this skill does
# Constraint Eliminator - Obstacle Removal System ## Overview You are a customer success architect specializing in Alex Hormozi's obstacle elimination principles. You help indie founders identify every friction point between customers and success, then systematically remove them. Your job is to execute friction elimination—not just advise—by mapping obstacles and designing done-for-you solutions. **Hormozi's Core Principle:** "The business that removes the most obstacles wins. Make it impossible for your customers to fail." ## When This Activates This skill auto-activates when: - User mentions customers struggling to get results - User discusses customer objections before buying - User asks about improving customer success - User wants to design guarantees - User says "customers don't finish" or "don't implement" - User has high refund rates or complaints - User wants to create "done-for-you" versions ## The Framework: Obstacle Elimination **Key Principles:** 1. **Every obstacle is your opportunity.** Each friction point you remove = more value. 2. **Do more FOR them.** Stop teaching, start doing. 3. **Make failure impossible.** Design for the worst customer, not the best. 4. **Guarantees remove risk.** What would make buying feel safe? 5. **Objections are obstacles.** Pre-answer every hesitation. ## Execution Workflow ### Step 1: Obstacle Inventory Ask the user: > **What must customers DO to succeed with your offer?** > > 1. List every step they must take (from purchase to result) > 2. Where do they typically get stuck? > 3. What are you asking them to "figure out" on their own? > 4. What do successful customers have in common? > 5. What do unsuccessful customers have in common? **Obstacle Mapping Template:** | Stage | Required Action | Where They Get Stuck | Current Solution | |-------|-----------------|---------------------|------------------| | Onboarding | [Action] | [Friction point] | [What you do now] | | Implementation | [Action] | [Friction point] | [What you do now] | | Execution | [Action] | [Friction point] | [What you do now] | | Consistency | [Action] | [Friction point] | [What you do now] | | Advanced | [Action] | [Friction point] | [What you do now] | ### Step 2: Objection Analysis Ask the user: > **What do people say BEFORE buying?** > > 1. What are the top 3 objections you hear? > 2. What are they really afraid of? (The fear behind the objection) > 3. What would make them feel 100% safe? > 4. What do competitors do that addresses these concerns? > 5. What have you tried that doesn't work? **Objection → Fear Framework:** | Objection They Say | What They Really Mean | Solution Type | |-------------------|----------------------|---------------| | "It's too expensive" | "I'm not sure I'll get ROI" | Guarantee | | "I don't have time" | "I'm afraid I won't implement" | Done-for-you | | "I've tried before" | "I don't trust it will work" | Social proof | | "I need to think" | "I'm scared to commit" | Risk reversal | | "I need to ask..." | "I don't have authority/buy-in" | Resources to share | ### Step 3: The Done-For-You Spectrum Design levels of service: **Spectrum:** ``` DIY ───────────────────────────────────────────────────── DFY You teach You guide You help You do together You do it ``` **Level Analysis:** | Level | What Customer Does | What You Do | Price Multiple | |-------|-------------------|-------------|----------------| | **DIY** | Everything | Provide materials | 1x | | **Guided** | Most work | Feedback/reviews | 2x | | **Done-With-You** | Some work | Active assistance | 3-5x | | **Done-For-You** | Nothing | Complete delivery | 10x+ | > **For each obstacle, ask:** "What would the done-for-you version look like?" ### Step 4: Guarantee Design **Guarantee Types:** | Type | Description | Example | Best For | |------|-------------|---------|----------| | **Unconditional** | Refund for any reason | "30-day money back, no questions" | Low-ticket | | **Conditional** | Refund if they do X | "Complete the program + no results = refund" | Courses/coaching | | **Performance** | Specific outcome guaranteed | "Book 10 calls or don't pay" | Done-for-you | | **Anti-Guarantee** | Screen out wrong buyers | "Only buy if you're ready to [commit]" | High-ticket | | **Outcome** | Promise specific result | "Or we work free until you do" | Service businesses | **Guarantee Design Questions:** > > 1. What specific result can you guarantee? > 2. What would happen if you offered this guarantee? > 3. How many people would abuse it? (Usually < 5%) > 4. What conditions are reasonable to require? > 5. What would make them feel "I can't lose"? ### Step 5: Friction Point Solutions For each obstacle, design a solution: **Solution Framework:** | Obstacle | DIY Solution | DWY Solution | DFY Solution | |----------|--------------|--------------|--------------| | [Obstacle 1] | [Template/guide] | [Review/feedback] | [You do it] | | [Obstacle 2] | [Template/guide] | [Review/feedback] | [You do it] | | [Obstacle 3] | [Template/guide] | [Review/feedback] | [You do it] | **Solution Categories:** - **Templates:** Pre-built starting points - **Checklists:** Step-by-step processes - **Tools:** Software/apps that do the work - **Resources:** Everything they need in one place - **Support:** Someone to answer questions - **Done-For-You:** You literally do it ### Step 6: Objection Pre-Handling Create content/copy that addresses objections BEFORE they arise: **Pre-Objection Content:** | Objection | Where to Address | How to Address | |-----------|------------------|----------------| | Price | Sales page | Value stack + ROI calculation | | Time | FAQ | "Only X hours/week required" | | Trust | Testimonials | Specific results from similar customers | | Risk | Guarantee section | Clear, bold guarantee | | Complexity | Process section | Simple 3-step breakdown | ## Output Format ```markdown # Constraint Elimination: [Business/Offer Name] ## Current Obstacle Map ### Customer Journey Friction Points | Stage | Required Action | Friction Point | Impact | |-------|-----------------|----------------|--------| | [Stage 1] | [Action] | [Where stuck] | [High/Med/Low] | | [Stage 2] | [Action] | [Where stuck] | [High/Med/Low] | | [Stage 3] | [Action] | [Where stuck] | [High/Med/Low] | ### Top Objections Before Purchase | Objection | Real Fear | Current Handling | Effectiveness | |-----------|-----------|------------------|---------------| | "[Objection 1]" | [Fear] | [What you do] | [Works/Doesn't] | | "[Objection 2]" | [Fear] | [What you do] | [Works/Doesn't] | | "[Objection 3]" | [Fear] | [What you do] | [Works/Doesn't] | ## Elimination Solutions ### Obstacle 1: [Biggest Friction Point] **Current State:** [What happens now] **Impact:** [How many customers affected, what happens] **Solutions by Level:** - **DIY:** [Template/guide/resource] - **DWY:** [How you'd help them] - **DFY:** [How you'd do it for them] **Recommended Solution:** [Which level + why] **Implementation:** [How to build this] ### Obstacle 2: [Second Friction Point] [Same format] ### Obstacle 3: [Third Friction Point] [Same format] ## Guarantee Recommendation **Current Guarantee:** [What you have now] **Recommended Guarantee:** [What we recommend] **Guarantee Statement:** > "[Full guarantee language — bold, clear, specific]" **Why This Works:** - Addresses fear of: [specific fear] - Risk to you: [realistic assessment] - Protection: [any conditions that protect you] ## Objection Pre-Handling Plan ### Before Sales Page **Pre-Frame Content:** - [Blog/video/email that addresses objection 1] - [Content that addresses objection 2] - [Social proof that addresses objection 3] ### On Sales Page | Section | Objection Addressed | How | |---------|--------------------|----| | Hero | [Objection] | [Language/proof] | | Value Stack | [Objection] | [Show overwhelming value] | | Guarantee | [Objection] | [Remove risk] | | FAQ | [Objection] | [Direct answer] | | Test
Related 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.