Claude Skills by martineserios

Break down complex problems to their fundamental truths, then reason up from there. Master Aristotle's ancient method modernized by Elon Musk to solve seemingly impossible problems. Use when: **Facing a \"impossible\" problem** where conventional solutions don't work; **Challenging industry assumptions** that everyone accepts as truth; **Pricing or cost analysis** to find dramatic savings (like Musk with batteries); **Product innovation** when iterating on existing solutions isn't enough; **S...

\"Invert, always invert.\" Apply Carl Jacobi's mathematical principle and Charlie Munger's investing wisdom to solve problems by thinking backward from failure. Use when: **Goal setting** - Define what would guarantee failure, then avoid it; **Risk analysis** - Identify what could destroy your project before starting; **Decision making** - Evaluate choices by examining their worst outcomes; **Problem solving** - When direct approaches aren't working, reverse the question; **Strategy developme...

Discover what customers truly need by analyzing the "job" they hire your product to do. Use when the user mentions "customer discovery", "why customers churn", "what job does this solve", "competing against luck", "product-market fit", "switching behavior", "milkshake moment", or "functional vs emotional jobs". Also trigger when investigating why users choose competitors, designing features around real customer needs, or reframing a value proposition. Covers JTBD interviews, competition analy...

Help users understand the core mechanics of marketplace businesses, from solving the cold start problem to maintaining quality and preventing platform leakage at scale.

Help users define precise liquidity metrics, set competitive take rates based on value delivery, and manage the delicate balance between supply-side health and platform profitability.

Imagine your project has failed spectacularly—then work backward to identify why. Apply Gary Klein's \"prospective hindsight\" technique to catch failures before they happen. Use when: **Before launching** a product, campaign, or major initiative; **Before making** an important decision (hiring, investment, partnership); **Starting a project** to identify risks the team hasn't considered; **When overconfident** and everyone agrees the plan is great; **Before committing resources** to a signif...

Think beyond immediate consequences to understand the chain reactions of decisions. Master Howard Marks' investment framework for seeing what others miss. Use when: **Strategic decisions** where long-term consequences matter; **Policy/rule changes** that will trigger behavioral responses; **Competitive moves** to anticipate market reactions; **Product decisions** where user behavior may shift; **Investment analysis** to see past obvious conclusions

Apply Edward de Bono's parallel thinking framework (1985) to make better decisions by examining ideas from six distinct perspectives systematically. Use when: **Making complex decisions** that require multiple perspectives; **Evaluating new products, offers, or strategies** before launch; **Breaking out of analysis paralysis** with structured thinking; **Running productive meetings** where everyone thinks in the same direction; **Balancing optimism with caution** in strategic planning

Help users identify whether supply or demand is their primary growth bottleneck and apply tactical levers to achieve marketplace liquidity and long-term health.

Help users think in systems and understand complex dynamics. Use when someone is dealing with multi-stakeholder problems, trying to understand second-order effects, managing platform ecosystems, or analyzing complex organizational dynamics.

Surface hidden assumptions, detect logical fallacies, examine evidence quality, and stress-test arguments before committing to them.

Weighted criteria scoring for multi-option decisions — makes trade-offs explicit and defensible with sensitivity analysis.

Bottom-up reasoning from fundamentals — strip assumptions, interrogate each one, rebuild from what's actually true.

Backward-from-failure thinking — define what would guarantee failure, then systematically avoid it.

Understand what customers are actually hiring a product to do — functional, emotional, and social dimensions — to design solutions that win.

Prospective hindsight — imagine the project already failed, then diagnose why. Surfaces hidden risks before commitment.

Chain-reaction mapping — trace consequences beyond the obvious first effect to reveal hidden risks and opportunities.

Six parallel thinking perspectives — White/Red/Black/Yellow/Green/Blue — to separate facts, feelings, risks, benefits, creativity, and process.

Map Strengths, Weaknesses, Opportunities, Threats — then generate cross-referenced strategic moves (SO, WO, ST, WT).

Map players, stocks, flows, and feedback loops to understand why a system behaves the way it does — and where leverage lives.

Master defensive Bash programming techniques for production-grade scripts. Use when writing robust shell scripts, CI/CD pipelines, or system utilities requiring fault tolerance and safety.

Decision support — criteria, scenarios, patterns, recommendation.

Token architecture and component specs: three-layer tokens (primitive→semantic→component), CSS variables, spacing/typography scales, slide generation. Use for design tokens, systematic design, brand-compliant presentations.

Hard-bug diagnosis: tight loop, ranked hypotheses.

Runtime catalog — list all installed skills, agents, and active hooks. Use when you want to know what's available.

DDD tactical patterns — entities, value objects, aggregates, domain services, repositories, specifications, bounded contexts (Python/TypeScript).

Mechanism design (reverse game theory): incentive-compatible rules for allocation — auctions, voting, matching. Use when designing or evaluating a mechanism for incentive compatibility and rationality.

Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing,...

Brainstorm product ideas, explore problem spaces, and challenge assumptions as a thinking partner. Use when exploring an opportunity, generating solutions, or stress-testing an idea before converging on a direction.

Bash wizard for human-only setup.

Reference for drawing any diagram as plain monospace terminal text — box-drawing/ASCII, no external renderer. Read when work-preferences.md's trigger fires.

Two-axis review: Standards vs Spec, unmerged.

Review UI code for Web Interface Guidelines compliance. Use when asked to \"review my UI\", \"check accessibility\", \"audit design\", or \"vs best practices\".