Explorar skills

Execute ONE test level (L1/L2/L3/L4) from subtask verification plan. Only run tests, do not record results. Called by autoworker:dispatch with level argument. Ends by calling autoworker:checkpoint.

Update subtask with fixes or new steps. Two trigger modes: (A) Auto-called by autoworker:gate-check on FAIL — reads FAIL info, adds supplementary steps. (B) User calls with a finding/bug during testing — diagnoses, fixes, updates subtask. Both modes end by invoking autoworker:dispatch to re-enter the loop.

Sync tracking documents based on current conversation results. Updates subtask, progress, findings, task_plan, project CLAUDE.md. Use when finishing a task or reaching a milestone.

Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working w

Design and analyze A/B tests — sample sizes, significance testing, multiple comparisons, and results interpretation.

Create Vue 3 components with Composition API — composables, Pinia store integration, TypeScript, and unit tests.

Final quality gate before reporting task completion (Gate 3). Fills confidence assessment, runs supplementary verification for <95% items, completes self-check checklist. Writes PASS/FAIL result to subtask.md, then calls autoworker:dispatch for routing.

Implement ONE pending Phase from subtask plan. Only write code, do not mark checkboxes or run tests. Called by autoworker:dispatch. Ends by calling autoworker:checkpoint.

Smart code scanner that detects Spring Boot patterns and routes to appropriate skills. Use when editing Java or Kotlin files in Spring Boot projects, working with pom.xml/build.gradle containing spring-boot-starter, or when context suggests Spring Boot development. Detects annotations (@RestController, @Entity, @EnableWebSecurity, @SpringBootTest) to determine relevant skills and provides contextu

Reflective pass over your memory files — merge duplicates, fix stale facts, prune the index.

Load this skill whenever the project contains text, UI components, icons, form controls, data visualisations, or focus indicators — in short, almost every project. Under no circumstances hard-code colour values without verifying contrast ratios. Absolutely always ensure text meets 4.5:1, large text meets 3:1, and non-text UI elements meet 3:1 against adjacent colours. Test in light mode, dark mode

Complete subtask verification plan: upstream traceability table + L1-L4 test plan + self-check. Call after autoworker:subtask-init. Makes subtask ready for code implementation.