model-selection

Route .NET development tasks to Opus, Sonnet, or Haiku models.

1|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/Trossitec/dotnet-claude-kit --skill model-selection-trossitec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: model-selection
Source: https://github.com/Trossitec/dotnet-claude-kit/tree/main/skills/model-selection
Command: npx skills add https://github.com/Trossitec/dotnet-claude-kit --skill model-selection-trossitec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents wasted tokens and slow outputs by helping you choose the best Claude model for the complexity of your .NET work.

Core Features & Use Cases

  • Model-to-task routing: Selects Opus 4.6 for deep trade-offs, Sonnet 4.6 for high-throughput implementation, and Haiku 4.5 for fast, cheap subagent lookup-style work.
  • Workflow patterns for model switching: Uses an Opus plan → Sonnet execute → Opus review loop to improve decision quality without sacrificing speed.
  • Subagent model assignment guidance: Assigns lighter work to Haiku and reasoning-heavy work to Sonnet/Opus to reduce cost while maintaining correctness.
  • Operational triggers and shortcuts: Covers when to switch models based on user intent (e.g., asking about “model”, “Opus”, “Sonnet”, “Haiku”, “cost”, “switch model”, or “fast mode”).

Quick Start

Load the model-selection Skill and ask your AI to choose between Opus 4.6, Sonnet 4.6, and Haiku 4.5 for your next .NET task based on complexity and whether it’s planning, implementation, review, or subagent lookup.

Frequently Asked Questions about model-selection

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

FAQPage Schema
How do I choose the right Claude model for my .NET development tasks?

Choosing the right Claude model for .NET tasks requires mapping task complexity to Opus for deep trade-offs, Sonnet for high-throughput implementation, and Haiku for fast subagent lookups to optimize quality and cost.

What is the best workflow for switching between Claude Opus and Sonnet during implementation?

The best model switching workflow uses an Opus plan, Sonnet execute, and Opus review loop to improve decision quality without sacrificing speed during .NET development tasks.

When should I use Claude Haiku instead of Sonnet for subagent routing?

Use Claude Haiku for subagent routing when assigning lighter lookup-style work to reduce cost, and reserve reasoning-heavy work for Sonnet or Opus to maintain correctness.

Can I optimize Claude API costs by routing tasks to different models?

You can optimize Claude API costs by assigning routine .NET work to Haiku, high-throughput implementation to Sonnet, and complex architecture decisions to Opus based on task complexity.

Does the model selection approach work for both planning and debugging .NET applications?

Model selection applies to planning, implementation, debugging, and architecture decisions in .NET, selecting Opus for deep trade-offs and Sonnet or Haiku based on the specific task complexity.