Software teams need structured approaches to plan new features, but manually gathering requirements and designing architecture takes significant time. This skill provides a systematic workflow for analyzing requirements, exploring existing codebase patterns, and creating actionable implementation plans saved to persistent markdown files.

Building effective Claude skills requires understanding proper structure and best practices. This skill provides a complete 6-step guide to create, validate, and package reusable skills for any domain.

Documentation drift happens when project changes are not reflected in README and docs. This skill audits documentation, verifies links and statistics, and ensures CLAUDE.md and project files stay synchronized with actual project state.

Managing documentation at scale leads to duplicated content and inconsistent structures. This skill provides section-level editing tools, templates, and workflows to maintain clean, DRY documentation that stays in sync with code.

Developers often miss critical SEO elements or use incorrect HTML semantics. This skill systematically reviews web pages for title tags, meta descriptions, heading hierarchy, and semantic HTML to improve search visibility.

Code reviews often miss error handling issues that cause silent failures and poor user experience. This gate provides a structured checklist to ensure all code handles failures gracefully with helpful user feedback.

Poor documentation wastes team time and creates confusion. This skill enforces documentation standards for README files, JSDoc comments, and inline code explanations following the WHY not WHAT principle. Get consistent, maintainable documentation that explains context and rationale.

Users often struggle to create well-structured Agent Skills that follow best practices. This skill provides step-by-step guidance for creating, validating, and testing Claude Code Skills with proper structure, frontmatter, and documentation.

This skill evaluates UI components and pages against WCAG 2.1 guidelines. It identifies accessibility issues and provides specific fixes. Use it to ensure your interfaces are usable by people with disabilities.

Writing skills helps you build reusable, tested documentation that Claude can discover and apply. This skill adapts test-driven development to process documentation, ensuring your skills actually work when agents need them.

Breaking complex features into actionable tasks is difficult and error-prone. This skill provides a structured template for writing comprehensive implementation plans with test-driven steps, exact file paths, and verification commands.

Documentation drifts from codebase reality over time. This skill provides a systematic process to audit, update, and synchronize all documentation with current implementation state.

Engineering decisions often lose their rationale over time, causing teams to repeat mistakes or reverse carefully considered choices. The Archivist ensures every technical decision is documented with context, alternatives, and reasoning using Architecture Decision Records.

Manual code review is time-consuming and inconsistent. This skill provides a systematic framework for reviewing git changes, checking plan compliance, and identifying engineering issues with specific line numbers and actionable recommendations.

Complex projects require organized documentation that remains navigable as they grow. This skill provides templates and workflows for creating Obsidian-compatible markdown wikis with progressive disclosure, task tracking, and research integration.

Context is lost the moment you stop thinking about a problem. This skill captures maximum context at ticket creation time, including requirements, implementation details, file locations, and acceptance criteria. The result is tickets that developers can implement immediately without asking follow-up questions.

Creating pull requests without issue links misses opportunities to close issues automatically and track work. This skill ensures every PR links related issues and uses closing keywords for seamless issue management.

Creating MCP server skills from scratch takes significant research and experimentation. This skill provides a proven template, discovery workflow, and performance best practices so you can build optimized skills in minutes instead of hours.

Agents often skip documentation or use skills inconsistently under pressure. This skill provides a test-driven development framework for creating skills that agents actually follow. Build skills using RED-GREEN-REFACTOR cycles, then pressure-test them to ensure compliance even when agents face time pressure, sunk costs, or authority conflicts.

Developers struggle to break down complex features into clear, executable tasks. This skill generates comprehensive implementation plans with exact file paths, test code, and step-by-step instructions following TDD principles.