← ClaudeAtlas

github-pages-createlisted

Build or repair GitHub Pages sites from repository evidence. Use for immediate implementation and authorized delivery configuration. Staged proposals and resuming approved GP- IDs belong to github-pages-improve.
ValentinNikolaev/agent-skills · ★ 1 · AI & Automation · score 74
Install: claude install-skill ValentinNikolaev/agent-skills
# GitHub Pages: Create Build a useful, maintainable site from repository evidence. ## Operating contract - Inspect repository instructions, current changes, documentation, manifests, source, site files, Pages workflows, `CNAME`, and branding before editing. - Preserve user work, canonical documentation, branding, and public URLs. Prefer improving a viable site over replacing it. - Derive commands, examples, compatibility, API behavior, status, and other project claims from current repository evidence. - Mark unknowns as unknown. Never invent metrics, testimonials, roadmaps, examples, or support claims. - Keep one canonical source for each fact. Import or generate from existing Markdown when possible; avoid unsynchronized copies. - Keep dependencies proportionate to the site. - Do not commit, push, publish, change repository settings, buy a domain, or create credentials without explicit authorization. ## Read the references - Read [references/framework-selection.md](references/framework-selection.md) before choosing or changing the stack. - Read [references/quality-and-deployment.md](references/quality-and-deployment.md) before implementation and during final verification. - Read [references/workflow-handoffs.md](references/workflow-handoffs.md) when coordinating passes or continuing previous work. It owns the shared handoff format and drift check. ## Coordinate the Pages specialists Keep repository truth, framework choice, routes, build behavior, and deployment in this