From cwp-how-i-vibe
Analyzes your current project and interviews you about technology preferences to create or update a tech stack document. If /docs/tech-stack.md already exists, updates it with any changes. Use when starting a new project, documenting an existing codebase, or updating technology choices.
How this command is triggered — by the user, by Claude, or both
Slash command
/cwp-how-i-vibe:create-tech-stackThe summary Claude sees in its command listing — used to decide when to auto-load this command
# Tech Stack - Technology Stack Documentation Creates or updates a comprehensive technology stack document by analyzing your current project and interviewing you about your preferences and requirements. ## Process ### 1. Check for Existing Tech Stack First, check if `/docs/tech-stack.md` already exists. If it does: - Read the existing document to understand current decisions - Use it as a baseline for the interview (confirm or update each section) - Preserve any custom sections or notes the user has added ### 2. Analyze Current Project Examine the existing codebase to understand: - Cu...
Creates or updates a comprehensive technology stack document by analyzing your current project and interviewing you about your preferences and requirements.
First, check if /docs/tech-stack.md already exists. If it does:
Examine the existing codebase to understand:
Use the AskUserQuestion tool to gather preferences and requirements. Ask about:
Project Goals & Scale
Frontend Preferences (if applicable)
Backend Preferences (if applicable)
Infrastructure & Deployment
Development Experience
Based on analysis and user input, recommend:
Create or update /docs/tech-stack.md with:
/docs/tech-stack.md - Complete technology stack documentation (created or updated)# Technology Stack
## Architecture Overview
[High-level architecture diagram/description]
## Frontend Stack
- Framework: React 19 with TypeScript
- Build Tool: Vite
- UI Component Library: ShadCN/UI
- Styling: TailwindCSS
- State Management: TanStack Query + Zustand
## Backend Stack
- Runtime: Node.js/Bun
- Framework: Hono
- Database: PostgreSQL
- Cache: Redis
- Authentication: Clerk
## Infrastructure
- Hosting: Cloudflare Workers
- Database Hosting: Convex / Supabase
- CDN: Cloudflare
- Email: Resend / SendGrid
## Development Tools
- Package Manager: Bun
- Linter: Biome
- Type Checking: TypeScript Strict Mode
- Testing: Vitest + Testing Library
- CI/CD: GitHub Actions
## Decision Rationale
[Detailed rationale for each choice]
## Trade-offs & Alternatives
[Document what else was considered and why it was rejected]
npx claudepluginhub codewithpassion/plugin-marketplace --plugin cwp-how-i-vibe/init-tech-stackGuides users through interactive prompts to define a project's tech stack, then generates a structured docs/tech-stack.md file.
/create-tech-stackAnalyzes codebase and configs to generate tech stack documentation covering technologies, architecture, patterns, and deployment details via interactive Q&A. Saves to .claude/skills/2-tech-stack.mdc.
/initDetects project tech stack from root files (Shopify priority, then Next.js, React, etc.) and creates or updates project.json.
/startInitializes a new project repository with stack definition, project structure, and team configuration. Interviews the founder to determine repo type (hub or service) and tech stack.
/research-itResearches optimal 2026 tools, dependencies, architecture patterns, and dev tooling for your project description or codebase, generating concise RESEARCH.md