technical-spec

Codify environment variable management, architecture patterns, and build commands.

2|1|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/tundraray/overture --skill technical-spec-tundraray
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: technical-spec
Source: https://github.com/tundraray/overture/tree/main/skills/technical-spec
Command: npx skills add https://github.com/tundraray/overture --skill technical-spec-tundraray

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides technical design rules including environment variable management, architecture design, and build/testing commands. It is automatically loaded when discussing architecture, environment variables, build commands, or when "tech stack", "architecture pattern", "environment config", or "build command" are mentioned.

Core Features & Use Cases

  • Environment Variable Management: Central guidance to manage environment configuration with type safety, avoiding direct use of process.env.
  • Security & Compliance: Do not commit .env files; enforce secret handling through a configuration layer; prevent sensitive data leakage.
  • Architecture & Data Flow: Principles for separation of responsibilities, unified data flow, and reusable design patterns across projects.
  • Build & Testing Guidance: Standardized build and test commands aligned with the project's package manager and CI practices.

Quick Start

Load these design rules into your planning discussions and reference them during architecture reviews and implementation planning. Then describe your project’s tech stack to apply the guidelines to your codebase.

Frequently Asked Questions about technical-spec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize environment variable management to prevent secret leakage?

Standardize environment variable management by avoiding direct process.env usage and enforcing a configuration layer with type safety. This prevents sensitive data leakage and ensures secure secret handling across teams.

What are the best architecture patterns for scalable application data flow?

Architecture patterns for scalable apps should enforce separation of responsibilities and unified data flow. Applying these reusable design principles ensures consistent architecture reviews and standardized technical design decisions across projects.

How do I set up reproducible build and testing commands aligned with my CI?

Reproducible build and testing commands are set up by standardizing them according to the project's package manager and CI practices. This ensures consistent execution and reliable builds across development environments.

Do I need a configuration layer for environment config in small libraries?

A configuration layer is needed for environment config even in small libraries. This skill applies to projects ranging from small libraries to large-scale systems, enforcing secure config handling and avoiding direct secret usage.

Why should I avoid direct process.env usage in my tech stack?

Direct process.env usage should be avoided to maintain type safety and prevent sensitive data leakage. Routing environment variables through a configuration layer centralizes guidance and enforces secure secret handling.

When do I need technical design rules for architecture reviews?

Technical design rules are needed during architecture reviews and implementation planning to codify environment variable management, architecture patterns, and testing standards. This ensures reproducible builds and consistent data flow across teams.