raccioly

API contract validator that ensures API responses match documented contracts and catches breaking changes. Activate when validating API contracts, checking schema validation, detecting contract drift, comparing OpenAPI specs with implementation, finding undocumented endpoints, or auditing response shapes.

API contract validation and Zod-first design patterns. Use when designing, implementing, or validating API routes and schemas.

API design, style selection, and contract validation. REST vs GraphQL vs tRPC decision-making, Zod-first validation, response formats, versioning, pagination, API contracts. Use when designing APIs, choosing REST vs GraphQL, implementing API validation, creating Zod schemas, or defining API contracts.

API design principles and decision-making. REST vs GraphQL vs tRPC selection, response formats, versioning, pagination.

Main application building orchestrator. Creates full-stack applications from natural language requests. Determines project type, selects tech stack, coordinates agents.

Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 12 templates for various tech stacks.

Enterprise architecture review with comprehensive codebase analysis and prioritized remediation plan. Activate when reviewing architecture, performing codebase audit, assessing architecture quality, evaluating system design, or scoring production readiness. Covers folder structure, separation of concerns, DynamoDB patterns, code quality, security, performance, testing, and documentation.

Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.

AI-driven documentation repair with structured research workflow, template-aware generation, and quality validation loops. Generates or fixes canonical documentation by researching the actual codebase, not using placeholders. Iterates until guard passes.

Run DocGuard guard validation against Canonical-Driven Development standards. Parses output, triages severity, suggests targeted fixes, and optionally chains to docguard-fix for automated remediation. Use as a quality gate before commits or after implementation phases.

Cross-document consistency analysis and quality assessment. Performs read-only analysis across all canonical docs, identifies drift, coverage gaps, and quality issues. Produces a structured report with severity-ranked findings. Modeled after speckit-analyze.

CDD maturity assessment with category-aware improvement roadmap. Runs scoring engine, analyzes category breakdown, identifies highest-impact improvements, and generates a before/after improvement plan with projected score gains.

Keep canonical documentation ALWAYS UP TO DATE. Refreshes code-truth doc sections in place (mechanical, idempotent, preserves human prose) and flags the prose sections you must review when code changes.

Perform cross-artifact consistency analysis across spec.md, plan.md, and tasks.md. Use after task generation to identify gaps, duplications, and inconsistencies before implementation.

Generate custom quality checklists for validating requirements completeness and clarity. Use to create unit tests for English that ensure spec quality before implementation.

Structured clarification workflow for underspecified requirements. Use before planning to resolve ambiguities through coverage-based questioning. Records answers in spec clarifications section.

Defensive security self-assessment of the operator's OWN Python or Node codebase. Local and read-only by default — it reads the repo, runs static scanners, and writes a briefing; no live system is touched. Active probes are opt-in, run only against a TEST instance the human owns and supplies, and require explicit per-run human approval; production and third-party targets are out of scope. Use when the user wants to security-review their own app, harden it, check for BOLA/IDOR/JWT/SSRF/mass-assignment issues, pentest their own code, or "see if my app is safe" before shipping.

Convert documents and URLs to clean Markdown using Microsoft MarkItDown. Use whenever you need to READ or extract content from Office and structured formats — .docx, .pptx, .xlsx/.xls, .csv, .html, .epub, .msg (Outlook email), .json, .xml, ZIP archives, or web/YouTube URLs — instead of writing ad-hoc extraction scripts. NOT for creating or editing Office files, and NOT for PDFs or images (read those natively).