The Website Specification — Agent Skill
A single source of truth for what a good website does. Ten categories, 128 topics, every item tagged with a status (required, recommended, optional, avoid). This skill bundles all 128 topic pages as local Markdown so the agent can answer offline, plus optional MCP / HTTP routes for the freshest data.
Upstream: <https://specification.website> · Repo: <https://github.com/1991513ccie-png
When to use this skill
Invoke it whenever the user:
- Asks "what should my site have", "is X required", "audit this URL", "what does the spec say about Y".
- Asks about HTML foundations, SEO, accessibility (WCAG), HTTP security headers, well-known URIs (
/.well-known/*), agent/AI readiness (llms.txt, MCP,robots.txt, structured data), Core Web Vitals, privacy/consent, error/offline pages, i18n/hreflang. - Reviews a real site and wants to cite primary standards (WHATWG, W3C, IETF, IANA, WCAG, schema.org) rather than vendor blog posts.
- Needs a tickable checklist of required + recommended items.
- Wants a machine-readable contract for a platform-agnostic audit.
Do not invoke for: writing application logic, choosing a JS framework, generic programming questions unrelated to web platform features.
File layout
specification-website/
├── SKILL.md ← this file (overview, routing, statuses, workflows)
├── references/
│ ├── checklist.md ← full required/recommended/avoid checklist (tickable)
│ ├── topics-index.md ← every topic with category + status + summary
│ ├── categories/
│ │ ├── foundations.md ← per-category index, topics grouped by status
│ │ ├── seo.md
│ │ ├── accessibility.md
│ │ ├── security.md
│ │ ├── well-known.md
│ │ ├── agent-readiness.md
│ │ ├── performance.md
│ │ ├── privacy.md
│ │ ├── resilience.md
│ │ └── i18n.md
│ ├── topics/<category>/<slug>.md ← all 128 full spec pages, with frontmatter
│ ├──
（为兼容发布已截断）
