Tech Stack
Documents and evaluates technology decisions. Covers language, framework, infrastructure choices, and dependency management. Use when making technology choices, evaluating new dependencies, or onboarding to the project.
Install
$ agentstack add skill-pvnarp-agent-skills-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.
About
Tech Stack Decisions
Every dependency is a liability. Every technology choice is a trade-off. Document the "why" so future-you doesn't re-debate settled decisions.
Decision Record Template
For each major technology choice:
| Area | Choice | Why | |------|--------|-----| | Language | ? | ? | | Framework | ? | ? | | Database | ? | ? | | Hosting | ? | ? | | CI/CD | ? | ? | | Monitoring | ? | ? |
Dependency Evaluation Framework
Before adding any dependency, answer:
- Does it solve a real problem? Not "might be useful someday" - is it needed NOW?
- What's the cost? Bundle size, build time, learning curve, transitive dependencies.
- Is it maintained? Last release date, open issues, bus factor.
- Can we remove it later? How deeply does it integrate? Is there an escape hatch?
- Can we do without it? Is the alternative (writing it ourselves) truly worse?
Dependency Health Checks
| Signal | Healthy | Concerning | |--------|---------|-----------| | Last release | 18 months | | Open issues | Triaged, responded to | Hundreds unacknowledged | | Contributors | Multiple active | Single maintainer inactive | | Breaking changes | Documented migration path | Frequent with no guidance | | License | Permissive (MIT, Apache) | Restrictive or ambiguous |
Anti-Patterns
- Resume-driven development: Choosing tech because it's trendy, not because it fits
- Framework churn: Rewriting in the latest framework every 18 months
- Over-engineering: Kubernetes for a single-server app, microservices for a team of 2
- Dependency sprawl: 5 different HTTP clients, 3 JSON parsers
- Ignoring the boring option: Postgres, Redis, and a monolith solve most problems
When to Reconsider
Re-evaluate tech choices when:
- The team size or skill set changes significantly
- Performance requirements change by 10x+
- The project's scope fundamentally shifts
- A dependency becomes unmaintained or insecure
- NOT because something newer exists
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: pvnarp
- Source: pvnarp/agent-skills
- 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.