[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79SPRT8GV1RPQ2VVR9K08BB":3,"skill-same:01M79SPRT8GV1RPQ2VVR9K08BB":46},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M79SPRT8GV1RPQ2VVR9K08BB","tui-screenshots",null,"Use for generating or refreshing TUI screenshots for docs — \"regenerate the screenshots\", \"the README screenshots are stale\". Drives a Textual\u002FTUI app headlessly and exports SVG. Not for reading a user's screenshot — that is `screenshot`.","dannybrown37\u002Fskill-tree","dannybrown37","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F28059438?v=4","01M79SKVHAKWQH9VF0G6KQRZZ2","Danny Brown","01M79SKVJ1X8VHPTK7MKMHBRD2",0,"MIT","https:\u002F\u002Fgithub.com\u002Fdannybrown37\u002Fskill-tree\u002Fblob\u002Fmain\u002Fskills\u002Ftui-screenshots\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: tui-screenshots\ndescription: \"Use for generating or refreshing TUI screenshots for docs — \\\"regenerate the screenshots\\\", \\\"the README screenshots are stale\\\". Drives a Textual\u002FTUI app headlessly and exports SVG. Not for reading a user's screenshot — that is `screenshot`.\"\n---\n\n# TUI screenshots\n\nDocs screenshots of a terminal app go stale silently. Nothing fails, nothing lints — the\nREADME just shows an app that no longer exists. This is the workflow that makes regenerating\nthem a single command instead of an afternoon.\n\nDo not reach for a desktop screen capture. Photographing a real terminal window bakes in the\nuser's font, theme, window size, and whatever real data was on screen. Drive the app instead.\n\n## The shape\n\nFour pieces, in order. Skipping any one of them is where these efforts usually fail:\n\n1. **A fake data source.** Never screenshot real data — it is the user's private life, and it\n   also produces a different picture every run.\n2. **A headless driver.** Run the app in-process at a fixed terminal size.\n3. **An export step.** Write a vector image per screen.\n4. **A drift guard.** Something that fails when a new screen exists and no one screenshotted it.\n\n### 1. Fake data, in a real store\n\nThe tempting shortcut is to mock the data layer. Resist it: a mock screenshots the mock, not\nthe app, and it drifts from the real schema without telling you.\n\nSeed a **real but separate store** instead — a demo database, a scratch directory, a throwaway\nnamespace. Then point the app at it with the same environment variable a real user would set.\nThe app has no idea it is being screenshotted, so the picture is honest.\n\nRules for the seed script:\n\n- It must **never** write to the real store. Take the real store's ID only to find out where to\n  put the sibling demo one.\n- Cache the demo store's ID in a **gitignored** file, so a rerun reseeds rather than piling up\n  a new demo store every time.\n- Make the fake data cover **every screen**, including the empty and the crowded case. A tab\n  that is empty in the demo data screenshots as a blank box, which teaches the reader nothing.\n- Fictional names only. \"Call Rachel about the mortgage\" is fine; a real contact is not.\n\n### 2. Driving it headlessly\n\nFor **Textual**, the test harness is the driver — no extra dependency:\n\n```python\napp = MyApp()\nasync with app.run_test(size=(130, 45)) as pilot:\n    await pilot.pause(2)  # let async\u002Fthreaded data loads land\n    tabs = app.query_one('#tabs', TabbedContent)\n    for tab_id, name in TABS:\n        tabs.active = tab_id\n        await pilot.pause(0.5)\n        Path(f'docs\u002Fscreenshots\u002F{name}.svg').write_text(\n            app.export_screenshot(title='app'),\n        )\n```\n\nTwo failure modes account for nearly every bad capture:\n\n- **Screenshotting before the data arrives.** Anything loading on a worker thread or a network\n  call is still a spinner at frame zero. Pause generously once after mount, and again after\n  each navigation. A slow script is cheaper than eight screenshots of a loading state.\n- **A variable terminal size.** Pin it. `size=(130, 45)` is a good wide-docs default. If the\n  size changes between runs, every image in the diff churns and review becomes useless.\n\nFor a **non-Textual** TUI, the equivalents are `asciinema rec` + `agg` for a moving picture, or\n`termtosvg` for a still. Prefer the app's own harness whenever it has one — anything that\nrecords a real terminal reintroduces the font and theme problem.\n\n### 3. Export SVG, not PNG\n\nSVG is text, so a diff shows what actually changed, it stays sharp at any width, and the\nreader can select the text. GitHub renders it inline in a README via `\u003Cimg src=\"...\">`.\n\nOne caveat: GitHub strips scripts and external references from SVG. Textual's export is\nself-contained, so this is fine — but do not hand-edit an exported file to pull in a font.\n\n### 4. The drift guard\n\nThis is the part everyone skips, and it is the reason the screenshots were stale in the first\nplace. A hardcoded list of screens **will** fall behind the app.\n\nBest: **derive the screen list from the app**, not from a constant. Query the real widget tree\nfor the tabs and iterate whatever is there. A new tab then screenshots itself.\n\nIf a hardcoded list is unavoidable, add a test that asserts the list matches the app's actual\nscreens, so adding a screen fails the suite until someone captures it.\n\n## Wiring it up\n\nTwo scripts, chained by an ID the first one prints:\n\n```\nseed_demo_data.py  ──prints demo store id──▶  capture_screenshots.py  ──▶  docs\u002Fscreenshots\u002F*.svg\n```\n\nKeep them as two commands, not one. Seeding hits the network hard and rarely needs redoing;\ncapture gets rerun over and over while you fix a layout.\n\nDocument the chain in the repo's own `CLAUDE.md` or a project skill, including the exact\nenvironment variables. The whole point is that the next person does not have to rediscover it.\n\n## Before you finish\n\n- Look at the images. Read one of the SVGs, or open the directory — a capture that \"succeeded\"\n  can still be eight pictures of an empty tab.\n- Check the README references every image, and every image is referenced.\n- Say plainly in the README that the data is fictional.\n","# TUI screenshots\n\nDocs screenshots of a terminal app go stale silently. Nothing fails, nothing lints — the\nREADME just shows an app that no longer exists. This is the workflow that makes regenerating\nthem a single command instead of an afternoon.\n\nDo not reach for a desktop screen capture. Photographing a real terminal window bakes in the\nuser's font, theme, window size, and whatever real data was on screen. Drive the app instead.\n\n## The shape\n\nFour pieces, in order. Skipping any one of them is where these efforts usually fail:\n\n1. **A fake data source.** Never screenshot real data — it is the user's private life, and it\n   also produces a different picture every run.\n2. **A headless driver.** Run the app in-process at a fixed terminal size.\n3. **An export step.** Write a vector image per screen.\n4. **A drift guard.** Something that fails when a new screen exists and no one screenshotted it.\n\n### 1. Fake data, in a real store\n\nThe tempting shortcut is to mock the data layer. Resist it: a mock screenshots the mock, not\nthe app, and it drifts from the real schema without telling you.\n\nSeed a **real but separate store** instead — a demo database, a scratch directory, a throwaway\nnamespace. Then point the app at it with the same environment variable a real user would set.\nThe app has no idea it is being screenshotted, so the picture is honest.\n\nRules for the seed script:\n\n- It must **never** write to the real store. Take the real store's ID only to find out where to\n  put the sibling demo one.\n- Cache the demo store's ID in a **gitignored** file, so a rerun reseeds rather than piling up\n  a new demo store every time.\n- Make the fake data cover **every screen**, including the empty and the crowded case. A tab\n  that is empty in the demo data screenshots as a blank box, which teaches the reader nothing.\n- Fictional names only. \"Call Rachel about the mortgage\" is fine; a real contact is not.\n\n### 2. Driving it headlessly\n\nFor **Textual**, the test harness is the driver — no extra dependency:\n\n```python\napp = MyApp()\nasync with app.run_test(size=(130, 45)) as pilot:\n    await pilot.pause(2)  # let async\u002Fthreaded data loads land\n    tabs = app.query_one('#tabs', TabbedContent)\n    for tab_id, name in TABS:\n        tabs.active = tab_id\n        await pilot.pause(0.5)\n        Path(f'docs\u002Fscreenshots\u002F{name}.svg').write_text(\n            app.export_screenshot(title='app'),\n        )\n```\n\nTwo failure modes account for nearly every bad capture:\n\n- **Screenshotting before the data arrives.** Anything loading on a worker thread or a network\n  call is still a spinner at frame zero. Pause generously once after mount, and again after\n  each navigation. A slow script is cheaper than eight screenshots of a loading state.\n- **A variable terminal size.** Pin it. `size=(130, 45)` is a good wide-docs default. If the\n  size changes between runs, every image in the diff churns and review becomes useless.\n\nFor a **non-Textual** TUI, the equivalents are `asciinema rec` + `agg` for a moving picture, or\n`termtosvg` for a still. Prefer the app's own harness whenever it has one — anything that\nrecords a real terminal reintroduces the font and theme problem.\n\n### 3. Export SVG, not PNG\n\nSVG is text, so a diff shows what actually changed, it stays sharp at any width, and the\nreader can select the text. GitHub renders it inline in a README via `\u003Cimg src=\"...\">`.\n\nOne caveat: GitHub strips scripts and external references from SVG. Textual's export is\nself-contained, so this is fine — but do not hand-edit an exported file to pull in a font.\n\n### 4. The drift guard\n\nThis is the part everyone skips, and it is the reason the screenshots were stale in the first\nplace. A hardcoded list of screens **will** fall behind the app.\n\nBest: **derive the screen list from the app**, not from a constant. Query the real widget tree\nfor the tabs and iterate whatever is there. A new tab then screenshots itself.\n\nIf a hardcoded list is unavoidable, add a test that asserts the list matches the app's actual\nscreens, so adding a screen fails the suite until someone captures it.\n\n## Wiring it up\n\nTwo scripts, chained by an ID the first one prints:\n\n```\nseed_demo_data.py  ──prints demo store id──▶  capture_screenshots.py  ──▶  docs\u002Fscreenshots\u002F*.svg\n```\n\nKeep them as two commands, not one. Seeding hits the network hard and rarely needs redoing;\ncapture gets rerun over and over while you fix a layout.\n\nDocument the chain in the repo's own `CLAUDE.md` or a project skill, including the exact\nenvironment variables. The whole point is that the next person does not have to rediscover it.\n\n## Before you finish\n\n- Look at the images. Read one of the SVGs, or open the directory — a capture that \"succeeded\"\n  can still be eight pictures of an empty tab.\n- Check the README references every image, and every image is referenced.\n- Say plainly in the README that the data is fictional.\n",{"name":5,"description":7},"main","aec70683dacdf9512d27e04a1e04069bbd199b5e","skills\u002Ftui-screenshots","https:\u002F\u002Fgithub.com\u002Fdannybrown37\u002Fskill-tree","https:\u002F\u002Fgithub.com\u002Fdannybrown37","dannybrown.dev","Software Engineer","2026-11-12 15:25:14",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add dannybrown37\u002Fskill-tree --skill tui-screenshots",{"tool":38,"command":39},"bunx","bunx skills add dannybrown37\u002Fskill-tree --skill tui-screenshots",{"tool":41,"command":42},"pnpm","pnpm dlx skills add dannybrown37\u002Fskill-tree --skill tui-screenshots","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdannybrown37\u002Fskill-tree\u002Fblob\u002Fmain\u002Fskills\u002Ftui-screenshots\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M79SQ7Z4DXMYJECV1NTEP9WY","wait-what","Stop. Your plan\u002Fidea did not land. Re-pitch it.","https:\u002F\u002Fgithub.com\u002Fdannybrown37\u002Fskill-tree\u002Fblob\u002Fmain\u002Fskills\u002Fwait-what\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M79SQ4WQB5YZ7Q2A87JVR219","verify","Verify before answering whether something works, still passes, is gone, is used, or is correct — and whenever the user says \"can you confirm\", \"are you sure\", \"did that actually work\", or reports something is \"still\" broken. Produces the answer plus the evidence that would have falsified it. A failed GitHub Actions run is skill-tree:debug-ci instead.","https:\u002F\u002Fgithub.com\u002Fdannybrown37\u002Fskill-tree\u002Fblob\u002Fmain\u002Fskills\u002Fverify\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M79SQ0GKSM5891DKPXE8J7TZ","ui-designer","Design or restyle a web UI — landing pages, dashboards, docs sites, app chrome — or when the user asks why a site \"looks generic\", \"looks like a template\", or wants it to feel intentional. A running list of design lessons learned, applied as rules rather than suggestions.","https:\u002F\u002Fgithub.com\u002Fdannybrown37\u002Fskill-tree\u002Fblob\u002Fmain\u002Fskills\u002Fui-designer\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M79SPVN5C0XYAXWBH9HD1YF1","two-axis-review","Two-axis review of changes since a fixed point (commit, tag, HEAD~N, or default HEAD~1): Standards (does the code follow this repo's conventions?) and Spec (does the code do what it should?). Axes run as parallel sub-agents so neither masks the other. Use when the user says \"review against the spec\", \"does this follow our conventions\", \"standards and spec review\", or \"two-axis review\". Not a correctness bug hunt — that's the built-in `\u002Fcode-review`.","https:\u002F\u002Fgithub.com\u002Fdannybrown37\u002Fskill-tree\u002Fblob\u002Fmain\u002Fskills\u002Ftwo-axis-review\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},"01M79SPNVJQ0WNWH7PBEM5Y463","to-tickets","Break a spec, plan, or conversation into tracer-bullet vertical-slice tickets with blocking edges — \"turn this into tickets\", \"break this down\", \"what's the work?\". Pairs with skill-tree:to-spec upstream and skill-tree:handoff downstream.","https:\u002F\u002Fgithub.com\u002Fdannybrown37\u002Fskill-tree\u002Fblob\u002Fmain\u002Fskills\u002Fto-tickets\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},"01M79SPH2AAARBSV1VWZJCPMFA","to-spec","A conversation has settled on what to build and it's time to turn it into a written spec — \"turn this into a spec\", \"write this up\", \"spec this out\". Synthesis only: no interview. Pairs well with skill-tree:grill-for-planning, which is where the settled understanding usually comes from.","https:\u002F\u002Fgithub.com\u002Fdannybrown37\u002Fskill-tree\u002Fblob\u002Fmain\u002Fskills\u002Fto-spec\u002FSKILL.md",[],[]]