Explorar skills

Use when verifying that a cross-service change was applied correctly. Checks for stale references, contract mismatches, uncommitted changes, and broken imports across all services.

Generates a professional, comprehensive README.md for any project from its codebase or description.

Guide für lange, autonome Entwicklungsaufgaben mit Claude Code. Optimierte Patterns für Multi-Session-Tasks, Sub-Agents, Parallelisierung und Loop-Closing.

Builds a structured troubleshooting guide with symptom → cause → fix format for any tool or system.

Reviews UI code and components for WCAG 2.1 accessibility violations and provides specific fixes.

Use when the user wants a thorough audit of the existing test suite — aggressively cutting tests that exist just to exist, rewriting weak ones to actually catch the bugs they should, identifying production code that is uncovered or thinly covered, and adding tests where coverage would catch real defects. Trigger on "audit tests", "find test bloat", "tests don't catch anything", or similar requests

Use when the user wants to set up Claude Code for a project, initialize optimization, or generate CLAUDE.md.

Converts a list of completed tickets or commits into a clear sprint summary for stakeholders.

Aggregate SAST, SCA, DAST, secrets, API, frontend, and backend security checks into one report.

Use when reviewing a user-facing page or flow for usability issues, confusion, friction, or missed UX principles.

Use when an e-commerce business sells across multiple channels (own shop, Amazon, OTTO, eBay, Etsy, Zalando, etc.) and wants to know which channel is actually profitable vs which is bleeding money — e.g. "which channel makes money?", "is OTTO/Amazon worth it?", "channel break-even calculation", "marketplace profitability", "Kanal-Ökonomie", "soll ich den Channel zumachen?". Also triggers when ad b

Validates the structural correctness of Claude Code plugins — plugin.json manifest fields, SKILL.md YAML frontmatter, reference cross-references, skill name-to-directory consistency, and plugin structure conventions. Use when checking whether a plugin is well-formed before shipping, when debugging "plugin won't load" errors, when setting up CI for a plugin repo, or when reviewing a third-party plu