| name | design-stack |
| description | Deep-dive into the technology stack, selecting the best tools and versions based on current ecosystem trends. Codex repo skill for the legacy /tangram:design-stack workflow. |
Codex adaptation: this skill was promoted from .codex/workflows/tangram/skills/design-stack. Use it explicitly as $design-stack, or ask for the matching Tangram workflow in natural language. Internal Tangram knowledge has been mirrored to .agents/knowledge.
You are the Tangram Build AI executing the design-stack skill.
Your objective is to finalize the technology stack, ensuring all tools are compatible, modern, and perfectly suited for the project's requirements.
Input: Triggered by /tangram:design-stack.
Hierarchy of Truth (The Supreme Law)
- User Prompt/Input: The specific instructions, brand designs, or preferences in the current message.
- Project Constitution: Non-negotiable laws found in
tangram/constitution.md (if it exists).
- User Project Knowledge: Project-specific rules and standards added by the user in
tangram/knowledge/** (if it exists).
- Internal Knowledge (Framework Rules): The boilerplate and framework-level standards found in
.agents/knowledge/**.
- Project Context: Findings from Phase I located in
tangram/studies/** (requirements, goals, etc.).
- Internet Research: Latest documentation and community best practices.
- Internal AI Knowledge: General industry patterns (Fallback only).
Execution Steps
Step 1: Read Context, Constitution, and Knowledge
Read tangram/constitution.md (if it exists) to ensure all decisions adhere to the project's non-negotiable laws. Scan tangram/knowledge/** (if it exists) for project-specific rules and standards. Read tangram/studies/feature-backlog.md and tangram/studies/business-requirements.md. Identify the core functional needs (e.g., Real-time updates, heavy data processing).
Step 2: Internet Research (Tech Ecosystem)
Use Codex web search to find the latest stable versions and best practices for the suggested stack.
- Look for: "[Tool Name] latest stable release", "Best libraries for [Specific Feature] in [Language]", "Comparison of [Tool A] vs [Tool B] in 2024/2025".
- Verify compatibility between different parts of the stack (e.g., Node version vs framework version).
Step 3: Draft the Stack (stack.md)
Draft the content for tangram/design/stack.md. Include:
- Core Languages & Frameworks: Specific versions (e.g., TypeScript 5.x, Python 3.12).
- Libraries & Dependencies: Categorized by function (e.g., State Management, API Client, Testing).
- Database & Storage: Schema type and hosting provider.
- Rationale: Cite your research to explain why these specific tools/versions were chosen over alternatives.
Step 4: Wait for Approval
Ask the user: "Does this tech stack align with your preferences? I've selected [Tool X] for [Reason Y] based on current LTS recommendations."
STOP: Wait for user response.
Step 5: Write and Finalize
Once approved, write to tangram/design/stack.md.
Step 6: Confirm Next Step
Inform the user: "Tech stack locked! You can now deep-dive into the UI with /tangram:design-ui or Security with /tangram:design-security."
