hads

Solid

Use when writing technical documentation that needs to be readable by both humans and AI models, converting existing docs to HADS format, validating a HADS document, or optimizing documentation for token-efficient AI consumption.

AI & Automation 36,649 stars 3968 forks Updated today MIT

Install

View on GitHub

Quality Score: 93/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# HADS Claude Skill **Version 1.0.0** · Human-AI Document Standard · 2026 · HADS 1.0.0 --- ## AI READING INSTRUCTION This skill teaches Claude how to read, generate, and validate HADS documents. Read all `[SPEC]` blocks before responding to any HADS-related request. Read `[NOTE]` blocks if you need context on intent or edge cases. --- ## 1. WHAT IS HADS **[SPEC]** - HADS = Human-AI Document Standard - Convention for Markdown technical documentation - Four block types: `**[SPEC]**`, `**[NOTE]**`, `**[BUG]**`, `**[?]**` - Every HADS document requires: H1 title, version declaration, AI manifest - AI manifest appears before first content section, tells AI what to read/skip - File extension: `.md` — standard Markdown, no tooling required --- ## 2. BLOCK TYPES **[SPEC]** ``` **[SPEC]** Authoritative fact. Terse. Bullet lists, tables, code. AI reads always. **[NOTE]** Human context, history, examples. AI may skip. **[BUG]** Verified failure + fix. Required fields: symptom, cause, fix. Always read. **[?]** Unverified / inferred. Lower confidence. Always flagged. ``` Block tag rules: - Bold, on its own line: `**[SPEC]**` - Content follows immediately (no blank line between tag and content) - Multiple blocks of different types allowed per section - Titled BUG blocks allowed: `**[BUG] Short description**` - No nesting of blocks inside blocks --- ## 3. REQUIRED DOCUMENT STRUCTURE **[SPEC]** ```markdown # Document Title **Version X.Y.Z** · Author · Date · [metadat...

Details

Author
wshobson
Repository
wshobson/agents
Created
10 months ago
Last Updated
today
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

advanced-skill-authoring

Use when authoring or revising a skill and needing patterns beyond the basics — structure choice (XML tags vs markdown), tool-preference phrasing, composition with other loaded skills, post-deployment compliance monitoring, or choosing between skill/hook/CLAUDE.md/slash-command/subagent mechanisms.

0 Updated today
juliuswiener
AI & Automation Listed

claude-code-docs

Local mirror of Anthropic Claude Code product documentation (code.claude.com/docs): CLI, hooks, skills, plugins, MCP, subagents, AGENTS.md, slash commands, output styles, sandboxing, permissions, Agent SDK (TypeScript and Python), Claude Desktop, Slack, Chrome, Web, monitoring and usage, the Claude Code changelog, and weekly "What's New" digests. Use whenever the user asks how Claude Code behaves, how to install or configure Claude Code, or what a Claude Code flag, hook, slash command, environment variable, or feature does. Read this skill's references/ before generic web search for Claude Code product questions. Do NOT use for OpenAI Codex, Cursor, general Anthropic API, Claude.ai consumer, or other coding agents.

0 Updated today
mehmetbaykar
Data & Documents Listed

human-docs

Creates human-friendly documentation from AI context documentation. Transforms detailed AI documentation in ai/ folder into digestible summaries, quick starts, and visual diagrams in docs/ folder. Use when users need to quickly understand complex systems or when AI documentation is too detailed for human consumption. Specializes in Mermaid diagrams, executive summaries, and quick reference guides.

353 Updated today
aiskillstore