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.
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "global-tech-stack" from https://skillstore.io/skills/eis-its-global-tech-stack.md and its manifest at https://skillstore.io/api/skills/eis-its-global-tech-stack/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Using "global-tech-stack". Can we add a new payment SDK for checkout?
Expected outcome:
Recommendation: use the approved payment provider unless requirements demand another SDK. Risks include vendor overlap, duplicated webhooks, and compliance review.
Using "global-tech-stack". Which test framework should cover a new API route?
Expected outcome:
Use the project's existing API test framework. Add integration coverage for route behavior and avoid introducing a second runner.
Using "global-tech-stack". Should this service use a new database?
Expected outcome:
Start with the approved database unless scale, data shape, or compliance needs justify a change. Document tradeoffs before adoption.
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.
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
https://skillstore.io/skills/eis-its-global-tech-stack/audits/10?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report[](https://skillstore.io/skills/eis-its-global-tech-stack?utm_source=security_passport_badge)<a href="https://skillstore.io/skills/eis-its-global-tech-stack?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/eis-its-global-tech-stack/security.svg" alt="Skillstore security assessment" loading="lazy"></a><iframe src="https://skillstore.io/embed/skills/eis-its-global-tech-stack.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>EIS-ITS. (2026). global-tech-stack security audit report (audit version 10) [Author version unspecified]. Skillstore. https://skillstore.io/skills/eis-its-global-tech-stack/audits/10@techreport{eis-its-eis-its-global-tech-stack-2026,
author = {EIS-ITS},
title = {global-tech-stack security audit report (audit version 10)},
institution = {Skillstore},
year = {2026},
number = {10},
url = {https://skillstore.io/skills/eis-its-global-tech-stack/audits/10},
note = {Author version unspecified}
}cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "global-tech-stack security audit report (audit version 10)"
version: "unspecified"
type: report
authors:
- name: "EIS-ITS"
date-released: "2026-07-09"
url: "https://skillstore.io/skills/eis-its-global-tech-stack/audits/10"
identifiers:
- type: other
value: "skillstore:eis-its-global-tech-stack:audit:10"
description: "Skillstore immutable audit report identifier"
Each author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
eis-its-global-tech-stack
2026-08-21
devanb-global-tech-stack
2026-08-21
Compare a proposed library with project standards before adding it to the application.
Check new service, database, and framework decisions against approved stack guidance.
Help new contributors understand which tools and patterns the project expects.
Use global-tech-stack to review whether [library] fits this project. Compare it with the current stack standards and list concerns.
Use global-tech-stack to choose tools for [feature]. Recommend options that match the existing frameworks, testing tools, and build process.
Use global-tech-stack to plan an integration with [service]. Identify stack conventions, required configuration areas, and review risks.
Use global-tech-stack to audit this stack change: [proposal]. Compare it with approved standards and recommend accept, revise, or reject.
Author
EIS-ITSLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
26421118b848d9f1efc0aa169d8a7a9e7e0a877e
Maintenance freshness
7/18/2026
Usage
7 downloads · 207 views
File structure
📄 SKILL.md
Build Reusable Frontend Components
Frontend teams need consistent component structure across frameworks. This skill guides Claude, Codex, and Claude Code to design focused, reusable UI components.
Improve Frontend Accessibility
Frontend teams often miss keyboard, semantic, and screen reader requirements during routine UI work. This skill guides Claude, Codex, and Claude Code to apply accessibility checks while creating or editing interfaces.
Apply Consistent Coding Style
Inconsistent code slows reviews and makes maintenance harder. This skill gives Claude, Codex, and Claude Code clear rules for readable, consistent code.
Write Focused Behavior Tests
Teams often add brittle tests that mirror implementation details instead of user behavior. This skill guides Claude, Codex, and Claude Code to write focused tests for critical workflows.
Validate Inputs Across Entry Points
Input validation often becomes inconsistent across forms, APIs, and business rules. This skill guides Claude, Codex, and Claude Code toward secure validation patterns.
Build Consistent Frontend CSS
Frontend styling often drifts across files, components, and frameworks. This skill guides Claude, Codex, and Claude Code toward consistent CSS methods and design tokens.
Analyze Any Codebase Fast
by CloudAI-X
Understanding an unfamiliar codebase takes hours of manual exploration across scattered files and configs. This skill gives Claude a structured six-step workflow to map a project's tech stack, structure, patterns, and development commands into a clear summary report.
Build Fullstack Project Plans
by davila7
Teams often need a clear starting point for fullstack architecture, workflows, and quality checks. This skill provides stack guidance, reference patterns, and lightweight Python tools for planning and reviewing web projects.
Plan Next.js App Router Architecture
by 89jobrien
Next.js teams can struggle to choose routes, components, data loading, and migration steps. This skill gives structured architecture guidance for App Router, Server Components, and performance.
Apply Python Design Patterns
by wshobson
Python projects often grow complex when responsibilities mix and abstractions appear too early. This skill guides focused refactors using KISS, SRP, layering, composition, and dependency injection.
Design LangChain Application Architectures
by sickn33
LLM applications can become difficult to structure as agents, memory, retrieval, and tools grow. This skill guides LangChain design choices and production checks.
Analyze Codebases for Business Logic
by DoubleslashSE
Existing systems often hide requirements inside code, tests, and configuration. This skill guides structured analysis that turns code observations into clear business documentation.