Global Tech Stack

Codify project technology choices to maintain codebase consistency.

Updated Jan 15, 2026
One-click install
npx skills add https://github.com/dpietersz/pietersz.me --skill global-tech-stack-dpietersz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Global Tech Stack
Source: https://github.com/dpietersz/pietersz.me/tree/main/.claude/skills/global-tech-stack
Command: npx skills add https://github.com/dpietersz/pietersz.me --skill global-tech-stack-dpietersz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reference and maintain the project's technical stack including frameworks, languages, databases, testing tools, and third-party services to ensure consistency across the project. Use this skill when making technology choices, adding new dependencies or configuring frameworks, or ensuring consistency with existing stack decisions. When setting up new features that need to align with the project's chosen technologies. When documenting or updating the tech stack. This skill applies when working with any technology-specific configuration, framework setup, or when making architectural decisions about tools and libraries.

Core Features & Use Cases

  • Establish centralized tech-stack guidelines to guide decision making.
  • Align dependencies, configurations, and tooling with existing standards.
  • Use to onboard new team members and expedite feature planning while maintaining consistency.

Quick Start

Apply the project’s tech stack guidelines when selecting tools for a new 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 maintain consistency when adding new dependencies to my tech stack?

To maintain tech stack consistency, codify your project's technology choices and enforce adherence to established stack standards when adding new dependencies or configuring frameworks. This ensures alignment with existing configurations and architecture decisions.

What is the best way to document my project's frameworks and databases for onboarding?

Documenting your tech stack involves establishing centralized guidelines that reference frameworks, databases, languages, and testing tools. This codifies your technology choices to expedite feature planning and onboard new team members effectively.

When do I need to codify my project's technology choices?

You need to codify technology choices when setting up new features that require alignment with existing technologies, making architectural decisions about libraries, or updating project documentation to maintain consistency across the codebase.

Can I use existing tech stack guidelines for configuring CI-CD and testing tools?

Yes, you can apply existing tech stack guidelines when configuring testing tools and CI-CD pipelines. The guidelines ensure your tooling, dependencies, and configurations align with established project standards and architecture decisions.

How do I align architecture decisions for new features with my current tech stack?

Aligning architecture decisions involves applying established tech stack guidelines when selecting tools for new features. This maintains consistency by enforcing documentation and adherence to chosen languages, frameworks, and third-party services.