tech-stack

amattas's avatarfrom amattas

Describes the primary technologies, frameworks, libraries, and language conventions used in this codebase.

⭐0stars🔀0forks📁View on GitHub🕐Updated Dec 26, 2025
[Architecture Design]

When & Why to Use This Skill

The Tech Stack skill provides a comprehensive architectural overview of a codebase, detailing the primary programming languages, frameworks, and libraries in use. It establishes a clear technical blueprint and coding standards, ensuring that both developers and AI agents maintain consistency in naming conventions, error handling, and dependency management across the project lifecycle.

Use Cases

  • Project Onboarding: Quickly align new developers or AI assistants with the project's specific technology stack and architectural patterns to reduce ramp-up time.
  • Standardizing Development: Enforce uniform coding conventions and best practices, such as naming styles and error handling protocols, to ensure high-quality, maintainable code.
  • Architectural Documentation: Maintain an up-to-date record of infrastructure choices and library dependencies, serving as a single source of truth for technical decision-making.
nametech-stack
descriptionDescribes the primary technologies, frameworks, libraries, and language conventions used in this codebase.

Tech Stack Overview

Primary Languages

  • Backend: [e.g., TypeScript / Node.js]
  • Frontend: [e.g., React / TypeScript]
  • Infrastructure: [e.g., Terraform / YAML]
  • Other: [e.g., Python for data tasks]

Frameworks & Libraries

  • Backend framework(s): [e.g., NestJS, Express]
  • Frontend framework(s): [e.g., Next.js, Redux, React Query]
  • Database: [e.g., PostgreSQL + Prisma, MongoDB]
  • Messaging / queues: [e.g., Kafka, RabbitMQ]
  • Observability: [e.g., OpenTelemetry, Prometheus, Grafana]

Language Conventions

General

  • Prefer [functional / OO / mixed] style for [language].
  • Follow [link to style guide] for formatting and structure when possible.

Naming

  • Types / classes: [e.g., PascalCase]
  • Functions: [e.g., camelCase verbs]
  • Constants: [e.g., UPPER_SNAKE_CASE]
  • Files: [e.g., kebab-case.ts, PascalCase.tsx]

Error Handling

  • Use [custom error types / Result types / exceptions] with:
    • Consistent error codes
    • User- vs system-facing messages

Dependency Management

  • Use [npm / yarn / pnpm / pip / etc.] with:
    • Lockfiles committed
    • Reproducible installs in CI

Project-Specific Notes

  • [Any special constraints, e.g., "no experimental language features" or "avoid reflection."]