[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FDNR60SWMZEF2K412HFWQ4":3,"skill-same:01M7FDNR60SWMZEF2K412HFWQ4":48},{"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},"01M7FDNR60SWMZEF2K412HFWQ4","figure-spec",null,"Generate deterministic publication-quality architecture, workflow, and pipeline diagrams from structured JSON (FigureSpec) into editable SVG. Use when user says \"架构图\", \"workflow 图\", \"pipeline 图\", \"确定性矢量图\", \"figure spec\", \"draw architecture\", or needs precise, editable, publication-ready vector diagrams. Preferred over AI illustration for formal architecture\u002Fworkflow figures.","CZX-LBJ\u002Fdeepseek-science","CZX-LBJ","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F204594689?v=4","01M7FC59WQ9PFXT04MKGJDCFFT","czx","01M7FC59XB2GW0BKWN9JTDBQS7",1,"MIT","https:\u002F\u002Fgithub.com\u002FCZX-LBJ\u002Fdeepseek-science\u002Fblob\u002Fmain\u002Fpackages\u002Fskill\u002Fskill-science\u002Fassets\u002Fsources\u002Faris\u002Fskills\u002Fskills-codex\u002Ffigure-spec\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: figure-spec\ndescription: \"Generate deterministic publication-quality architecture, workflow, and pipeline diagrams from structured JSON (FigureSpec) into editable SVG. Use when user says \\\"架构图\\\", \\\"workflow 图\\\", \\\"pipeline 图\\\", \\\"确定性矢量图\\\", \\\"figure spec\\\", \\\"draw architecture\\\", or needs precise, editable, publication-ready vector diagrams. Preferred over AI illustration for formal architecture\u002Fworkflow figures.\"\nargument-hint: \"[description-of-diagram]\"\nallowed-tools: Bash(*), Read, Write, Edit\n---\n\n# FigureSpec: Deterministic JSON → SVG Figure Generation\n\nGenerate publication-quality **architecture diagrams**, **workflow pipelines**, **audit cascades**, and **system topology** figures as editable SVG vector graphics using a deterministic JSON → SVG renderer.\n\n## When to Use This Skill\n\n**Use `figure-spec`** for:\n- System architecture diagrams (layered, hub-and-spoke, multi-plane)\n- Workflow \u002F pipeline figures\n- Audit cascade \u002F flow-control diagrams\n- Any structured diagram where node positions, connections, and groupings are semantically important\n- Figures that need to be edited\u002Ftweaked later (SVG is plain text)\n- Figures where determinism matters (same spec → same SVG)\n\n**Do NOT use for:**\n- Data plots (bar\u002Fline\u002Fscatter) — use `\u002Fpaper-figure`\n- Natural\u002Fqualitative illustrations — use `\u002Fpaper-illustration`\n- Quick state-machine \u002F flowchart — use `\u002Fmermaid-diagram` (lighter syntax)\n\n## Core Properties\n\n- **Deterministic**: identical FigureSpec JSON always produces identical SVG output (for a fixed renderer version + fonts)\n- **Editable**: SVG output is plain-text, can be post-edited by hand or programmatically\n- **Validated**: renderer enforces schema, rejects malformed specs with clear error messages\n- **Shape-aware**: edge clipping works correctly for rect\u002Frounded\u002Fcircle\u002Fellipse\u002Fdiamond\n- **CJK support**: multi-line labels with proper Chinese character width estimation\n- **No external API**: runs fully local, no network, no API keys\n\n## Tool Location\n\nPhase 3.1 (Arch C) move: the canonical implementation now lives at\n`skills\u002Ffigure-spec\u002Fscripts\u002Ffigure_renderer.py`. `tools\u002Ffigure_renderer.py`\nis kept as a backwards-compatible `os.execv` shim so legacy layers\ncontinue to resolve. Codex-side install layouts that previously\ncopied the canonical into `~\u002F.codex\u002Fskills\u002Ffigure-spec\u002Ffigure_renderer.py`\nmust now place it at `~\u002F.codex\u002Fskills\u002Ffigure-spec\u002Fscripts\u002Ffigure_renderer.py`\nto match the new layout (re-run `install_aris_codex.sh` to pick up\nthe new symlink target).\n\nResolve `$FIGURE_RENDERER` via the Codex-side hybrid chain (layer 0\npreferred for self-contained owner SKILL; layers 1-4 are legacy\nshared-runtime compatibility):\n\n```bash\n# Layer 0: self-contained at the new canonical location (Phase 3.1).\nFIGURE_RENDERER=\"\"\nif [ -z \"${ARIS_REPO:-}\" ] && [ -f .aris\u002Finstalled-skills-codex.txt ]; then\n    ARIS_REPO=$(awk -F'\\t' '$1==\"repo_root\"{print $2; exit}' .aris\u002Finstalled-skills-codex.txt 2>\u002Fdev\u002Fnull) || true\nfi\n[ -n \"${ARIS_REPO:-}\" ] && [ -f \"$ARIS_REPO\u002Fskills\u002Ffigure-spec\u002Fscripts\u002Ffigure_renderer.py\" ] && FIGURE_RENDERER=\"$ARIS_REPO\u002Fskills\u002Ffigure-spec\u002Fscripts\u002Ffigure_renderer.py\"\n\n# Layers 1-3: legacy shared-runtime chain via shim at tools\u002Ffigure_renderer.py.\n[ -z \"$FIGURE_RENDERER\" ] && [ -n \"${ARIS_REPO:-}\" ] && [ -f \"$ARIS_REPO\u002Ftools\u002Ffigure_renderer.py\" ] && FIGURE_RENDERER=\"$ARIS_REPO\u002Ftools\u002Ffigure_renderer.py\"\n[ -z \"$FIGURE_RENDERER\" ] && [ -f tools\u002Ffigure_renderer.py ] && FIGURE_RENDERER=\"tools\u002Ffigure_renderer.py\"\n\n# Layer 4: Codex-side skill-local install (`install_aris_codex.sh` may place it here).\n[ -z \"$FIGURE_RENDERER\" ] && [ -f ~\u002F.codex\u002Fskills\u002Ffigure-spec\u002Fscripts\u002Ffigure_renderer.py ] && FIGURE_RENDERER=\"$HOME\u002F.codex\u002Fskills\u002Ffigure-spec\u002Fscripts\u002Ffigure_renderer.py\"\n[ -z \"$FIGURE_RENDERER\" ] && [ -f ~\u002F.codex\u002Fskills\u002Ffigure-spec\u002Ffigure_renderer.py ] && FIGURE_RENDERER=\"$HOME\u002F.codex\u002Fskills\u002Ffigure-spec\u002Ffigure_renderer.py\"  # pre-Phase-3.1 layout\n\n[ -n \"$FIGURE_RENDERER\" ] || {\n  echo \"ERROR: figure_renderer.py not found at any of: \\$ARIS_REPO\u002Fskills\u002Ffigure-spec\u002Fscripts\u002F, \\$ARIS_REPO\u002Ftools\u002F, tools\u002F, ~\u002F.codex\u002Fskills\u002Ffigure-spec\u002Fscripts\u002F, ~\u002F.codex\u002Fskills\u002Ffigure-spec\u002F. Set ARIS_REPO, rerun install_aris_codex.sh, or copy the canonical \\$ARIS_REPO\u002Fskills\u002Ffigure-spec\u002Fscripts\u002Ffigure_renderer.py next to this skill.\" >&2\n  exit 1\n}\n\npython3 \"$FIGURE_RENDERER\" render \u003Cspec.json> --output \u003Cout.svg>\npython3 \"$FIGURE_RENDERER\" validate \u003Cspec.json>\npython3 \"$FIGURE_RENDERER\" schema\n```\n\n## Workflow\n\n### Step 1: Understand the Diagram Goal\n\nFrom `$ARGUMENTS` (description or path to `PAPER_PLAN.md` \u002F `NARRATIVE_REPORT.md`), identify:\n- **Purpose**: architecture, workflow, pipeline, audit cascade, topology?\n- **Main entities**: what are the boxes?\n- **Relationships**: how do they connect? (uses, produces, calls, verifies, chains)\n- **Grouping**: do entities cluster into named regions?\n- **Hierarchy vs network**: stacked layers, left-to-right flow, or central hub?\n\n### Step 2: Draft the FigureSpec JSON\n\nCanvas sizing guide:\n- Single-column figure: ~500×350 px\n- Two-column (full-width): ~900×500 px\n- Tall topology: ~700×700 px\n\nStart from a template based on the diagram type:\n\n**Architecture (stacked rows)**:\n```json\n{\n  \"canvas\": {\"width\": 900, \"height\": 520},\n  \"nodes\": [\n    {\"id\": \"layer1_label\", \"label\": \"Layer 1\", \"x\": 450, \"y\": 60, ...},\n    {\"id\": \"node_a\", \"label\": \"A\", \"x\": 180, \"y\": 120, ...},\n    {\"id\": \"node_b\", \"label\": \"B\", \"x\": 350, \"y\": 120, ...}\n  ],\n  \"edges\": [...],\n  \"groups\": [\n    {\"label\": \"Layer 1\", \"node_ids\": [\"node_a\", \"node_b\"], \"fill\": \"#F0F9FF\", \"stroke\": \"#BAE6FD\"}\n  ]\n}\n```\n\n**Workflow (left-to-right chain)**:\n```json\n{\n  \"canvas\": {\"width\": 900, \"height\": 300},\n  \"nodes\": [\n    {\"id\": \"step1\", \"label\": \"Step 1\", \"x\": 100, \"y\": 150, \"shape\": \"rounded\"},\n    {\"id\": \"step2\", \"label\": \"Step 2\", \"x\": 280, \"y\": 150, \"shape\": \"rounded\"}\n  ],\n  \"edges\": [\n    {\"from\": \"step1\", \"to\": \"step2\", \"label\": \"produces\"}\n  ]\n}\n```\n\n**Decision diamond**:\n```json\n{\"id\": \"check\", \"label\": \"Passes?\", \"shape\": \"diamond\", \"x\": 450, \"y\": 200}\n```\n\n### Step 3: Render and Validate\n\n```bash\n# Validate first\npython3 \"$FIGURE_RENDERER\" validate \u002Ftmp\u002Fspec.json\n\n# Render to SVG\npython3 \"$FIGURE_RENDERER\" render \u002Ftmp\u002Fspec.json --output figures\u002Ffig_arch.svg\n\n# Convert to PDF for LaTeX inclusion\nrsvg-convert -f pdf figures\u002Ffig_arch.svg -o figures\u002Ffig_arch.pdf\n```\n\nIf validation fails, inspect the error (missing field, duplicate ID, overlap warning, invalid hex color) and fix the JSON.\n\n### Step 4: Visual Review\n\nOpen the SVG\u002FPDF and check:\n- **No overlaps**: nodes don't collide with each other or group boundaries\n- **Readability**: font sizes are consistent, labels aren't clipped\n- **Edge clarity**: arrows hit nodes at clean angles, labels near edges are legible\n- **Group alignment**: background rectangles frame their members cleanly\n- **Color distinction**: categories are visually distinct in both color and grayscale\n\nIf issues found, edit the JSON spec (never the generated SVG) and re-render.\n\n### Step 5: Iterate with Codex Review (Optional, for High-Stakes Figures)\n\nFor paper architecture figures, invoke fresh-agent review (same-family provisional in the base mirror):\n\n```text\nspawn_agent:\n  model: gpt-6-astra\n  reasoning_effort: xhigh\n  message: |\n    Review this SVG figure for a technical paper (architecture \u002F workflow diagram).\n\n    Spec file: \u002Fpath\u002Fto\u002Fspec.json\n    Rendered: \u002Fpath\u002Fto\u002Ffig.svg\n\n    Evaluate:\n    1. Clarity (C): can a reader understand the system from this figure alone?\n    2. Readability (R): font sizes, label placement, visual hierarchy\n    3. Semantic accuracy (S): do relationships match the described system?\n\n    Score each axis 1-10 and list specific issues to fix.\n```\n\nIterate until all three axes ≥ 7\u002F10. The ARIS tech report figures went through 5 rounds of this loop to reach C:7\u002FR:7\u002FS:8.\n\n## Schema Quick Reference\n\nRun `python3 \"$FIGURE_RENDERER\" schema` for the authoritative schema.\n\n### Nodes\n\n| Field | Required | Default | Notes |\n|-------|----------|---------|-------|\n| `id` | ✓ | — | Unique |\n| `label` | ✓ | — | `\\n` for multi-line |\n| `x`, `y` | ✓ | — | Center coordinates |\n| `width`, `height` | | 120, 50 | |\n| `shape` | | `rounded` | `rect` \u002F `rounded` \u002F `circle` \u002F `ellipse` \u002F `diamond` |\n| `fill`, `stroke` | | auto from palette | `#RRGGBB` |\n| `text_color` | | `#333333` | |\n| `font_size` | | 14 | Override style default |\n\n### Edges\n\n| Field | Default | Notes |\n|-------|---------|-------|\n| `from`, `to` | required | Same = self-loop |\n| `label` | — | Short edge label |\n| `style` | `solid` | `solid` \u002F `dashed` \u002F `dotted` |\n| `color` | `#555555` | |\n| `curve` | `false` | Curved path |\n\n### Groups\n\nRectangular background regions framing a set of nodes:\n```json\n{\"label\": \"Layer Name\", \"node_ids\": [\"a\", \"b\", \"c\"], \"fill\": \"#EFF6FF\", \"stroke\": \"#BFDBFE\"}\n```\n\n## Design Patterns\n\n### Pattern 1: Layered Architecture\nStack rows of related nodes, each row is a group, add inter-layer arrows with semantic labels (`uses↓`, `produces↑`, `checks↓`).\n\n### Pattern 2: Hub-and-Spoke\nCentral node (e.g., Executor), peripheral nodes (skills, tools), solid arrows for primary relations, dashed for feedback.\n\n### Pattern 3: Pipeline with Feedback\nLeft-to-right main flow, feedback arrows curve below with `curve: true`.\n\n### Pattern 4: Audit Cascade\nThree-stage horizontal cascade with inputs feeding in from top, outputs exiting right, each stage in its own group.\n\n## Anti-Patterns\n\n- **Don't use groups as hierarchy**: groups frame peer nodes, not containment\n- **Don't nest groups**: renderer draws them as background rectangles; nested groups look like Russian dolls\n- **Don't cross-draw long diagonals**: if an arrow crosses 3+ rows, rethink the layout\n- **Don't mix font sizes for same role**: keep one size per node category\n\n## Output Contract\n\n- SVG file in `figures\u002F` (vector, editable, hand-tweakable)\n- Source FigureSpec JSON saved in `figures\u002Fspecs\u002F` for reproducibility\n- PDF version via `rsvg-convert` for LaTeX inclusion\n\n## Integration with Other Skills\n\n- **`\u002Fpaper-writing`** (Workflow 3): when `illustration: figurespec` (default for architecture figures), this skill handles Phase 2b\n- **`\u002Fpaper-figure`**: handles data plots; they complement each other (data + architecture = complete figure set)\n- **`\u002Fpaper-illustration`**: fallback for figures that need natural\u002Fqualitative style (method illustrations with photos, qualitative result grids)\n- **`\u002Fmermaid-diagram`**: lighter alternative for simple flowcharts\n\n## Review Tracing\n\nAfter each reviewer agent call, save the trace following `shared-references\u002Freview-tracing.md` (Policy C — forensic; never silently skip). Use `save_trace.sh` (resolved per the chain in `shared-references\u002Fintegration-contract.md` §2) or write files directly to `.aris\u002Ftraces\u002F\u003Cskill>\u002F\u003Cdate>_run\u003CNN>\u002F`. Respect the `--- trace:` parameter (default: `full`).\n","# FigureSpec: Deterministic JSON → SVG Figure Generation\n\nGenerate publication-quality **architecture diagrams**, **workflow pipelines**, **audit cascades**, and **system topology** figures as editable SVG vector graphics using a deterministic JSON → SVG renderer.\n\n## When to Use This Skill\n\n**Use `figure-spec`** for:\n- System architecture diagrams (layered, hub-and-spoke, multi-plane)\n- Workflow \u002F pipeline figures\n- Audit cascade \u002F flow-control diagrams\n- Any structured diagram where node positions, connections, and groupings are semantically important\n- Figures that need to be edited\u002Ftweaked later (SVG is plain text)\n- Figures where determinism matters (same spec → same SVG)\n\n**Do NOT use for:**\n- Data plots (bar\u002Fline\u002Fscatter) — use `\u002Fpaper-figure`\n- Natural\u002Fqualitative illustrations — use `\u002Fpaper-illustration`\n- Quick state-machine \u002F flowchart — use `\u002Fmermaid-diagram` (lighter syntax)\n\n## Core Properties\n\n- **Deterministic**: identical FigureSpec JSON always produces identical SVG output (for a fixed renderer version + fonts)\n- **Editable**: SVG output is plain-text, can be post-edited by hand or programmatically\n- **Validated**: renderer enforces schema, rejects malformed specs with clear error messages\n- **Shape-aware**: edge clipping works correctly for rect\u002Frounded\u002Fcircle\u002Fellipse\u002Fdiamond\n- **CJK support**: multi-line labels with proper Chinese character width estimation\n- **No external API**: runs fully local, no network, no API keys\n\n## Tool Location\n\nPhase 3.1 (Arch C) move: the canonical implementation now lives at\n`skills\u002Ffigure-spec\u002Fscripts\u002Ffigure_renderer.py`. `tools\u002Ffigure_renderer.py`\nis kept as a backwards-compatible `os.execv` shim so legacy layers\ncontinue to resolve. Codex-side install layouts that previously\ncopied the canonical into `~\u002F.codex\u002Fskills\u002Ffigure-spec\u002Ffigure_renderer.py`\nmust now place it at `~\u002F.codex\u002Fskills\u002Ffigure-spec\u002Fscripts\u002Ffigure_renderer.py`\nto match the new layout (re-run `install_aris_codex.sh` to pick up\nthe new symlink target).\n\nResolve `$FIGURE_RENDERER` via the Codex-side hybrid chain (layer 0\npreferred for self-contained owner SKILL; layers 1-4 are legacy\nshared-runtime compatibility):\n\n```bash\n# Layer 0: self-contained at the new canonical location (Phase 3.1).\nFIGURE_RENDERER=\"\"\nif [ -z \"${ARIS_REPO:-}\" ] && [ -f .aris\u002Finstalled-skills-codex.txt ]; then\n    ARIS_REPO=$(awk -F'\\t' '$1==\"repo_root\"{print $2; exit}' .aris\u002Finstalled-skills-codex.txt 2>\u002Fdev\u002Fnull) || true\nfi\n[ -n \"${ARIS_REPO:-}\" ] && [ -f \"$ARIS_REPO\u002Fskills\u002Ffigure-spec\u002Fscripts\u002Ffigure_renderer.py\" ] && FIGURE_RENDERER=\"$ARIS_REPO\u002Fskills\u002Ffigure-spec\u002Fscripts\u002Ffigure_renderer.py\"\n\n# Layers 1-3: legacy shared-runtime chain via shim at tools\u002Ffigure_renderer.py.\n[ -z \"$FIGURE_RENDERER\" ] && [ -n \"${ARIS_REPO:-}\" ] && [ -f \"$ARIS_REPO\u002Ftools\u002Ffigure_renderer.py\" ] && FIGURE_RENDERER=\"$ARIS_REPO\u002Ftools\u002Ffigure_renderer.py\"\n[ -z \"$FIGURE_RENDERER\" ] && [ -f tools\u002Ffigure_renderer.py ] && FIGURE_RENDERER=\"tools\u002Ffigure_renderer.py\"\n\n# Layer 4: Codex-side skill-local install (`install_aris_codex.sh` may place it here).\n[ -z \"$FIGURE_RENDERER\" ] && [ -f ~\u002F.codex\u002Fskills\u002Ffigure-spec\u002Fscripts\u002Ffigure_renderer.py ] && FIGURE_RENDERER=\"$HOME\u002F.codex\u002Fskills\u002Ffigure-spec\u002Fscripts\u002Ffigure_renderer.py\"\n[ -z \"$FIGURE_RENDERER\" ] && [ -f ~\u002F.codex\u002Fskills\u002Ffigure-spec\u002Ffigure_renderer.py ] && FIGURE_RENDERER=\"$HOME\u002F.codex\u002Fskills\u002Ffigure-spec\u002Ffigure_renderer.py\"  # pre-Phase-3.1 layout\n\n[ -n \"$FIGURE_RENDERER\" ] || {\n  echo \"ERROR: figure_renderer.py not found at any of: \\$ARIS_REPO\u002Fskills\u002Ffigure-spec\u002Fscripts\u002F, \\$ARIS_REPO\u002Ftools\u002F, tools\u002F, ~\u002F.codex\u002Fskills\u002Ffigure-spec\u002Fscripts\u002F, ~\u002F.codex\u002Fskills\u002Ffigure-spec\u002F. Set ARIS_REPO, rerun install_aris_codex.sh, or copy the canonical \\$ARIS_REPO\u002Fskills\u002Ffigure-spec\u002Fscripts\u002Ffigure_renderer.py next to this skill.\" >&2\n  exit 1\n}\n\npython3 \"$FIGURE_RENDERER\" render \u003Cspec.json> --output \u003Cout.svg>\npython3 \"$FIGURE_RENDERER\" validate \u003Cspec.json>\npython3 \"$FIGURE_RENDERER\" schema\n```\n\n## Workflow\n\n### Step 1: Understand the Diagram Goal\n\nFrom `$ARGUMENTS` (description or path to `PAPER_PLAN.md` \u002F `NARRATIVE_REPORT.md`), identify:\n- **Purpose**: architecture, workflow, pipeline, audit cascade, topology?\n- **Main entities**: what are the boxes?\n- **Relationships**: how do they connect? (uses, produces, calls, verifies, chains)\n- **Grouping**: do entities cluster into named regions?\n- **Hierarchy vs network**: stacked layers, left-to-right flow, or central hub?\n\n### Step 2: Draft the FigureSpec JSON\n\nCanvas sizing guide:\n- Single-column figure: ~500×350 px\n- Two-column (full-width): ~900×500 px\n- Tall topology: ~700×700 px\n\nStart from a template based on the diagram type:\n\n**Architecture (stacked rows)**:\n```json\n{\n  \"canvas\": {\"width\": 900, \"height\": 520},\n  \"nodes\": [\n    {\"id\": \"layer1_label\", \"label\": \"Layer 1\", \"x\": 450, \"y\": 60, ...},\n    {\"id\": \"node_a\", \"label\": \"A\", \"x\": 180, \"y\": 120, ...},\n    {\"id\": \"node_b\", \"label\": \"B\", \"x\": 350, \"y\": 120, ...}\n  ],\n  \"edges\": [...],\n  \"groups\": [\n    {\"label\": \"Layer 1\", \"node_ids\": [\"node_a\", \"node_b\"], \"fill\": \"#F0F9FF\", \"stroke\": \"#BAE6FD\"}\n  ]\n}\n```\n\n**Workflow (left-to-right chain)**:\n```json\n{\n  \"canvas\": {\"width\": 900, \"height\": 300},\n  \"nodes\": [\n    {\"id\": \"step1\", \"label\": \"Step 1\", \"x\": 100, \"y\": 150, \"shape\": \"rounded\"},\n    {\"id\": \"step2\", \"label\": \"Step 2\", \"x\": 280, \"y\": 150, \"shape\": \"rounded\"}\n  ],\n  \"edges\": [\n    {\"from\": \"step1\", \"to\": \"step2\", \"label\": \"produces\"}\n  ]\n}\n```\n\n**Decision diamond**:\n```json\n{\"id\": \"check\", \"label\": \"Passes?\", \"shape\": \"diamond\", \"x\": 450, \"y\": 200}\n```\n\n### Step 3: Render and Validate\n\n```bash\n# Validate first\npython3 \"$FIGURE_RENDERER\" validate \u002Ftmp\u002Fspec.json\n\n# Render to SVG\npython3 \"$FIGURE_RENDERER\" render \u002Ftmp\u002Fspec.json --output figures\u002Ffig_arch.svg\n\n# Convert to PDF for LaTeX inclusion\nrsvg-convert -f pdf figures\u002Ffig_arch.svg -o figures\u002Ffig_arch.pdf\n```\n\nIf validation fails, inspect the error (missing field, duplicate ID, overlap warning, invalid hex color) and fix the JSON.\n\n### Step 4: Visual Review\n\nOpen the SVG\u002FPDF and check:\n- **No overlaps**: nodes don't collide with each other or group boundaries\n- **Readability**: font sizes are consistent, labels aren't clipped\n- **Edge clarity**: arrows hit nodes at clean angles, labels near edges are legible\n- **Group alignment**: background rectangles frame their members cleanly\n- **Color distinction**: categories are visually distinct in both color and grayscale\n\nIf issues found, edit the JSON spec (never the generated SVG) and re-render.\n\n### Step 5: Iterate with Codex Review (Optional, for High-Stakes Figures)\n\nFor paper architecture figures, invoke fresh-agent review (same-family provisional in the base mirror):\n\n```text\nspawn_agent:\n  model: gpt-6-astra\n  reasoning_effort: xhigh\n  message: |\n    Review this SVG figure for a technical paper (architecture \u002F workflow diagram).\n\n    Spec file: \u002Fpath\u002Fto\u002Fspec.json\n    Rendered: \u002Fpath\u002Fto\u002Ffig.svg\n\n    Evaluate:\n    1. Clarity (C): can a reader understand the system from this figure alone?\n    2. Readability (R): font sizes, label placement, visual hierarchy\n    3. Semantic accuracy (S): do relationships match the described system?\n\n    Score each axis 1-10 and list specific issues to fix.\n```\n\nIterate until all three axes ≥ 7\u002F10. The ARIS tech report figures went through 5 rounds of this loop to reach C:7\u002FR:7\u002FS:8.\n\n## Schema Quick Reference\n\nRun `python3 \"$FIGURE_RENDERER\" schema` for the authoritative schema.\n\n### Nodes\n\n| Field | Required | Default | Notes |\n|-------|----------|---------|-------|\n| `id` | ✓ | — | Unique |\n| `label` | ✓ | — | `\\n` for multi-line |\n| `x`, `y` | ✓ | — | Center coordinates |\n| `width`, `height` | | 120, 50 | |\n| `shape` | | `rounded` | `rect` \u002F `rounded` \u002F `circle` \u002F `ellipse` \u002F `diamond` |\n| `fill`, `stroke` | | auto from palette | `#RRGGBB` |\n| `text_color` | | `#333333` | |\n| `font_size` | | 14 | Override style default |\n\n### Edges\n\n| Field | Default | Notes |\n|-------|---------|-------|\n| `from`, `to` | required | Same = self-loop |\n| `label` | — | Short edge label |\n| `style` | `solid` | `solid` \u002F `dashed` \u002F `dotted` |\n| `color` | `#555555` | |\n| `curve` | `false` | Curved path |\n\n### Groups\n\nRectangular background regions framing a set of nodes:\n```json\n{\"label\": \"Layer Name\", \"node_ids\": [\"a\", \"b\", \"c\"], \"fill\": \"#EFF6FF\", \"stroke\": \"#BFDBFE\"}\n```\n\n## Design Patterns\n\n### Pattern 1: Layered Architecture\nStack rows of related nodes, each row is a group, add inter-layer arrows with semantic labels (`uses↓`, `produces↑`, `checks↓`).\n\n### Pattern 2: Hub-and-Spoke\nCentral node (e.g., Executor), peripheral nodes (skills, tools), solid arrows for primary relations, dashed for feedback.\n\n### Pattern 3: Pipeline with Feedback\nLeft-to-right main flow, feedback arrows curve below with `curve: true`.\n\n### Pattern 4: Audit Cascade\nThree-stage horizontal cascade with inputs feeding in from top, outputs exiting right, each stage in its own group.\n\n## Anti-Patterns\n\n- **Don't use groups as hierarchy**: groups frame peer nodes, not containment\n- **Don't nest groups**: renderer draws them as background rectangles; nested groups look like Russian dolls\n- **Don't cross-draw long diagonals**: if an arrow crosses 3+ rows, rethink the layout\n- **Don't mix font sizes for same role**: keep one size per node category\n\n## Output Contract\n\n- SVG file in `figures\u002F` (vector, editable, hand-tweakable)\n- Source FigureSpec JSON saved in `figures\u002Fspecs\u002F` for reproducibility\n- PDF version via `rsvg-convert` for LaTeX inclusion\n\n## Integration with Other Skills\n\n- **`\u002Fpaper-writing`** (Workflow 3): when `illustration: figurespec` (default for architecture figures), this skill handles Phase 2b\n- **`\u002Fpaper-figure`**: handles data plots; they complement each other (data + architecture = complete figure set)\n- **`\u002Fpaper-illustration`**: fallback for figures that need natural\u002Fqualitative style (method illustrations with photos, qualitative result grids)\n- **`\u002Fmermaid-diagram`**: lighter alternative for simple flowcharts\n\n## Review Tracing\n\nAfter each reviewer agent call, save the trace following `shared-references\u002Freview-tracing.md` (Policy C — forensic; never silently skip). Use `save_trace.sh` (resolved per the chain in `shared-references\u002Fintegration-contract.md` §2) or write files directly to `.aris\u002Ftraces\u002F\u003Cskill>\u002F\u003Cdate>_run\u003CNN>\u002F`. Respect the `--- trace:` parameter (default: `full`).\n",{"name":5,"description":7,"allowed-tools":24,"argument-hint":25},"Bash(*), Read, Write, Edit","[description-of-diagram]","main","18193d71ea3441d7c033dbf195b8a7c75ac96f75","packages\u002Fskill\u002Fskill-science\u002Fassets\u002Fsources\u002Faris\u002Fskills\u002Fskills-codex\u002Ffigure-spec",0,"https:\u002F\u002Fgithub.com\u002FCZX-LBJ\u002Fdeepseek-science","https:\u002F\u002Fgithub.com\u002FCZX-LBJ","一个没事喜欢随便写点代码的小菜鸡\r\n","2026-10-22 09:48:04",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add CZX-LBJ\u002Fdeepseek-science --skill figure-spec",{"tool":40,"command":41},"bunx","bunx skills add CZX-LBJ\u002Fdeepseek-science --skill figure-spec",{"tool":43,"command":44},"pnpm","pnpm dlx skills add CZX-LBJ\u002Fdeepseek-science --skill figure-spec","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCZX-LBJ\u002Fdeepseek-science\u002Fblob\u002Fmain\u002Fpackages\u002Fskill\u002Fskill-science\u002Fassets\u002Fsources\u002Faris\u002Fskills\u002Fskills-codex\u002Ffigure-spec\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7FEEKSNMRMKW6JEK93PFDFY","bio-free-energy-calculations","Performs alchemical free-energy calculations including relative binding free energy (RBFE \u002F FEP+) and absolute binding free energy (ABFE) via OpenFE, FEP+, GROMACS, AMBER pmemd, and OpenMM with explicit lambda scheduling, soft-core potentials, MBAR\u002FBAR analysis, cycle-closure validation, and protocol-appropriate enhanced sampling. Compares ML alternatives (Boltz-2 affinity, DeepDock). Use when ranking analogs by binding affinity beyond docking accuracy, performing prospective lead optimization, or validating SAR predictions.","https:\u002F\u002Fgithub.com\u002FCZX-LBJ\u002Fdeepseek-science\u002Fblob\u002Fmain\u002Fpackages\u002Fskill\u002Fskill-science\u002Fassets\u002Fsources\u002Fbioskills\u002Fchemoinformatics\u002Ffree-energy-calculations\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7FEE5CTE5QK55CEMXNNVWY9","bio-conformer-generation","Generates 3D conformer ensembles using RDKit ETKDGv3 with knowledge-enhanced distance geometry, MMFF94\u002FUFF force-field optimization, CREST + GFN2-xTB semi-empirical refinement, and macrocycle-aware torsion preferences. Provides explicit decision rules for single vs ensemble conformer use, RMSD pruning, energy windows, conformer count, and force-field choice. Use when preparing 3D ligands for docking, generating descriptor input for 3D QSAR, or sampling macrocycle\u002Fpeptide conformational ensembles.","https:\u002F\u002Fgithub.com\u002FCZX-LBJ\u002Fdeepseek-science\u002Fblob\u002Fmain\u002Fpackages\u002Fskill\u002Fskill-science\u002Fassets\u002Fsources\u002Fbioskills\u002Fchemoinformatics\u002Fconformer-generation\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7FEDNGFEMFWD1MSEDR5H7CY","bio-admet-prediction","Predicts ADMET properties using ADMETlab 3.0 (119 platform features, including 77 prediction models with modeled-endpoint uncertainty), ADMET-AI, DeepChem MolNet, and chemprop D-MPNN with explicit handling of OECD QSAR principles, applicability domain assessment, calibration, hERG\u002FCYP\u002FAMES endpoints, and PAINS \u002F Lipinski \u002F Ro5 \u002F Veber \u002F BBB druglikeness filters. Use when filtering compounds for drug-likeness, prioritizing leads by predicted safety, or building an in-house ADMET QSAR model.","https:\u002F\u002Fgithub.com\u002FCZX-LBJ\u002Fdeepseek-science\u002Fblob\u002Fmain\u002Fpackages\u002Fskill\u002Fskill-science\u002Fassets\u002Fsources\u002Fbioskills\u002Fchemoinformatics\u002Fadmet-prediction\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7FED69GFB54FRF7AV5066DN","writing-systems-papers","Paragraph-level structural blueprint for 10-12 page systems papers targeting OSDI, SOSP, ASPLOS, NSDI, and EuroSys. Provides page allocation, paragraph templates, and writing patterns. Use when user says \"写系统论文\", \"systems paper structure\", \"OSDI paper\", \"SOSP paper\", or wants fine-grained structural guidance for a systems conference submission.","https:\u002F\u002Fgithub.com\u002FCZX-LBJ\u002Fdeepseek-science\u002Fblob\u002Fmain\u002Fpackages\u002Fskill\u002Fskill-science\u002Fassets\u002Fsources\u002Faris\u002Fskills\u002Fwriting-systems-papers\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7FECVVDWZ0X0VEDTCE4B4DZ","wiki-enrich","Fill in the per-paper TODO sections of research-wiki\u002Fpapers\u002F\u003Cslug>.md pages that literature-ingest skills leave as bare scaffolds. Use when user says 'enrich wiki', 'fill paper TODOs', 'wiki body 補完', '把 paper 摘要寫進 wiki', 'research-wiki 自動填', or after a batch ingest that left papers\u002F as TODO scaffolds.","https:\u002F\u002Fgithub.com\u002FCZX-LBJ\u002Fdeepseek-science\u002Fblob\u002Fmain\u002Fpackages\u002Fskill\u002Fskill-science\u002Fassets\u002Fsources\u002Faris\u002Fskills\u002Fwiki-enrich\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7FECD4BCJ2MTSBDDSE3ZAJ5","web-debug-search","Search GitHub, Stack Exchange, Chinese technical communities, official documentation, and general developer web sources for software errors, compatibility problems, API usage questions, and real-world workarounds. Use for debugging and discovery only; results are not paper-citation evidence.","https:\u002F\u002Fgithub.com\u002FCZX-LBJ\u002Fdeepseek-science\u002Fblob\u002Fmain\u002Fpackages\u002Fskill\u002Fskill-science\u002Fassets\u002Fsources\u002Faris\u002Fskills\u002Fweb-debug-search\u002FSKILL.md",[],[]]