generate-tech-stacklisted

FIRE this skill when the user's intent is to discover, list, visualize, document, or summarize the technologies used in a software project. This includes all of the following triggers: EXPLICIT COMMANDS: /generate-tech-stack; "generate tech stack"; "create tech stack"; "show tech stack"; "build tech stack"; "make tech stack page"; "tech stack report". DISCOVERY / INVENTORY INTENT: user wants to know what libraries, packages, dependencies, frameworks, tools, or services a project uses — phrased as: "what libraries does this use", "what packages are installed", "what dependencies does this project have", "list all tools", "what frameworks are in use", "show me the dependencies", "what's in requirements.txt", "scan my project", "audit the stack", "inventory the project", "what's this project built with", "what tech does this use", "show all packages", "detect the stack". VISUALIZATION / DOCUMENTATION INTENT: user wants an HTML page, visual report, or summary document of the project's technology choices — phrased
askuma/generate-tech-stack · ★ 0 · Data & Documents · score 63

Install: claude install-skill askuma/generate-tech-stack

# generate-tech-stack Scan the current project and produce a complete visual tech stack page. ## Steps 1. **Locate the project root** — use the current working directory unless the user specified a path. 2. **Run the analyzer**: ```bash python3 ~/.claude/skills/generate-tech-stack/scripts/analyze.py <project_root> <project_root>/TECH_STACK.html ``` 3. **Open the output**: ```bash xdg-open <project_root>/TECH_STACK.html 2>/dev/null || open <project_root>/TECH_STACK.html 2>/dev/null || true ``` 4. **Report to the user** — include: - Number of tools detected and categories found - Clickable link to the output file - One-line per-category breakdown from the script's stdout ## Output format The generated HTML must include all of the following sections (the script produces all of them automatically): 1. **Stat row** — large number tiles: Total Tools · Categories · AI Backends (if any) · Data Stores 2. **Architecture diagram** — layered flow: - Row 1: Your Application / LLM Application (purple box) - Row 2: Web/API framework(s) (green box with auth/middleware subtitle) - Row 3: AI SDK boxes side-by-side (blue, one per backend — only if AI SDKs detected) - Row 4: Database boxes + Observability + Frontend (dark row) 3. **Bar chart summary** — horizontal bars, one per category, colour-matched 4. **Tool cards grid** — one card per category with: - Coloured icon box + category title + tool count in the header - Each tool: colour dot ·