自然人物
- 作者仓库星标 16,057
- 作者仓库 nature-skills
- 领域
- 通用
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @Yuan1z0825 · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 需简单配置
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- Python
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 命令执行
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
# Nature Figure Making — Router
This skill is split into two layers:
- A **static layer** under `static/` that holds versioned, reusable content fragments (the figure contract and default stance, plus a per-backend quick-start for Python and R).
- A **dynamic layer** (this file plus `manifest.yaml`) that detects the plotting backend and loads only the fragment needed for the current job. The large design, API, pattern, and QA material lives in on-demand references.
Do not try to apply the figure logic from memory or from this router. Always load fragments from disk as described below.
## Routing protocol
Follow these five steps every time the skill is invoked.
### 1. Load the manifest and the core layer
Read [manifest.yaml](manifest.yaml). It declares the `backend` axis, the allowed values, and the file paths each value maps to.
Also read every file listed under `always_load` (`static/core/contract.md` and `static/core/stance.md`). These hold the figure contract, the backend gate, the missing-runtime rule, the privacy rule, and the default operating stance that apply to every figure job.
### 2. Resolve the backend — a blocking gate
Backend selection blocks everything else. Decide the `backend` value only from an explicit user choice or a clearly language-specific input file/workflow:
- `python` — matplotlib / seaborn.
- `r` — ggplot2 / patchwork / ComplexHeatmap.
If the user has **not** explicitly chosen, ask exactly one concise question — **Python or R?** — and stop. Do not default, guess, generate mock data, or write scripts before the answer. Only recommend a backend when the user explicitly asks you to choose; then use `references/backend-selection.md`, state the reason, and proceed. Once selected, the backend is **exclusive** for all drawing, previewing, exporting, and visual QA (see `core/contract.md`).
### 3. Load the matching backend fragment
After the backend is resolved, Read the mapped fragment (`static/fragments/backend/python.md` or `static/fragments/backend/r.md`). It carries the backend-only execution rule and the publication quick-start (rcParams/theme and export helper). Do **not** load the other backend's fragment.
### 4. Build the figure using the loaded material
Apply the loaded material in this order:
1. Figure contract (`core/contract.md`) — write the core conclusion, map the evidence chain, classify the archetype, set the journal/export contract, before any code.
2. Default stance (`core/stance.md`) — archetype-first composition, hero panel, restrained palette, statistics/integrity as part of the figure.
3. Backend fragment — the exclusive Python or R quick-start and execution rule.
The chart serves the scientific logic; aesthetic polish is subordinate to making the core conclusion clear, defensible, and reviewable.
### 5. Reach for references only when needed
The files under `references/` are deep references, not defaults. Open them on demand per the `references.on_demand` table in the manifest — for example `references/figure-contract.md` to build the contract, `references/api.md` for the Python palette and helpers, `references/r-workflow.md` for R, `references/design-theory.md` for color/typography/export rationale, `references/common-patterns.md` and `references/chart-types.md` for layout/chart recipes, `references/nature-2026-observations.md` for real Nature page archetypes, `references/qa-contract.md` before final delivery, and `references/tutorials.md` / `references/demos.md` for worked examples.
## Why this split
- The static layer is versioned and reviewable. The backend gate is now explicit in the manifest rather than buried in prose.
- The dynamic layer keeps each invocation cheap: only the selected backend's quick-start enters context, and the 2,600+ lines of reference depth load only when a step needs them.
- The router itself is short on purpose. Update fragments and references, not this file, when adding scope.
- This structure mirrors `nature-writing`, `nature-polishing`, `nature-reader`, and `nature-paper2ppt`.
章节与文件索引
按说明文件中的顺序排列。
1.加载manifest和核心层
2. 解决后端——阻塞门
3.加载匹配的后端片段
4. 使用加载的材料构建图形
5. 仅在需要时才获取参考资料
文件/命令 -> static/ · manifest.yaml · backend · always_load · static/core/contract.md · static/core/stance.md · python · references/backend-selection.md
内容校验值 -> c9fe7aa85426
当前原文的自动摘译,尚未人工审校。
1.加载manifest和核心层
阅读manifest.yaml。它声明了
backend轴、允许的值以及每个值映射到的文件路径。另请阅读always_load(static/core/contract.md和static/core/stance.md)下列出的每个文件。它们包含适用于每个图形作业的图形合同、后端门、缺失运行时规则、隐私规则和默认操作立场。2. 解决后端——阻塞门
后端选择会阻止其他一切。 仅根据明确的用户选择或明确的特定于语言的输入文件/工作流程来确定
backend值:python— matplotlib / seaborn。3.加载匹配的后端片段
后端解析后,读取映射的片段(
static/fragments/backend/python.md或static/fragments/backend/r.md)。它携带仅后端执行规则和发布快速启动(rcParams/主题和导出帮助程序)。不要加载其他后端的片段。4. 使用加载的材料构建图形
按此顺序应用加载的材料:图形合约 (
core/contract.md) — 在任何代码之前编写核心结论、绘制证据链、对原型进行分类、设置日志/导出合约。默认立场(core/stance.md)——原型优先的构图、英雄面板、克制的调色板、统计/完整性作为图形的一部分。后端片段——独有的Python或R快速启动和执行规则。5. 仅在需要时才获取参考资料
references/下的文件是深层引用,而不是默认文件。 根据清单中的references.on_demand表按需打开它们 - 例如references/figure-contract.md用于构建合同,references/api.md用于Python调色板和助手,references/r-workflow.md用于R,references/design-theory.md用于颜色/排版/导出原理,references/common-patterns.md和references/chart-types.md用于布局/图表食谱,references/nature-2026-observations.md用于真实的自然页面原型,references/qa-contract.md在最终交付之前,以及references/tutorials.md/references/demos.md用于工作示例。