github-pages-content-architecturelisted

<!-- GENERATED BY generate_skill_wrappers.py; DO NOT EDIT MANUALLY. --> ## Generated Claude Code skill — do not edit manually This complete skill and its bundled resources are generated from `agent-plugins/skills/github-pages-content-architecture/SKILL.md`. Manual changes in this directory will be overwritten the next time the generator runs. Edit the canonical skill instead. # GitHub Pages Content Architecture 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 `create-github-pages` and keep this skill focused on the content model. ## Read the contract Read [references/pages-content-contract.md](references/pages-content-co