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

global--tech-stack skill

safe

/.codex/skills/global--tech-stack

This skill applies the Agent OS global tech stack standard to ensure consistent architecture and tooling across projects.

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

363 B

---
name: global--tech-stack
description: Apply the Agent OS standard for global tech stack.
tags: [agent-os, standard, global]
---

# Global Tech Stack

Use this skill when working on global tech stack in this repo.

## Instructions

- Follow the standard in `agent-os/standards/global/tech-stack.md`.

## References

- `agent-os/standards/global/tech-stack.md`

Overview

This skill applies the Agent OS global tech stack standard to a codebase. It ensures consistent language, tooling, and configuration choices across projects to simplify onboarding, maintenance, and cross-team collaboration. Use it to align a repository with organization-wide tech guidelines quickly and consistently.

How this skill works

The skill inspects project metadata, package manifests, and configuration files to detect current stack components and deviations from the Agent OS global tech stack. It reports discrepancies, suggests concrete fixes, and can produce a checklist or patch suggestions to bring the codebase into compliance. The output focuses on actionable changes for tooling, versions, and common conventions.

When to use it

Initial repository setup to align with organization standards
During audits to verify tech stack consistency across projects
Before merging major infra or dependency changes
When onboarding a new project or team to company-wide tooling
Preparing repositories for cross-project automation or CI/CD

Best practices

Run the skill early in the project lifecycle and integrate into CI checks
Treat suggested changes as actionable patches and review them in pull requests
Keep tech stack decisions documented and update the standard when exceptions are justified
Use the skill’s reports to drive small, incremental fixes rather than large disruptive changes
Automate acceptance of non-breaking formatting or config updates

Example use cases

Detecting inconsistent Node/TypeScript versions and suggesting version alignment
Identifying missing or misconfigured linters, formatters, and test scripts
Generating a checklist for migrating repositories to company-approved CI templates
Flagging unsupported or deprecated libraries that violate the global stack policy
Creating a minimal patch that updates package manifests and config files to the standard

FAQ

Can the skill make changes automatically?

It can produce patch suggestions and automated diffs, but changes should be reviewed and merged through normal code review practices.

What if a repository needs an exception?

Document the justification and request an exception in the organization governance process; the skill’s report can include contextual notes to support that request.