Claude Skills

Invoke BEFORE writing PHP code. Provides coding standards and naming conventions.

Invoke before designing presenters, modules, or application structure in web applicartion.

Provides Nette Utils helper classes. Use when working with arrays, strings, files, images, JSON, validators, DateTime, or other utility functions.

Provides frontend development guidelines for Nette. Use when working with Vite, SCSS, JavaScript, Nette Assets, or build configuration.

Invoke before creating or modifying Nette Forms. Provides form controls, validation, rendering patterns.

Accessibility review orchestrator. Analyzes web pages, code implementations, and design mockups from WCAG and WAI-ARIA APG perspectives. Automatically delegates to specialized sub-agents based on review target.

Invoke before configuring Nette DI - services, .neon files, autowiring.

Provides Nette Schema for data validation and normalization. Use when validating configuration, API inputs, or any data structures with Expect class.

Invoke before writing or modifying any .phpt test files. Provides Nette Tester conventions, Assert methods, and tester commands.

Invoke before creating or modifying .latte files. Provides Latte syntax, tags, filters, layouts, and extensions.

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation. Also used during /shipyard:init for requirements gathering.

Use when starting feature work that needs a branch, creating worktrees for isolation, making atomic commits during development, or completing a development branch via merge, PR, preserve, or discard

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Use when working with any code, infrastructure-as-code, configuration files, dependencies, or before claiming security posture is adequate — covers OWASP Top 10, secrets detection, dependency vulnerabilities, IaC security, Docker hardening, and supply chain risks

Surface what needs human attention during complex AI work. Use when context is large, user seems overwhelmed, or after substantial output. Triggers on "what just happened", "summarize progress", "what do I need to know", "lost track", "overwhelmed".

Human-in-the-loop code review with chunk-by-chunk approve/reject/chat loop (git add -p style). Use when reviewing PRs, diffs, patches, or documents interactively. Triggers on "review my PR", "walk through changes", "interactive review".

Product workflows router. Use when validating product ideas, writing specs, analyzing competitors, or tracking metrics. Triggers on "PRD", "competitive analysis", "metrics", "OKRs", "cohort", "requirements", "tech debt", "game-changing features", market positioning, retention analysis, or product strategy tasks.

Use when preparing for interviews, assessing skills, analyzing job opportunities, navigating stakeholder politics, or developing professional capabilities. Auto-activates on interview prep, career assessment, job search, skill gaps, feedback interpretation, leadership development, or professional growth tasks.

Evaluate skill quality using 8-dimension framework. Use when reviewing skills, before publishing, or auditing existing skills. Triggers on "evaluate skill", "review skill", "skill quality", "audit skills".

Expert simulation for code guidance. Use when asking "code like [expert]", "what would [expert] say", "idiomatic", "best practice", "panel", or needing domain-specific guidance.

Surface relevant learnings from past sessions. Use when starting work in a domain to avoid repeating mistakes. Triggers on "recall learnings", "past failures", "surface insights", "what did I learn".

Precision editing for prose and copy. Use when user says "edit this", "improve this", "review my writing", "use [name]'s voice", or provides draft text to refine. Triggers on editing, voice extraction, voice library, narrative structure, microcopy.

Scaffold structured documents (RFC, ADR, Blog) using industry best practices. Use when creating RFCs, ADRs, blog posts, or technical articles. Triggers on "write RFC", "create ADR", "blog post template", "scaffold document", "RFC template". Produces draft for refinement with /wordsmith:edit.

Root cause analysis for complex bugs. Use when initial fix fails, bug keeps returning, or incident is severe. Triggers on "root cause", "why does this keep happening", "trace the bug".