Define technology stacks with languages, runtimes, frameworks, and deployment models.
npx skills add https://github.com/gballer77/gspec --skill gspec-stack
Please help me install this Agent Skill. Skill: gspec-stack Source: https://github.com/gballer77/gspec/tree/main/pages/.claude/skills/gspec-stack Command: npx skills add https://github.com/gballer77/gspec --skill gspec-stack
Defines a clear, scalable technology stack and architecture blueprint to prevent drift between design and implementation, ensuring consistent tooling, runtimes, and deployment patterns across the project.
Provide a concise technology stack for the given project description, including primary languages, runtimes, and deployment targets.
High-intent search queries and answers about installing and using this skill.
Defining a technology stack requires selecting primary languages, runtimes, and frameworks, then mapping them to deployment models. This skill generates a comprehensive stack definition that enforces explicit runtime versions and architecture patterns to prevent design drift.
Choosing a deployment model involves evaluating scalability targets and architecture patterns. This skill aligns your technology stack with monolith, microservices, or serverless styles, providing explicit tradeoffs and rationale for each deployment decision.
Documenting framework choices and security considerations is enforced within the final stack documentation. The generated technology stack definition requires explicit inclusion of security considerations alongside architecture patterns and runtime versions.
Yes, you can generate a stack definition when re-architecting an application. Provide a concise project description to output a tailored technology stack with primary languages, runtimes, and deployment targets that guide new code structure decisions.
Explicit runtime versions are required to prevent drift between design and implementation. Enforcing specific runtime versions in your stack documentation ensures consistent tooling and deployment patterns across the entire project lifecycle.
Yes, this approach explicitly targets serverless deployment styles and scalability targets. It builds a technology stack definition that maps framework choices and runtime versions directly to your serverless architecture requirements.
thoreinsteinCoordinate expert consultation and automated research for multi-phase systems analysis.
CarlosAndresBF1Document Odyssey RAG patterns and anti-patterns for ingestion, MCP server, and retrieval stack.
bomberoxenviosdosruedasAutomate DevOps workflows with Terraform, GitHub Actions, Kubernetes, and Prometheus.
nextcScaffold Flutter projects from product proposals with dependencies and architecture docs.
