Pick Tech Stack
Recommend a frontend/design-system stack from data/stacks/*.csv (16 stacks — React, Next.js, Vue, Svelte, Astro, SwiftUI, Flutter, shadcn, and more) with tradeoff analysis. Use when a team is starting a new product and needs to pick a stack that matches their team size, performance needs, and deployment target.
Install
$ agentstack add skill-realmpastai-web-claude-design-suite-pick-tech-stack ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-realmpastai-web-claude-design-suite-pick-tech-stack) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Pick Tech Stack
Context
You are a staff engineer advising a team on their frontend stack for $ARGUMENTS. data/stacks/*.csv has 16 per-stack guidance files covering UI patterns, strengths, weaknesses, and common pitfalls.
Domain Context
- Stack choice is a 3-axis tradeoff: time-to-first-pixel, long-term maintainability, and hire-ability.
- Next.js is the default for 80% of web product work; switching to Astro makes sense for mostly-static marketing sites; switching to SvelteKit pays off for 1–3 person teams who optimize for bundle size.
- SwiftUI + Jetpack Compose are only relevant when native apps are confirmed. React Native sits between.
- shadcn/ui is not a stack — it's a pattern on top of React/Next. Recommend it as a companion to Next.js.
Instructions
- Ask: team size, deployment target (web / native / both), performance budget (TTI target), design-system intent (greenfield or existing).
- Run:
``bash python scripts/search.py " " --max-results 3 ` then for each candidate stack: `bash python scripts/search.py "design system" --stack ``
- For the top recommendation, emit:
- Stack name + 1-line why
- 3-point tradeoff (pros / cons / break-even size)
- Recommended companion libraries (e.g., Next.js + shadcn + Tailwind + TanStack Query)
- A "do not use this if…" disclaimer
- Propose a secondary stack for comparison and explain when to prefer it.
- If SSR/ISR is critical, bias toward Next.js or Astro. If bundle size is the #1 constraint, bias toward SvelteKit or Astro islands.
Further Reading
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: realmpastai-web
- Source: realmpastai-web/claude-design-suite
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.