github-pages-designlisted
Install: claude install-skill ValentinNikolaev/agent-skills
# GitHub Pages: Design
Create a coherent, lightweight visual layer that supports repository content and survives static hosting constraints.
## Stay inside the Pages boundary
- Inspect the existing site stack, theme, CSS, assets, screenshots, logos, and documented branding before changing visual direction.
- Preserve a healthy framework-native theme and its accessible behavior. Prefer small token and component overrides over a replacement design system.
- Design for documentation, project explanation, code, tables, and navigation—not for an imaginary application dashboard.
- Keep remote fonts, trackers, scripts, and asset hosts out unless explicitly authorized and reviewed for privacy, reliability, and integrity.
- Treat exact colors, typefaces, and breakpoints as repository decisions. Do not copy illustrative values as universal requirements.
- Leave route generation, base-path configuration, framework migration, and deployment ownership with `github-pages-create`. If visual work exposes a defect in one of those areas, report and hand it off instead of silently changing it.
## Read the relevant references
- Read [references/pages-visual-contract.md](references/pages-visual-contract.md) before creating or materially changing the Pages visual system.
- Read [references/design-direction-and-redesign.md](references/design-direction-and-redesign.md) before choosing a direction or extending or redesigning an existing visual layer.
- Read [references/pages-design-directions.md