J03Fr0st

Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

Create instruction files for GitHub Copilot, coding guidelines, auto-applied rules, editor standards, workspace conventions. Use whenever the user mentions .instructions.md, copilot rules, coding guidelines, auto-applied context, workspace coding standards, or per-file-type conventions.

Create reusable prompt files for GitHub Copilot, custom slash commands, chat templates, prompt templates. Use whenever the user mentions .prompt.md, slash commands, custom commands, reusable prompts, chat templates, or Copilot prompt files.

Use when working with Azure DevOps from the command line. Covers managing PRs, pipelines, work items, repos, and variable groups via `az devops` CLI. Make sure to use this skill whenever the user mentions "az devops", "Azure DevOps", "ADO pipeline", "create PR in DevOps", "work item", or "variable group", even if they don't explicitly ask for it.

Use when reviewing PRs, doing self-review before submission, training new reviewers, or establishing review standards. Make sure to use this skill whenever the user mentions "review my code", "check this PR", "code quality", "review standards", "PR feedback", or "code review", even if they don't explicitly ask for it.

Refine code for clarity, consistency, and maintainability without changing behavior. Use this skill whenever the user says "simplify", "clean up this code", "reduce complexity", "code smell", "make this more readable", "refactor for clarity", "tidy up", or "this code is messy". Also activate after completing a coding task, fixing a bug, or finishing an implementation when the resulting code could be clearer. Make sure to use this skill whenever the user mentions simplifying, cleaning up, or improving code readability, even if they don't explicitly ask for it.

Build distinctive, production-grade frontend interfaces with exceptional aesthetic quality. Use this skill whenever the user says "make it look good", "UI design", "CSS styling", "visual polish", "responsive layout", "build a landing page", "create a component", "style this", "beautify", "make it pretty", or "design a page". Make sure to use this skill whenever the user mentions building web UI, styling components, or creating visually polished interfaces, even if they don't explicitly ask for design guidance.

Use before creative or behavior-changing work. Clarifies intent, explores options, writes a design file for approval, then stops before plan-feature.

Create a structured feature specification with design context and self-contained task files organized into parallel execution waves. Use this skill after brainstorming has produced an approved docs/design/YYYY-MM-DD-{feature-name}/design.md, or when the user provides an existing approved design.md and asks to turn it into actionable task waves. This skill produces local spec files under docs/specs/YYYY-MM-DD-{feature-name}/ using the same dated folder name as the design — no GitHub integration.

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when the user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

Use when a plan needs to be stress-tested against project language, CONTEXT.md, ADRs, existing code, or documented domain decisions before design approval or task planning.

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Use when creating new skills, editing existing skills, or verifying skills work before deployment

Orchestrate parallel implementation of a feature specification by dispatching coder agents wave-by-wave with spec-compliance and code-quality review gates between waves. Use this skill when the user says "implement this feature", "start implementing", "run the spec", "execute the plan", "continue implementing", or wants to begin coding a previously planned feature from a docs/specs/YYYY-MM-DD-{feature-name}/ folder. Also use when the user says "/build-feature" or drags a spec folder into the conversation and asks to implement it. This skill does NOT write code itself - it orchestrates coder subagents that work in parallel.