thinking-archetypes
Use when the same problem keeps recurring despite fixes, growth stalled with no obvious cause, or a quick fix made things worse—match it to a known structural pattern instead of re-diagnosing.
- Installs
- 127
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/tjboudreaux/cc-thinking-skills --skill thinking-archetypes- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads thinking-archetypes automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Systems Archetypes
Overview
Systems archetypes (Peter Senge, "The Fifth Discipline") are recurring structural patterns. Like design patterns in software, once you recognize one you can predict where it leads and where to intervene. Most stubborn, recurring problems aren't unique—they're an instance of a known pattern, and the pattern names the leverage point.
Core Principle: A recurring problem usually has a structural pattern. Match the pattern and the intervention follows.
Trigger Card
When the same problem keeps recurring despite multiple fixes:
- Describe the problem neutrally — symptoms, what's been tried, what keeps coming back.
- Match to an archetype using the Quick Reference Card below (Fixes That Fail, Shifting the Burden, Limits to Growth, Tragedy of the Commons, Escalation, Success to the Successful, Growth and Underinvestment).
- Intervene at the structure, not the symptom — use the Key Question for that archetype.
If no archetype fits after a genuine look, don't force one — drop to thinking-systems and map from scratch. For a first-time one-off problem, just fix it.
When to Use
- The same problem keeps recurring despite multiple "fixes"
- A quick fix made things worse over time
- Growth stalled without an obvious cause
- A shared resource (CI, staging, a cache, a service quota) keeps degrading
- Two efforts are escalating against each other (duplicated services, alert/threshold arms races)
Problem keeps recurring despite fixes? → match an archetype
Quick fix made it worse? → match an archetype
Growth hit an invisible ceiling? → match an archetype
Shared resource degrading? → match an archetype
When NOT to Use
- You need to map the system from scratch (components, interactions, emergent behavior) — use
thinking-systemsinstead. Archetypes are pattern-matching shortcuts for recurring structures; if the system is unfamiliar, map it first, then see if an archetype fits. - You've found the pattern and need to know where to intervene — use
thinking-leverage-points(Meadows' hierarchy). Archetypes name the structure; leverage-points tell you where in that structure to act for maximum effect. - A first-time, one-off problem with a clear cause → just fix it; there's no recurring structure to match.
- No candidate archetype fits after a genuine look → don't force one. Drop to
thinking-systemsand map the actual structure from scratch. - You need to localize a specific faulty codepath → use a hypothesis differential, not pattern-matching.
Quick Reference Card
Match the symptom to the pattern; the Key Question points at the leverage.
| Archetype | Structure | Recognize it by | Key Question (leverage) |
|---|---|---|---|
| Fixes That Fail | Quick fix relieves symptom but a delayed side effect makes it worse | "We fixed this last quarter, why is it back?"; the fix needs ever-larger doses | "What side effect will this fix create?" |
| Shifting the Burden | A symptomatic workaround is used instead of the fundamental fix, creating dependency | Permanent workarounds; "we know the real fix but have no time"; the real capability is atrophying | "What capability are we not building by leaning on this workaround?" |
| Limits to Growth | A reinforcing growth loop hits a balancing constraint | Strong growth that plateaued; more effort, diminishing returns; a resource maxed out | "What will limit us at 10x scale?" |
| Tragedy of the Commons | Each actor gains by using a shared resource; collective overuse depletes it | Shared CI/staging/cache/quota degrading; everyone optimizes locally; no clear owner | "Who owns the long-term health of this resource?" |
| Escalation | Two parties react to each other's moves in a competitive spiral | "They did X so we must do Y"; arms-race dynamics; each side feels defensive | "Can we change the game instead of playing it harder?" |
| Success to the Successful | Initial success grants more resources, compounding advantage and starving alternatives | Past success is the main predictor of new investment; experiments starved to feed the incumbent | "Are we starving future successes to feed current ones?" |
| Growth and Underinvestment | Demand grows toward a limit; capacity investment is delayed until performance degrades into crisis | Reactive investment after the incident; chronic "good enough for now" | "What fails if we grow 50% without adding capacity now?" |
Software Examples (per archetype)
- Fixes That Fail: Adding servers to mask a memory leak → cost spirals, leak remains. Silencing alerts → system degrades until outage.
- Shifting the Burden: Ops manually intervening forever instead of automating; feature flags hiding bugs that never get fixed.
- Limits to Growth: Velocity drops as the codebase grows (complexity limit); adding engineers doesn't speed delivery (coordination overhead).
- Tragedy of the Commons: Teams overload shared CI → everyone's builds slow; cloud costs spike as nobody cleans up resources.
- Escalation: Microservice teams duplicating functionality in response to each other; ever-stricter alert thresholds chasing each other.
- Success to the Successful: Legacy monolith gets all attention so the new architecture never matures.
- Growth and Underinvestment: Database not upgraded until it crashes under load; security investment only after a breach.
Diagnosis Process
- Describe the problem neutrally — symptoms, who/what is involved, what's been tried, what keeps recurring. No blame.
- Sketch the loops — what causes what; where reinforcing (amplifying) loops are, where balancing (limiting) loops are, and where the delays sit.
- Match to an archetype using the Quick Reference Card. If two fit, the system may be layered—note both.
- Intervene at the structure, not the symptom — use the Key Question to find the fundamental solution, the constraint to remove, or the missing/ delayed feedback to add. If none match, stop and use
thinking-systems.
Verification Checklist
- Problem described without blame
- Loops sketched (reinforcing, balancing, delays)
- Matched to a specific archetype (or escalated to
thinking-systemsbecause none fit) - Intervention targets structure, not the recurring symptom
- Considered the side effects of the intervention
Senge's Wisdom
"Structures of which we are unaware hold us prisoner. Once we can see them, they no longer have the same hold on us."
The pattern continues until someone sees it and changes the structure driving it—not the behaviors, but what produces them.
FAQ
What does the thinking-archetypes skill do?
Use when the same problem keeps recurring despite fixes, growth stalled with no obvious cause, or a quick fix made things worse—match it to a known structural pattern instead of re-diagnosing.
How do I install thinking-archetypes?
Run npx skills add https://github.com/tjboudreaux/cc-thinking-skills --skill thinking-archetypes in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/thinking-archetypes/ (personal) or .claude/skills/thinking-archetypes/ (project).
Which AI agents can use thinking-archetypes?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is thinking-archetypes safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains thinking-archetypes?
It is published by tjboudreaux in tjboudreaux/cc-thinking-skills. It has 127 recorded installs.
More from tjboudreaux/cc-thinking-skills
thinking-first-principles
tjboudreaux/cc-thinking-skills
When a constraint is treated as fixed, separate physics from convention, keep only independently supported primitives, and rebuild the simplest solution that satisfies real constraints.
thinking-red-team
tjboudreaux/cc-thinking-skills
For authorized security review of code, auth, or APIs you control, model the attacker, map the attack surface, and report only findings with a reproducible exploit path and verified mitigation.
thinking-pre-mortem
tjboudreaux/cc-thinking-skills
Before committing to a plan or launch, assume it already failed and reason backward through concrete causes — convert failure paths into mitigations, gates, and stop checks.
thinking-theory-of-constraints
tjboudreaux/cc-thinking-skills
When throughput or latency is pipeline-limited, identify the single binding constraint and exploit, subordinate, elevate, then recheck—ignore non-constraints.
thinking-socratic
tjboudreaux/cc-thinking-skills
When a request is vague, assumption-laden, or "obvious," ask the few load-bearing questions that expose hidden requirements before building or committing.
thinking-opportunity-cost
tjboudreaux/cc-thinking-skills
Before committing scarce time, people, or money, name the best forgone use of those resources and the value delta of the chosen path versus that alternative.
Popular marketing & seo skills
reddit-automation
flowkit-labs/skills
Find Reddit threads where people are genuinely asking for what you offer, then draft short, genuinely helpful replies — disclosing your affiliation honestly and naming your product only when it truly answers the question. Two moves: discovery — scan the right subreddits for real needs (recommendation asks, expressed pain, competitor mentions) and rank the few threads where you can actually help; drafting — write from real experience, respect each community's self-promo rules, and keep a human in the loop to review and post. This markets on Reddit the honest way: contribute value, disclose who you are, never astroturf. Distilled from the playbook behind doany.ai's Reddit agent. Triggers on "find reddit opportunities", "reddit marketing", "reddit automation", "reply on reddit for my product", "reddit community engagement", "reddit lead gen", or any ask to turn Reddit threads into genuine, disclosed marketing replies.
twitter-automation
101-skills/superpowers
Automate Twitter/X with posting, engagement, and user management via inference.sh CLI. Apps: x/post-tweet, x/post-create (with media), x/post-like, x/post-retweet, x/dm-send, x/user-follow. Capabilities: post tweets, schedule content, like posts, retweet, send DMs, follow users, get profiles. Use for: social media automation, content scheduling, engagement bots, audience growth, X API. Triggers: twitter api, x api, tweet automation, post to twitter, twitter bot, social media automation, x automation, tweet scheduler, twitter integration, post tweet, twitter post, x post, send tweet
twitter-automation
magentosh/superpowers
Automate Twitter/X with posting, engagement, and user management via inference.sh CLI. Apps: x/post-tweet, x/post-create (with media), x/post-like, x/post-retweet, x/dm-send, x/user-follow. Capabilities: post tweets, schedule content, like posts, retweet, send DMs, follow users, get profiles. Use for: social media automation, content scheduling, engagement bots, audience growth, X API. Triggers: twitter api, x api, tweet automation, post to twitter, twitter bot, social media automation, x automation, tweet scheduler, twitter integration, post tweet, twitter post, x post, send tweet
twitter-automation
qu-skills/superpowers
Automate Twitter/X with posting, engagement, and user management via inference.sh CLI. Apps: x/post-tweet, x/post-create (with media), x/post-like, x/post-retweet, x/dm-send, x/user-follow. Capabilities: post tweets, schedule content, like posts, retweet, send DMs, follow users, get profiles. Use for: social media automation, content scheduling, engagement bots, audience growth, X API. Triggers: twitter api, x api, tweet automation, post to twitter, twitter bot, social media automation, x automation, tweet scheduler, twitter integration, post tweet, twitter post, x post, send tweet
product-launch-video
heygen-com/hyperframes
Turn a product or marketing URL, pasted script, or brief into a product launch / promo video — SaaS promos, feature reveals, product demos, app and company launches. Use when the user wants to market, launch, promote, or reveal a product; the default for any commercial URL. Site tours / showcases of a website route here too — the brief carries the show-it-as-is intent. Unclear → /hyperframes.
twitter-automation
skills-shell/superpowers
Automate Twitter/X with posting, engagement, and user management via inference.sh CLI. Apps: x/post-tweet, x/post-create (with media), x/post-like, x/post-retweet, x/dm-send, x/user-follow. Capabilities: post tweets, schedule content, like posts, retweet, send DMs, follow users, get profiles. Use for: social media automation, content scheduling, engagement bots, audience growth, X API. Triggers: twitter api, x api, tweet automation, post to twitter, twitter bot, social media automation, x automation, tweet scheduler, twitter integration, post tweet, twitter post, x post, send tweet