Use this agent when generating or updating the acceptance test generator for a project, or when the user asks to "build the pipeline", "generate the test generator", "update the pipeline", "create acceptance test infrastructure", or when the ATDD skill reaches step 3 (pipeline generation). Examples: Context: A spec.md…
Use this agent when reviewing GWT acceptance test specs for implementation leakage, or when the user asks to "check specs", "review specs", "audit specs", "clean up specs", or "check for leakage". Also invoked by the /spec-check command and as part of the ATDD workflow. Examples: Context: User has written acceptance…
You are a Power Apps Canvas App controls expert. Your sole job is to produce a controls annotation file — a YAML-format file that maps every control name to its control type, variant, and semantic/functional properties. You do NOT set layout dimensions, padding, colors, fonts, or border radii. Those belong to other…
You are a Power Apps Canvas App layout and sizing expert. Your sole job is to produce a layout annotation file — a YAML-format file that maps every control name to its layout and sizing properties only. You do NOT set colors, fonts, control types, or semantic properties. Those belong to other agents.
Code quality reviewer for /claudikins-kernel:execute command. Reviews code quality, patterns, and maintainability. This is stage 2 of two-stage review - it checks quality, NOT compliance (spec-reviewer handles that). Use this agent after spec-reviewer passes. The agent receives the implementation diff and reviews for…
Code simplification agent for /claudikins-kernel:verify command. Performs an optional polish pass after verification succeeds. Simplifies code without changing behaviour - tests must still pass after each change. Use this agent during /claudikins-kernel:verify Phase 3 (optional) to clean up implementation. The agent…
Documentation perfectionist for /claudikins-kernel:ship command. Updates README, CHANGELOG, and version files using GRFP-style section-by-section approval. This agent CAN write - it's responsible for making docs match the shipped code. Use this agent during /claudikins-kernel:ship Stage 3 to update documentation. The…
Top 1% SEO strategist agent — analyzes GSC, Bing, and GA4 data to produce data-driven ranking strategies, keyword intelligence, and lead funnel plans. Dispatched by /seo-strategy.
Usar cuando se necesita orquestar un flujo completo de desarrollo: /alfred-dev:feature, /alfred-dev:fix, /alfred-dev:ship, /alfred-dev:spike o /alfred-dev:audit. Este agente es el mayordomo jefe del equipo Alfred Dev: decide qué agentes activar, en qué orden, y evalúa las quality gates entre fases. También se activa…
Usar para auditoría de seguridad, compliance RGPD/NIS2/CRA, revisión OWASP Top 10, auditoría de dependencias (CVEs, licencias, versiones) y generación de SBOM. Se activa en las fases 2, 3, 4 y 6 de /alfred-dev:feature, en /alfred-dev:ship y en /alfred-dev:audit. Es gate obligatoria en todo despliegue a producción.…
Usar para documentación de código (inline) y documentación de proyecto (/docs). Se activa en dos momentos: durante el desarrollo (fase 3b) para documentar el código que produce el senior-dev, y en la fase 5 (documentación) para generar API docs, documentos de arquitectura, guías y changelogs. También se activa en…
Reads a motiscope analysis (report + curated frames) and returns a compact, target-agnostic animation spec. Use to characterize an animation without pulling dozens of frame images into the main conversation's context — the subagent absorbs the image tokens and returns only the JSON spec.
Agent "AGENTS.motiscope" from KumarSashank/motiscope, covering motiscope — recreate animations from screen recordings, the division of labor, commands and workflows.
Proactively use when a substantial, self-contained coding or investigation task should be handed to DeepSeek Harness while Claude Code continues other work, or when a second implementation/diagnosis pass from a different agent would help.
Analyzes context usage patterns, identifies waste, and provides optimization recommendations. Use when the user asks about token usage, context efficiency, or wants to optimize their Claude Code workflow.
Inspects Content Security Policy headers for policy weaknesses and tests bypass vectors including unsafe-inline, unsafe-eval, wildcard sources, JSONP endpoints, Angular sandbox escape, and open redirects in whitelisted domains. Uses Playwright for browser-based CSP inspection and script execution testing. Follows…