← ClaudeAtlas

github-pages-contentlisted

Organize GitHub Pages content, reader tasks, navigation, copy, and local search from verified repository sources. Use for Pages content work, not general product information architecture.
ValentinNikolaev/agent-skills · ★ 1 · AI & Automation · score 74
Install: claude install-skill ValentinNikolaev/agent-skills
# GitHub Pages: Content Turn repository evidence into a small, findable Pages site whose structure matches real reader tasks. ## Stay inside the Pages boundary - Establish the repository's readers, public URL shape, existing routes, documentation sources, and first successful task before proposing structure. - Treat README files, maintained docs, examples, schemas, changelogs, contribution guidance, security policy, and license as evidence. Do not invent missing content. - Prefer links or generated imports over copied canonical facts. - Design for static generation and client-side behavior. Do not prescribe server search, personalization, accounts, or analytics unless another authorized system provides them. - Preserve existing public routes and anchors; content reorganization does not authorize URL breakage. - When the request also requires implementing framework, route, build, or deployment changes, hand those concerns to `github-pages-create` and keep this skill focused on the content model. ## Read the contract Read [references/pages-content-contract.md](references/pages-content-contract.md) before designing or restructuring the site's content, navigation, labels, or search. For a handoff to design or implementation, use the family's [shared format](../github-pages-create/references/workflow-handoffs.md). Tie it to the inspected revision and relevant working files. Keep a small task's handoff inline rather than creating mandatory ledgers. ## Produce a reviewable co