create-architecture-docslisted

# Create Architecture Docs When this skill is activated, analyze the current project thoroughly and create a comprehensive `ARCHITECTURE.md` file in the project root. ## Clarifying Questions Before starting, ask the engineer the following questions. Skip any already clearly answered in the conversation. **Wait for the answers before proceeding.** 1. Who is the primary audience for this document — new team members, external reviewers, or yourself? 2. Are there parts of the architecture that are particularly important to document in depth? 3. Are there known design decisions or trade-offs that should be captured, even if they are not obvious from the code? 4. Are there any areas that should be excluded or treated lightly? ## Steps 1. Explore the project structure (files, folders, config files, package managers) 2. Identify the tech stack (languages, frameworks, libraries, tools) 3. Understand the major components and their responsibilities 4. Trace data flow and key interactions between components 5. Note important design decisions, patterns, and conventions visible in the code ## Output Write a file called `ARCHITECTURE.md` in the project root with the following sections: ### 1. Overview A short paragraph summarizing what the project does and its main purpose. ### 2. Tech Stack A table or list of all languages, frameworks, libraries, and tools used, with a brief note on the role of each. ### 3. Project Structure An annotated directory tree of the top-level structure