Global Tech Stack

Identify the project's established technology stack for development decisions.

1|Updated Jan 9, 2026

Search Tags:#devops #architecture #frameworks #libraries #guidance #standards #tech-stack

Ready to run

npx skills add https://github.com/TorbenMerrald/StableManager --skill global-tech-stack-torbenmerrald

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often struggle to stay aligned on the project's technology choices, leading to inconsistent tooling and increased onboarding time.

Core Features & Use Cases

Central reference for allowed languages, frameworks, libraries, and tooling across the project.
Guidance for architectural decisions, deployment strategies, and testing standards.
Use Case: When starting a new module, consult this stack to select compatible tech and avoid duplicative tooling.

Quick Start

Review the global tech stack reference and apply the approved libraries, frameworks, and deployment conventions to your current feature.

Frequently Asked Questions about Global Tech Stack

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

FAQPage Schema

How do I standardize tech stack choices across a development team?▼

Standardize tech stack choices by identifying the project's established languages, frameworks, and tooling, then applying them as the default reference for feature development and architecture decisions to ensure consistency. This minimizes risk and reduces onboarding time.

What is the best way to align frontend and backend tooling with project standards?▼

Align frontend and backend tooling by consulting a central reference of approved libraries and frameworks, ensuring your selected tools match the established runtime environments, dependencies, and security guidelines.

How do I maintain consistency in CI/CD and deployment strategies?▼

Maintain consistency in CI/CD and deployment strategies by using the project's established technology stack as a guide, ensuring all deployment planning and monitoring practices align with defined architectural standards.

When do I need a central reference for allowed libraries and frameworks?▼

A central reference for allowed libraries and frameworks is needed when starting a new module, helping you select compatible tech, avoid duplicative tooling, and ensure alignment with project standards.

Can I use this to guide architecture decisions for new features?▼

Yes, you can use the established technology stack to guide architecture decisions for new features, ensuring alignment with runtime environments, dependencies, and security guidelines to minimize deployment risk.

Why does inconsistent tooling increase onboarding time?▼

Inconsistent tooling increases onboarding time because teams struggle to stay aligned on project technology choices, leading to fragmented practices and a lack of standardized guidance for development and deployment.