Two small npm CLI tools for scaffolding new content files:
shane-new-post
For AstroPaper-style Astro blogs — any blog collection with a title / pubDatetime / tags / featured / draft frontmatter shape similar to AstroPaper’s. Interactive mode or a single command, with automatic image-folder creation, filename suggestions from the title, and support for tags / featured / draft / mdx fields.
shane-new-doc
For Astro Starlight sites (like this one) — any project with @astrojs/starlight as a dependency. Same interactive and command modes, plus directory/filename safety checks and automatic renaming on collision instead of overwriting.
The two tools are not interchangeable: shane-new-post writes into a flat posts collection (src/content/posts/), while shane-new-doc writes into Starlight’s nested docs collection (src/content/docs/<directory>/) and understands sidebar ordering. Pick the one that matches the target project’s framework, not the one that matches the content type.
Each tool supports English and Chinese out of the box — there is no separate -chinese variant to choose between. All prompts, comments, and error messages come from an en.json / zh-cn.json pair bundled inside the package, both installed together every time.
Language is picked once, at install time: if the terminal is interactive and no flag was passed, the installer asks “Select CLI language / 选择界面语言” and saves the answer to .shane-new-post.json / .shane-new-doc.json in the project root, so every later run reuses it automatically without asking again. The prompt can also be skipped up front with --lang=en / --lang=zh-cn, or overridden later on a single command without touching the saved setting. See Install & Quick Start for the full language-resolution order.
Applies to both tools A few rules are shared across new-post and new-doc’s command mode — worth knowing before reading either tool’s individual guide:
key:value pairs can appear in any order, and can be separated by / or by spaces (with a trailing \ for a multi-line command). Only the positional arguments that come before the key:value pairs — the filename for new-post, the directory and filename for new-doc — have a fixed order.T / F as well as the full words true / false. Concretely: only t or true (in any casing, e.g. T, True, TRUE) is read as yes; every other value — f, false, empty, or anything else — is read as no.description can be written desc) — see each tool’s own argument reference table for the full list.Both packages ship a postinstall script that runs automatically the moment the dependency finishes installing (via npm/pnpm/yarn’s own lifecycle-script mechanism — standard package.json behavior, not something this project invents). In short: it checks whether the project is a fit, then drops a ready-to-run script into scripts/, saves a small config file, and wires up a pnpm new-doc / pnpm new-post command in package.json — no manual copy-pasting. Every check it performs (framework detection, conflict scanning, package-manager detection, and what to do if a step gets silently skipped) is documented in full, step by step, in Installation Internals — worth a read even if nothing ever goes wrong, since it also covers how to fix things by hand.