
TypeScript strict patterns and best practices. Trigger: When writing TypeScript code - types, interfaces, generics.
Git commit standards, conventions, and commit message formatting
Angular core patterns: standalone components, signals, inject, control flow, zoneless. Trigger: When creating Angular components, using signals, or setting up zoneless.
Yoizen UI design system guidelines and resources. Trigger: When working on Yoizen UI components, styling, colors, typography, or icons.
Azure DevOps YAML pipelines and Helm Umbrella chart conventions for multi-service projects. Concrete actions: create multi-stage pipeline YAML for Docker build/push to ACR, generate Umbrella Helm charts with sub-charts, configure values.yaml environment contracts, set up tag-triggered versioning strategy. Trigger: When the user asks to create or modify Azure DevOps pipelines, generate or maintain Helm Umbrella charts, configure values.yaml service nodes, set up Docker-to-ACR image tagging, or scaffold the DevOps directory for a new project.
.NET 9 / ASP.NET Core patterns with Minimal APIs, Clean Architecture, and EF Core. Trigger: When writing C# code, .NET APIs, or Entity Framework models.
Angular architecture: Scope Rule, project structure, file naming, style guide. Trigger: When structuring Angular projects or deciding where to place components.
Implement tasks from the change, writing actual code following the specs and design. Trigger: "apply", "implement", "implementar", "code it", "build it", "sdd apply", "ejecutar tareas", "/sdd:apply".
name: skill-sync description: > Sync skill metadata with the Auto-invoke sections in AGENTS.md. Trigger: When you change a skill's metadata (metadata.scope/metadata.auto_invoke), regenerate the Auto-invoke tables, or run ./skills/skill-sync/assets/sync.sh. metadata: author: Yoizen version: "1.0" scope: [root] auto_invoke: - "skill operations" - "workflow" - "sdd" author: Yoizen version: "1.0" scope: [root] auto_invoke: - "skill operations" - "workflow"
--- name: skill-creator description: > Creates new AI agent skills following the Agent Skills spec. Trigger: When user asks to create a new skill, add agent instructions, or document patterns for AI. license: Apache-2.0 metadata: author: Yoizen version: "1.0" scope: [root] auto_invoke: - "skill operations" - "workflow" - "sdd" author: Yoizen version: "1.0" scope: [root] auto_invoke: - "skill operations" - "workflow" - "sdd" version: "1.0" allowed-
Validate that implementation matches specs, design, and tasks. Trigger: "verify", "verificar", "validate", "check implementation", "quality gate", "sdd verify", "revisar cambio", "/sdd:verify".
Break down a change into an implementation task checklist. Trigger: "tasks", "breakdown", "task list", "desglosar", "tareas", "sdd tasks", "plan de implementación", "/sdd:continue (when design exists but tasks don't)".
Write specifications with requirements and scenarios (delta specs for changes). Trigger: "spec", "requerimientos", "requirements", "especificaciones", "write specs", "sdd spec", "acceptance criteria", "/sdd:continue (when proposal exists but specs don't)".
Create a change proposal with intent, scope, and approach. Trigger: "propose", "propuesta", "proposal", "new change", "nuevo cambio", "sdd new", "sdd propose", "/sdd:new", "sdd:ff", "fast-forward", "fast forward". When triggered by "sdd:ff" or "fast-forward": after creating the proposal, AUTOMATICALLY continue by executing sdd-spec, sdd-design, and sdd-tasks in sequence (do NOT stop after the proposal).
Bootstrap the SDD structure in any project. Detects stack, conventions, and initializes the active persistence backend. Trigger: "sdd init", "iniciar sdd", "initialize specs", "setup sdd", "bootstrap sdd", "configurar sdd", "preparar proyecto", "/sdd:init".
Create technical design document with architecture decisions and approach. Trigger: "design", "diseño técnico", "technical design", "architecture", "diseñar", "sdd design", "/sdd:continue (when specs exist but design doesn't)".
Evaluate implementation options before coding changes. Creates comparison matrices, pros/cons analysis, risk assessment, and a recommended approach for architecture, feature planning, refactors, and debugging strategy decisions. Use when the user wants to compare multiple approaches before implementation. Trigger: "explore", "investigar", "think through", "analizar", "research", "sdd explore", "evaluar opciones", "/sdd:explore".
React 19 patterns with React Compiler. Trigger: When writing React components - no useMemo/useCallback needed.
Angular performance: NgOptimizedImage, @defer, lazy loading, SSR. Trigger: When optimizing Angular app performance, images, or lazy loading.
Sync delta specs to main specs and archive a completed change. Trigger: "archive", "archivar", "close change", "cerrar cambio", "sdd archive", "finalizar", "merge specs", "/sdd:archive".
Linting, formatting, and code quality using Biome
Use when writing Playwright tests, fixing flaky tests, debugging failures, implementing Page Object Model, configuring CI/CD, optimizing performance, mocking APIs, handling authentication or OAuth, testing accessibility (axe-core), file uploads/downloads, date/time mocking, WebSockets, geolocation, permissions, multi-tab/popup flows, mobile/responsive layouts, touch gestures, GraphQL, error handling, offline mode, multi-user collaboration, third-party services (payments, email verification), console error monitoring, global setup/teardown, test annotations (skip, fixme, slow), test tags (@smoke, @fast, @critical, filtering with --grep), project dependencies, security testing (XSS, CSRF, auth), performance budgets (Web Vitals, Lighthouse), iframes, component testing, canvas/WebGL, service workers/PWA, test coverage, i18n/localization, Electron apps, or browser extension testing. Covers E2E, component, API, visual, accessibility, security, Electron, and extension testing.
Angular forms: Signal Forms (experimental) and Reactive Forms. Trigger: When working with forms, validation, or form state in Angular.
Tailwind CSS 4 patterns and best practices. Trigger: When styling with Tailwind - cn(), theme variables, no var() in className.