
Build admin dashboard interfaces with data tables, filters, charts, CRUD operations, real-time data updates, RBAC, auditability, and operational UI states. Covers layout patterns, data contracts, state management, and safety gates. [EXPLICIT] Trigger: "admin panel", "dashboard", "data table", "CRUD interface", "back-office", "RBAC dashboard", "admin console"
LLM-assisted code review patterns, automated suggestion generation. [EXPLICIT] Trigger: "ai code review"
Alert fatigue prevention, escalation rules, severity classification. [EXPLICIT] Trigger: "alerting strategy"
Comprehensive testing strategy for AI systems — testing scope matrix (6 types x 6 layers), model prediction testing, data quality testing, compliance and fairness testing, integration approaches, and CI/CD test automation. This skill should be used when the user asks to "define AI testing strategy", "test ML models", "design data quality tests", "plan fairness testing", "test AI pipelines", "design integration tests for ML", or mentions adversarial testing, drift simulation, model regression testing, bias testing, explainability testing, or AI test automation. [EXPLICIT]
This skill should be used when the user asks to "design analytics models", "set up a dbt project", "plan data transformations", "define data contracts", or "model a star schema", or mentions staging models, marts, incremental strategies, or materializations. It produces analytics pipeline designs with dbt-style transformations, data modeling patterns, testing strategies, and documentation plans. [EXPLICIT] Use this skill whenever the user needs source-to-target mapping, materialization decisions, or transformation framework architecture, even if they don't explicitly ask for "analytics engineering". [EXPLICIT]
Plan, execute, and report web accessibility tests with axe-core, Playwright/Jest evidence, keyboard scripts, screen reader smoke checks, color contrast validation, and explicit WCAG target scope. [EXPLICIT] Trigger: "accessibility test", "a11y test", "WCAG test", "screen reader", "axe-core", "keyboard accessibility"
LLM-in-the-loop workflows, human-AI handoff, approval gates. [EXPLICIT] Trigger: "ai workflow automation"
Designs and implements WCAG 2.1 AA accessibility patterns for web applications using native HTML first, targeted ARIA only when needed, keyboard interaction maps, focus management, screen reader semantics, contrast tokens, accessible forms, reduced motion, and inclusive interaction requirements. [EXPLICIT] Trigger: "accessibility", "WCAG", "ARIA", "a11y", "screen reader", "inclusive design"
Automatic agent and skill selection based on user request analysis. Use when: routing, which agent, find skill, search capability, match request.
Content filters, output guardrails, jailbreak prevention, safety evaluation. [EXPLICIT] Trigger: "ai safety"
--- name: agent-constitution-creator version: 1.0.0 description: [EXPLICIT] This skill should be used when the user asks to "create an agent constitution", [EXPLICIT] "define agent identity", "write agent.md", "generate agent spec", or "design [EXPLICIT] agent governance". Generates constitutional agent.md documents with 22 mandatory [EXPLICIT] fields covering identity, authority, governance, and quality for multi-agent [EXPLICIT] ecosystems. Use this skill whenever someone is buildin
--- name: agent-creator version: 1.0.0 description: [EXPLICIT] This skill should be used when the user asks to "create an agent", [EXPLICIT] "add a subagent", "make a custom agent", "define agent definition", [EXPLICIT] or "build an agent for X". Creates Claude Code custom agent definitions [EXPLICIT] with system prompts, tool restrictions, model selection, and reasoning [EXPLICIT] discipline. Use this skill whenever someone needs a new autonomous [EXPLICIT] subprocess for their pro
AI-generated test cases, fuzzing, mutation testing, coverage optimization. [EXPLICIT] Trigger: "ai assisted testing"
AI-generated content detection, watermarking, human-AI hybrid strategies. [EXPLICIT] Trigger: "ai content detection"
AI pipeline architecture design — development pipelines, production pipelines, data stores, model registry, CI/CD for AI, and non-functional requirements. This skill should be used when the user asks to "design AI pipelines", "architect ML pipelines", "select data stores for AI", "design model registry", "implement CI/CD for ML", "define AI pipeline requirements", or mentions MLOps, training pipeline, inference pipeline, feature pipeline, Blue and Gold deployment, or pipeline patterns. [EXPLICIT]
Audits existing AI system architectures against best practices — structural integrity, AI quality attributes, pattern adherence, anti-pattern detection, security compliance, and technical debt inventory. This skill should be used when the user asks to "audit AI architecture", "review ML system quality", "assess AI technical debt", "evaluate AI compliance", "detect AI anti-patterns", "review AI security posture", or mentions AI architecture review, AI system assessment, AI quality audit, drift monitoring audit, or AI governance review. [EXPLICIT]
Guides implementation of AI system architectures — technology selection, pipeline implementation, model serving setup, monitoring deployment, and CI/CD automation. This skill should be used when the user asks to "implement AI architecture", "build ML pipeline", "set up model serving", "deploy AI system", "implement MLOps", "configure drift monitoring", "set up feature store", or mentions AI implementation plan, ML infrastructure setup, model deployment guide, RAG implementation, or agent framework setup. [EXPLICIT]
Auto-generated docs from code, README generation, API doc automation. [EXPLICIT] Trigger: "ai documentation"
Concept of Operations (CONOPS) for AI systems — system vision, stakeholder mapping, AI-human interaction spectrum, business value assessment, success metrics, and operational modes. This skill should be used when the user asks to "define the AI operational concept", "map AI stakeholders", "design AI-human interaction levels", "assess AI business value", "define AI success metrics", "plan AI operational modes", or mentions CONOPS, IEEE 1362, AI autonomy levels, AI value matrix, or AI system vision. [EXPLICIT]
AI-specific design patterns and system tactics — Feature Store, Champion-Challenger, Shadow Deployment, Drift Detection, Explainability Wrapper, Canary Deployment, Bulkhead, and traditional patterns adapted for AI. This skill should be used when the user asks to "select AI design patterns", "apply ML patterns", "design drift detection", "implement feature store", "plan shadow deployment", "design champion-challenger", "select availability tactics for AI", or mentions AI anti-patterns, maintainability tactics, fault recovery for models, or pattern selection for ML systems. [EXPLICIT]
Generates formal meeting records (actas) with legal/corporate format, numbered sections, signatures block, and branded HTML output. [EXPLICIT] Trigger: "acta formal", "formal minutes", "acta corporativa", "acta de junta", "acta de consejo", "acta con firmas", "quorum"
AI software architecture design — modules, layers, boundaries, design patterns, ADRs, quality attributes, and technical debt strategy for AI-enabled systems. This skill should be used when the user asks to "design AI system structure", "define AI module boundaries", "select AI architecture patterns", "document AI architecture decisions", "evaluate AI code architecture", or mentions AI pipelines, feature stores, model serving, drift detection, ML quality attributes, explainability architecture, or AI technical debt. [EXPLICIT]
WCAG 2.1 AA automated scanning with axe-core plus manual checklist for keyboard, screen reader, and contrast
Rewrite and review content so it is accessible, understandable, inclusive, and safe to publish: alt text, plain language, reading-level estimates, descriptive links, helpful errors, non-sensory instructions, localization, and evidence-backed limits. [EXPLICIT] Trigger: "accessibility writing", "accessible copy", "alt text", "plain language", "inclusive language", "reading level", "descriptive links"
Designs and reviews A/B tests with explicit hypothesis, primary metric, guardrail metrics, variants, sample-size assumptions, duration, stopping rules, instrumentation checks, and decision criteria. [EXPLICIT] Trigger: "ab testing, a/b test, experiment design, split test, hypothesis formulation, statistical significance, sample size calculation, test duration"
Generate a technical design document from a feature spec — selects frameworks, defines data models, produces API contracts, and creates a dependency-ordered implementation strategy. Use when planning how to build a feature, writing a technical design doc, choosing libraries, defining database schemas, or setting up Tessl tiles for runtime library knowledge.
Generate quality checklists that validate requirements completeness, clarity, and consistency — produces scored checklist items linked to specific spec sections (FR-XXX, SC-XXX). Use when reviewing a spec for gaps, doing a requirements review, verifying PRD quality, auditing user stories and acceptance criteria, or gating before implementation.
Generate Gherkin .feature files from requirements before implementation — produces executable BDD scenarios with traceability tags, computes assertion integrity hashes, and locks acceptance criteria for test-driven development. Use when writing tests first, doing TDD, creating test cases from a spec, locking acceptance criteria, or setting up red-green-refactor with hash-verified assertions.
Create or update a CONSTITUTION.md that defines project governance — establishes coding standards, quality gates, TDD policy, review requirements, and non-negotiable development principles with versioned amendment tracking. Use when defining project rules, setting up coding standards, establishing quality gates, configuring TDD requirements, or creating non-negotiable development principles.
Generate dependency-ordered task breakdown from plan and specification. Use when breaking features into implementable tasks, planning sprints, or creating work items with parallel markers.
Create a feature specification from a natural language description — generates user stories with Given/When/Then scenarios, functional requirements (FR-XXX), success criteria, and a quality checklist. Use when starting a new feature, writing a PRD, defining user stories, capturing acceptance criteria, or documenting requirements for a product idea.