Use this skill for Python code, typing, tests, and tooling. Apply it when the task involves Python files, pytest, Ruff, mypy or pyright, packaging or environment setup, dataclasses or Pydantic, API or service boundaries, or Python application and repository logic.
Use this skill alongside the primary implementation, review, or workflow skill when the user wants code review, repo scanning, maintainability or architecture feedback, implementation planning, documentation cleanup, readable comparisons, or a clearer structured answer. Apply it when shared formatting, alignment, and response-structure rules must be enforced across touched code or documents. Do not use it as the primary owner of language, framework, runtime, or workflow decisions.
Use this skill when work needs durable planning, adaptive product slicing, discovery before delivery, resumable sprint execution, wave or initiative scaffolding, source-pack routing, closeout evidence, final audits, or repeatable product-agile workflow structure. Do not use it for small direct fixes that do not need a durable artifact, or for governance-only questions that belong to ub-governance.
Create, update, review, or refactor VS Code Copilot skills, hooks, and MCP configs. Use when the user wants to build or maintain reusable skills, lifecycle hooks, MCP integrations, or the supporting references and validation flow around those artifacts, or needs help deciding between a skill, hook, or MCP config.
Use this skill when the user wants to review governance rules, check testing posture, decide whether ADR or claim evidence is needed, evaluate repository or release controls, or understand exception and gate behavior; when the task involves governance modes, test-signal review, evidence levels, or decision-memory boundaries; or when they ask whether work needs governance escalation. Do not use it for workflow planning, framework implementation, or this repository's repo-maintenance catalog, path, and skill-integrity checks.
Use this skill when the task involves creating, reviewing, or refactoring installable skills, shared skill references, or reusable agent-authoring guidance; when the work depends on routing-quality descriptions, non-use boundaries, naming, progressive disclosure, or cross-skill authoring conventions; or when you want to normalize skill and guidance structure without turning the task into a full customization-builder workflow. Do not use it for end-to-end customization generation, normal code implementation, or general repository planning.
Use this skill for plain CSS and style-block architecture. Apply it when the task involves .css files, selectors, specificity, cascade layers, tokens, layout or theming, accessibility styling, browser-support fallbacks, or CSS architecture in Vue, Nuxt, or Tailwind-bearing projects.
Use this skill for Nuxt framework, runtime, and app-structure work. Apply it when the task involves nuxt.config.*, Nuxt modules, middleware or plugins, runtime config, Nitro or server routes, rendering or deployment mode, data fetching, route structure, app setup, or Nuxt migration.