Explorar skills

Classify a proposed code change as Leaf Node or Core Code to decide how much AI usage and review rigor is appropriate. Use this skill whenever the user asks "is this leaf or core", "what kind of change is this", "should I vibe code this", "can AI write this", "how rigorous should the review be", or before starting any non-trivial change. Also useful as a sub-step inside other workflows (planning,

Review a Pull Request or code change with rigor calibrated to whether it's leaf-node or core code. Use this skill whenever the user asks to review, audit, or evaluate code — phrases like "review this PR", "audit this code", "is this PR ready", "look at this branch", "review my changes", "what do you think of this", "code review please". Also trigger when reviewing AI-authored code specifically. Th

Financial projections and viability analysis for bootstrapped founders. Assesses revenue model clarity, unit economics, cash-flow profile, break-even path, revenue stairs, AI-native cost structure, pricing power, stress resilience, and founder sustainability. Use when user runs `/financial-projections`, asks about "unit economics", "break-even", "cash flow", "revenue projections", "pricing power",

30/60/90-day execution roadmap for bootstrapped founders. Synthesizes all prior analysis into a chronological plan with weekly action items, deliverables, decision gates, kill criteria, tools/budget, and phase exit criteria. Best after running dimension skills. Use when user runs `/launch-plan`, asks about "launch plan", "execution roadmap", "what do I do first", "90-day plan", "action plan", "nex

Risk matrix and pre-mortem analysis for bootstrapped founders. Produces a pre-mortem exercise, ranked risk matrix (10-15 risks), blind spot detection, and 7-dimension risk assessment with 5 validation gates. Surfaces the risks founders aren't thinking about. Use when user runs `/risk-assessment`, asks about "risks", "what could go wrong", "blind spots", "pre-mortem", "risk analysis", "failure mode

Product fitness and solution validation for bootstrapped founders. Assesses whether THIS specific solution is the right way to address a validated problem — value proposition clarity, solution-problem fit, minimum product achievability, differentiation reality, switching motivation, time-to-value, retention potential, and substitute vulnerability. Use when user runs `/solution-analysis`, asks abou

Use when you want to audit environment variable usage — scans the entire codebase for all env var references across all sources (code, Docker, CI, config files) and flags anything undocumented or inconsistent. Works for any stack and any env var pattern.

Use before committing or opening a pull request — reviews staged changes as a principal engineer for correctness, edge cases, and logic flaws. Always invoke this before creating a PR.

This skill should be used when the user asks to "optimize a task with parallel strategies", "deploy winning strategies", "run competing approaches", "find the best approach by trying multiple strategies", or mentions "winning", "parallel optimization", "strategy competition". Orchestrates multiple background agents running Ralph-style loops to converge on the best solution.

Comprehensive guide for Pixi package manager - Python environment management, CUDA/GPU support, PyPI integration, Docker/Pixi-Pack deployment, and best practices for ML research

Gancho

Comprehensive guide for building Python monorepos with uv workspaces - unified dependency resolution, shared lock files, editable installs, testing strategies, Docker optimization, and CI/CD patterns for managing multiple packages in a single repository