# Align Tech Stack Decisions

Teams can introduce conflicting frameworks, services, or build tools when stack decisions are scattered. This skill guides Claude, Codex, and Claude Code to follow documented technology standards.

## Install

```bash
npx skillstore add eis-its/global-tech-stack
```

## Metadata

- Status: approved
- Slug: eis-its-global-tech-stack
- Skillstore revision: r1
- Version status: missing
- Tree hash: 06959cd897b1c1f76dc339339796309c10a2afab9c73463b86187fc88981e0ac
- Author: EIS-ITS
- GitHub username: EIS-ITS
- License: MIT
- Repository: https://github.com/EIS-ITS/vss-cli/tree/main/.claude/skills/global-tech-stack
- Ref: 26421118b848d9f1efc0aa169d8a7a9e7e0a877e
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: filesystem
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/eis-its-global-tech-stack
- Manifest: https://skillstore.pages.dev/api/skills/eis-its-global-tech-stack/manifest

## Capabilities

- Guides technology choices against the project's documented stack standards.
- Helps evaluate new libraries, frameworks, and dependencies for consistency.
- Supports framework-specific implementation decisions for common web stacks.
- Frames database, ORM, testing, build, and deployment choices.
- Prompts consistent decisions for authentication and third-party service integrations.

## Use Cases

- Review Dependency Choices: Compare a proposed library with project standards before adding it to the application.
- Keep Architecture Consistent: Check new service, database, and framework decisions against approved stack guidance.
- Support Stack Onboarding: Help new contributors understand which tools and patterns the project expects.

## Prompt Templates

### Check Stack Fit

```
Use global-tech-stack to review whether [library] fits this project. Compare it with the current stack standards and list concerns.
```

### Choose Implementation Tools

```
Use global-tech-stack to choose tools for [feature]. Recommend options that match the existing frameworks, testing tools, and build process.
```

### Plan Service Integration

```
Use global-tech-stack to plan an integration with [service]. Identify stack conventions, required configuration areas, and review risks.
```

### Audit Stack Change Proposal

```
Use global-tech-stack to audit this stack change: [proposal]. Compare it with approved standards and recommend accept, revise, or reject.
```

## Limitations

- The skill depends on a referenced tech stack file outside SKILL.md.
- It does not install packages, run tests, or verify code by itself.
- It does not replace security, license, or maintenance review for new dependencies.
- It may be incomplete when the referenced standards file is unavailable.

## Best Practices

- Check the referenced stack standards before adding a dependency.
- Document why a new tool is necessary when the approved stack is insufficient.
- Keep implementation choices aligned with existing framework and testing patterns.

## Anti Patterns

- Introducing a second framework for a problem already solved by the stack.
- Choosing a dependency before checking project standards and maintenance status.
- Using the skill as approval for risky authentication or payment changes.

## Security Audit

- Audited at: 2026-07-09T14:24:30.837\+00:00
- Summary: One static filesystem finding is confirmed because SKILL.md line 29 uses a ../../../ relative link that escapes the skill directory. The system reconnaissance finding is a false positive; line 3 describes technology decision guidance, not host reconnaissance. No prompt injection or other semantic threats were found in SKILL.md.

## Stats

- Views: 207
- Downloads: 14
- Favorites: 0
- Popularity score: 0