Claude Skills by laurigates

WCAG 2.1/2.2 compliance implementation, ARIA patterns, keyboard navigation, focus management, and accessibility testing. Use when implementing accessible components, fixing accessibility issues, or when the user mentions WCAG, ARIA, screen readers, or keyboard navigation.

CSS custom property architecture, theme systems, design token organization, and component library integration. Use when implementing design systems, theme switching, dark mode, or when the user mentions tokens, CSS variables, theming, or design system setup.

Set up Claude Code lifecycle hooks and event handlers in settings.json. Use when you want to trigger a script on session start, run a hook before or after tool calls (PreToolUse/PostToolUse), configure hook timeouts to prevent cancellation errors, or debug hooks that aren't firing correctly.

Write and configure custom agent definitions in Claude Code's agents/ directory. Use when you want to create a new agent .md file, define a specialized agent with its own system prompt and tools, set up an agent with isolated context, or configure agent capabilities and restrictions in your project's .claude/ configuration.

Design and scaffold the code execution pattern for MCP-based agent systems. Use when building agents that interact with many MCP tools, when intermediate data is too large for model context, when you need loops/conditionals across tool calls, or when PII must stay out of the model context. Based on Anthropic's engineering guidance.

Install and configure Model Context Protocol (MCP) servers for Claude Code projects. Use when you want to add or enable an MCP server, connect a tool or integration (database, API, file system), update MCP settings in .mcp.json, or troubleshoot MCP server connection issues.

Analyze and assimilate project-specific Claude configurations

Audit Claude subagent configurations for completeness, security, and best practices

Analyze all plugins for sub-agent opportunities. Identifies skills with verbose output, gaps in agent coverage, and model selection improvements.

HTTP API testing for TypeScript (Supertest) and Python (httpx, pytest). Covers REST APIs, GraphQL, request/response validation, authentication, and error handling. Use when user mentions API testing, Supertest, httpx, REST testing, endpoint testing, HTTP response validation, or testing API routes.

Check and configure API contract testing with Pact, OpenAPI validation, and schema testing

Advanced Bevy ECS patterns including complex queries, system scheduling, change detection, entity relationships, and performance optimization. Use when working on advanced Bevy game architecture, optimizing ECS performance, or implementing complex game systems.

Bevy game engine development including ECS architecture, rendering, input handling, asset management, and game loop design. Use when building games with Bevy, working with entities/components/systems, or when the user mentions Bevy, game development in Rust, or 2D/3D games.

Consistent style guide for writing blog posts about projects and technical work. Supports quick updates, detailed write-ups, retrospectives, and tutorials. Designed for low-friction entry and easy scanning.

Create a blog post about your work with guided prompts and templates

Domain analysis, conflict detection, and relationship validation for Architecture Decision Records. Use when creating or validating ADRs to ensure consistency.

List all ADRs with title, status, date, and domain in a markdown table

Validate ADR relationships, detect orphaned references, and check domain consistency

Generate or update CLAUDE.md from project context and blueprint artifacts

Curate library or project documentation for ai_docs to optimize AI context

Derive Architecture Decision Records from existing project structure, dependencies, and documentation

Derive PRDs, ADRs, and PRPs from git history, codebase structure, and existing documentation

Derive PRD from existing project documentation, README, and codebase analysis

Derive Claude rules from git commit log decisions. Newer commits override older decisions when conflicts exist.

Generate project-specific rules and commands from PRDs for Blueprint Development methodology. Use when generating behavioral rules for architecture patterns, testing strategies, implementation guides, or quality standards from requirements documents.

List blueprint documents (ADRs, PRDs, PRPs) with metadata extracted from frontmatter and headers

Idempotent meta command that determines and executes the next logical blueprint action

Display feature tracker statistics and completion summary

Synchronize feature tracker with TODO.md and PRDs, manage tasks

Generate project-specific rules from PRDs

Initialize Blueprint Development structure in current project

Versioned migration procedures for upgrading blueprint structure between format versions

Move generated artifact to custom layer to preserve modifications

Create a PRP (Product Requirement Prompt) with systematic research, curated context, and validation gates

Execute a PRP with validation loop, TDD workflow, and quality gates

Manage modular rules in .claude/rules/ directory

Show blueprint version, configuration, and check for available upgrades

Scan all blueprint documents and assign IDs to those missing them, update manifest registry

Check for stale generated content and offer regeneration or promotion

Upgrade blueprint structure to the latest format version

Create work-order with minimal context for isolated subagent execution, optionally linked to GitHub issue

Assess quality of PRPs and work-orders using systematic confidence scoring. Use when evaluating readiness for execution or subagent delegation.

Detect PRD/ADR/PRP opportunities in conversations and prompt for document creation. Activates when users discuss features, architecture decisions, or implementation planning.

Unified ID system for PRDs, ADRs, PRPs, and GitHub issues. Auto-generates IDs on document access, maintains bidirectional links, and provides traceability across all artifacts.

Track feature implementation status against requirements documents. Provides hierarchical FR code tracking, phase management, task tracking, and sync with TODO.md.

Find and replace code patterns structurally using ast-grep. Use when you need to match code by its AST structure (not just text), such as finding all functions with specific signatures, replacing API patterns across files, or detecting code anti-patterns that regex cannot reliably match.

Analyze codebases for anti-patterns, code smells, and quality issues using ast-grep structural pattern matching. Use when reviewing code quality, identifying technical debt, or performing comprehensive code analysis across JavaScript, TypeScript, Python, Vue, React, or other supported languages.

Analyze codebase for anti-patterns, code smells, and quality issues using ast-grep

Refactor code following SOLID principles and best practices

Structured code review approach covering security, quality, performance, and consistency.