Global Tech Stack

Name: Global Tech Stack
Availability: InStock
Author: grimm

Enforce approved tech stack standards across projects and governance artifacts.

Updated Aug 23, 2026

Search Tags:#architecture #CI/CD #tech stack #TypeScript #development standards #technology #Python #infrastructure-as-code

Ready to run

npx skills add https://github.com/grimmolf/mga-soap-calculator --skill global-tech-stack-grimmolf

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Global Tech Stack
Source: https://github.com/grimmolf/mga-soap-calculator/tree/main/.claude/skills/global-tech-stack
Command: npx skills add https://github.com/grimmolf/mga-soap-calculator --skill global-tech-stack-grimmolf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents tech sprawl, ensures consistency, and enforces quality standards across projects by guiding the selection and maintenance of an approved technology stack, tooling, and infrastructure-as-code practices.

Core Features & Use Cases

Approved Technology Selection: Guides on choosing languages, frameworks, and libraries.
Quality Gate Enforcement: Ensures CI/CD pipelines, linters, and formatters maintain code quality.
Infrastructure-as-Code: Promotes managing infrastructure through Ansible playbooks.
Use Case: When proposing a new library, use this skill to evaluate its fit within the approved tech stack and ensure it meets quality gate requirements before integration.

Quick Start

Using the Global Tech Stack skill, evaluate the suitability of 'X' library for our backend service, considering approved languages and quality gates.

Frequently Asked Questions about Global Tech Stack

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I enforce a consistent tech stack across multiple projects?▼

Enforce a consistent tech stack by documenting approved languages, frameworks, and tools—such as TypeScript, Python, React, Node.js, and FastAPI—then apply CI/CD quality gates, linters, and formatters to validate compliance across package.json, requirements.txt, and infrastructure code. This prevents tech sprawl and ensures standardization.

Can I evaluate whether a new library fits our approved tech stack?▼

Yes. Assess library fit by checking alignment with approved languages and frameworks, verifying it passes quality gate requirements in CI/CD pipelines, and ensuring it integrates with your existing linters, formatters, and testing frameworks before integration.

What's the best way to standardize infrastructure-as-code across teams?▼

Standardize infrastructure-as-code by adopting Ansible playbooks as your approved automation tool, documenting governance standards in ADRs, and enforcing them through CI/CD pipelines. Apply consistent linting and approval workflows to all infrastructure definitions.

How do I manage technology upgrades across an approved tech stack?▼

Manage upgrades by documenting migration strategies for each approved technology, enforcing upgrade cadences through CI/CD quality gates, and using ADRs to record decisions. Apply version constraints in package.json and requirements.txt with documented approval workflows.

What coding standards should I enforce in CI/CD pipelines?▼

Enforce coding standards by configuring linters and formatters in CI/CD pipelines to validate TypeScript, Python, and other approved languages. Set quality gates that block commits failing standards checks, ensuring consistency across all projects.

Do I need database standardization as part of tech stack governance?▼

Yes. Standardize approved databases—PostgreSQL for relational data and Redis for caching—in your tech stack documentation and enforce their use through architecture review and CI/CD validation of infrastructure-as-code artifacts.