
Design, instrument, and build customer onboarding for any business model. Routes to the right configuration (B2B SaaS self-serve, B2B SaaS sales-led, B2C subscription, B2C ecommerce, marketplace/platform, agency/professional services, fintech/regulated), then produces a screen-by-screen build spec with pattern selection, component anatomy, copy direction, layout, flow state machine (abandon/return/skip/error handling), behavioral email sequences, activation milestones, measurement, compliance, benchmarks, and experiments. Supports touch-model overlays (product-led, low-touch automated, hybrid, high-touch, concierge, community-led, partner-led) that modify delivery mechanics. Grounded in observed implementations across 30+ companies (Notion, Figma, Slack, Duolingo, Stripe, Airbnb, Rocketlane, etc.).
Select and define the ideal customer avatar from market research. Extracts candidate segments, scores them on pain/money/reachability/fit with route-specific dimensions, deepens the winner into a full profile with belief maps and objection inventory. Run before brand-guide-creation, constructing-a-funnel, or constructing-a-landing-page. Use when the user has market research and needs to decide WHO to target, or when another skill needs avatar input that doesn't exist yet.
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", or "switch to --preset".
Make a digital product feel professionally crafted. Encodes the brand-agnostic implementation knowledge that separates polished SaaS products from amateur ones — spacing systems, animation, shadows, typography, color, component states, micro-interactions, and invisible polish details. Routes to build (new design system setup), audit (polish an existing product), or deep-dive (specific domain guidance). Procedural, not declarative — every section has fill-in-the-blank fields, decision rules, worked examples from Linear/Vercel/Stripe, and near-miss counter-examples. Anchored on 4 deep-research files with 60+ sources and exact CSS/Tailwind/React values.
Create, critique, or refresh brand guides and brand guideline documents through a collaborative workflow. Use when the user wants to build brand guidelines, brand books, style guides, tone-of-voice docs, logo and visual identity rules, messaging systems, or a full brand manual. Starts with discovery, anchors on local branding assets, then drafts a practical, example-heavy guide with governance, templates, and real usage guidance. Includes procedural visual system rules, AI-readiness layer for design tokens and prompt constraints, and a 7-layer quality audit for digital products.
Design, instrument, and optimize conversion funnels for any business model. Routes to the right configuration (B2B sales-led, B2B PLG, B2C ecommerce, high-consideration application, local service, subscription continuity), then produces an explicit stage-by-stage build spec with measurement, compliance, benchmarks, tactics, and experiments. Supports optional format overlays (VSL, webinar, quiz, tripwire/OTO, product launch, sales letter, bridge) that modify stage maps and add format-specific events.
Refresh your memory on any topic by synthesizing local repo files, Hormozi assets, skills, and web research into a tiered briefing. Use when the user says /explain [topic], asks "what do we know about X", "remind me about X", "catch me up on X", or wants to explore and internalize a topic from the repo or the web.
Create domain-expertise playbook skills for the bilbo repo. Routes to the right architectural pattern (router, linear pipeline, routed playbook, configured playbook with overlays) based on domain complexity, then provides a procedural build guide for each layer. Use when the user wants to create a new business-analysis or strategy skill, or improve the structure of an existing one.
Repeatable playbook for finding and interviewing key stakeholders to validate an offer pillar hypothesis. Produces a pain proximity map, target list, outreach plan, interview protocol, and structured synthesis of findings. Use when a hypothesis needs human validation before building.
Translate role-based organizations into workflow-based organizations by decomposing roles into scored tasks, extracting dark playbooks (proprietary tacit knowledge), formalizing workflows, calculating automation ROI, and producing a sequenced automation roadmap. Use when a company wants to identify what work can be automated, extract undocumented expert knowledge, or build an automation strategy.
Governs agent behavior during coding tasks. Forces the agent to confirm intent before executing, size tasks into reviewable chunks, surface assumptions, stay within declared scope, and present review-friendly summaries. Use on every coding task to keep the human aligned and able to verify the work.
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
Builds stakeholder-friendly project status updates from markdown sources. Use when asked for progress reports, implementation status, future plans, UI/UX flow summaries, infrastructure/data-flow summaries, risks, code smells, or scout-principle improvement notes.
Given an industry or avatar, surface deep, non-obvious, high-value offer pillars and dream outcomes. Routes to the right discovery workflow based on what the user knows (avatar, industry, or both), then applies Hormozi's Dream Outcome framework combined with advanced discovery methods. Use when the user needs to find structural problems with large economic gravity before building.
Generate high-converting lead magnets using Hormozi's frameworks combined with format-channel matching and conversion benchmarks. Produces magnet concepts that score 4/4 on the meta framework (reveals hidden problem, delivers quick result, qualifies prospect, leads to next step). Use for customer acquisition, affiliate attraction, employee recruiting, or early market validation.
Find structurally durable, high-growth markets — not hype cycles. Combines macro structural analysis with micro bottleneck discovery to identify markets with sustainable 10–20 year tailwinds.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
Conduct rigorous multi-source web research for high-stakes questions using hypothesis-driven search, source-quality scoring, contradiction checks, and evidence-backed synthesis. Use when the user asks for deep research, demanding web analysis, market/competitive intelligence, technology due diligence, or decision-grade reports.
Design, audit, or optimize landing pages for any business model. Routes to the right configuration (B2B SaaS, B2C ecommerce, high-consideration application, lead gen / local service, content / lead magnet, pricing page), then produces a section-by-section build spec with copy direction, CTA strategy, post-CTA experience, proof tactics, pricing display, micro-copy, performance targets, accessibility, compliance, and experiments.
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.
Read and maintain business decisions in `business-plan-desicions/`. Use when any task touches product scope, pricing, audience, branding, copy, funnel structure, or go-to-market — read the folder first so decisions stay consistent, and write back when new decisions are made.
Maintains Cantor architecture documentation with an index-plus-domain model. Use when code changes affect architecture, data flow, job execution, tools, auth/security, channels, schema, or UX flows.
Governs agent behavior during coding tasks. Forces the agent to confirm intent before executing, size tasks into reviewable chunks, surface assumptions, stay within declared scope, and present review-friendly summaries. Use on every coding task to keep the human aligned and able to verify the work.