aa3682

Guide Template — Development skill for Claude Code

Development community

Reusable starter for an open, public knowledge site built on Nextra 4 — process-first structure, plain-English section names, one reference page for regulated figures, and a CLAUDE.md that drives cont.

How to install Guide Template

This entry records only its repository, not the path inside it, so there is no exact command to give. Open aa3682/guide-template and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Guide Template does

Reusable starter for an open, public knowledge site built on Nextra 4 — process-first structure, plain-English section names, one reference page for regulated figures, and a CLAUDE.md that drives content through Claude Code.

Alternatives in Development

  • Product Name — Brainstorm 5 memorable product names aligned to brand values 7.8k ★
  • Portaljs Add Chart — Add a chart (line, bar, area, pie, or scatter) to a dataset's showcase in a PortalJS portal 2.3k ★
  • Dashclaw Quality — Recurring find-and-fix quality pass over the whole DashClaw app — browser smoke (frontend-verify) + code gates 297 ★

README

guide-template

Reusable starter for an open, public knowledge site built on Nextra 4 — process-first structure, plain-English section names, one reference page for regulated figures, and a CLAUDE.md that drives content through Claude Code.

What this is

A topic-neutral copy of a working guide site with the subject matter removed. It keeps the six-section layout (introduction, process, knowledge areas, tools, glossary, about), one example step page and one example area page as skeletons, an empty yearly-figures page, and the conventions in `CLAUDE.md` that shape every page. Anything specific to a topic is a bracketed all-caps token.

Stack

  • Nextra 4 with nextra-theme-docs
  • Next.js App Router
  • MDX content in content/
  • Pagefind search index generated at build time
  • pnpm as the only package manager

Starting a new guide

Replace every token, then edit every file in the list. A grep for `\[[A-Z ]\+\]` (excluding `node_modules` and `.next`) shows what is left.

Tokens:

  • [TOPIC] — the subject of the guide as it reads in a sentence.
  • [PROCESS NAME] — the name of the step-by-step process the guide is organized around; also the title of the process section.
  • [AREA LABEL] — the name of one knowledge area; repeated once per area on the domains landing page and the figures page.
  • [AUTHOR LINE] — how the author is described on the About page, without a personal name, employer, credential, or license.
  • [DISCLAIMER] — the standard disclaimer that sits in a Callout on each section landing page and as plain prose on the About page.

Files to edit:

  • CLAUDE.md — the tokens, the step and area names under Structure, the Go deeper sources, and the Glossary running list as pages are written.
  • README.md — the title, the opening description, and the repository URL.
  • package.json — name.
  • app/layout.jsx — the site title, description, and REPO_URL.
  • app/globals.css — the accent hue, if a d