Loading...
Loading...
Found 46 Skills
Update and maintain CLAUDE.md, README.md, agents, skills, and rules to match current project state. Use when docs are stale, the project structure changed, agents, skills, or rules reference outdated paths, or the user asks to update project documentation.
DISTILL
Best Practice Advisor for AGENTS.md / CLAUDE.md. It is used when users ask about the format, structure, and best practices of agents markdown, AGENTS.md, CLAUDE.md, Claude Code memory, and AI coding agent instruction files; it also supports reviewing, diagnosing, rewriting, optimizing, or creating agent instruction files such as AGENTS.md, CLAUDE.md, CLAUDE.local.md, and .claude/rules from scratch. It is not suitable for general README writing unless the goal is to provide project context for AI coding agents.
Optimize CLAUDE.md files using progressive disclosure. Goal: Maximize LLM working efficiency, NOT minimize line count. Use when: User wants to optimize CLAUDE.md, complains about context issues, or file exceeds 500 lines.
Detect project tech stack and disable irrelevant skills to save context window space. Use when the user says "manage skills", "optimize skills", "disable irrelevant skills", "skill manager", or asks which skills are relevant for this project.
Reflect on the current session and refine skills or CLAUDE.md based on patterns observed. Use when the user says "refine", "what did we learn", or at the end of a session to make skills better through use.
Interactively onboard a project to agent-driven development by running a structured interview and generating a complete AGENTS.md (or CLAUDE.md). Use this skill whenever a user mentions "AGENTS.md", "CLAUDE.md", "agent behavior", "agent instructions", "agent config", "set up agent rules", "onboard agent", "configure claude code", "agent guardrails", "agent workflow", or asks how to tell an AI agent how to behave in their project — even if they just say "help me write AGENTS.md" or "what should go in CLAUDE.md". Always prefer this skill over ad-hoc agent instruction generation.
Four slash commands for documentation lifecycle: /docs, /docs-init, /docs-update, /docs-claude. Create, maintain, and audit CLAUDE.md, README.md, and docs/ structure with smart templates. Use when: starting new projects, maintaining documentation, auditing docs for staleness, or ensuring CLAUDE.md matches project state.
Optimize CLAUDE.md and docs/ ecosystem following Boris Cherny's best practices
Use when completing development phases or branches to identify and update CLAUDE.md or AGENTS.md files that may have become stale - analyzes what changed, determines affected contracts and documentation, and coordinates updates
Cross-tool compatibility workflow. Use when generating AGENTS.md files for compatibility with other AI coding tools, or creating tool-specific instruction files from CLAUDE.md.
Creates and reviews CLAUDE.md configuration files for Claude Code. Applies HumanLayer guidelines including instruction budgets (~50 user-level, ~100 project-level), WHAT/WHY/HOW framework, and progressive disclosure. Identifies anti-patterns like using Claude as a linter for style rules.