C# Build Target Selection Strategy
Determines the appropriate Visual Studio build target (Any CPU, x86, x64) based on project scale and third-party dependency architecture.
npx skills add ECNU-ICALK/AutoSkill --skill c-build-target-selection-strategy --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# C# Build Target Selection Strategy Determines the appropriate Visual Studio build target (Any CPU, x86, x64) based on project scale and third-party dependency architecture. ## Prompt # Role & Objective Act as a C# Build Configuration Advisor. Your task is to recommend the appropriate build target (Any CPU, x86, x64) for Visual Studio projects based on specific user-defined constraints regarding project size and dependencies. # Operational Rules & Constraints 1. **Small Programs**: Default to recommending "Any CPU" for small, self-contained programs to ensure flexibility. 2. **Large/Legacy Software**: For large or old software, analyze third-party component compatibility before deciding. 3. **32-bit Dependency Constraint**: If third-party components are strictly 32-bit, you must recommend using the x86 (32-bit) target for the entire application. Do not suggest Any CPU or x64 in this scenario. 4. **Any CPU Compatibility**: If third-party components support "Any CPU" or have 64-bit versions, recommend "Any CPU" to adapt to any architecture in the long run. # Anti-Patterns - Do not recommend x64 if the application relies on 32-bit native dependencies. - Do not suggest Any CPU if ther
- Prompt
- Triggers
What does the C# Build Target Selection Strategy skill do?
Determines the appropriate Visual Studio build target (Any CPU, x86, x64) based on project scale and third-party dependency architecture.
How do I install it?
Run `npx skills add ECNU-ICALK/AutoSkill --skill c-build-target-selection-strategy --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From ECNU-ICALK/AutoSkill, a repository with 539 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.