All authors

Claude Skills by tjboudreaux
github.com/tjboudreaux29 skills0 installs79 views
- Thinking Bounded RationalityApply Herbert Simon's Bounded Rationality and satisficing to make good-enough decisions under real-world constraints. Use for design decisions under time pressure, recognizing cognitive limits, and setting appropriate stopping criteria.Votes: 0GitHub stars: 1,281
- Thinking Circle Of CompetenceKnow the boundaries of your expertise and operate within them. Use when evaluating opportunities, making decisions outside your domain, or assessing when to defer to experts.Votes: 0GitHub stars: 1,281
- Thinking CynefinClassify problems by complexity domain (clear, complicated, complex, chaotic) and match approach to domain. Use for choosing methodologies, problem framing, and process design.Votes: 0GitHub stars: 1,281
- Thinking EffectuationStart with means, not goals; co-create with partners; leverage contingencies. Use for startup strategy, innovation projects, and uncertain/novel domains where planning is unreliable.Votes: 0GitHub stars: 1,281
- Thinking First PrinciplesBreak complex problems into fundamental truths by questioning assumptions and rebuilding from irreducible components. Use for innovation, challenging status quo, or when conventional solutions fail.Votes: 0GitHub stars: 1,281
- Thinking Five Whys PlusEnhanced root cause analysis with explicit bias guards and stopping criteria. Use for incident post-mortems, bug investigations, and process failures where standard 5 Whys might mislead.Votes: 0GitHub stars: 1,281
- Thinking Jobs To Be DoneUnderstand what "job" users hire your product to do, focusing on progress users seek rather than features. Use for product development, feature prioritization, user research, and market positioning.Votes: 0GitHub stars: 1,281
- Thinking Kepner TregoeSystematic rational process for complex problem analysis, decision making, and risk assessment. Use for high-stakes engineering decisions, root cause analysis beyond 5 Whys, and multi-factor evaluations requiring structured criteria.Votes: 0GitHub stars: 1,281
- Thinking Lindy EffectFor non-perishable things, future life expectancy is proportional to current age. Use for technology selection, evaluating frameworks/libraries, and predicting tool longevity.Votes: 0GitHub stars: 1,281
- Thinking Map TerritoryRecognize limits of mental models and diagrams. Use when models diverge from reality, debugging expectation mismatches, or questioning abstraction accuracy.Votes: 0GitHub stars: 1,281
- Thinking Margin Of SafetyBuild in buffers for unknown unknowns and don't optimize to the edge. Use for capacity planning, deadline estimation, architecture design, and risk management.Votes: 0GitHub stars: 1,281
- Thinking Model CombinationCombine multiple mental models for richer analysis. Use for complex problems requiring multiple lenses, high-stakes decisions, or when single models leave blind spots.Votes: 0GitHub stars: 1,281
- Thinking Model RouterRoute to the right mental model based on your domain and problem type. The single entry point for all thinking skills.Votes: 0GitHub stars: 1,281
- Thinking OodaRapid decision-making loop for dynamic situations. Use for incident response, competitive scenarios, time-sensitive decisions, and situations requiring quick adaptation.Votes: 0GitHub stars: 1,281
- Thinking Opportunity CostEvaluate decisions by what you give up, not just what you gain. Use for resource allocation, prioritization, build vs. buy choices, and technical debt evaluation.Votes: 0GitHub stars: 1,281
- Thinking Pre MortemImagine a project has failed and work backward to identify why. Use at project kickoffs, before major decisions, or when optimism may be obscuring risks.Votes: 0GitHub stars: 1,281
- Thinking ProbabilisticExpress confidence in ranges, update predictions with new information, and track calibration over time. Use for project estimation, risk assessment, and decision making under uncertainty.Votes: 0GitHub stars: 1,281
- Thinking Red TeamDeliberately attack your own plans, systems, and assumptions to find weaknesses before adversaries or reality does. Use for security review, architecture validation, plan stress-testing, and pre-launch preparation.Votes: 0GitHub stars: 1,281
- Thinking ReversibilityClassify decisions by reversibility and match decision process to decision type. Use for technology choices, architecture decisions, process changes, and hiring decisions.Votes: 0GitHub stars: 1,281
- Thinking Scientific MethodHypothesis → Prediction → Test → Revise with explicit falsification. Use for debugging, feature experimentation, performance investigation, and A/B testing design.Votes: 0GitHub stars: 1,281
- Thinking Second OrderThink beyond immediate consequences to second and third-order effects. Use for strategic decisions, policy changes, and avoiding unintended consequences.Votes: 0GitHub stars: 1,281
- Thinking SocraticSystematic questioning framework to deepen understanding, challenge assumptions, and uncover hidden beliefs. Use for requirements gathering, debugging, coaching, and critical analysis.Votes: 0GitHub stars: 1,281
- Thinking Steel ManningArgue against the strongest version of opposing positions, not the weakest. Use for design reviews, evaluating alternatives, conflict resolution, and decision validation.Votes: 0GitHub stars: 1,281
- Thinking SystemsAnalyze problems as interconnected systems with feedback loops, emergent behavior, and non-linear effects. Use for debugging complex systems, architecture decisions, and understanding unexpected behavior.Votes: 0GitHub stars: 1,281
- Thinking Theory Of ConstraintsIdentify and manage the bottleneck; improvements elsewhere don't matter until the constraint is addressed. Use for performance optimization, process improvement, and resource allocation.Votes: 0GitHub stars: 1,281
- Thinking Thought ExperimentTest ideas through hypothetical scenarios when empirical testing is impractical. Use for architecture evaluation, edge case analysis, ethics considerations, and strategy development.Votes: 0GitHub stars: 1,281
- Thinking TrizApply TRIZ (Theory of Inventive Problem Solving) methodology to resolve technical contradictions and find innovative solutions. Use for engineering design, breaking through impossible constraints, and systematic innovation.Votes: 0GitHub stars: 1,281
- Thinking Via NegativaImprove by removal rather than addition. Focus on what to stop doing, eliminate the negative, and subtract complexity. Use for system simplification, process improvement, and feature prioritization.Votes: 0GitHub stars: 1,281
- RosettaReconcile ALL prior agent conversations (Claude Code, Codex, Droid/Factory, Hermes, Cursor) with git history and docs into a cited ground truth, and distill durable decision records (ADRs/PDRs/BDRs). Use whenever the user wants to catch up on or get the state of a project, build or refresh a ground truth, read or mine previous agent/AI conversations, recover or record what was decided (technical, product, or business), capture/index/validate ADRs or PDRs, discover which projects on the machin...Votes: 0GitHub stars: 2