windsurf-skills

Use when creating application icons for Windows apps, from initial SVG design through to final ICO file

Use when improving code structure, applying design patterns, ensuring backward compatibility, or making incremental changes without altering behavior

Use when planning work items, managing backlogs, creating epics/features/stories/tasks, or organizing development work in Agile/SCRUM methodology

Use when implementing any feature or bugfix, before writing implementation code

Use when designing application structure, implementing layered architecture, applying DDD patterns, or making architectural decisions about separation of concerns

Use when building, designing, or coding Azure Logic Apps Consumption workflows - covers architecture patterns, Code View JSON conventions, error handling, performance optimization, security, naming conventions, and deployment best practices

Use when updating version numbers in SharePoint Framework (SPFx) solutions after features or bugfixes

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

Use when upgrading .NET Framework (3.5, 4.x) to modern .NET (6, 8, 9, 10), migrating between .NET versions, encountering compatibility issues during upgrades, or planning .NET modernization projects

Use when building UI that needs systematic design decisions, accessibility compliance, UX best practices, or pre-delivery quality checks - complements designing-frontends for production-grade interfaces

Use when writing React/Next.js code, reviewing for performance issues, optimizing bundle size, implementing data fetching, or refactoring existing React components

Use when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing.

Use when building React or Blazor applications that need Microsoft Fluent 2 design system components, enterprise UI consistency, or accessibility-first interfaces

Use when you need current, accurate information from the web - verifying claims, researching unfamiliar topics, looking up error codes, or when LLM training data may be outdated or insufficient. Selects appropriate Perplexity tool based on depth needed.

Use when facing a significant decision with multiple viable paths - choosing between approaches, architectures, tools, or solutions. Applies the 1-3-1 method for structured decision-making.

Use when building web components, pages, or applications that need distinctive, production-grade design with high aesthetic quality and creative direction

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Use when you have a written implementation plan to execute with review checkpoints

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

Use when starting any conversation - establishes how to find and use skills before ANY response including clarifying questions

Use when you have a spec or requirements for a multi-step task, before touching code

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