Stack Recommendation
Purpose
Recommend a stack per relevant area, with justification and credible alternatives, for the selected applications only. Implements ../../system/STACK_DECISION_RULES.md. The user approves before any implementation (Gate 2).
When to Use
- After
application-selection, before architecture and implementation.
- When an existing repo needs a stack decision for a new application area.
- Not when the stack is already approved and unchanged (respect it).
Inputs
- Selected applications (
application-selection).
- Requirement baseline (constraints, scale, team familiarity).
- Audit findings for existing stacks (
existing-project-audit).
Discovery Questions
- Any mandated or pre-existing stack to align with?
- Team familiarity and ecosystem preferences?
- Expected scale, and any lock-in tolerance?
- Constraints (offline, real-time, compliance) that force a choice?
Responsibilities
- For each required area, recommend a choice with 1–3 sentence justification and note alternatives + lock-in risk.
- Decision areas: Mobile (Expo · RN CLI; nav: Expo Router · React Navigation; state: local · Context · Redux Toolkit · Zustand · server-state; API: fetch · Axios · RTK Query · TanStack Query); Web (Next.js · Vite+React); Backend (Express · NestJS · justified other); Database (PostgreSQL · MySQL · MongoDB); Data layer (Prisma · Drizzle · Mongoose · native driver, paired to the DB); Testing (Jest · Vitest · Supertest · Playwright · Maestro · RNTL).
- Produce a recommendation table: area → recommendation → justification → alternatives.
Required Workflow
- Take the selected applications.
- For each required area, evaluate options against the requirements.
- Pair database + data layer correctly.
- Build the recommendation table, then the version baseline with
technology-governance: latest stable per area, verified against the registry and official version-matched docs (not memory), compatible across the chain (../../system/TECHNOLOGY_GOVERNANCE_RULES.md). In an existing project, the installed technology is the first option for every area it covers.
- Present for Gate 2 approval; record the approved stack and baseline.
- Do not install dependencies here.
Decision Rules
- Pair, don't mis-compare: a database is storage; a data layer/ORM is access. Correct: PostgreSQL+Prisma, MySQL+Drizzle, MongoDB+Mongoose. Incorrect: "Prisma vs MongoDB."
- Relational DB → relational ORM; document DB → document ODM.
- Recommend only areas the selected apps require; keep it proportional.
- Prefer shared ecosystem across apps when it reduces cost, but never force a poor fit.
Rules
- No stack is pre-selected by the system; recommend and get approval.
- No dependency installation at this stage.
- Justify every recommendation; name alternatives considered.
Anti-Patterns
- Comparing a database against an ORM.
- Recommending a full stack for a small feature.
- Installing packages before approval.
- Silent, unjustified stack picks.
Validation Checklist
Definition of Done
An approved per-area stack recommendation table recorded in ../../projects/current/, with correct DB/data-layer pairings and no dependencies installed.
Related Skills
application-selection, architecture-design, dependency-audit, testing-strategy, project-orchestrator.
Related Knowledge
../../knowledge/ (existing architecture/constraints).
Related References
../../references/<stack-topic>/ only when an option needs grounding.
Context Loading Guidance
- Requires: selected applications, requirement constraints, existing-stack findings.
- Does not require: full source, unrelated references, implementation skills.
- May load:
dependency-audit (existing deps), one stack reference folder if needed.
- Stop when: the table is approved and recorded.
Token Efficiency Guidance
Evaluate from requirement/audit summaries. Keep justifications to a few sentences; link a reference folder rather than pasting comparisons.
1---2name: stack-recommendation3description: Use after applications are selected to recommend a technology stack per area (mobile, web, backend, database + data layer, testing) with justification and alternatives. Pairs databases with data layers correctly; never compares a database against an ORM. Requires user approval before any code.4metadata:5 source: https://skillmd.com/skills/ahtishamshahzad/stack-recommendation6---78# Stack Recommendation910## Purpose1112Recommend a stack per relevant area, with justification and credible alternatives, for the selected applications only. Implements `../../system/STACK_DECISION_RULES.md`. The user approves before any implementation (Gate 2).1314## When to Use1516- After `application-selection`, before architecture and implementation.17- When an existing repo needs a stack decision for a new application area.18- **Not** when the stack is already approved and unchanged (respect it).1920## Inputs2122- Selected applications (`application-selection`).23- Requirement baseline (constraints, scale, team familiarity).24- Audit findings for existing stacks (`existing-project-audit`).2526## Discovery Questions2728- Any mandated or pre-existing stack to align with?29- Team familiarity and ecosystem preferences?30- Expected scale, and any lock-in tolerance?31- Constraints (offline, real-time, compliance) that force a choice?3233## Responsibilities3435- For each **required** area, recommend a choice with 1–3 sentence justification and note alternatives + lock-in risk.36- Decision areas: **Mobile** (Expo · RN CLI; nav: Expo Router · React Navigation; state: local · Context · Redux Toolkit · Zustand · server-state; API: fetch · Axios · RTK Query · TanStack Query); **Web** (Next.js · Vite+React); **Backend** (Express · NestJS · justified other); **Database** (PostgreSQL · MySQL · MongoDB); **Data layer** (Prisma · Drizzle · Mongoose · native driver, paired to the DB); **Testing** (Jest · Vitest · Supertest · Playwright · Maestro · RNTL).37- Produce a **recommendation table**: area → recommendation → justification → alternatives.3839## Required Workflow40411. Take the selected applications.422. For each required area, evaluate options against the requirements.433. Pair database + data layer correctly.444. Build the recommendation table, then the **version baseline** with `technology-governance`: latest stable per area, verified against the registry and official version-matched docs (not memory), compatible across the chain (`../../system/TECHNOLOGY_GOVERNANCE_RULES.md`). In an existing project, the installed technology is the first option for every area it covers.455. Present for Gate 2 approval; record the approved stack and baseline.466. Do **not** install dependencies here.4748## Decision Rules4950- **Pair, don't mis-compare:** a database is storage; a data layer/ORM is access. Correct: PostgreSQL+Prisma, MySQL+Drizzle, MongoDB+Mongoose. Incorrect: "Prisma vs MongoDB."51- Relational DB → relational ORM; document DB → document ODM.52- Recommend only areas the selected apps require; keep it proportional.53- Prefer shared ecosystem across apps when it reduces cost, but never force a poor fit.5455## Rules5657- No stack is pre-selected by the system; recommend and get approval.58- No dependency installation at this stage.59- Justify every recommendation; name alternatives considered.6061## Anti-Patterns6263- Comparing a database against an ORM.64- Recommending a full stack for a small feature.65- Installing packages before approval.66- Silent, unjustified stack picks.6768## Validation Checklist6970- [ ] Only required areas covered.71- [ ] Each area: recommendation + justification + alternatives.72- [ ] Database paired with a matching data layer.73- [ ] No database-vs-ORM comparison.74- [ ] Presented for Gate 2; approval recorded.75- [ ] No dependencies installed.7677## Definition of Done7879An approved per-area stack recommendation table recorded in `../../projects/current/`, with correct DB/data-layer pairings and no dependencies installed.8081## Related Skills8283`application-selection`, `architecture-design`, `dependency-audit`, `testing-strategy`, `project-orchestrator`.8485## Related Knowledge8687`../../knowledge/` (existing architecture/constraints).8889## Related References9091`../../references/<stack-topic>/` only when an option needs grounding.9293## Context Loading Guidance9495- **Requires:** selected applications, requirement constraints, existing-stack findings.96- **Does not require:** full source, unrelated references, implementation skills.97- **May load:** `dependency-audit` (existing deps), one stack reference folder if needed.98- **Stop when:** the table is approved and recorded.99100## Token Efficiency Guidance101102Evaluate from requirement/audit summaries. Keep justifications to a few sentences; link a reference folder rather than pasting comparisons.