using-agent-skills

Discovers and routes tasks to the right .NET engineering skill by development phase.

7|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/peterblazejewicz/claude-plugins --skill using-agent-skills-peterblazejewicz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: using-agent-skills
Source: https://github.com/peterblazejewicz/claude-plugins/tree/main/plugins/dotnet-skills/skills/using-agent-skills
Command: npx skills add https://github.com/peterblazejewicz/claude-plugins --skill using-agent-skills-peterblazejewicz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working on .NET projects, it is hard to know which of the 23 available engineering workflow skills applies to your current task. This meta-skill maps any task to the correct skill across the Define, Plan, Build, Verify, Review, and Ship phases, so you never start work without the right process guidance. ## Core Features & Use Cases - Phase-Based Discovery Tree: Routes tasks like spec writing, Avalonia UI work, integration testing, or performance tuning to the matching skill such as spec-driven-development or integration-testing-dotnet. - Core Operating Behaviors: Enforces six cross-cutting rules including surfacing assumptions, managing confusion, pushing back on bad approaches, and verifying with dotnet test and dotnet build. - Lifecycle Sequences: Provides ready-made skill chains for common scenarios like bug fixes, performance hotfixes, and schema migrations. - Use Case: You start a session unsure how to add a feature to an Avalonia app. This skill directs you through spec-driven-development, incremental-implementation, frontend-ui-engineering-avalonia, and test-driven-development in the right order. ## Quick Start Ask the assistant which dotnet-skills workflow applies to your current .NET task, or run /dotnet-skills to list all skills grouped by phase.

Frequently Asked Questions about using-agent-skills

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find the right .NET skill for my task?

Describe your task in natural language and Claude Code matches it against each skill's keyword-dense description, or run /dotnet-skills to list all skills grouped by phase. The discovery tree in this meta-skill also maps task types like testing, debugging, or shipping to specific skills.

What skills are available in the dotnet-skills plugin?

The plugin contains 23 skills organized by phase: Define (interview-me, idea-refine, spec-driven-development), Plan, Build (incremental-implementation, frontend-ui-engineering-avalonia, and others), Verify (test-driven-development, integration-testing-dotnet), Review, and Ship (ci-cd-and-automation, shipping-and-launch).

Does this work with Avalonia 11 and Avalonia 12 projects?

Yes. Version-aware skills like frontend-ui-engineering-avalonia read Directory.Packages.props or .csproj files to detect the Avalonia version before applying patterns. Structural Avalonia reviews are delegated to the companion avalonia-dev plugin's /avalonia-review command.

When should I use a lifecycle sequence instead of a single skill?

Use a sequence for multi-stage work like a full feature, which chains spec-driven-development through shipping-and-launch. Simple tasks need fewer skills: a bug fix only requires debugging-and-error-recovery, test-driven-development, and code-review-and-quality.

What verification does each skill require before completion?

Every skill requires evidence such as dotnet test passing with visible counts, dotnet build -warnaserror clean, dotnet format --verify-no-changes clean, and before/after numbers for performance work. Visual features need headless Avalonia tests or Playwright assertions.