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]

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]

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]

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]

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]

This skill should be used when the user asks 'how do I parallelize this', 'which parallel primitive should I use', 'subagent vs agent teams vs workflow', 'should I use a worktree', 'run work in the background', or needs to choose between subagents, agent view, agent teams, dynamic workflows, and git worktrees. Routes to the right primitive skill; it does not re-explain each one.

This skill should be used when the user asks to 'operate Claude Code agent view', 'use claude agents', 'manage background Claude Code sessions', 'dispatch multiple Claude Code agents', 'monitor background sessions', 'peek reply attach sessions', 'troubleshoot agent view', or compare agent view with subagents, agent teams, dynamic workflows, and worktrees.

This skill should be used when the user asks to 'run Claude Code agent teams', 'orchestrate teammates', 'enable CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS', 'compare agent teams with subagents', 'assign work to Claude teammates', or 'design team lead and teammate coordination'.

Create deterministic Claude Code custom subagent definitions with supported frontmatter, description-driven delegation, bounded system prompts, least-privilege tools, permission and MCP policy, model selection, and validation checks. Use when the user asks to create an agent, add a subagent, make a custom agent, define an agent definition, or build an autonomous subprocess for a specific project responsibility. [EXPLICIT]

Use when the user asks to create an agent constitution, define persistent agent identity, write agent.md, generate an agent governance spec, or add a constitution-grade agent to a multi-agent ecosystem. Produces deterministic agent.md constitutions with 22 required fields covering identity, authority, governance, quality, validation, and version control.

WCAG 2.1/2.2 compliance assessment — a11y testing strategy, remediation priorities, inclusive design. Use when the user asks to 'audit accessibility', 'assess WCAG compliance', 'evaluate a11y', 'review inclusive design', or mentions screen readers, ARIA, color contrast, keyboard navigation. [EXPLICIT]

This skill should be used when the user asks to isolate Claude Code work with git worktrees, run Claude Code with --worktree or -w, configure .worktreeinclude, add WorktreeCreate or WorktreeRemove hooks, set worktree.baseRef, run subagents with isolation: worktree, clean up .claude/worktrees, use EnterWorktree, or avoid file conflicts between parallel sessions.

This skill should be used when the user asks to scrape a web page, crawl a site, search the web, extract structured data from URLs, or run deep web research on a topic.

Provider-agnostic web infrastructure: DNS architecture, SSL/TLS certificate lifecycle, CDN and edge optimization, backup and disaster recovery, domain lifecycle. [EXPLICIT] Cross-cuts Firebase/Vercel/Hostinger. Trigger: 'dns', 'ssl', 'tls', 'cdn', 'backup', 'disaster recovery', 'rto', 'rpo', 'domain'.

Build and deploy on Vercel: Edge and Serverless Functions, Vercel Postgres/Neon, KV, Blob storage, environment secrets, Incremental Static Regeneration, and deploy via CLI. [EXPLICIT] One of the three target platforms (Firebase + Vercel + Hostinger). Trigger: 'vercel', 'edge function', 'vercel deploy', 'vercel postgres', 'ISR', 'next on vercel'.

UX writing and document accessibility standards for technical deliverables. Use when the user asks to 'improve readability', 'fix information hierarchy', 'reduce cognitive load', 'write microcopy', 'check readability score', or mentions 'UX writing', 'scanability', 'Flesch-Kincaid', 'escritura UX', 'legibilidad', 'cognitive load'. [EXPLICIT]

Performs structured trade-off analysis using weighted scoring matrices, decision matrices, and ATAM (Architecture Tradeoff Analysis Method) to make defensible architectural and technology decisions. [EXPLICIT] Trigger: 'trade-off', 'decision matrix', 'ATAM', 'weighted scoring', 'pros and cons'

This skill should be used when the user asks to 'harden a toolkit skill', 'check a skill against the Definition of Done', 'audit packet completeness', 'validate a skill against the katas', 'bring a skill to gold-standard', or 'run the excellence gate' for the claude-native-toolkit. Enforces the packet DoD + kata best-practices + the toolkit brand + evidence honesty before a skill is declared done.

Use when designing or troubleshooting Claude Platform tool contracts: names, descriptions, input_schema, input_examples, strict, tool_choice, cache/privacy, versions, and routing boundaries.

This skill should be used for Claude Code permission rules, modes, settings, MCP permission syntax, and hooks boundaries. Do not use it as the authorization contract for Claude Platform memory, bash, text-editor, computer-use, server tools, or Messages API handlers.