[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ERDSNCK9HDDCVCMWZ3VTMF":3,"skill-same:01M7ERDSNCK9HDDCVCMWZ3VTMF":146},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7ERDSNCK9HDDCVCMWZ3VTMF","statechart",null,"Draw what an app's user sees as a Mermaid statechart from a TLA+ model, each bug TLC finds a numbered path. Use for 'show the PM the bug', or to turn an agreed chart into a TLA+ skeleton.","JoshuaHayesWasHere\u002Fjstack","JoshuaHayesWasHere","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F78288453?v=4","01M7EQPZP0GDYN3SYY9SZZHFJE","Joshua Hayes","01M7EQPZPQKJDZR99NG512A8X2",1,"MIT","https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fskill-library\u002Fskills\u002Fstatechart\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: statechart\ndescription: \"Draw what an app's user sees as a Mermaid statechart from a TLA+ model, each bug TLC finds a numbered path. Use for 'show the PM the bug', or to turn an agreed chart into a TLA+ skeleton.\"\ntip: draws what the user sees as a statechart from a TLA+ model, each bug a numbered path | statechart | state chart | show the pm the bug | draw the state machine | chart from the tla spec\ncard: \"Distrust the change | 9 | Draws what an app's user sees as a Mermaid statechart from a TLA+ model checked by TLC, with each bug a numbered path, or turns a chart the PM agreed to into a TLA+ skeleton. | Reach for it when a product call rests on a state machine, or a bug TLC found has to be shown to someone who does not read TLA+. | op: the operator\"\n---\n\n# Statechart\n\nSource: pstack, `pstack\u002Fskills\u002Fstatechart\u002FSKILL.md`\n\nThe chart shows what an app's user sees.\nA PM reads it to decide whether that behavior is right.\nLabel each state with what is on the screen, such as \"Paying\".\nLabel each step with what the user does or sees happen, such as \"tap Pay\" or \"the charge goes through\".\nKeep variable and action names out of labels.\nThe scripts call this user the reader, as in `reader_actions` and reader steps.\n\n## The command\n\nThe scripts are a uv project in `scripts\u002F` beside this file, a port of pstack's Node scripts to Python.\nSet `S=$(dirname \"$(realpath ~\u002F.claude\u002Fskills\u002Fstatechart\u002FSKILL.md)\")\u002Fscripts`, the `scripts\u002F` folder beside the real file and not beside the install's link to it, so that nothing is written into the installed layout.\nRun each command as `UV_PROJECT_ENVIRONMENT=\"$HOME\u002F.cache\u002Fjstack\u002Fstatechart-venv\" uv run --frozen --exact --project \"$S\" statechart \u003Ccommand>`: the environment lives in the cache, and `--frozen` keeps `uv.lock` as it is, and `--exact` removes from it what another checkout's sync left there, such as a `jgauge` whose checkout is gone.\nStart with `statechart --help`, which gives the commands and how to read a chart.\n`uv run` brings Java through the pinned `jdk4py` package, so nothing is installed by hand; jdk4py has no wheel for musl Linux, such as Alpine, so set `JAVA` to a java binary there.\nTLC's `tla2tools.jar` is pinned in `scripts\u002Fstatechart\u002Ftools.py` and is downloaded to `~\u002F.cache\u002Fjstack\u002Ftla2tools\u002F` on the first run, checked against its sha256; set `TLA2TOOLS` to use another copy.\n`--png` renders with Mermaid's `@mermaid-js\u002Fmermaid-cli` through `npx`, at the version pinned in the same file, so it needs Node.\nIn jstack a chart folder commits only `chart.mmd`, any `bug-N.mmd`, `stories.md` and `summary.json`: git cannot merge a drawing, and every chart change rewrites one.\nIn jstack a model's prose, its rules, how to check them and draw its chart, and what it leaves out, goes in `features\u002F\u003Cfeature>\u002Fspec\u002F\u003CModel>.md` beside its `\u003CModel>.tla`, and the spec folder's `README.md` lists no model.\nA new model then adds only files of its own, `.tla`, `.cfg`, `.map.py`, `.md` and its `\u003CModel>-statechart\u002F` folder, which the folder's `.gitattributes` glob already marks generated, so two pull requests that each add a model never conflict.\n`make charts` runs `statechart site --lanes`, which draws from those the charts page and a PNG and Excalidraw scenes of each chart and its overview beside it, in a folder git ignores, and prints the page's path.\nRun it when you want to look at them; no hook or check runs it.\nA mapping that names `lanes` draws its chart as reference lanes instead: one row of boxes per thing that moves on its own, every step of TLC's graph on one arrow, table cell or row, no two lines crossing and no words on a line; `scripts\u002Fstatechart\u002Flanes.py` says what such a mapping holds, and `features\u002Fjbus\u002Fspec\u002FMainRed.map.py` has a worked one.\nFor those charts it runs TLC and prints the coverage and layout counts, and `statechart lanes-check` then measures the layout in a headless browser; every count should be 0.\nThe mapping that labels a model is a Python file, `SPEC.map.py`, and `scripts\u002Fmodel\u002F` has a worked one: `OutputFolder.tla` models the command's own output folder, and `OutputFolder.map.py` labels it.\nThe project skill in `features\u002Fskill-library\u002Fproject-skill\u002Fverify-output-folder\u002F` names the code that model covers, how to check it, and the commit it was last read against.\nWork in a scratch folder outside the repo.\nThe command writes its files next to its input.\n\n## Pick the direction\n\nUse `from-spec` when a TLA+ model exists or the code is concrete enough to model.\nUse `from-chart` when there is no model and the PM should agree on the behavior before anyone writes or changes the code.\n\nIf the code already has a TLA+ spec, start from a copy of that spec.\nAdd the variables the user sees, and keep the spec's existing invariants.\nTo audit the code against that spec, make the copy model what the code does, and pass the spec unchanged as `--against`.\nCheck it with the config that its authors say it passes, and pass that config as `--against-config` unless it has the spec's file name.\nOne mapping labels both models, so label states and steps only from variables that both have.\nIn a code model or a new spec, tie every variable and action to code that a reviewer can open, and take its name from that code.\nMake each action one indivisible step in the code.\nPut the file of the code that checks each condition of an action in a comment on that condition, with the code it quotes in backticks, as in ``\\* pay.ts `if (sent > 0)` ``.\nA file and line, as in `\\* pay.ts:120`, cites it too, but a quote needs no edit when the lines above it move.\n\n## Spec to chart\n\n1. Choose the chart's states.\n   When the PM cares about something the screen does not show, such as a second charge while the screen still says \"Paying\", name the state \"Paying, charged twice\".\n   Start with few states, and split a state only when the split separates two bugs.\n2. Write each rule the PM agrees to as one invariant, with the PM's sentence as its comment.\n   Each rule names what the user sees on a screen or gets from a request, and the code that can change it.\n   Refuse a rule that lacks one of them.\n   For a rule that applies once everything settles, define `Settled == ~ENABLED System`, where `System` is the disjunction of the actions the user does not take.\n   Report each broken rule as a bug.\n   Never weaken a rule to make the chart pass.\n3. Run `from-spec`, then fill in the mapping file it writes.\n   Put the labels in `state` and `step`, and list the user's actions in `reader_actions` by action name.\n   When two bugs end on the same screen through different code paths, add `cause` and make it name the code path.\n   To color the states by what the PM cares about, such as \"Toast shown\", return that group from `group`.\n   The legend names the groups, and states that break a rule still get a red border.\n4. If there is an open fix, model it from the code and pass that model as `--fixed`.\n5. Render each chart with `--png`, or in jstack with `make charts`, and look at every PNG.\n   Check that each numbered path reads in order.\n   If a label reads like code, fix `state` or `step` and run the command again.\n6. Replay each bug's story against the real code, as a test or a live repro, one step per model action.\n   Drive only entry points that a user or client reaches, and assert only what they see.\n   A test that asserts a flag that it sets, or that searches the source text, proves nothing.\n   When a run proves part of the story and reading the code proves the rest, say which part each proves.\n   When the test copies code that it cannot import, give the commit and line range of the copy, and list what the copy leaves out.\n   If a bug does not reproduce, assume the model is wrong until you show otherwise.\n   Fix the model, not the rule.\n\n## Chart to spec\n\n1. Draw the chart the PM agrees to.\n   Use one region for each thing that changes independently, such as the connection and the sync badge.\n   Add one `%% never` line per rule, with the PM's sentence.\n   Draw \"the app closes\" as an edge to the state the user sees next.\n2. Run `from-chart`.\n   If a rule breaks, the agreed chart has a design bug.\n   Take the bug to the PM.\n3. Add the real code's guards and variables to the spec that `from-chart` wrote, and run `from-chart` again.\n   For each difference it prints, ask the PM whether the code is wrong or the chart needs a correction.\n\n## Replay a run's log\n\nWhen the code writes a log of each step it takes, `statechart replay SPEC.tla --trace SPEC.trace.py --log FILE.jsonl` checks that a real run took only steps the model allows.\nIt runs TLC once for the spec's state graph, walks each unit's lines over it, and prints `\u003Cn> lines, \u003Cm> matched, \u003Ck> matched no step` with one `MISS` line per line no step makes, exiting 1 on a miss.\nThe trace file says how a line reads: its unit, the variables it shows before and after, and, for a line a verb writes, the actions that make it.\n`statechart replay --help` gives the contract, and `features\u002Fjbus\u002Fspec\u002FRowLife.trace.py` is a worked one.\nA miss is a code path the model lacks: change the model or the code until the log replays, and never the trace file alone.\n\n## Hand off\n\nGive the PM the PNG and the Mermaid source of each chart.\nFor a reader who wants the shape before the states, add `statechart overview CHART.mmd`, the chart at the level of its groups: one box per group, each arrow counting the steps between two groups.\n`--out FILE.excalidraw` draws it for Excalidraw.\nAdd one line per bug with the rule it breaks, its steps as the chart numbers them, whether it reproduced, and whether the open fix fixes it.\nWith `--against`, also say whether the spec already lists it: in the configs that `stories.md` names, in the spec's notes on what the model leaves out, or not at all.\nDo not report that a rule holds while the command lists conditions with no file and quote or line.\nTake every count you quote from `summary.json`.\nSay what the chart covers: the bounds of the cfg it was drawn with, the model's counts beside the chart's, and that a chart state joins the model states the user cannot tell apart, so the chart is not every path of the code.\nA chart joins states and draws only some arrows, so `from-spec` writes `states.tsv` and `arrows.tsv` beside it: every chart state of the model and every arrow between two, with its TLA+ action and its count of model steps.\nTheir counts add up to TLC's, so a review or a migration checked against them misses no state.\nDraw a chart from the cfg TLC checks; where that cfg costs too much to draw and a smaller one draws, pass the checked one as `--also-config`, and the tables count what it reaches too.\n`statechart site` writes these lines on each chart's tab, with the tables under the chart, and with `--flow` it lists the models with no chart and the state no model has, from the flow file's `[[uncharted]]` and `[[unmodeled]]`.\nIt stops on a model under a feature's `spec\u002F` that has neither a chart nor an `[[uncharted]]` line.\nAttach `stories.md` and the command that regenerates everything.\nSay what the model leaves out.\n","# Statechart\n\nSource: pstack, `pstack\u002Fskills\u002Fstatechart\u002FSKILL.md`\n\nThe chart shows what an app's user sees.\nA PM reads it to decide whether that behavior is right.\nLabel each state with what is on the screen, such as \"Paying\".\nLabel each step with what the user does or sees happen, such as \"tap Pay\" or \"the charge goes through\".\nKeep variable and action names out of labels.\nThe scripts call this user the reader, as in `reader_actions` and reader steps.\n\n## The command\n\nThe scripts are a uv project in `scripts\u002F` beside this file, a port of pstack's Node scripts to Python.\nSet `S=$(dirname \"$(realpath ~\u002F.claude\u002Fskills\u002Fstatechart\u002FSKILL.md)\")\u002Fscripts`, the `scripts\u002F` folder beside the real file and not beside the install's link to it, so that nothing is written into the installed layout.\nRun each command as `UV_PROJECT_ENVIRONMENT=\"$HOME\u002F.cache\u002Fjstack\u002Fstatechart-venv\" uv run --frozen --exact --project \"$S\" statechart \u003Ccommand>`: the environment lives in the cache, and `--frozen` keeps `uv.lock` as it is, and `--exact` removes from it what another checkout's sync left there, such as a `jgauge` whose checkout is gone.\nStart with `statechart --help`, which gives the commands and how to read a chart.\n`uv run` brings Java through the pinned `jdk4py` package, so nothing is installed by hand; jdk4py has no wheel for musl Linux, such as Alpine, so set `JAVA` to a java binary there.\nTLC's `tla2tools.jar` is pinned in `scripts\u002Fstatechart\u002Ftools.py` and is downloaded to `~\u002F.cache\u002Fjstack\u002Ftla2tools\u002F` on the first run, checked against its sha256; set `TLA2TOOLS` to use another copy.\n`--png` renders with Mermaid's `@mermaid-js\u002Fmermaid-cli` through `npx`, at the version pinned in the same file, so it needs Node.\nIn jstack a chart folder commits only `chart.mmd`, any `bug-N.mmd`, `stories.md` and `summary.json`: git cannot merge a drawing, and every chart change rewrites one.\nIn jstack a model's prose, its rules, how to check them and draw its chart, and what it leaves out, goes in `features\u002F\u003Cfeature>\u002Fspec\u002F\u003CModel>.md` beside its `\u003CModel>.tla`, and the spec folder's `README.md` lists no model.\nA new model then adds only files of its own, `.tla`, `.cfg`, `.map.py`, `.md` and its `\u003CModel>-statechart\u002F` folder, which the folder's `.gitattributes` glob already marks generated, so two pull requests that each add a model never conflict.\n`make charts` runs `statechart site --lanes`, which draws from those the charts page and a PNG and Excalidraw scenes of each chart and its overview beside it, in a folder git ignores, and prints the page's path.\nRun it when you want to look at them; no hook or check runs it.\nA mapping that names `lanes` draws its chart as reference lanes instead: one row of boxes per thing that moves on its own, every step of TLC's graph on one arrow, table cell or row, no two lines crossing and no words on a line; `scripts\u002Fstatechart\u002Flanes.py` says what such a mapping holds, and `features\u002Fjbus\u002Fspec\u002FMainRed.map.py` has a worked one.\nFor those charts it runs TLC and prints the coverage and layout counts, and `statechart lanes-check` then measures the layout in a headless browser; every count should be 0.\nThe mapping that labels a model is a Python file, `SPEC.map.py`, and `scripts\u002Fmodel\u002F` has a worked one: `OutputFolder.tla` models the command's own output folder, and `OutputFolder.map.py` labels it.\nThe project skill in `features\u002Fskill-library\u002Fproject-skill\u002Fverify-output-folder\u002F` names the code that model covers, how to check it, and the commit it was last read against.\nWork in a scratch folder outside the repo.\nThe command writes its files next to its input.\n\n## Pick the direction\n\nUse `from-spec` when a TLA+ model exists or the code is concrete enough to model.\nUse `from-chart` when there is no model and the PM should agree on the behavior before anyone writes or changes the code.\n\nIf the code already has a TLA+ spec, start from a copy of that spec.\nAdd the variables the user sees, and keep the spec's existing invariants.\nTo audit the code against that spec, make the copy model what the code does, and pass the spec unchanged as `--against`.\nCheck it with the config that its authors say it passes, and pass that config as `--against-config` unless it has the spec's file name.\nOne mapping labels both models, so label states and steps only from variables that both have.\nIn a code model or a new spec, tie every variable and action to code that a reviewer can open, and take its name from that code.\nMake each action one indivisible step in the code.\nPut the file of the code that checks each condition of an action in a comment on that condition, with the code it quotes in backticks, as in ``\\* pay.ts `if (sent > 0)` ``.\nA file and line, as in `\\* pay.ts:120`, cites it too, but a quote needs no edit when the lines above it move.\n\n## Spec to chart\n\n1. Choose the chart's states.\n   When the PM cares about something the screen does not show, such as a second charge while the screen still says \"Paying\", name the state \"Paying, charged twice\".\n   Start with few states, and split a state only when the split separates two bugs.\n2. Write each rule the PM agrees to as one invariant, with the PM's sentence as its comment.\n   Each rule names what the user sees on a screen or gets from a request, and the code that can change it.\n   Refuse a rule that lacks one of them.\n   For a rule that applies once everything settles, define `Settled == ~ENABLED System`, where `System` is the disjunction of the actions the user does not take.\n   Report each broken rule as a bug.\n   Never weaken a rule to make the chart pass.\n3. Run `from-spec`, then fill in the mapping file it writes.\n   Put the labels in `state` and `step`, and list the user's actions in `reader_actions` by action name.\n   When two bugs end on the same screen through different code paths, add `cause` and make it name the code path.\n   To color the states by what the PM cares about, such as \"Toast shown\", return that group from `group`.\n   The legend names the groups, and states that break a rule still get a red border.\n4. If there is an open fix, model it from the code and pass that model as `--fixed`.\n5. Render each chart with `--png`, or in jstack with `make charts`, and look at every PNG.\n   Check that each numbered path reads in order.\n   If a label reads like code, fix `state` or `step` and run the command again.\n6. Replay each bug's story against the real code, as a test or a live repro, one step per model action.\n   Drive only entry points that a user or client reaches, and assert only what they see.\n   A test that asserts a flag that it sets, or that searches the source text, proves nothing.\n   When a run proves part of the story and reading the code proves the rest, say which part each proves.\n   When the test copies code that it cannot import, give the commit and line range of the copy, and list what the copy leaves out.\n   If a bug does not reproduce, assume the model is wrong until you show otherwise.\n   Fix the model, not the rule.\n\n## Chart to spec\n\n1. Draw the chart the PM agrees to.\n   Use one region for each thing that changes independently, such as the connection and the sync badge.\n   Add one `%% never` line per rule, with the PM's sentence.\n   Draw \"the app closes\" as an edge to the state the user sees next.\n2. Run `from-chart`.\n   If a rule breaks, the agreed chart has a design bug.\n   Take the bug to the PM.\n3. Add the real code's guards and variables to the spec that `from-chart` wrote, and run `from-chart` again.\n   For each difference it prints, ask the PM whether the code is wrong or the chart needs a correction.\n\n## Replay a run's log\n\nWhen the code writes a log of each step it takes, `statechart replay SPEC.tla --trace SPEC.trace.py --log FILE.jsonl` checks that a real run took only steps the model allows.\nIt runs TLC once for the spec's state graph, walks each unit's lines over it, and prints `\u003Cn> lines, \u003Cm> matched, \u003Ck> matched no step` with one `MISS` line per line no step makes, exiting 1 on a miss.\nThe trace file says how a line reads: its unit, the variables it shows before and after, and, for a line a verb writes, the actions that make it.\n`statechart replay --help` gives the contract, and `features\u002Fjbus\u002Fspec\u002FRowLife.trace.py` is a worked one.\nA miss is a code path the model lacks: change the model or the code until the log replays, and never the trace file alone.\n\n## Hand off\n\nGive the PM the PNG and the Mermaid source of each chart.\nFor a reader who wants the shape before the states, add `statechart overview CHART.mmd`, the chart at the level of its groups: one box per group, each arrow counting the steps between two groups.\n`--out FILE.excalidraw` draws it for Excalidraw.\nAdd one line per bug with the rule it breaks, its steps as the chart numbers them, whether it reproduced, and whether the open fix fixes it.\nWith `--against`, also say whether the spec already lists it: in the configs that `stories.md` names, in the spec's notes on what the model leaves out, or not at all.\nDo not report that a rule holds while the command lists conditions with no file and quote or line.\nTake every count you quote from `summary.json`.\nSay what the chart covers: the bounds of the cfg it was drawn with, the model's counts beside the chart's, and that a chart state joins the model states the user cannot tell apart, so the chart is not every path of the code.\nA chart joins states and draws only some arrows, so `from-spec` writes `states.tsv` and `arrows.tsv` beside it: every chart state of the model and every arrow between two, with its TLA+ action and its count of model steps.\nTheir counts add up to TLC's, so a review or a migration checked against them misses no state.\nDraw a chart from the cfg TLC checks; where that cfg costs too much to draw and a smaller one draws, pass the checked one as `--also-config`, and the tables count what it reaches too.\n`statechart site` writes these lines on each chart's tab, with the tables under the chart, and with `--flow` it lists the models with no chart and the state no model has, from the flow file's `[[uncharted]]` and `[[unmodeled]]`.\nIt stops on a model under a feature's `spec\u002F` that has neither a chart nor an `[[uncharted]]` line.\nAttach `stories.md` and the command that regenerates everything.\nSay what the model leaves out.\n",{"tip":24,"card":25,"name":5,"description":7},"draws what the user sees as a statechart from a TLA+ model, each bug a numbered path | statechart | state chart | show the pm the bug | draw the state machine | chart from the tla spec","Distrust the change | 9 | Draws what an app's user sees as a Mermaid statechart from a TLA+ model checked by TLC, with each bug a numbered path, or turns a chart the PM agreed to into a TLA+ skeleton. | Reach for it when a product call rests on a state machine, or a bug TLC found has to be shown to someone who does not read TLA+. | op: the operator","main","daff051d2674b46e2eb8a333bbd3f3e40f8d1cea","features\u002Fskill-library\u002Fskills\u002Fstatechart",0,"https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack","https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere","Software Engineer @ Markel\r\n","2026-11-15 11:25:06",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add JoshuaHayesWasHere\u002Fjstack --skill statechart",{"tool":40,"command":41},"bunx","bunx skills add JoshuaHayesWasHere\u002Fjstack --skill statechart",{"tool":43,"command":44},"pnpm","pnpm dlx skills add JoshuaHayesWasHere\u002Fjstack --skill statechart","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fskill-library\u002Fskills\u002Fstatechart\u002FSKILL.md",true,[48,54,58,62,66,70,74,78,82,86,90,94,98,102,106,110,114,118,122,126,130,134,138,142],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"scripts\u002Fmodel\u002FOutputFolder.cfg","SCRIPT","脚本",154,"https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fskill-library\u002Fskills\u002Fstatechart\u002Fscripts\u002Fmodel\u002FOutputFolder.cfg",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"scripts\u002Fmodel\u002FOutputFolder.map.py",3966,"https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fskill-library\u002Fskills\u002Fstatechart\u002Fscripts\u002Fmodel\u002FOutputFolder.map.py",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"scripts\u002Fmodel\u002FOutputFolder.tla",6944,"https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fskill-library\u002Fskills\u002Fstatechart\u002Fscripts\u002Fmodel\u002FOutputFolder.tla",{"path":63,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":64,"sourceHtmlUrl":65},"scripts\u002Fpyproject.toml",788,"https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fskill-library\u002Fskills\u002Fstatechart\u002Fscripts\u002Fpyproject.toml",{"path":67,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":68,"sourceHtmlUrl":69},"scripts\u002Fstatechart\u002F__init__.py",46,"https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fskill-library\u002Fskills\u002Fstatechart\u002Fscripts\u002Fstatechart\u002F__init__.py",{"path":71,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":72,"sourceHtmlUrl":73},"scripts\u002Fstatechart\u002F__main__.py",62,"https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fskill-library\u002Fskills\u002Fstatechart\u002Fscripts\u002Fstatechart\u002F__main__.py",{"path":75,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":76,"sourceHtmlUrl":77},"scripts\u002Fstatechart\u002Fchart_to_tla.py",11249,"https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fskill-library\u002Fskills\u002Fstatechart\u002Fscripts\u002Fstatechart\u002Fchart_to_tla.py",{"path":79,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":80,"sourceHtmlUrl":81},"scripts\u002Fstatechart\u002Fcli.py",75270,"https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fskill-library\u002Fskills\u002Fstatechart\u002Fscripts\u002Fstatechart\u002Fcli.py",{"path":83,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":84,"sourceHtmlUrl":85},"scripts\u002Fstatechart\u002Fcompare_charts.py",4530,"https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fskill-library\u002Fskills\u002Fstatechart\u002Fscripts\u002Fstatechart\u002Fcompare_charts.py",{"path":87,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":88,"sourceHtmlUrl":89},"scripts\u002Fstatechart\u002Fexcalidraw.py",26892,"https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fskill-library\u002Fskills\u002Fstatechart\u002Fscripts\u002Fstatechart\u002Fexcalidraw.py",{"path":91,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":92,"sourceHtmlUrl":93},"scripts\u002Fstatechart\u002Flanes_check.py",4768,"https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fskill-library\u002Fskills\u002Fstatechart\u002Fscripts\u002Fstatechart\u002Flanes_check.py",{"path":95,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":96,"sourceHtmlUrl":97},"scripts\u002Fstatechart\u002Flanes_probe.js",6139,"https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fskill-library\u002Fskills\u002Fstatechart\u002Fscripts\u002Fstatechart\u002Flanes_probe.js",{"path":99,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":100,"sourceHtmlUrl":101},"scripts\u002Fstatechart\u002Flanes.py",30819,"https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fskill-library\u002Fskills\u002Fstatechart\u002Fscripts\u002Fstatechart\u002Flanes.py",{"path":103,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":104,"sourceHtmlUrl":105},"scripts\u002Fstatechart\u002Flib.py",43230,"https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fskill-library\u002Fskills\u002Fstatechart\u002Fscripts\u002Fstatechart\u002Flib.py",{"path":107,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":108,"sourceHtmlUrl":109},"scripts\u002Fstatechart\u002Fmapping.py",783,"https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fskill-library\u002Fskills\u002Fstatechart\u002Fscripts\u002Fstatechart\u002Fmapping.py",{"path":111,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":112,"sourceHtmlUrl":113},"scripts\u002Fstatechart\u002Foverview.py",5319,"https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fskill-library\u002Fskills\u002Fstatechart\u002Fscripts\u002Fstatechart\u002Foverview.py",{"path":115,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":116,"sourceHtmlUrl":117},"scripts\u002Fstatechart\u002Freplay.py",13354,"https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fskill-library\u002Fskills\u002Fstatechart\u002Fscripts\u002Fstatechart\u002Freplay.py",{"path":119,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":120,"sourceHtmlUrl":121},"scripts\u002Fstatechart\u002Fsite.css",15101,"https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fskill-library\u002Fskills\u002Fstatechart\u002Fscripts\u002Fstatechart\u002Fsite.css",{"path":123,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":124,"sourceHtmlUrl":125},"scripts\u002Fstatechart\u002Fsite.html",1844,"https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fskill-library\u002Fskills\u002Fstatechart\u002Fscripts\u002Fstatechart\u002Fsite.html",{"path":127,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":128,"sourceHtmlUrl":129},"scripts\u002Fstatechart\u002Fsite.js",21303,"https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fskill-library\u002Fskills\u002Fstatechart\u002Fscripts\u002Fstatechart\u002Fsite.js",{"path":131,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":132,"sourceHtmlUrl":133},"scripts\u002Fstatechart\u002Fsite.py",60443,"https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fskill-library\u002Fskills\u002Fstatechart\u002Fscripts\u002Fstatechart\u002Fsite.py",{"path":135,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":136,"sourceHtmlUrl":137},"scripts\u002Fstatechart\u002Ftlc_to_chart.py",89273,"https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fskill-library\u002Fskills\u002Fstatechart\u002Fscripts\u002Fstatechart\u002Ftlc_to_chart.py",{"path":139,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":140,"sourceHtmlUrl":141},"scripts\u002Fstatechart\u002Ftools.py",8828,"https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fskill-library\u002Fskills\u002Fstatechart\u002Fscripts\u002Fstatechart\u002Ftools.py",{"path":143,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":144,"sourceHtmlUrl":145},"scripts\u002Fuv.lock",1934,"https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fskill-library\u002Fskills\u002Fstatechart\u002Fscripts\u002Fuv.lock",[147,154,161,168,175,182],{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":153,"publishedAt":19},"01M7ERF9GXMY62V7QTVAR6G8DG","no-key","A skill its skills.json lists as hidden that a model may still call by itself, kept broken so the lint is seen to catch it.","https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ftesting\u002Ftests\u002Ffixtures\u002Fskills\u002Fno-key\u002FSKILL.md",[],[],{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":160,"publishedAt":19},"01M7ERF83ZG3XKJ2SB8MJHCZ8H","fake-skill","A FAKE skill in a FAKE tree, named for its folder until the test renames the folder.","https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ftesting\u002Ftests\u002Ffixtures\u002Fskills\u002Fnamed-tree\u002Fskills\u002Ffake-skill\u002FSKILL.md",[],[],{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":167,"publishedAt":19},"01M7ERF698RV4VF8QCDF8H8DA4","extra-key","A skill its skills.json does not list as hidden that a model still cannot call, kept broken so the lint is seen to catch it.","https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ftesting\u002Ftests\u002Ffixtures\u002Fskills\u002Fextra-key\u002FSKILL.md",[],[],{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":174,"publishedAt":19},"01M7ERF2V8N73X9T0Y9PJ4SFV6","unslop","Cut AI tells from writing. Use when the user says text reads like AI, asks to unslop it, or before prose ships to people.","https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fwriting\u002Fskills\u002Funslop\u002FSKILL.md",[],[],{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":181,"publishedAt":19},"01M7EREWM67WX934XKABM4XCSZ","technical-writing","Write or review docs, READMEs, RFCs, PR descriptions and commit messages to a layered standard: Diataxis structure, Google developer style, STE rules and Global English.","https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fwriting\u002Fskills\u002Ftechnical-writing\u002FSKILL.md",[],[],{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":188,"publishedAt":19},"01M7EREMHJS9JY10AM5EKVX3GP","why","Find why code is the way it is, from its history and every evidence source this session can query, with citations. Use for 'why does X work this way', 'why did we pick Y', regressions and postmortems. Use how for runtime behavior.","https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fwhy\u002FSKILL.md",[],[]]