DojoCodingLabs

Designs the legal structure for attaching a venture fund to a studio — Management Co + GP entity + LP entity layered per govclab recommendation. Use when the user asks "attached fund", "studio fund", "management company", "GP LP structure", "fund formation", "LP agreement", "/attached-fund-structure", or has a mature studio and considers launching a fund alongside it. STRONG LEGAL DISCLAIMER — fund formation is highly regulated and jurisdiction-specific; this skill is a preparation aid, NOT legal advice.

Sets up a "Services Hub Model" — a central Services LLC that contracts bilateral MSAs with each independent Venture LLC in a multi-venture portfolio. Middle ground between serial-entrepreneur-with-Multi-LLCs and formal-venture-studio-with-holding. Generates MSA template + SOW template + transfer pricing methodology + IP assignment rider + billing calendar. Use when the user asks "services hub", "MSA template", "shared services setup", "central services entity", "transfer pricing methodology", "/services-hub-setup", or has chosen Services Hub pattern (patrón #6) via structure-decision skill. STRONG LEGAL DISCLAIMER — MSAs are legal contracts that require lawyer review.

Tracks how shared services (engineers, designers, marketing, legal, accounting, infrastructure) are allocated across multiple ventures. Supports two operating modes: Services Hub (bilateral MSAs, independent venture cap tables) and Full Studio (centralized via Management Co + Holding). Essential for transfer pricing compliance, accurate venture P&Ls, and LP reporting. Use when the user asks "shared services", "allocation", "transfer pricing", "studio overhead", "intercompany services", "services hub ledger", "MSA tracking", "/shared-services-ledger". STRONG TAX DISCLAIMER applies.

Guides the founder/studio operator through a decision tree for choosing the corporate structure of their venture(s): Single-LLC vs Multi-LLC vs Cayman Sandwich vs Delaware Tostada vs Skip-CR pattern vs Delaware C-Corp. Use when the user asks "structure-decision", "decidir estructura legal", "¿single LLC o multi LLC?", "Cayman Sandwich", "Delaware Tostada", "Skip-CR pattern", "holding vs multi-LLC", "estructura corporativa", "LATAM incorporation", "/structure-decision", or needs to decide the legal structure for a new venture or for a portfolio of ventures. Produces a structured recommendation with rationale, cost estimates, risks, and an evolution roadmap (migration triggers).

Helps a serial entrepreneur decide whether to formalize their multi-venture operation into a Services Hub or a formal Venture Studio. Evaluates 3 operating modes (not binary): serial entrepreneur puro / services hub operator / formal studio with fund. Use when the user asks "when to become a studio", "serial entrepreneur vs studio", "systematize multi-venture", "formalize studio", "services hub readiness", "venture studio readiness", "/when-to-become-studio".

Identifies "high-liability" ventures in a portfolio that are dangerous to combine under a single-LLC multi-brand structure. Prevents liability contamination across ventures that, if one is sued or has a regulatory incident, could drag down all the others. Use when the user asks "liability contagion", "contagio de responsabilidad", "can I combine these ventures under one LLC", "single-LLC risk", "liability analysis", "regulatory risk portfolio", "/liability-contagion-analysis", or is considering a single-LLC multi-brand structure for multiple ventures. Founder-mode skill — critical for serial entrepreneurs.

Generates a migration roadmap for evolving from the current corporate structure to the next-appropriate one, with specific triggers (ARR thresholds, term sheet, geography changes, regulatory events). Use when the user asks "when to migrate", "structure evolution", "cuándo migrar estructura", "Skip-CR to Tostada", "Tostada to Cayman Sandwich", "flip to Delaware C-Corp", "/structure-evolution-roadmap", or has already chosen their current structure via structure-decision and needs to plan the future transitions.

Generates a sweat equity agreement between co-founders, early employees, advisors, or service providers who contribute work in exchange for equity instead of cash. Covers vesting schedule, cliff, hours-to-equity formula, 83(b) election (for US entities), and dilution considerations. Use when the user asks "sweat equity", "equity for work", "vesting schedule", "cliff", "co-founder equity", "advisor equity", "FAST agreement", "83(b) election", "acuerdo de equity por trabajo", "/sweat-equity-agreement". Extends FAST Agreement template from business-model-toolkit.

Interactive course workbook design system — turns a course's text classes into one standalone, accessible, interactive HTML explainer (a navigable document chunked by module, Articulate-Rise lesson model; stepped mode for screen-recording). Defines the curated component kit, the content-shape -> component mapping rules, the accessibility contract, and the consumer-spec (instruction-bundle-spec.yaml) consumption + graceful-degrade rules. Consumer plugins own the brand tokens and the component vocabulary via their `workbooks` spec section; this skill stays voice-neutral.

Diálogo guiado para diseñar un Path — una super-estructura SOBRE la capa cmi5-curso que agrupa cursos existentes en milestones ordenados y los envuelve en una credential OpenBadge 3.0. NO modifica ningún course.json (aditivo). Produce path.json (fuente de verdad, validado contra path.schema.json) + content/paths/<slug>/path-overview.md (frontmatter alineado con el contrato dojo-academy). Use when user asks to "create a path", "design a path", "new path", "crear un path", "diseñar un path", "nuevo path", "ruta de aprendizaje", "learning path", "armar un path", "/new-path".

Builder's Bloom's — cognitive scaffolding for course design. Use when planning learning objectives, sequencing modules, writing assessment criteria, designing challenge progression, or reviewing whether a course builds toward higher-order thinking. Activated when discussing cognitive levels, objective writing, or skill progression.

Learning Evaluation — measuring whether courses actually work. Use when designing post-course surveys, analyzing course metrics, planning retention strategies, reviewing challenge rubrics, or discussing how to measure learning outcomes beyond quiz scores. Reference skill for evaluation planning.

Systematic research methodology for deep-diving into topics, frameworks, and tech stacks before course creation. Defines source quality standards, research artifact formats, and framework extraction criteria.

Ship-First Design — backward design for builders. Use when planning a new course, structuring modules, aligning assessments to objectives, designing challenges, or reviewing whether content connects to ship milestones. Activated when discussing course planning, curriculum design, assessment alignment, or backward design.

Hormozi-style slide design system for course videos — slide types, accent rules, typography hierarchy, and anti-patterns. Consumer plugins ship the actual HTML/CSS templates referenced here (e.g. dojo-academy ships `content/_templates/slides/dojo-slides-light.html` and `dojo-slides-dark.html`).

Generates and validates per-course teaching-context.md files — defines the target student persona, anxiety points, motivation, and AI positioning for consistent content creation

Email marketing automation — drip sequences, deliverability, template patterns, provider APIs (Resend, SendGrid, Postmark)

Funnel diagnostics engine — bottleneck detection, cross-data correlation, AARRR benchmarks by vertical

High-Velocity Advertising (HVA) — the discipline for creative discovery at machine speed. CLEAR decision rule, the five-layer Stack, the Read Ladder, the two-clocks asymmetry, Benjamini-Hochberg correction, the Vault moat, and the Fit Boundary. The spec behind /hva, /hva-forge, /hva-lint, /hva-review, /hva-vault and the hva-desk agent.

Direct response copywriting framework for paid ads — Hormozi offers, PAS, AIDA, variation generation, LATAM hooks

Synthetic Demand Validation (SDV) — predict purchase intent, price tolerance, and objections for ad creatives, offers, and landing copy by eliciting free-text reactions from a synthetic persona panel and mapping them to Likert distributions. Comparative ranking is the headline signal. Use for "will this convert", "which variant wins", "is $X the right price", "pre-test this creative/offer/copy before spend".

Cross-channel GTM orchestration — channel sequencing, attribution models, retargeting chains, multi-touch journeys

Google Ads expertise — read/measure via the google-ads-open CLI + REST :mutate deploy, signal-first architecture (Hagakure, brand isolation, intent ladder, 5-pillar budget), Performance Max control + Moran feeder, Smart Bidding migration ladder, Enhanced Conversions + Consent Mode v2 + GCLID-to-CRM, broad-match-era keywords + n-gram mining, AI Max for Search, RSA/YouTube creative, policy/reinstatement. Ethical scores (whitehat/grayhat/blackhat 1-10) from the Google Ads Atlas 2026.

GTM Creativity Atlas 2026 — 130+ documented tactics across 15 sections, ethical ratings, tool directory. The full knowledge base for autonomous GTM engineering.

Distribute apps through alternative channels beyond mainstream stores. Android: F-Droid, GitHub Releases (Obtainium-compatible), IzzyOnDroid, direct APK. Linux desktop: Flathub (Phase 2). Covers reproducible builds, fdroiddata metadata, AppStream metadata for Flathub, flatpak-builder manifests, and PR workflow to flathub/flathub. Use this skill when the user asks about F-Droid publishing, open source app distribution, APK distribution outside Play Store, Obtainium, reproducible builds, FOSS app stores, fdroiddata, IzzyOnDroid, self-hosted repos, sideloading, distributing without Google Play, Flathub, flatpak, flatpak-builder, AppStream, 'publish to Flathub', or 'Linux desktop FOSS distribution'.

.NET MAUI multi-target publishing for Android, iOS, Windows (Microsoft Store), and macOS (Mac Catalyst). Covers .NET workload setup, project structure (Platforms/{Android,iOS,Windows,MacCatalyst}), build modes (Debug, Release with AOT/R2R/trimming), per-target signing (Android keystore, iOS provisioning, MSIX self-signing or Microsoft Store, Mac App Store), entitlements, code signing CI workflow, .csproj target framework matrix, MAUI Hot Reload limits in production, and typical migration pitfalls from Xamarin.Forms. Use this skill when the user asks about .NET MAUI, MAUI publishing, dotnet workload install maui, .csproj TargetFrameworks for MAUI, MAUI Android/iOS/Windows packaging, MAUI MSIX, MAUI App Store submission, Xamarin to MAUI migration, or 'ship a .NET MAUI app'.

Build, test, and prepare a Kotlin Multiplatform (KMP / KMM) project for shipping to Google Play and Apple App Store. Covers project structure (commonMain, androidMain, iosMain, iosApp/), Gradle Kotlin DSL config, Kotlin/Native compilation, iOS framework integration via CocoaPods or Swift Package Manager, Compose Multiplatform setup, expect/actual patterns, build commands per platform, signing, version sync between Gradle and iOS Info.plist, and common pitfalls (framework size, transitive Kotlin dependencies, kotlinx.* version conflicts). Use this skill when the user asks about KMP, KMM, Kotlin Multiplatform Mobile, shared Kotlin code, Compose Multiplatform, expect/actual, kotlin-multiplatform Gradle plugin, KMP iOS framework, embed Kotlin in iOS, or 'ship a Kotlin Multiplatform app'.

Package and publish a Linux desktop application to the Snap Store. Covers snapcraft.yaml authoring (parts, plugs, slots, confinement), build via LXD/Multipass, naming registration on Snap Store, channels strategy (edge/beta/candidate/stable), branch tracks, public/private/unlisted visibility, and CI/CD integration. Use this skill when the user asks about Snap Store, snapcraft, Snapcraft, Ubuntu Store, Linux app distribution, snap publishing, '.snap' files, snap channels, snap confinement, classic snaps, or 'publish to Snap Store'.

Submit an app to Microsoft Store via Microsoft Partner Center. Covers two packaging paths (PWA via PWA Builder MSIX, native MSIX from Win32/UWP/desktop apps), Partner Center account setup, app reservation, package upload, store listing requirements (description, screenshots, age rating), certification process (1-7 days typical), and post-launch updates. Use this skill when the user asks about Microsoft Store, Partner Center, MSIX, AppX, Windows Store submission, MS Store certification, Windows app distribution, 'publish to Microsoft Store', or 'Windows app store'.

Validate and improve a Progressive Web App's quality before shipping to stores. Covers Web App Manifest schema, service worker patterns (Workbox 7 / offline-plugin / vanilla), Lighthouse PWA audits (the 14 PWA checks), HTTPS + mixed content, install prompts (beforeinstallprompt), iOS-specific quirks (apple-touch-icon, status bar, safe-areas), and common pitfalls that block app store submission. Use this skill when the user asks about PWA readiness, manifest validation, service worker setup, Lighthouse PWA score, Workbox, offline-plugin, install prompts, 'is my PWA ready', 'why does my PWA fail Lighthouse', PWA Builder requirements, or before /ship-pwa runs gate validation.

Set up over-the-air (OTA) updates for Flutter apps using Shorebird Code Push. Use this skill when the user asks about hot updates, OTA updates, code push, patching without store review, instant updates, bypassing store releases, Shorebird setup, or deploying Dart code changes without going through the app store submission process. Also triggers on: 'push a fix without store update', 'update without releasing', 'Shorebird', 'patch my app', or 'instant deploy'.

Master orchestration for launching a Flutter app to Google Play and App Store in 24 hours. Use this skill when the user wants to ship a Flutter app, plan a mobile release, create a launch timeline, or asks about the steps to publish to app stores. Also triggers when the user mentions 'release plan', 'launch checklist', 'ship my app', 'publish to stores', 'go live', or 'release strategy'. Even if they just say 'I want to launch my app' — this is the skill to use.

Software architecture, design patterns, and system design concepts. Activated for Blue Belt and above when Claude makes significant architectural decisions.

Servers, routes, APIs, and backend architecture. Activated when Claude creates server-side code, API routes, or Express/Fastify/Next.js API handlers.

SQL, databases, ORMs, and data modeling. Activated when Claude works with database code, .sql files, Prisma schemas, or database-related npm packages.

Reading errors, troubleshooting, and fixing bugs. Activated when Claude encounters errors or when the user is debugging. Teaches the most valuable skill: understanding what went wrong.

Hosting, deployment, CI/CD, and going live. Activated when Claude works with deployment configs, Dockerfiles, Vercel/Netlify configs, or deployment-related commands.

React, components, state management, and modern frontend concepts. Activated when Claude works with .jsx/.tsx files or React-related code. Most vibecoded apps use React.

Core programming concepts: variables, functions, conditionals, loops, and data types. Activated when Claude writes basic code structures. Provides teaching context for CodeSensei explanations at the foundational level.

JavaScript essentials for vibecoders. Activated when Claude works with .js/.mjs/.jsx/.ts files. Covers the language concepts most commonly encountered during vibecoding.

Guided entry point for repo health when you don't know which audit you need. Use when the user asks "which audit", "where do I start", wants to check "repo health", or mentions "domain driven" design. Inspects the repo, asks a few plain-language questions, recommends which audit(s) to run (or the full ordered sweep), runs them via the audit-engine, and finishes with a premortem on the remediation plan. Best first command for a new repo.

Audit a repo for structural anti-patterns and repo health: schema drift, duplicated logical columns, multiple writers with no owner, and the broader six-family sweep. Use when the user asks to "audit" a repo, hunt for "drift" or an "anti-pattern", check "repo health", or run a named detector profile (e.g. schema-drift / SCH). Owns the full flow: preflight, scope, detect, verify, cure-map, emit (findings doc + OpenSpec change + Bilingual Linear issues + 4-cure scaffold proposals). Do NOT trigger for premortems, code review of a single PR, or generic status reports.

Reads spec files or SRD tasks and produces structured implementation briefs in the Bilingual Format (Human Layer + Agent Layer). Use when the user asks to "analyze this spec", "create an implementation brief", "process this SRD task", "what needs to be built from this spec", or wants to turn a spec document into actionable implementation steps. Supports OpenSpec, numbered steps, and SRD gap audit. Do NOT trigger for: issue analysis (use spike-recommend), code review, or status reports.

Cross-references open PRs across all repos in the current org with Linear issues, checks Greptile review scores, forces mergeable calculation, and generates an actionable report with merge/rebase/fix recommendations. Use when the user asks "show me open PRs", "what PRs need attention", "review PRs", "check Greptile scores", "what's ready to merge", or wants a comprehensive PR status overview. Do NOT trigger for: creating PRs, code review, or single PR inspection.

Detects when the user wants to work on a Linear issue, implement a feature, fix a bug, or start development work. Suggests the /make-no-mistakes:implement command. Triggers on: "implement", "work on issue", "start on", "pick up issue", "Linear issue", "build feature", "fix bug", "start coding", "work on <PREFIX>-NNN" or "implement <PREFIX>-NNN" for any Linear issue prefix (APP, BACK, SEC, MYTEAM, etc. — based on your workspace), "implement this", "let's build", "start implementing", "pick up this ticket", "work on this task", "execute this issue", "develop this feature", "ship this", pastes a Linear issue URL, or provides an issue ID. Does NOT trigger on: rebase, sync branches, standup, test execution, code review, general coding questions, or session management tasks.

Analyzes issues and produces structured bilingual implementation briefs (Human Layer + Agent Layer). Use when the user asks to "analyze this issue", "create an issue brief", "what does this Linear issue need", pastes a Linear issue URL, or wants to understand and plan work for an issue. By default, the brief is written back to the tracker (Linear / GitHub Issues / etc.) — not to a local file. Do NOT trigger for: general project management or status updates unrelated to a specific issue.

Applies MoSCoW (bucket) + RICE-adapted (intra-bucket ranking) to Linear issues of a product pillar, traceable to its PIBER+IDCF sub-spike and the latest vision audit. Use when the user asks to "prioritize issues", "priorizar el pillar", "aplicar MoSCoW", "rank the backlog", "RICE scoring", "/prioritize", or wants a data-backed decision on what to work on next within a pillar. Do NOT trigger for: generic backlog ranking without pillar context (use spike-recommend or implement-advisor instead), issue creation, or PR review.

Reviews active Linear issues with GitHub cross-referencing, activity insights, and actionable recommendations. Use when the user asks "what are my active issues", "review my Linear issues", "what's the status of my issues", "show me my backlog", "what issues need attention", or wants a comprehensive view of their Linear workspace. Do NOT trigger for: creating new issues, PR review, or code implementation.

This skill should be used when the user asks to "product vision audit", "gap analysis PIBER", "IDCF audit", "auditar vision de producto", "gap analysis", "auditoria de producto", "vision vs implementation", "PIBER audit", "IDCF gap", "audit my module vs spike", "/product-vision-audit", or wants a structured comparison between a declared product vision (PIBER + IDCF spike) and the actual state of a codebase. Produces evidence-backed reports with Design Theses scoring, Capabilities status, Features tier analysis, anti-patterns detected, and prioritized recommendations.

This skill should be used when the user asks to "validate my problem", "founder profile", "customer forces", "customer profile", "market research", "problem interview", "perfil del fundador", "validar mi idea", "validar mi problema", "fuerzas del cliente", "perfil del cliente", "investigacion de mercado", "entrevista del problema", "/problem-validation", or wants guided help with the first stage of building a business model: understanding the founder, validating the problem, profiling the customer, mapping customer forces, and researching the market. Covers Phases 1-5 of the startup lifecycle (Space 1: Problem-Hypothesis).

This skill should be used when the user asks to conduct customer interviews, needs help with "customer interview", "entrevista cliente", "entrevistar clientes", "script de entrevista", "voy a entrevistar", "mentor de entrevistas", "outreach para entrevistas", "resumir entrevista", "patrones en entrevistas", or wants structured guidance through the complete customer development interview methodology (Lean Customer Development by Cindy Alvarez, 2014): 5 core questions, opening/closing scripts, 60-second silence rule, magic wand, "other people" method, speech pattern detection (real vs. aspirational), milestone tracking (2/5/10/15-20 interviews), pattern detection across interviews, V/I/AI summary format, and post-interview self-evaluation. Invocable standalone OR from business-model-toolkit Phase 2 (Problem Validation) and Phase 7 (Solution Interview).

This skill should be used when the user asks about "revenue model", "unit economics", "financial model", "branding", "brand identity", "legal foundation", "modelo de ingresos", "economia unitaria", "modelo financiero", "marca e identidad", "fundacion legal", "costos fijos", "LTV", "CAC", "pricing", "precios", "constitucion legal", "equity", "/execution-plan", or wants guided help with the financial and operational foundation of their startup: revenue streams, unit economics, financial projections, brand identity, and legal structure. Covers Phases 9-13 of the startup lifecycle (Space 3a: Execution Foundation). Requires Space 2 (Solution Validation) to be completed first.

This skill should be used when the user asks to "build a business model canvas", "business model canvas", "BMC", "create my BMC", "build my BMC", "lean canvas", "solution interview", "MVP experiment", "modelo de negocio", "canvas de modelo de negocio", "entrevista de solucion", "experimento MVP", "arma mi business model canvas", "/solution-design", or wants guided help designing the solution, building the Business Model Canvas (14 modules), conducting the solution interview, and designing the MVP experiment. Covers Phases 6-8 of the startup lifecycle (Space 2: Solution-Validation). Requires Space 1 (Problem Validation) to be completed first.

This skill should be used when the user asks to "create a pitch deck", "pitch deck", "investor presentation", "investor deck", "presentacion a inversores", "deck para inversores", "arma mi pitch deck", "genera mi presentacion", "MARP presentation", "presentacion MARP", "/pitch-deck", or wants to generate an investor-ready pitch deck that synthesizes all prior business model work into a compelling 12-slide presentation. Covers Phase 18 of the startup lifecycle. Requires all prior phases (1-17) to be completed first for full context.

This skill should be used when the user asks to "create a pitch script", "pitch script", "video pitch", "guion de pitch", "guion para video", "teleprompter", "script de presentacion", "guion de 3 minutos", "pitch de 3 minutos", "grabar un pitch", "script para grabar", "/pitch-script", or wants to generate a teleprompter-style script for recording a short video pitch (max 3 minutes) in Marp format. The output is a black-background presentation designed for full-screen reading, where the presenter advances slides with mouse or remote.

This skill should be used when the user asks to "create a landing page", "design a landing", "build a conversion page", "funnel page", "pagina de aterrizaje", "pagina de conversion", "pagina de embudo", "landing page", "disenar landing", "/landing-page", or mentions creating a marketing page for their product/service. Also auto-activates when the user mentions "CRO", "conversion rate optimization", "triangulo invertido", or "What/Why/How" in the context of a web page. Covers: Audience Targeting → Conversion Strategy → Emotional Sequence → Content Structure → Section-by-Section Copy → Design Tokens → Spec Output. If the user has completed prior brainstorming phases (Space 1-3 from business-model-toolkit), this skill automatically reads those deliverables to pre-fill context and reduce questions. Output: Landing page spec document + ADR in `./business/04-landing-pages/`

Direct creation of Customer Journey Maps. Use when the user explicitly asks for "customer journey map", "journey map", "mapa del journey", "mapa de viaje del cliente", "journey del cliente", "customer journey", "mapear el viaje", "viaje del usuario", "flujo del cliente", "/customer-journey-map", or when mapping the experience with a specific existing product/service. Shortcut that skips map type selection.

Direct creation of Experience Maps (Day in the Life). Use when the user explicitly asks for "experience map", "day in the life map", "mapa de experiencia", "dia en la vida del usuario", "dia en la vida", "day in the life", "mapear un dia tipico", "rutina del usuario", "como es el dia de mi usuario", "/experience-map", or when the end user does not yet have an existing product/service. Shortcut that skips map type selection.

Guided UX research map creation from scratch. Use when the user asks to "create a journey map", "map user experience", "day in the life", "experience map", "mapear experiencia", "journey del usuario", "mapa de experiencia", "customer journey", "service blueprint", "mapa del cliente", "investigacion de usuarios", "UX research", "mapear la experiencia del usuario", "como vive mi usuario", "mapa de viaje", "experiencia del cliente", "entender a mis usuarios", "/map-workshop", or wants to understand their users' experience. Detects existing personas and guides non-experts through the full process.

Sets up and maintains a continuous research cadence using the 3-12-1 format from Lean UX: 3 users tested per week, by 12:00 noon on 1 day (usually Thursday). Use when the user asks for "research cadence", "weekly user testing", "continuous discovery", "3-12-1", "Thursday user tests", "investigacion continua", "testing semanal", "/research-cadence", or wants to establish a sustainable weekly rhythm for UX research instead of big-bang research events. Generates weekly plans (Mon-Fri activities) and tracks cumulative findings.

Direct creation of Service Blueprints. Use when the user explicitly asks for "service blueprint", "plano de servicio", "blueprint", "procesos internos", "backstage", "frontstage", "linea de visibilidad", "line of visibility", "/service-blueprint", or when mapping internal processes behind a customer journey. Shortcut that skips map type selection.

Direct creation of Storyboards (visual narratives). Use when the user asks for "storyboard", "guion visual", "historia visual", "narrativa del usuario", "comic", "escenas", "/storyboard", or wants to tell the story of a user experience through sequential scenes. Simplest map type, focused on emotion.

Direct creation of User Story Maps for agile planning. Use when the user asks for "user story map", "mapa de historias", "story map", "historias de usuario", "planificacion agil", "agile planning", "backlog", "sprint planning", "/user-story-map", or wants to break down a user journey into development stories.

Runs a collaborative sketch exercise (Design Studio / Design Charrette) adapted for AI-assisted workflows. Use when the user asks for "design studio", "design charrette", "ideacion colaborativa", "ejercicio de sketches", "generar ideas de UI", "6-up", "divergencia de ideas", "/design-studio", or wants to rapidly explore design solution space for a specific problem. Based on Lean UX (Jeff Gothelf, O'Reilly 2013), cap. 5. Focuses on divergent thinking first, then convergence. Output is a decision document with 6 variants + critique + converged solution + parking lot.

Rubric-based co-founder matching methodology. Scores candidate co-founders against a founder's startup profile using a 6-axis framework (domain fit, skill complementarity, values alignment, equity expectations, time commitment, track record). Produces a ranked shortlist with gap analysis + interview questions per candidate. Works standalone (manual candidate input) — can consume DojoOS candidate pool via dojoos-api-consumer agent when available. Use when the user asks "co-founder matching", "find co-founder", "evaluate candidate", "co-founder fit", "co-founder scoring", "/cofounder-matching". NOT legal or HR advice.

Investor fit scoring methodology. Evaluates investor candidates against a startup profile using a 5-axis framework (stage fit, check size fit, thesis alignment, geography / vertical overlap, value-add depth). Produces ranked target list with customized outreach per investor. Works standalone (manual investor input or curated lists like YC, NVCA directory) — can consume DojoOS investor database via dojoos-api-consumer agent when available. Use when the user asks "investor matching", "find investors", "investor fit", "fundraising targets", "VC list", "angel matching", "/investor-matching". NOT financial or legal advice.

Milestone tracking across the 6 DojoOS Launchpad stages (Ideation → Formation → MVP → Traction → Funded → Scaling) with per-stage exit criteria, blockers log, and Dojo-Score-compatible scoring. Produces current-stage.md, milestones.md, blockers.md, dojo-score.md artifacts. Schema-compatible with DojoOS Launchpad stage data model. Use when the user asks "stage tracker", "milestones", "current stage", "startup stage", "Dojo Score", "readiness for next stage", "/stage-tracker". Standalone methodology; syncs with DojoOS via dojoos-api-consumer agent when available.

Demo Day preparation workflow — from application write-up (YC, Techstars, etc.) to pitch deck (10-slide standard) to pitch script (3-min standard) to Q&A prep. Produces deck.md, script.md, qa-bank.md, application.md artifacts. Methodology-driven (adapted from YC, Techstars, DojoCoding demo day patterns); standalone — can later consume DojoOS demo day queue via dojoos-api-consumer agent. Use when the user asks "demo day prep", "pitch deck", "pitch script", "demo day application", "accelerator application", "pitch rehearsal", "Q&A prep", "/demo-day-prep".

Builds the initial cap table for a single venture in the launchpad stage — founders + employee option pool + advisor pool + convertible instruments (SAFEs, notes) + vesting schedule. Produces `cap-table.md` artifact compatible with Carta/Pulley export formats. Use when the user asks "cap table", "build cap table", "vesting calculator", "SAFE terms", "equity split", "founder equity", "option pool", "/cap-table-builder". LEGAL DISCLAIMER applies — output is preparation aid, NOT legal or tax advice. For multi-venture portfolio cap tables, see sibling plugin `venture-studio-toolkit:cap-table-per-venture`.

Generates the standard founder document stack for a new venture — Founder Stock Purchase Agreement (or Operating Agreement for LLCs), IP Assignment, Vesting Schedule Exhibit, Advisor Agreement (FAST framework), SAFE (post-money YC standard), Term Sheet (Series Seed NVCA standard). Each output is a preparation draft, NOT legal advice. Use when the user asks "founder documents", "founder agreement", "IP assignment", "advisor agreement", "SAFE", "term sheet", "FAST agreement", "/founder-documents". STRONG LEGAL DISCLAIMER applies.

Transforms methodology learnings from dog-food sessions of launchpad-toolkit into Linear SPIKE issues formatted for William Ugalde (DojoOS Launchpad owner). This is the plugin's DIFFERENTIATOR — the piece that makes launchpad-toolkit a "methodology laboratory" not just a founder tool. Use when the user asks "propose spike", "generate spike", "feature to spike", "productize this", "send to William", "/feature-to-spike".

AI intake interview structured to produce a `startup-profile.md` artifact compatible schema-wise with DojoOS Launchpad Startup Profile. Use when the user asks "startup intake", "startup profile", "onboard my startup", "create startup profile", "AI intake", "/startup-intake". Produces a structured profile covering problem, customer, solution, team, stage, traction, and funding needs — ready for co-founder matching, investor matching, and demo day prep in subsequent skills (or DojoOS Launchpad).

Comprehensive backend development guide for Supabase Edge Functions + PostgreSQL. Use when working with Supabase (database, auth, storage, realtime), Edge Functions, PostgreSQL, Row-Level Security (RLS), Resend email, Stripe payments, or TypeScript backend patterns. Covers database design, auth flows, Edge Function patterns, RLS policies, email integration, payment processing, and deployment to Supabase.

Waypoint plans methodology and session survival patterns for Claude Code. Use when working on long-running features, need to resume after context reset, want to document task progress, or need to survive session interruptions. Covers three-file structure (plan/context/tasks), SESSION PROGRESS tracking, quick resume instructions, update frequency, and context handoff patterns.

Frontend development guidelines for Next.js + React 19 + shadcn/ui applications. Modern patterns including App Router, Server Components, Client Components, Server Actions, shadcn/ui with Tailwind CSS, React Hook Form, lazy loading, Suspense boundaries, Supabase client integration, performance optimization, and TypeScript best practices. Use when creating pages, components, forms, styling, data fetching, or working with Next.js/React code.

Context tracking and decision logging patterns for intentional memory management in Claude Code Waypoint Plugin. Use when you need to remember user preferences, track decisions, capture context across sessions, learn from corrections, or maintain project-specific knowledge. Covers when to persist context, how to track decisions, context boundaries, storage mechanisms, and memory refresh strategies.

Plan-approval workflow patterns for user control over AI actions in Claude Code Waypoint Plugin. Use when planning complex changes, need user approval before execution, want to prevent mistakes, or need to document proposed changes. Covers plan creation, approval checkpoints, plan deviation tracking, revision management, and learning from approved/rejected plans.

Create and manage Claude Code skills with auto-activation, progressive disclosure, and memory patterns. Use when creating skills, modifying skill-rules.json, understanding triggers (keywords, intent, file, content), working with hooks (UserPromptSubmit, PreToolUse, Stop), debugging activation, implementing guardrails, or building memory-aware skills that persist context across sessions. Covers 500-line rule, session tracking, enforcement levels (block, suggest, warn), plan-approval workflows, and best practices.

Core SRD (Synthetic Reality Development) methodology engine. Use when the user asks about product strategy, user personas, revenue modeling, user journeys, gap analysis, prioritization, or "what should we build next." Activated automatically when SRD-related concepts are discussed.

Synthetic Demand Validation (SDV) engine for SRD. Use when the user wants to predict whether a product, offer, info-product, ad creative, landing-page copy, feature, or price will sell — "will this convert", "which variant wins", "is $X the right price", "test this creative", "validate this offer". Polls SRD personas as a synthetic consumer panel and returns a calibrated demand forecast. Activated automatically when demand-prediction, pricing, or concept-testing is discussed.

Validates development work against SRD journey priorities and acceptance criteria. Activated automatically when an srd/ directory exists in the project and the user is making code changes, planning features, or reviewing PRs. Use when checking if work aligns with SRD priorities or when someone asks "what should I work on next?"

Full video production workflow for Remotion projects. Teaches how to orchestrate MCP tools (TTS, music, SFX, stock footage, video analysis) into complete Remotion compositions. Use this skill whenever producing a video that needs audio, voiceovers, music, stock footage, or analyzing existing video files.

Knowledge for helping users set up the Remotion Superpowers plugin. Covers API key acquisition, dependency installation, and MCP server troubleshooting. Use when running /setup or when a user has issues with MCP connections.