Loading...
Loading...
Found 54 Skills
"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 development...
Assumption Inversion — list the assumptions behind the current approach and flip each one, then ask where the flipped version could actually be true. Use when requirements encode beliefs nobody has questioned, when a design feels inevitable, or when incumbents all share one blind spot. Triggers include "invert", "flip it", "flip the assumption", "reverse the premise", "what if the opposite were true", "challenge the assumption". Do NOT use for analytical work like debugging, code review, or implementation tasks.
Original prompt text for the Inversion method. Use it when the user is worried that a plan has pitfalls, wants to defuse risks in advance, prepare a risk contingency plan, or test the robustness of a plan. Trigger words include 逆向法 (inversion), 怎么会失败 (how could it fail), 提前排雷 (defuse risks in advance), 风险预案 (risk contingency), 什么会出错 (what could go wrong), 怎么才能搞砸 (how to screw it up), 反面思考 (backward thinking), inversion, 防护措施 (safeguards), 保证失败 (guarantee failure). Output: a list of guaranteed-failure moves, the flipped rules, the single most easily overlooked rule, and one safeguard action you can take right now. Complements first principles: first principles digs down to the essence and rebuilds from scratch, while inversion works backward from failure to find the defenses.
Analyze a cyclical business - locate where it sits in its cycle (with evidence), normalize its earnings vs peak/trough, run the P/E inversion that trips up naive valuation, read the structural top/bottom tells, and end in a disposition framed as thinking (never buy/sell). A decision-support thinking tool, not financial advice. A standalone skill, independent of /munger and /investment-checklist. Use when the user invokes /cyclicals, says "analyze this cyclical", "where is X in its cycle", "normalize earnings for X", "is it time to buy cyclicals", or pastes a cyclical business (commodity, metals, semis, autos, housing, shipping, airlines, chemicals, paper) to think through.
cmux package architecture, refactor layering, dependency inversion, file organization, DocC documentation, package design discipline, testability, and Swift 6 concurrency rules. Use before adding or meaningfully rewriting Swift files, Swift packages, coordinators, services, repositories, or public package APIs.
Designs and reviews NestJS application architecture using cohesive feature modules, modular monoliths, layered or hexagonal boundaries, dependency inversion, and pragmatic engineering principles. Use when planning a NestJS project, changing module boundaries, evaluating Clean Architecture or DDD, resolving circular dependencies, defining ports and adapters, reviewing coupling, or deciding whether CQRS or microservices are justified. Do not use for pure frontend work or non-NestJS backends. When other skills also apply, reconcile ownership before mutation.
This skill should be used when the user asks to "implement dependency injection in Python", "use the dependency-injector library", "decouple Python components", "write testable Python services", or needs guidance on Inversion of Control, DI containers, provider types, and wiring in Python applications.
Provides comprehensive guidance for hexagonal architecture including ports and adapters, domain isolation, and dependency inversion. Use when the user asks about hexagonal architecture, needs to implement ports and adapters pattern, or structure applications with hexagonal architecture.
Object-oriented design principles including object calisthenics, dependency inversion, fail-fast error handling, feature envy detection, and intention-revealing naming. Triggers on: writing new classes or functions, refactoring, code review, 'clean up', method longer than 10 lines, feature envy, primitive obsession, deep nesting.
Clean Architecture for .NET applications. Covers the 4-project layout (Domain, Application, Infrastructure, Api), dependency inversion, use case handlers, domain entities with behavior, and infrastructure as a plugin. Load this skill when building a project with Clean Architecture, discussing layered architecture, dependency inversion, use cases, or when the architecture-advisor recommends Clean Architecture.
Systematic problem-solving techniques for stuck-ness. Techniques: simplification cascade (complexity spirals), collision-zone thinking (innovation blocks), meta-pattern recognition (recurring issues), inversion exercise (assumption constraints), scale game (uncertainty). Actions: simplify, analyze, recognize patterns, invert assumptions, scale thinking. Keywords: problem solving, complexity spiral, innovation block, stuck, simplification, meta-pattern, assumption inversion, scale uncertainty, breakthrough thinking, root cause, systematic analysis, Microsoft Amplifier, debugging approach, creative solution. Use when: complexity spiraling, hitting innovation blocks, seeing recurring patterns, constrained by assumptions, uncertain about scale, generally stuck on problems.
Use when assessing AI/ML systems for prompt injection, jailbreak vulnerabilities, model inversion risk, data poisoning exposure, or agent tool abuse. Covers MITRE ATLAS technique mapping, injection signature detection, and adversarial robustness scoring.