home / skills / tlabs-xyz / tbtc-v2-performance / global-tech-stack

global-tech-stack skill

/.claude/skills/global-tech-stack

This skill helps maintain project-wide tech stack consistency by guiding dependency choices, tooling, and configurations across frontend, backend, and infra.

npx playbooks add skill tlabs-xyz/tbtc-v2-performance --skill global-tech-stack

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
2.0 KB
---
name: Global Tech Stack
description: Maintain consistency with the project's technology stack including frameworks, languages, package managers, databases, testing tools, and third-party services. Use this skill when adding new dependencies or libraries, choosing technologies for new features, configuring build tools or package managers, setting up testing frameworks, implementing authentication or email services, configuring databases or ORMs, selecting CSS or UI frameworks, setting up linting or formatting tools, configuring CI/CD pipelines, or making any technology choices that should align with the project's established stack. Use when working with package.json, requirements.txt, Gemfile, go.mod, Cargo.toml, or any configuration files that define project dependencies and tooling.
---

## When to use this skill

- When adding new dependencies or libraries to the project
- When choosing technologies for implementing new features
- When configuring build tools, bundlers, or package managers
- When setting up or modifying testing frameworks
- When implementing authentication, email, or monitoring services
- When configuring databases, ORMs, or caching solutions
- When selecting or configuring CSS frameworks or UI component libraries
- When setting up linting, formatting, or code quality tools
- When configuring CI/CD pipelines or deployment workflows
- When making technology choices that should align with existing stack
- When working with package.json, requirements.txt, Gemfile, go.mod, Cargo.toml
- When documenting the project's tech stack or updating stack documentation
- When ensuring consistency across frontend, backend, database, and infrastructure choices

# Global Tech Stack

This Skill provides Claude Code with specific guidance on how to adhere to coding standards as they relate to how it should handle global tech stack.

## Instructions

For details, refer to the information provided in this file:
[global tech stack](../../../agent-os/standards/global/tech-stack.md)

Overview

This skill enforces consistency with the project's global technology stack when making any dependency or tooling decisions. It helps authors choose libraries, configure build and test tools, and align services with the established languages, package managers, frameworks, databases, and CI/CD practices. Use it to avoid drifting from the agreed stack and to document choices clearly.

How this skill works

The skill inspects dependency manifests and configuration files (package.json, requirements.txt, Gemfile, go.mod, Cargo.toml, etc.) and compares proposed changes to the project's declared stack and conventions. It flags mismatches, recommends preferred alternatives, and provides concrete configuration snippets that follow existing tools, package managers, and version constraints. It also advises on integration concerns for testing, deployment, and third-party services.

When to use it

  • Adding new dependencies or libraries to the project
  • Choosing technologies for new features (frontend, backend, infra)
  • Configuring build tools, bundlers, or package managers
  • Setting up or modifying testing frameworks and linters
  • Configuring databases, ORMs, authentication, email, or monitoring
  • Designing or updating CI/CD pipelines and deployment workflows

Best practices

  • Prefer versions and packages already used in the repo to minimize conflicts
  • Keep package manager and lockfile changes atomic and documented
  • Match testing and linting frameworks to existing conventions and CI jobs
  • Avoid introducing multiple overlapping tools for the same concern
  • Document deliberate deviations and the migration plan if a change is required

Example use cases

  • Replacing a library: recommend an in-stack alternative and show migration steps
  • Adding auth/email: suggest services compatible with existing env and secrets management
  • New frontend feature: pick the UI framework and bundler that align with current build
  • CI change: propose pipeline steps that reuse existing runners and caching
  • Database change: advise ORM choices and schema migration patterns already in use

FAQ

What if a needed tool is not yet in the stack?

Recommend the best-fit option and require justification, a migration plan, and a small proof-of-concept that demonstrates compatibility and minimal disruption.

How strict should adherence be?

Favor consistency for maintainability, but allow exceptions with documented trade-offs and approvals for technical debt, security, or performance reasons.