← ClaudeAtlas

field-guide-publicationlisted

Turn a published field-guide or installation-guide website into a downloadable paginated PDF and isolated repository documentation without changing application runtime files. Use when a live guide needs a matching PDF, a safe docs-only GitHub commit, branded attribution, or troubleshooting for a documentation-publishing push.
SteveKinzey/claude-code-tools-installer · ★ 1 · Code & Development · score 67
Install: claude install-skill SteveKinzey/claude-code-tools-installer
# Field Guide Publication Use this workflow to turn a published guide into a downloadable PDF and a repository-safe documentation package. Treat the live website as the **canonical visual source** and keep all publishing artifacts isolated from application or installer runtime paths. ## Inputs Collect the live guide URL, target repository, current local repository checkout, product owner and author names, copyright year, and the intended documentation directory. For installer repositories, default to `docs/<guide-name>/`. Read `references/repository-isolation.md` before copying files into a repository or making a Git commit. Read `references/github-write-access.md` when a GitHub push returns `403`, when a workflow file or GitHub Pages configuration is being published, or when the user asks for PAT or SSH setup commands. Read `references/ssh-publishing.md` when the user wants SSH-only Git publishing or a dedicated SSH key for a single repository. ## Workflow ### 1. Confirm the canonical guide Open the supplied live site and capture its section structure, CTA labels, visual hierarchy, author credit, ownership statement, and copyright. Do not treat a separately written article as the source of truth when the user explicitly identifies the website version. Record the canonical URL and any design constraints. The PDF should preserve the same section sequence and branded attribution. ### 2. Produce the paginated PDF Render the static guide, rather than an unrelated conten