[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AS0RJ383D8BKH8VBGY8MMF":3,"skill-same:01M7AS0RJ383D8BKH8VBGY8MMF":44},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":43},"01M7AS0RJ383D8BKH8VBGY8MMF","thinking-systems",null,"When behavior is emergent across components—fixes elsewhere break, loops\u002Fdelays dominate—map boundary, stocks\u002Fflows, feedback, archetypes, then rank leverage.","ham-zax\u002Fwebharness","ham-zax","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F81289670?v=4","01M7AQGHAV4TPYCAZY23S7SVSC","Ahmed Hamza","01M7AQGHBCFJYE7KWZ34W9HEGH",0,"MIT","https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness\u002Fblob\u002Fmain\u002Fskill-library\u002Fpacks\u002Fthinking\u002Fthinking-systems\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: thinking-systems\ndescription: When behavior is emergent across components—fixes elsewhere break, loops\u002Fdelays dominate—map boundary, stocks\u002Fflows, feedback, archetypes, then rank leverage.\ndisable-model-invocation: true\n---\n\n# Systems Mapping and Leverage\n\nTreat the problem as structure and interaction, not isolated parts. Map boundary, stocks\u002Fflows, loops\u002Fdelays, and recurring patterns; intervene at the highest feasible leverage after a side-effect check.\n\n## When to Use\n\n- Symptom spans services\u002Fcomponents; single-stack fixes fail or bounce.\n- A change in one place breaks another; behavior is emergent.\n- Problem recurs despite local fixes (structure, not only symptom).\n- Need to rank interventions when parameter\u002Fbuffer tweaks do not stick.\n\n## When NOT to Use\n\n- Single-component linear bug with clear stack\u002Fdiff—trace and fix.\n- Throughput limited by one obvious stage—use theory-of-constraints.\n- Decision is a consequence chain of one proposed action—use second-order.\n- Approach selection (plan vs probe vs stabilize)—use cynefin first.\n\n## Procedure\n\n1. **Bound the system.** Name purpose, actors, boundary, and in\u002Fout flows. Exclude noise outside the decision horizon; include any path that can feed the symptom.\n2. **Map stocks and flows.** List accumulating stocks (queue depth, debt, cache size, WIP) and the rates that fill\u002Fdrain them. Note what changes slowly even when flows jump.\n3. **Find feedback and delays.** For each candidate loop: classify reinforcing (amplifies) vs balancing (resists); mark same-direction (+) vs opposite (-) links; name delays (TTL, deploy lag, metric lag, ramp-up). Even count of opposite links → reinforcing; odd → balancing. Long delay + strong correction → overshoot risk.\n4. **Match recurring structure when problems return.** Check only if recurrence or policy resistance is present; do not force a pattern:\n   - Fixes That Fail — quick fix, delayed worse side effect\n   - Shifting the Burden — workaround starves fundamental fix\n   - Limits to Growth — growth hits a balancing constraint\n   - Tragedy of the Commons — local optima deplete a shared stock\n   - Escalation — mutual reaction spiral\n   - Success to the Successful — advantage compounds via allocation\n   - Growth and Underinvestment — capacity lags demand until crisis\n   If none fits after a genuine pass, keep the from-scratch map.\n5. **Trace symptom to structure.** Walk upstream along flows and loops; separate proximate symptom from structural driver (interaction, delay, wrong goal, missing info).\n6. **Rank interventions by leverage, then side effects.** Prefer higher feasible class: goals\u002Fparadigm → rules\u002Finformation → loop structure (gain, balancing add, delay shorten) → stock\u002Fflow topology → buffers\u002Fparameters. For each candidate: feasibility, blast radius, delayed reversal risk. Prefer moves that cut harmful reinforcing gain or strengthen needed balancing loops without creating a new commons\u002Fescalation.\n7. **Stop.** Commit highest feasible intervention plus watch signals for loop\u002Fdelay response. Re-map only if the structure changes or the intervention fails its watch.\n\n**Stop when** boundary, key stocks\u002Fflows, dominant loop(s)+delay(s), optional archetype, and a ranked intervention with side-effect check are stated—or when the problem collapses to a single linear cause.\n\n## Output\n\n```text\nboundary: \u003Csystem purpose and edges>\nstocks_flows: \u003Cstock → inflow\u002Foutflow list>\nloops:\n  - name: \u003Cloop>\n    type: reinforcing | balancing\n    delay: \u003Cwhere cause lags effect>\n    links: \u003Cbrief +\u002F->\narchetype: \u003Cname or none>\nstructural_driver: \u003Cone sentence>\ninterventions_ranked:\n  - level: \u003Cgoals|rules|loops|structure|params>\n    action: \u003Cwhat>\n    side_effects: \u003Cfeedback\u002Felsewhere\u002Fdelay risk>\nchosen: \u003Chighest feasible>\nwatch: \u003Csignals that confirm or falsify>\n```\n\n## Verification\n\n- **Falsify:** If removing one component fully explains and fixes the issue with no cross-effects, systems mapping is wrong—drop to local debug. If utilization shows one fixed stage as the sole cap, switch to theory-of-constraints.\n- **Stop:** Do not keep adding loops after the chosen intervention and watch are set.\n- **Over-application guard:** No archetype without recurrence evidence. No low-leverage param tweak listed as primary when a feasible higher class exists. Do not recreate standalone archetype\u002Ffeedback\u002Fleverage procedures—those checks live only inside this map.\n","# Systems Mapping and Leverage\n\nTreat the problem as structure and interaction, not isolated parts. Map boundary, stocks\u002Fflows, loops\u002Fdelays, and recurring patterns; intervene at the highest feasible leverage after a side-effect check.\n\n## When to Use\n\n- Symptom spans services\u002Fcomponents; single-stack fixes fail or bounce.\n- A change in one place breaks another; behavior is emergent.\n- Problem recurs despite local fixes (structure, not only symptom).\n- Need to rank interventions when parameter\u002Fbuffer tweaks do not stick.\n\n## When NOT to Use\n\n- Single-component linear bug with clear stack\u002Fdiff—trace and fix.\n- Throughput limited by one obvious stage—use theory-of-constraints.\n- Decision is a consequence chain of one proposed action—use second-order.\n- Approach selection (plan vs probe vs stabilize)—use cynefin first.\n\n## Procedure\n\n1. **Bound the system.** Name purpose, actors, boundary, and in\u002Fout flows. Exclude noise outside the decision horizon; include any path that can feed the symptom.\n2. **Map stocks and flows.** List accumulating stocks (queue depth, debt, cache size, WIP) and the rates that fill\u002Fdrain them. Note what changes slowly even when flows jump.\n3. **Find feedback and delays.** For each candidate loop: classify reinforcing (amplifies) vs balancing (resists); mark same-direction (+) vs opposite (-) links; name delays (TTL, deploy lag, metric lag, ramp-up). Even count of opposite links → reinforcing; odd → balancing. Long delay + strong correction → overshoot risk.\n4. **Match recurring structure when problems return.** Check only if recurrence or policy resistance is present; do not force a pattern:\n   - Fixes That Fail — quick fix, delayed worse side effect\n   - Shifting the Burden — workaround starves fundamental fix\n   - Limits to Growth — growth hits a balancing constraint\n   - Tragedy of the Commons — local optima deplete a shared stock\n   - Escalation — mutual reaction spiral\n   - Success to the Successful — advantage compounds via allocation\n   - Growth and Underinvestment — capacity lags demand until crisis\n   If none fits after a genuine pass, keep the from-scratch map.\n5. **Trace symptom to structure.** Walk upstream along flows and loops; separate proximate symptom from structural driver (interaction, delay, wrong goal, missing info).\n6. **Rank interventions by leverage, then side effects.** Prefer higher feasible class: goals\u002Fparadigm → rules\u002Finformation → loop structure (gain, balancing add, delay shorten) → stock\u002Fflow topology → buffers\u002Fparameters. For each candidate: feasibility, blast radius, delayed reversal risk. Prefer moves that cut harmful reinforcing gain or strengthen needed balancing loops without creating a new commons\u002Fescalation.\n7. **Stop.** Commit highest feasible intervention plus watch signals for loop\u002Fdelay response. Re-map only if the structure changes or the intervention fails its watch.\n\n**Stop when** boundary, key stocks\u002Fflows, dominant loop(s)+delay(s), optional archetype, and a ranked intervention with side-effect check are stated—or when the problem collapses to a single linear cause.\n\n## Output\n\n```text\nboundary: \u003Csystem purpose and edges>\nstocks_flows: \u003Cstock → inflow\u002Foutflow list>\nloops:\n  - name: \u003Cloop>\n    type: reinforcing | balancing\n    delay: \u003Cwhere cause lags effect>\n    links: \u003Cbrief +\u002F->\narchetype: \u003Cname or none>\nstructural_driver: \u003Cone sentence>\ninterventions_ranked:\n  - level: \u003Cgoals|rules|loops|structure|params>\n    action: \u003Cwhat>\n    side_effects: \u003Cfeedback\u002Felsewhere\u002Fdelay risk>\nchosen: \u003Chighest feasible>\nwatch: \u003Csignals that confirm or falsify>\n```\n\n## Verification\n\n- **Falsify:** If removing one component fully explains and fixes the issue with no cross-effects, systems mapping is wrong—drop to local debug. If utilization shows one fixed stage as the sole cap, switch to theory-of-constraints.\n- **Stop:** Do not keep adding loops after the chosen intervention and watch are set.\n- **Over-application guard:** No archetype without recurrence evidence. No low-leverage param tweak listed as primary when a feasible higher class exists. Do not recreate standalone archetype\u002Ffeedback\u002Fleverage procedures—those checks live only inside this map.\n",{"name":5,"description":7,"disable-model-invocation":24},true,"main","59ee67804bc373a9bd079a3a27f47277a6efe564","skill-library\u002Fpacks\u002Fthinking\u002Fthinking-systems","https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness","https:\u002F\u002Fgithub.com\u002Fham-zax","2026-11-15 01:18:51",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":24},[33,36,39],{"tool":34,"command":35},"npx","npx skills add ham-zax\u002Fwebharness --skill thinking-systems",{"tool":37,"command":38},"bunx","bunx skills add ham-zax\u002Fwebharness --skill thinking-systems",{"tool":40,"command":41},"pnpm","pnpm dlx skills add ham-zax\u002Fwebharness --skill thinking-systems","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness\u002Fblob\u002Fmain\u002Fskill-library\u002Fpacks\u002Fthinking\u002Fthinking-systems\u002FSKILL.md",[],[45,52,59,66,75,82],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":19},"01M7AS6BAQQ2WQJYS3WBNJPB2G","x-content","Create, rewrite, critique, select formats for, discover opportunities for, and learn from X\u002FTwitter content and X Articles for a technical AI-native developer\u002Fbuilder account. Use when turning ideas, source posts, releases, benchmarks, results, conversations, authenticated For You or creator-watch opportunities, or project evidence into an Original, Quote, Thread, Reply, or Article; reviewing article titles\u002Foutlines\u002Fvisual briefs\u002Flaunch hooks; improving drafts; choosing additive contributions from live X context; or learning from own-account outcomes. Own content intelligence only; compose with agent-browser for live X state and Growth OS for discovery provenance, approvals, measurement, and publication.","https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness\u002Fblob\u002Fmain\u002Fskills\u002Fx-content\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7AS66FXQR8FEQYW8G8RJB2N","writing-plans","Create detailed implementation plans for multi-step software work before editing code. Use when requirements or a specification must become concrete file-level tasks, interfaces, acceptance criteria, risks, rollout, or explicitly required validation. Default to no test creation, test modification, test execution, TDD, regression-test, or coverage work unless the user, authoritative specification, or mandatory repository policy explicitly requires testing.","https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7AS5ZCJX21NF2RESA2QDWPP","systematic-debugging","Root-cause debugging for concrete technical failures including bugs, failing builds or tests, integration issues, performance regressions, and unexpected behavior. Use before proposing or implementing a repair when diagnosis is required. Reproduce the symptom, trace the responsible owner, maintain one leading causal hypothesis, and falsify it with the smallest direct evidence. Compose with Causal Coding for source mutation; testing is opt-in and requires independent authorization.","https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness\u002Fblob\u002Fmain\u002Fskills\u002Fsystematic-debugging\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":70,"licenseFileUrl":71,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7AS548FQ63SAB9G0X81VPGJ","skill-creator","Guide for creating and updating high-quality skills by translating workflows, conventions, and reusable processes into well-structured skills. Includes context, use case examples and spec for skills. Use this skill whenever a user asks to create, update, edit, improve, package, or troubleshoot a skill, and also for conversational questions about skills in ChatGPT (e.g., \"What are skills?\", \"What can I use skills for?\", \"What are the best skill use cases for me?\", \"Where can I find my skills?\").","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness\u002Fblob\u002Fmain\u002Fskills\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness\u002Fblob\u002Fmain\u002Fskills\u002Fskill-creator\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7AS4XD121Q85Y06EXRGYS4F","reflexion","Self-refinement, multi-perspective critique, verification, and durable lesson curation adapted from NeoLabHQ Reflexion. Use when the user asks to reflect, self-review, critique, double-check, verify and improve prior work, run a rigorous review, memorize lessons, or says \"then reflect\" after a coding, analysis, or writing task. Supports repository-aware evidence gathering and works without subagents or Claude hooks.","https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness\u002Fblob\u002Fmain\u002Fskills\u002Freflexion\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7AS4RN5TYMA4P6SK6K7NVSR","ponytail","Enforce Ponytail's lazy-senior-developer approach for coding, fixing, refactoring, design, dependency choices, and explicit Ponytail modes such as review, audit, debt, gain, and help. Prefer YAGNI, existing code, standard library, native platform features, existing dependencies, low reader load, and the smallest correct diff. For source mutation, keep Causal Coding authoritative for scope, testing authorization, verification cadence, and stopping. On connected WSL\u002FLinux targets, compose with MCP Harness Router and use `wsl-web-harness` for authoritative repository work.","https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness\u002Fblob\u002Fmain\u002Fskills\u002Fponytail\u002FSKILL.md",[],[]]