Update Han plugin documentation so every skill, agent, guidance doc, index, and cross-reference is current and accurate. On a non-default branch, scopes the pass to entities the branch actually touched. On the default branch, performs a full documentation sweep across the whole plugin. Use when updating, refreshing, syncing, auditing, or verifying Han's docs after changing skills, agents, references, or top-level guidance — including "update the docs", "doc sweep", "refresh documentation", "audit the docs", "make sure the docs are current". This is a repository-maintenance skill for the Han repo itself, not a general documentation skill — use /project-documentation to document features in arbitrary projects, /han-release to cut a release (and update CHANGELOG), and /update-pr-description for PR bodies.
Complete workflow for project documentation including ADRs, PRDs, personas, and docs organization. Use when setting up documentation for a new project or improving existing docs. Triggers on project documentation, ADR, PRD, personas, docs structure, documentation setup.
Guidelines for writing documentation files including 11ty templates, Eleventy shortcodes, JSDoc annotations, and markdown content. Use this skill whenever the user works with documentation markdown files, Vale prose linting errors, Eleventy shortcodes (dodont, example), frontmatter, JSDoc annotations that must pass Vale, or the documentation site. Also trigger when the user mentions Vale errors, adding terms to the vocabulary, suppressing Vale rules, or writing and fixing prose in .md or .ts files.
Audits a documentation file line-by-line against the actual codebase, proving every factual claim with source file and line number citations. Produces a structured evidence table, applies corrections for inaccuracies, then verifies corrections are themselves accurate. Use when a user asks to review, audit, refresh, or update a documentation file, or says a doc is outdated.
Use when writing or reviewing pynchy documentation, deciding where to document things, updating the docs, checking doc consistency, or fixing broken links. Covers information architecture, writing philosophy, tree-shaped navigation, doc-code coupling, no hard-coded usernames, extensibility framing for pluggable subsystems, and when to add code comments.
Searches across your Notion workspace, synthesizes findings from multiple pages, and creates comprehensive research documentation saved as new Notion pages. Turns scattered information into structured reports with proper citations and actionable insights.
Use this skill when you need to record an architecture decision (ADR) or document the reasoning behind a design choice — when changing public APIs, shipping features that change behavior, or recording context that future engineers (human or agent) will need to understand the codebase. Does NOT replace code comments or inline docstrings; targets strategic documentation and decision capture. Primary keywords: ADR architecture decision record, technical documentation, design rationale, decision log, API documentation, README writing, changelog, documentation-driven development, inline documentation best practices, specification writing. For all major agentic platforms.
Use this skill when the user asks to check, audit, or update the project's documentation, or says things like "update docs", "are the docs current", "check documentation", "sync docs with code", "outdated documentation", or any phrasing that pairs "docs" / "documentation" / "README" / "landing page" with verbs like update / check / audit / sync / verify. Audits README.md, docs/index.html, resources/whisper/README.md, and any other tracked doc against the current source — flags drift, then offers to fix it.
Consult and maintain the agent-facing documentation tree at .claude-docs/. ALWAYS invoke — not optional. (1) BEFORE any non-trivial task — read .claude-docs/README.md + .claude-docs/LOOKUP.md + the topic file for the area you are touching. This replaces blind greping and gets you to the answer 5–10× faster. Skip ONLY for trivial one-line localised fixes (typos, renames, whitespace). (2) AFTER any change that adds, renames, or deletes a module / feature / endpoint / DB model / enum / UI primitive / shared hook / store / event / queue / pattern / security rule / workflow — update the affected catalog file IN THE SAME COMMIT as the code change. Not updating is a correctness bug, not a style preference. (3) When the user says "init / regenerate / rebuild / resync claude-docs" — do a full regeneration. Also triggered by /agentic-documentation.
Fetch current library, framework, and API documentation via the Context7 MCP instead of relying on training data. Use this skill whenever the user asks a question that depends on accurate, up-to-date behavior of any library, framework, SDK, or API — including setup/configuration questions, code examples, API references, migration guides, or version-specific behavior. Trigger even if the user doesn't name the skill explicitly but clearly needs current docs to get a correct answer.
Use up-to-date library and framework docs via Context7 MCP instead of training data. Activates for setup questions, API references, code examples, or when the user names a framework (e.g. React, Next.js, Prisma).
Audit project documentation to identify and correct drift, ensuring all documents are accurate and reflect current codebase state. Use when documentation feels stale, after major releases, before onboarding new team members, or to combat documentation drift. Trigger phrases: 'docs seem out of date', 'audit the documentation', 'is the README accurate', 'check for broken links and outdated info', 'review docs for accuracy'.
Plain text files in a repository that tell a coding agent how the project works: commands to run, conventions to follow and things to avoid. CLAUDE.md, AGENTS.md, cursor rules and skills are the common kinds.
CLAUDE.md or AGENTS.md?
CLAUDE.md is read by Claude Code. AGENTS.md is an open format that Codex, Cursor and other agents read. Many projects keep one and point the other at it.
What is a skill?
A folder with a SKILL.md that describes one capability, such as filling PDFs or reviewing code. The agent loads it only when the task calls for it.
Can I search my own team's files too?
Your agents already can, over MCP, limited to the files you're allowed to read. Searching them from this page is coming.
testdoubleSkill
