Installs into .claude/skills of the current project.
Are you the author of Technology Stack Selection?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/machenjie-technology-stack-selection)
---
name: technology-stack-selection
description: "Use when a framework, platform, infrastructure, or managed service creates a commitment; skip package, runtime, or fixed-stack work."
---
# technology-stack-selection
## Registry Trigger
**Use when**
- A framework, platform, datastore, infrastructure, or managed-service commitment is open.
**Do not use when**
- Language, package, build, or configuration choice is primary.
- Policy fixes the stack and no commitment or migration changes.
## Skill Role
Own stack compatibility, operation, lifecycle, cost, migration, and exit.
## High-Value Rules
- Screen hard constraints before comparing preferences.
- Bind the commitment to current ownership, lifecycle, transition, exit, and proof evidence.
- Load the benchmark when a material stack choice remains open.
## Anti-Patterns
- Local success is not stack-selection evidence.
## Stop Conditions
- Return adjacent mechanics to their owners.
## Output Contract
- technology-stack decision with hard-constraint fit existing-stack comparison ownership lifecycle supply chain total-change cost migration coexistence exit proof limits and residual risk
## Targeted References
| Path | Type | Load when | Do not load when | Required by | Required output |
|---|---|---|---|---|---|
| [benchmarks and patterns](references/benchmarks-and-patterns.md) | benchmark-pattern | Competing technology-stack commitments require compatibility ownership supply-chain migration cost or exit comparison | Current architecture and policy fix the technology stack and no new commitment or migration is proposed | analysis-agent, task-agent, review-agent | option-comparison, selected-approach |
