nature-polishinglisted

# Nature-Style Academic Polishing — Router This skill is split into two layers: - A **static layer** under `static/` that holds versioned, reusable content fragments (core principles, paper-type playbooks, per-section guidance, language-specific rules, per-journal style). - A **dynamic layer** (this file plus `manifest.yaml`) that detects the request's axes and loads only the fragments needed for the current job. Do not try to apply the polishing logic from memory or from this router. Always load fragments from disk as described below. ## Direct file polishing For manuscript revision, read `static/core/file-polishing.md` through `always_load`. It governs scope inference, language preservation, proportionate evidence checking and verification annotations across all journal routes. Short natural-language requests are sufficient; no fixed prompt or author questionnaire is required. Older guide examples asking to confirm or fill a template are planning aids, not mandatory pauses. Explicit scope restrictions and approval stages still apply. Read `../nature-shared/core/natural-academic-prose.md` for both ordinary polish and requests for vivid, natural or less formulaic prose. Keep layout-only work on its existing specialized route. ## 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 axes (`paper_type`, `section`, `language`, `journal`), the allowed valu