Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
yuan1z0825 avatar

Nature Figure

  • 4 installs
  • 33.4k repo stars
  • Updated August 4, 2026
  • yuan1z0825/nature-skill

This is a copy of nature-figure by yuan1z0825 - installs and ranking accrue to the original listing.

Helps with ai & agent building tasks during AI-assisted development.

About

nature-figure is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted coding.

  • nature-figure
  • AI & Agent Building
  • AI-coding skill

Nature Figure by the numbers

  • 4 all-time installs (skills.sh)
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/yuan1z0825/nature-skill --skill nature-figure

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs4
repo stars33.4k
Last updatedAugust 4, 2026
Repositoryyuan1z0825/nature-skill

What it does

Helps with ai & agent building tasks during AI-assisted development.

Files

SKILL.mdMarkdownGitHub ↗

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. 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.

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.