[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B14PBSP64109P6R4WC3GV2":3,"skill-same:01M7B14PBSP64109P6R4WC3GV2":53},{"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":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7B14PBSP64109P6R4WC3GV2","story-figs-designer",null,"Use to plan, create, or revise one thesis figure (conceptual, method, result, synthesis) as a figure file under manus\u002Ffigs\u002F with its rendered graphic and editable sources under manus\u002Ffigs\u002Fsrcs\u002F, and evidence mappings for every data mark, numeric label, and comparative caption statement. For a table of values, use story-tabs-builder.","wanghao9610\u002FSTORY","wanghao9610","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F53857938?v=4","01M7B13CG447X56WQM587XHEVK","Hao Wang","01M7B13CGRSPW02V06T50VYYD1",2,"MIT","https:\u002F\u002Fgithub.com\u002Fwanghao9610\u002FSTORY\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstory-figs-designer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: story-figs-designer\ndescription: Use to plan, create, or revise one thesis figure (conceptual, method, result, synthesis) as a figure file under manus\u002Ffigs\u002F with its rendered graphic and editable sources under manus\u002Ffigs\u002Fsrcs\u002F, and evidence mappings for every data mark, numeric label, and comparative caption statement. For a table of values, use story-tabs-builder.\n---\n\n# Design one traceable figure\n\n**Shared conventions.** Read `docs\u002Fmds\u002Fstory-workflow\u002Fwriting-workflow-conventions.md` in full before acting. Read `.env` once for the `STORY_LANG`, `INVOLVE`, and `STORY_MAIN` values this run needs, and reuse them. Resolve the language of replies and new Markdown under conventions §7: an explicit author request first, then a valid `STORY_LANG`, then the dialogue language, read from the author's latest own prose and never from a bare command or the English this run loads, or the invocation language when there is no user turn. Manuscript prose follows `degree\u002Fprofile.tex`, and an existing file keeps its language. A clear instruction may select the target and scope and authorize the corresponding action within this skill's documented paths, and work already authorized in this run is not asked for again; it never replaces a confirmation point or an `AGENTS.md` §1 ask-first choice (conventions §7).\n\nResolve one figure by its `F` ID or file in `notes\u002Foutline.md`, or `new`; without `notes\u002Foutline.md` or `notes\u002Fnotation.md`, route to `story-outl-planner` (conventions §1). For `new`, confirm its purpose, chapter, and claim IDs, then add its `planned` row with them in `Purpose`, `Chapter`, and `Claims` (conventions §3) and its `File` keyed by that chapter or other owning file (conventions §5, Manuscript file names); confirming is a judgment call, and `low` adds the row with the recommended values and reports them.\n\nChoose the simplest visual form that makes the intended relationship clear. Write the figure file `manus\u002Ffigs\u002F\u003Cowner>_\u003Cslug>.tex` — the figure environment, caption, and label, with the drawing itself (TikZ, pgfplots) or `\\includegraphics{figs\u002Fsrcs\u002F\u003Cowner>_\u003Cslug>}` — and keep the rendered graphic and every editable source (PDF, PPTX, SVG, plotting script) as `manus\u002Ffigs\u002Fsrcs\u002F\u003Cowner>_\u003Cslug>.*`, with one key and slug, `\u003Cowner>` being the key of the file the row's `Chapter` cell names (conventions §5, Manuscript file names), never replacing the source with a flattened or rasterized export. Beside or inside the source, keep a grep-readable map anchoring every data mark, numeric label, and comparative caption statement (conventions §2) to registered evidence read in this run; generated or decorative pixels are never evidence. Without a `cleared` row in `notes\u002Fpublications.md` (conventions §3), route adapted published material to `story-syns-coach`.\n\nKeep the figure accessible: legible type, non-color-only distinctions, suitable contrast, and an informative caption. Use `notes\u002Fnotation.md` symbols and terms in labels and captions, adding a row (`First use`: the chapter path) for a new one. Route a caveat the chapter text must carry to `story-chap-drafter`.\n\nInclude the figure file with `\\input{figs\u002F\u003Cowner>_\u003Cslug>}` only in the file its `Chapter` cell names. A figure that moves to another owner outside a renumber, split, or merge takes the new owner's key: rename the figure file and its graphic and sources with `git mv`, rewrite the `figs\u002Fsrcs\u002F` path inside the figure file, move the `\\input` line, and rewrite the row's `File` and `Chapter` cells and each `Stated in` cell naming the old path in the same change (conventions §7, Ownership). Handle `\\listoffigures` as conventions §7 (Ownership) assigns. In the same change, update the outline row and the claims the figure states (conventions §3, Who sets each status), and tick any `tasks\u002F` line the change resolves (§6); then build and lint (§8).\n","# Design one traceable figure\n\n**Shared conventions.** Read `docs\u002Fmds\u002Fstory-workflow\u002Fwriting-workflow-conventions.md` in full before acting. Read `.env` once for the `STORY_LANG`, `INVOLVE`, and `STORY_MAIN` values this run needs, and reuse them. Resolve the language of replies and new Markdown under conventions §7: an explicit author request first, then a valid `STORY_LANG`, then the dialogue language, read from the author's latest own prose and never from a bare command or the English this run loads, or the invocation language when there is no user turn. Manuscript prose follows `degree\u002Fprofile.tex`, and an existing file keeps its language. A clear instruction may select the target and scope and authorize the corresponding action within this skill's documented paths, and work already authorized in this run is not asked for again; it never replaces a confirmation point or an `AGENTS.md` §1 ask-first choice (conventions §7).\n\nResolve one figure by its `F` ID or file in `notes\u002Foutline.md`, or `new`; without `notes\u002Foutline.md` or `notes\u002Fnotation.md`, route to `story-outl-planner` (conventions §1). For `new`, confirm its purpose, chapter, and claim IDs, then add its `planned` row with them in `Purpose`, `Chapter`, and `Claims` (conventions §3) and its `File` keyed by that chapter or other owning file (conventions §5, Manuscript file names); confirming is a judgment call, and `low` adds the row with the recommended values and reports them.\n\nChoose the simplest visual form that makes the intended relationship clear. Write the figure file `manus\u002Ffigs\u002F\u003Cowner>_\u003Cslug>.tex` — the figure environment, caption, and label, with the drawing itself (TikZ, pgfplots) or `\\includegraphics{figs\u002Fsrcs\u002F\u003Cowner>_\u003Cslug>}` — and keep the rendered graphic and every editable source (PDF, PPTX, SVG, plotting script) as `manus\u002Ffigs\u002Fsrcs\u002F\u003Cowner>_\u003Cslug>.*`, with one key and slug, `\u003Cowner>` being the key of the file the row's `Chapter` cell names (conventions §5, Manuscript file names), never replacing the source with a flattened or rasterized export. Beside or inside the source, keep a grep-readable map anchoring every data mark, numeric label, and comparative caption statement (conventions §2) to registered evidence read in this run; generated or decorative pixels are never evidence. Without a `cleared` row in `notes\u002Fpublications.md` (conventions §3), route adapted published material to `story-syns-coach`.\n\nKeep the figure accessible: legible type, non-color-only distinctions, suitable contrast, and an informative caption. Use `notes\u002Fnotation.md` symbols and terms in labels and captions, adding a row (`First use`: the chapter path) for a new one. Route a caveat the chapter text must carry to `story-chap-drafter`.\n\nInclude the figure file with `\\input{figs\u002F\u003Cowner>_\u003Cslug>}` only in the file its `Chapter` cell names. A figure that moves to another owner outside a renumber, split, or merge takes the new owner's key: rename the figure file and its graphic and sources with `git mv`, rewrite the `figs\u002Fsrcs\u002F` path inside the figure file, move the `\\input` line, and rewrite the row's `File` and `Chapter` cells and each `Stated in` cell naming the old path in the same change (conventions §7, Ownership). Handle `\\listoffigures` as conventions §7 (Ownership) assigns. In the same change, update the outline row and the claims the figure states (conventions §3, Who sets each status), and tick any `tasks\u002F` line the change resolves (§6); then build and lint (§8).\n",{"name":5,"description":7},"main","f76f6207f1ec06664927c7bd35e015ded2492294",".agents\u002Fskills\u002Fstory-figs-designer",0,"https:\u002F\u002Fgithub.com\u002Fwanghao9610\u002FSTORY","https:\u002F\u002Fwanghao9610.github.io\u002FSTORY\u002F","https:\u002F\u002Fgithub.com\u002Fwanghao9610","Leave the world a little different.","2026-10-11 20:45:09",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add wanghao9610\u002FSTORY --skill story-figs-designer",{"tool":39,"command":40},"bunx","bunx skills add wanghao9610\u002FSTORY --skill story-figs-designer",{"tool":42,"command":43},"pnpm","pnpm dlx skills add wanghao9610\u002FSTORY --skill story-figs-designer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fwanghao9610\u002FSTORY\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstory-figs-designer\u002FSKILL.md",true,[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"agents\u002Fopenai.yaml","REFERENCE","参考文档",64,"https:\u002F\u002Fgithub.com\u002Fwanghao9610\u002FSTORY\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstory-figs-designer\u002Fagents\u002Fopenai.yaml",[54,61,68,75,82,89],{"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},"01M7B1F8ARGWXHQMPDTMA37GCD","story-tabs-builder","Use to build or revise one thesis table (results, comparisons, mappings, synthesis) from fingerprinted evidence, with a source anchor on every quantitative or comparative row and synchronized claim, outline, and notation records. For a design whose message depends on visual encoding, use story-figs-designer.","https:\u002F\u002Fgithub.com\u002Fwanghao9610\u002FSTORY\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Fstory-tabs-builder\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},"01M7B1F51A31HHMFKFZTH15HF9","story-syns-coach","Use before outlining, when the thesis lacks a coherent argument, or to record an author-supplied publication reuse or permission fact. Shapes the thesis problem, central argument, research questions, arc, synthesis, and degree contributions from the author's intent and registered evidence, with the contribution, publication, and claim maps. For chapter architecture, use story-outl-planner.","https:\u002F\u002Fgithub.com\u002Fwanghao9610\u002FSTORY\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Fstory-syns-coach\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},"01M7B1F21G24ZDVHBAE3HEJVBC","story-revs-resolver","Use after thesis feedback or an official outcome arrives from supervisors, coauthors, committees, examiners, defenses, corrections, or deposits. Converts it into an immutable-source point ledger, reasoned dispositions, tracked promises, and outcome records, without rewriting chapters. For a simulated review, use story-exam-reviewer.","https:\u002F\u002Fgithub.com\u002Fwanghao9610\u002FSTORY\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Fstory-revs-resolver\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},"01M7B1EY0M541ZQSSYE3KEE83H","story-refs-curator","Use when a thesis needs a trustworthy source record — add, verify, deduplicate, or re-check bibliography entries, write reading notes, or find candidates for a chapter's unsupported literature assertions, verifying only from records fetched in the run. For auditing what the manuscript already cites, use story-cite-auditor.","https:\u002F\u002Fgithub.com\u002Fwanghao9610\u002FSTORY\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Fstory-refs-curator\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},"01M7B1ESPP5X6E3HE3GCHXX34N","story-proj-adopt","Use when an existing thesis draft or Overleaf export should come under STORY. Inventories the draft, confirms a file map, copies (never moves) the source after the author commits a pre-adoption checkpoint, records the draft's claims, and verifies the resulting build without redesigning chapters. After adoption, story-syns-coach frames the thesis story.","https:\u002F\u002Fgithub.com\u002Fwanghao9610\u002FSTORY\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Fstory-proj-adopt\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7B1EP833P00G858ZEEWP81X","story-outl-planner","Use once the thesis story is finalized or the author chooses a provisional outline, and whenever chapter boundaries change. Turns the story and contribution map into chapter architecture, briefs, figure and table plans, and chapter scaffolds wired into the active entry point, mapping existing drafts instead of replacing them. For the thesis argument itself, use story-syns-coach.","https:\u002F\u002Fgithub.com\u002Fwanghao9610\u002FSTORY\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Fstory-outl-planner\u002FSKILL.md",[],[]]