[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74YKA5EDTSDCJ3M60GGWK42":3,"skill-same:01M74YKA5EDTSDCJ3M60GGWK42":52},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":29,"commitSha":30,"skillDirectory":31,"forksCount":32,"repositoryHtmlUrl":33,"repositoryHomepageUrl":6,"ownerHtmlUrl":34,"ownerBlogUrl":35,"ownerDescription":36,"updatedAt":37,"install":38,"resources":51},"01M74YKA5EDTSDCJ3M60GGWK42","tech-stack-eval",null,"When the user needs to choose between technologies, frameworks, or tools — or says \"which framework should I use\", \"compare X vs Y\", \"should we migrate from X to Y\", \"what database should I use\", \"calculate TCO\".","shawnpang\u002Fstartup-founder-skills","shawnpang","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F22985112?v=4","01M74YFD4GVKV76K78PEE9TNNW","Shawn Pang","01M74YFD562PQ7839XQB42P2GS",382,"MIT","https:\u002F\u002Fgithub.com\u002Fshawnpang\u002Fstartup-founder-skills\u002Fblob\u002Fmain\u002Fskills\u002Ftech-stack-eval\u002FSKILL.md",[],[],"2026-11-11 17:31:55",false,"---\nname: tech-stack-eval\ndescription: When the user needs to choose between technologies, frameworks, or tools — or says \"which framework should I use\", \"compare X vs Y\", \"should we migrate from X to Y\", \"what database should I use\", \"calculate TCO\".\nrelated: [architecture-design, cicd-setup]\nreads: [startup-context]\n---\n\n# Tech Stack Evaluation\n\n## When to Use\n\n- Comparing frontend\u002Fbackend frameworks or libraries for new projects\n- Evaluating cloud providers (AWS vs Azure vs GCP) for specific workloads\n- Planning technology migrations with risk and effort assessment\n- Calculating TCO including hidden costs; making build vs. buy decisions\n- Assessing open-source library viability and ecosystem health\n\nDo NOT use when: the decision is trivial (use team preference), the technology is already mandated, or this is an emergency production issue.\n\n## Context Required\n\nFrom `startup-context`: product type, team skills, tech stack, stage, scale, budget. Also ask:\n- What problem are you solving? (push back on solution-first thinking)\n- Non-negotiable requirements (performance, compliance, team familiarity)\n- Team experience with each option and timeline pressure (tight deadlines favor familiar tools)\n- Growth expectations that affect scalability requirements\n\n## Workflow\n\n1. **Clarify the decision** — What exactly is being decided and what are the real requirements? Push back if the user picks tech before defining the problem.\n2. **Identify candidates** — List 2-4 realistic options. Exclude clearly wrong choices early.\n3. **Define weighted evaluation criteria** — Select 6-8 criteria from the master list below. Assign weights based on the user's priorities (total = 100%).\n4. **Score each candidate** — Rate 1-5 on each criterion with one-line justification per score.\n5. **Assess ecosystem health** — Evaluate GitHub activity, npm\u002FPyPI adoption, community strength, corporate backing, and trajectory (growing, stable, declining).\n6. **Calculate TCO** — Project 5-year total cost including compute, storage, bandwidth, licensing, engineering time (setup + ongoing), and operational overhead. Engineering time is usually the largest cost for startups.\n7. **Analyze migration path** — If migrating, estimate effort, risks, timeline, and recommend phased approach (strangler fig pattern).\n8. **Deliver recommendation** — Clear winner with rationale and confidence level. No \"it depends\" without a follow-up question to resolve the ambiguity.\n\n## Output Format\n\n```markdown\n# Tech Stack Evaluation: [Decision Title]\n\n## Decision Context — what we are choosing and why it matters\n## Candidates — table: technology, version, license, one-liner\n## Evaluation Criteria — table: criterion, weight, why it matters\n## Scoring Matrix — table: criterion (weight), scores per option, weighted total\n## Ecosystem Health — table: GitHub stars, weekly downloads, last release, open issues, major users\n## TCO Estimate — table: cost category by option over 12 months or 5 years\n## Security & Compliance — vulnerability history, compliance readiness (SOC 2, GDPR)\n## Recommendation — clear winner, rationale, confidence level, caveats\n## Migration Path (if applicable) — phased plan with timeline and rollback strategy\n```\n\n## Frameworks & Best Practices\n\n### Master Evaluation Criteria\n\nSelect 6-8 and assign weights (total = 100%):\n\n- **Performance** — throughput, latency, resource efficiency for the specific workload\n- **Developer Experience** — tooling, debugging, documentation quality, error messages\n- **Learning Curve \u002F Team Familiarity** — time to productivity for the current team\n- **Ecosystem & Libraries** — packages, integrations, third-party support\n- **Maintenance & Longevity** — release cadence, corporate backing, bus factor\n- **Hiring Pool** — developer availability in your market and salary band\n- **Scalability** — handle 10-100x growth without a rewrite\n- **Cost \u002F Vendor Lock-in** — TCO and switching cost if you need to move later\n- **Security & Compliance** — vulnerability track record, compliance tooling readiness\n\n### Ecosystem Health Scoring\n\n| Level | Criteria |\n|-------|----------|\n| **Thriving** | Regular releases (\u003C 3 months), growing adoption, multiple corporate sponsors, active community |\n| **Stable** | Regular releases (\u003C 6 months), steady adoption, established community, no decline signs |\n| **At Risk** | Infrequent releases (> 12 months), declining downloads, key maintainers leaving, few contributors |\n\n### TCO Calculation Framework\n\nProject over 12 months minimum (5 years for infrastructure decisions): compute, storage, bandwidth, licensing, engineering time (setup + ongoing maintenance x loaded cost), operational overhead (monitoring, on-call), and hidden costs (training, migration tooling, dual-running).\n\n**Engineering time is usually the largest cost for startups.** A technology saving $200\u002Fmonth on hosting but costing 40 extra engineering hours to operate is a net loss.\n\n### Migration Risk Assessment\n\n| Risk Level | Criteria |\n|------------|----------|\n| **Low** | Additive change, no data migration, can run in parallel, \u003C 2 weeks |\n| **Medium** | Requires data migration or API changes, 2-8 weeks, can be phased |\n| **High** | Core system replacement, > 8 weeks, requires downtime or big-bang cutover |\n\nUse the strangler fig pattern: route new traffic to the new system, migrate old incrementally. Always maintain rollback capability. Set a concrete cut-off date -- half-migrated systems are the worst outcome.\n\n### Confidence Levels\n\n| Level | Score | Interpretation |\n|-------|-------|----------------|\n| **High** | 80-100% | Clear winner, strong data, wide margin |\n| **Medium** | 50-79% | Trade-offs present, recommendation holds but with caveats |\n| **Low** | \u003C 50% | Close call, limited data, suggest a proof-of-concept before committing |\n\n### Common Decision Anti-Patterns\n\n- **Resume-Driven Development** — choosing tech for resumes, not fit\n- **Hype Cycle Trap** — adopting at peak hype before stability is proven\n- **Premature Optimization** — distributed systems when a single Postgres handles the load\n- **Sunk Cost Fallacy** — refusing to migrate because of prior investment\n- **Ignoring Team Skills \u002F Solution-First Thinking** — picking tech nobody knows, or selecting technology before defining the problem\n\n## Related Skills\n\n- `architecture-design` — chain when the tech stack decision feeds into a broader system design\n- `cicd-setup` — chain to configure CI\u002FCD for the chosen technology\n\n## Examples\n\n**Example prompt:** \"Compare React vs Vue for a SaaS dashboard. Priorities: developer productivity (40%), ecosystem (30%), performance (30%).\"\n\n**Good output snippet:**\n```\n## Scoring Matrix\n| Criterion (weight)       | React | Vue  |\n|--------------------------|-------|------|\n| Developer Productivity (40%) | 4\u002F5   | 4\u002F5  |\n| Ecosystem (30%)          | 5\u002F5   | 4\u002F5  |\n| Performance (30%)        | 4\u002F5   | 5\u002F5  |\n| **Weighted Total**       | **4.3** | **4.3** |\n\nConfidence: Medium (55%). Scores are nearly identical. Recommendation: React,\nbut only because your team has 2 years of React experience (not captured in\nthe matrix). If the team were greenfield, Vue's developer experience gives it\na slight edge. This is close enough to warrant team preference as the tiebreaker.\n```\n\n**Example prompt:** \"We're on Heroku at $2,400\u002Fmo. Should we migrate to AWS?\"\n\n**Good output snippet:**\n```\n## TCO Estimate (12 months)\n| Category             | Heroku    | AWS               |\n|----------------------|-----------|-------------------|\n| Compute              | $1,200\u002Fmo | $480\u002Fmo (ECS)     |\n| Database             | $800\u002Fmo   | $350\u002Fmo (RDS)     |\n| Add-ons              | $400\u002Fmo   | $120\u002Fmo           |\n| Engineering (setup)  | $0        | $12,000 one-time  |\n| Engineering (ongoing)| 2 hrs\u002Fmo  | 8 hrs\u002Fmo          |\n| **Annual Total**     | **$28,800** | **$18,000**     |\n\nBreak-even at month 14. At Series A with a team of 6, wait until Heroku hits\n$4,000\u002Fmo — engineering hours are better spent on product right now.\n```\n","# Tech Stack Evaluation\n\n## When to Use\n\n- Comparing frontend\u002Fbackend frameworks or libraries for new projects\n- Evaluating cloud providers (AWS vs Azure vs GCP) for specific workloads\n- Planning technology migrations with risk and effort assessment\n- Calculating TCO including hidden costs; making build vs. buy decisions\n- Assessing open-source library viability and ecosystem health\n\nDo NOT use when: the decision is trivial (use team preference), the technology is already mandated, or this is an emergency production issue.\n\n## Context Required\n\nFrom `startup-context`: product type, team skills, tech stack, stage, scale, budget. Also ask:\n- What problem are you solving? (push back on solution-first thinking)\n- Non-negotiable requirements (performance, compliance, team familiarity)\n- Team experience with each option and timeline pressure (tight deadlines favor familiar tools)\n- Growth expectations that affect scalability requirements\n\n## Workflow\n\n1. **Clarify the decision** — What exactly is being decided and what are the real requirements? Push back if the user picks tech before defining the problem.\n2. **Identify candidates** — List 2-4 realistic options. Exclude clearly wrong choices early.\n3. **Define weighted evaluation criteria** — Select 6-8 criteria from the master list below. Assign weights based on the user's priorities (total = 100%).\n4. **Score each candidate** — Rate 1-5 on each criterion with one-line justification per score.\n5. **Assess ecosystem health** — Evaluate GitHub activity, npm\u002FPyPI adoption, community strength, corporate backing, and trajectory (growing, stable, declining).\n6. **Calculate TCO** — Project 5-year total cost including compute, storage, bandwidth, licensing, engineering time (setup + ongoing), and operational overhead. Engineering time is usually the largest cost for startups.\n7. **Analyze migration path** — If migrating, estimate effort, risks, timeline, and recommend phased approach (strangler fig pattern).\n8. **Deliver recommendation** — Clear winner with rationale and confidence level. No \"it depends\" without a follow-up question to resolve the ambiguity.\n\n## Output Format\n\n```markdown\n# Tech Stack Evaluation: [Decision Title]\n\n## Decision Context — what we are choosing and why it matters\n## Candidates — table: technology, version, license, one-liner\n## Evaluation Criteria — table: criterion, weight, why it matters\n## Scoring Matrix — table: criterion (weight), scores per option, weighted total\n## Ecosystem Health — table: GitHub stars, weekly downloads, last release, open issues, major users\n## TCO Estimate — table: cost category by option over 12 months or 5 years\n## Security & Compliance — vulnerability history, compliance readiness (SOC 2, GDPR)\n## Recommendation — clear winner, rationale, confidence level, caveats\n## Migration Path (if applicable) — phased plan with timeline and rollback strategy\n```\n\n## Frameworks & Best Practices\n\n### Master Evaluation Criteria\n\nSelect 6-8 and assign weights (total = 100%):\n\n- **Performance** — throughput, latency, resource efficiency for the specific workload\n- **Developer Experience** — tooling, debugging, documentation quality, error messages\n- **Learning Curve \u002F Team Familiarity** — time to productivity for the current team\n- **Ecosystem & Libraries** — packages, integrations, third-party support\n- **Maintenance & Longevity** — release cadence, corporate backing, bus factor\n- **Hiring Pool** — developer availability in your market and salary band\n- **Scalability** — handle 10-100x growth without a rewrite\n- **Cost \u002F Vendor Lock-in** — TCO and switching cost if you need to move later\n- **Security & Compliance** — vulnerability track record, compliance tooling readiness\n\n### Ecosystem Health Scoring\n\n| Level | Criteria |\n|-------|----------|\n| **Thriving** | Regular releases (\u003C 3 months), growing adoption, multiple corporate sponsors, active community |\n| **Stable** | Regular releases (\u003C 6 months), steady adoption, established community, no decline signs |\n| **At Risk** | Infrequent releases (> 12 months), declining downloads, key maintainers leaving, few contributors |\n\n### TCO Calculation Framework\n\nProject over 12 months minimum (5 years for infrastructure decisions): compute, storage, bandwidth, licensing, engineering time (setup + ongoing maintenance x loaded cost), operational overhead (monitoring, on-call), and hidden costs (training, migration tooling, dual-running).\n\n**Engineering time is usually the largest cost for startups.** A technology saving $200\u002Fmonth on hosting but costing 40 extra engineering hours to operate is a net loss.\n\n### Migration Risk Assessment\n\n| Risk Level | Criteria |\n|------------|----------|\n| **Low** | Additive change, no data migration, can run in parallel, \u003C 2 weeks |\n| **Medium** | Requires data migration or API changes, 2-8 weeks, can be phased |\n| **High** | Core system replacement, > 8 weeks, requires downtime or big-bang cutover |\n\nUse the strangler fig pattern: route new traffic to the new system, migrate old incrementally. Always maintain rollback capability. Set a concrete cut-off date -- half-migrated systems are the worst outcome.\n\n### Confidence Levels\n\n| Level | Score | Interpretation |\n|-------|-------|----------------|\n| **High** | 80-100% | Clear winner, strong data, wide margin |\n| **Medium** | 50-79% | Trade-offs present, recommendation holds but with caveats |\n| **Low** | \u003C 50% | Close call, limited data, suggest a proof-of-concept before committing |\n\n### Common Decision Anti-Patterns\n\n- **Resume-Driven Development** — choosing tech for resumes, not fit\n- **Hype Cycle Trap** — adopting at peak hype before stability is proven\n- **Premature Optimization** — distributed systems when a single Postgres handles the load\n- **Sunk Cost Fallacy** — refusing to migrate because of prior investment\n- **Ignoring Team Skills \u002F Solution-First Thinking** — picking tech nobody knows, or selecting technology before defining the problem\n\n## Related Skills\n\n- `architecture-design` — chain when the tech stack decision feeds into a broader system design\n- `cicd-setup` — chain to configure CI\u002FCD for the chosen technology\n\n## Examples\n\n**Example prompt:** \"Compare React vs Vue for a SaaS dashboard. Priorities: developer productivity (40%), ecosystem (30%), performance (30%).\"\n\n**Good output snippet:**\n```\n## Scoring Matrix\n| Criterion (weight)       | React | Vue  |\n|--------------------------|-------|------|\n| Developer Productivity (40%) | 4\u002F5   | 4\u002F5  |\n| Ecosystem (30%)          | 5\u002F5   | 4\u002F5  |\n| Performance (30%)        | 4\u002F5   | 5\u002F5  |\n| **Weighted Total**       | **4.3** | **4.3** |\n\nConfidence: Medium (55%). Scores are nearly identical. Recommendation: React,\nbut only because your team has 2 years of React experience (not captured in\nthe matrix). If the team were greenfield, Vue's developer experience gives it\na slight edge. This is close enough to warrant team preference as the tiebreaker.\n```\n\n**Example prompt:** \"We're on Heroku at $2,400\u002Fmo. Should we migrate to AWS?\"\n\n**Good output snippet:**\n```\n## TCO Estimate (12 months)\n| Category             | Heroku    | AWS               |\n|----------------------|-----------|-------------------|\n| Compute              | $1,200\u002Fmo | $480\u002Fmo (ECS)     |\n| Database             | $800\u002Fmo   | $350\u002Fmo (RDS)     |\n| Add-ons              | $400\u002Fmo   | $120\u002Fmo           |\n| Engineering (setup)  | $0        | $12,000 one-time  |\n| Engineering (ongoing)| 2 hrs\u002Fmo  | 8 hrs\u002Fmo          |\n| **Annual Total**     | **$28,800** | **$18,000**     |\n\nBreak-even at month 14. At Series A with a team of 6, wait until Heroku hits\n$4,000\u002Fmo — engineering hours are better spent on product right now.\n```\n",{"name":5,"reads":24,"related":26,"description":7},[25],"startup-context",[27,28],"architecture-design","cicd-setup","main","4ad31b43eef3ae3755cc57ec7e435dab4699ab44","skills\u002Ftech-stack-eval",44,"https:\u002F\u002Fgithub.com\u002Fshawnpang\u002Fstartup-founder-skills","https:\u002F\u002Fgithub.com\u002Fshawnpang","allscale.io","Building @allscale-io \r\nAlum @RichardIveyBusinessSchool \r\nExited from HashMatrix\r\nEx-Backend Dev @ByteDance\r\nEx-Product @CapitalOne @TikTok","2026-03-17 00:47:55",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add shawnpang\u002Fstartup-founder-skills --skill tech-stack-eval",{"tool":44,"command":45},"bunx","bunx skills add shawnpang\u002Fstartup-founder-skills --skill tech-stack-eval",{"tool":47,"command":48},"pnpm","pnpm dlx skills add shawnpang\u002Fstartup-founder-skills --skill tech-stack-eval","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshawnpang\u002Fstartup-founder-skills\u002Fblob\u002Fmain\u002Fskills\u002Ftech-stack-eval\u002FSKILL.md",true,[],[53,60,67,74,80,87],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M74YKFJBG7D7CVZHZQX9QB6X","user-research-synthesis","When the user has raw customer interview transcripts, survey responses, support tickets, or other qualitative data and needs to extract actionable insights.","https:\u002F\u002Fgithub.com\u002Fshawnpang\u002Fstartup-founder-skills\u002Fblob\u002Fmain\u002Fskills\u002Fuser-research-synthesis\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M74YKDA0DMZGMKN0ZXWQ83RS","terms-of-service","When the user needs to draft, review, or update terms of service for their SaaS product or web application.","https:\u002F\u002Fgithub.com\u002Fshawnpang\u002Fstartup-founder-skills\u002Fblob\u002Fmain\u002Fskills\u002Fterms-of-service\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M74YK6WBXMTA6QDMKWAC4EDV","support-docs","When the user needs to create help center articles, FAQs, troubleshooting guides, API documentation, or getting-started guides for customers.","https:\u002F\u002Fgithub.com\u002Fshawnpang\u002Fstartup-founder-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsupport-docs\u002FSKILL.md",[],[],{"skillNo":75,"name":25,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M74YK4RRS1AST1VVX3HP24ZZ","When the user wants to create or update their startup context document. Also use when the user mentions \"set up context\", \"tell you about my startup\", or any other skill needs context that doesn't exist yet.","https:\u002F\u002Fgithub.com\u002Fshawnpang\u002Fstartup-founder-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstartup-context\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M74YK26W3TXVY4MSC185QHY3","sourcing-outreach","When the user needs to write recruiting outreach messages to attract passive candidates or request referrals.","https:\u002F\u002Fgithub.com\u002Fshawnpang\u002Fstartup-founder-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsourcing-outreach\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M74YJZCJ6X3QZ480HE3C0MK8","social-content","When the user needs to build a LinkedIn authority system, create social content strategy, define content pillars, write posts, or establish thought leadership positioning. Activate on \"LinkedIn strategy,\" \"content pillars,\" \"what should I post,\" or \"build my personal brand.\"","https:\u002F\u002Fgithub.com\u002Fshawnpang\u002Fstartup-founder-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsocial-content\u002FSKILL.md",[],[]]