model-selection

Select Claude models for .NET tasks by reasoning depth and workflow complexity.

224|87|Updated Dec 15, 2018
One-click install
npx skills add https://github.com/Resgrid/Core --skill model-selection-resgrid
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: model-selection
Source: https://github.com/Resgrid/Core/tree/main/.opencode/skills/model-selection
Command: npx skills add https://github.com/Resgrid/Core --skill model-selection-resgrid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Model selection advice reduces cost and improves quality by matching the reasoning depth and throughput needed for a task with the right Claude model.

Core Features & Use Cases

  • Choose the right model by complexity: Select Sonnet for routine implementation and Haiku for fast subagent lookups, reserving Opus for architecture, trade-offs, and ambiguous decisions.
  • Run an efficient model-switch workflow: Use Opus for planning and review, then Sonnet for execution to keep both quality and speed high.
  • Assign models to subagents intelligently: Give each subagent an appropriate model based on whether it performs lookup/execution or deeper architectural/security reasoning.
  • Avoid common anti-patterns: Prevent overpaying by using Opus for simple work or using Sonnet for architecture decisions.

Quick Start

Load this skill and ask which model to use for your .NET task, including whether it is routine implementation, complex architecture, or a 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 .NET development tasks?

Model selection for .NET tasks depends on complexity: use Sonnet for routine implementation, Haiku for fast subagent lookups, and Opus for architecture trade-offs or ambiguous reasoning decisions to balance cost and quality.

What is the best way to route subagents to different Claude models?

Subagent routing assigns models based on task type: delegate to Haiku for fast, inexpensive lookups or execution, and reserve Opus for subagents handling deep architectural, security reasoning, or complex trade-offs.

Can I switch between Opus and Sonnet in a single development workflow?

Yes, an efficient model-switch workflow uses Opus for planning and architecture review, then switches to Sonnet for high-throughput execution, maintaining both quality and speed while optimizing costs.

Why does using Opus for routine software architecture tasks increase costs?

Using Opus for simple work or routine implementation causes overpaying because its deep reasoning capabilities are unnecessary; Sonnet handles high-throughput execution more cost-effectively for standard .NET tasks.

When do I need explicit model switching for debugging and architecture review?

Explicit model switching is needed when tasks vary in complexity: use Opus for ambiguous debugging or architecture trade-offs, then transition to Sonnet for execution to ensure cost-optimized routing.