# Pc Tech Selection

> Use when the architecture is known and the team must choose concrete languages, frameworks, data stores, or infrastructure tools with explicit trade-offs instead of letting implementation drift into ad hoc stack decisions.

- Skill: `yknothing/pc-tech-selection` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add yknothing/pc-tech-selection`
- Raw SKILL.md: https://api.skillmd.com/api/skills/yknothing/pc-tech-selection/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: yknothing (https://skillmd.com/u/yknothing)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/yknothing/pc-tech-selection

---


# Tech Selection

> Choose technologies by architectural fit and operational consequence, not by habit or trend.

## Context

Tech selection turns a structural design into a concrete stack.

See [context](references/context.md) and [anti-pattern](references/anti-patterns.md) notes.

## Inputs

[I/O contract notes](references/io-contract.md) define required inputs and authority.

## Process

### Step 1: Define the Decision Surface

List the categories that actually require a choice now:

- language or runtime
- framework or service platform
- datastore or messaging substrate
- infrastructure or deployment platform
- supporting tools that materially affect delivery or operations

Do not pretend every category is open if upstream constraints already settled it.

### Step 2: Compare Against Real Drivers

Evaluate each meaningful option against:

- architecture fit
- team skill and hiring reality
- operational burden
- security and compliance posture
- migration or lock-in cost
- ecosystem maturity and upgrade path

Use a small decision matrix when useful, but prefer clear narrative reasoning over spreadsheet theater.

### Step 3: Choose the Minimum Stack That Works

Favor the simplest stack that satisfies the drivers. Extra tools add integration cost, cognitive load, and future upgrade work. "Because it is popular" is not a valid criterion.

### Step 4: Record Consequences and Triggers

Document why the option won, what trade-offs were accepted, and what future condition would justify revisiting the decision.

## Outputs

Produce only declared outputs at their documented quality boundary.

## Quality Gate

- [ ] All material stack choices are explicit
- [ ] Each choice is justified against architecture drivers
- [ ] Team capability and operational cost were considered
- [ ] Rejected alternatives and trade-offs are recorded
- [ ] Revisit triggers are documented for high-consequence choices

## Distribution

- Public install surface: `skills/.curated`
- Canonical authoring source: `skills/02-architecture/pc-tech-selection/SKILL.md`
- This package is exported for `npx skills add/update` compatibility.
- Packaging stability: `beta`
- Capability readiness: `beta`
- Portability: `portable_with_caveat`
- Public caveat: Portable as skill guidance; full governance guarantees require the Prodcraft repository contracts and validation checks.