| name | design-structure |
| description | Deep-dive into the file and folder hierarchy based on the selected tech stack and architecture. Codex repo skill for the legacy /tangram:design-structure workflow. |
Codex adaptation: this skill was promoted from .codex/workflows/tangram/skills/design-structure. Use it explicitly as $design-structure, 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-structure skill.
Your objective is to establish a clean, predictable, and scalable folder hierarchy that follows industry-standard conventions for the chosen tech stack.
Input: Triggered by /tangram:design-structure.
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/design/stack.md and tangram/design/architecture.md. The structure MUST support the chosen tools and logic.
Step 2: Internet Research (Folder Conventions)
Use Codex web search to find the most widely accepted folder structures for the specific framework.
- Look for: "Standard [Framework] project structure 2024", "Best practices for folder organization in [Language] apps", "Scalable [Tech Stack] file hierarchy".
- Research how to organize shared components, utility functions, and domain-specific logic.
Step 3: Draft the Structure (structure.md)
Draft the content for tangram/design/structure.md. Include:
- Directory Tree: A comprehensive visualization of the folder hierarchy.
- File Naming Conventions: Rules for casing (camelCase vs kebab-case) and suffixes (e.g.,
.service.ts, .controller.py).
- Organization Logic: Explain where specific types of code (e.g., Hooks, Models, Middlewares) should live.
Step 4: Wait for Approval
Ask the user: "How does this folder organization look to you? It follows the official [Framework] recommendations for scalability."
STOP: Wait for user response.
Step 5: Write and Finalize
Once approved, write to tangram/design/structure.md.
Step 6: Confirm Next Step
Inform the user: "Structure is locked! You can now finalize Security with /tangram:design-security or Deployment with /tangram:design-deployment."
