global-tech-stack
Reference the project's defined technology stack including frameworks, languages, databases, testing tools, and deployment infrastructure. Use this skill when making technology decisions or choosing libraries. When working with project configuration files like package.json, requirements.txt, or Gemfile. When setting up new features that need to align with existing technology choices. When onboarding to understand the project's technical foundation. When choosing tools for testing, linting, CI/CD, or third-party services.
When & Why to Use This Skill
The Global Tech Stack skill enables Claude to maintain architectural consistency and technical integrity across a project. By referencing a defined foundation of frameworks, languages, and infrastructure, it ensures that all development decisions—from library selection to CI/CD configuration—align with established project standards and best practices.
Use Cases
- Informed Technology Decisions: Selecting libraries, frameworks, or databases that are compatible with the project's existing technical ecosystem.
- Dependency Configuration: Managing and updating project configuration files like package.json, requirements.txt, or Gemfile while adhering to versioning standards.
- Project Onboarding: Providing a comprehensive overview of the technical foundation for new contributors to ensure rapid and consistent integration.
- Infrastructure & Tooling Alignment: Choosing and configuring tools for testing, linting, CI/CD, and third-party services (Auth, Monitoring) that match the project's architectural patterns.
- Feature Standardization: Ensuring new features are built using the designated tech stack to prevent technical debt and maintain codebase uniformity.
| name | Global Tech Stack |
|---|---|
| description | Reference the project's defined technology stack including frameworks, languages, databases, testing tools, and deployment infrastructure. Use this skill when making technology decisions or choosing libraries. When working with project configuration files like package.json, requirements.txt, or Gemfile. When setting up new features that need to align with existing technology choices. When onboarding to understand the project's technical foundation. When choosing tools for testing, linting, CI/CD, or third-party services. |
When to use this skill:
- When making decisions about which library or framework to use
- When working on package.json, requirements.txt, Gemfile, or dependency files
- When setting up new features that should align with existing tech choices
- When needing to understand the project's technical foundation
- When choosing testing frameworks or test utilities
- When configuring linting or formatting tools
- When setting up CI/CD pipelines or deployment
- When integrating third-party services (auth, email, monitoring)
- When deciding on database or ORM approaches
- When configuring caching solutions
- When onboarding or getting oriented to the project
- When ensuring new code aligns with established technology patterns
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