← ClaudeAtlas

github-pages-visual-systemlisted

Design or refine the visual system of a GitHub Pages documentation site, repository website, wiki, or project landing page. Use for Pages-specific CSS tokens, color and dark themes, typography, reading measure, spacing, grids, hierarchy, responsive behavior, and repository branding. Do not use for generic product design systems, native mobile UI, or non-Pages websites.
ValentinNikolaev/agent-skills · ★ 0 · AI & Automation · score 70
Install: claude install-skill ValentinNikolaev/agent-skills
<!-- 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-visual-system/SKILL.md`. Manual changes in this directory will be overwritten the next time the generator runs. Edit the canonical skill instead. # GitHub Pages Visual System 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 `create-github-pages`. If visual work exposes a defect in one of those areas, report and hand it off instead of silently changing it. ## Read the contract Re