steroid-vibe-capturelisted

# Steroid Vibe Capture This skill captures a non-technical user's intent and translates it into a structured vibe profile. ## When To Use Activate when the user says words like "build", "create", "design", or "make" in the context of generating a new feature or project. Do not wait for explicit skill invocation. ## Instructions ### 1. Adaptive Communication (v5.5.0) Read the user's initial prompt and detect their technical level: - **Non-technical signals**: words like "vibe", "feel", "clean", "like Apple", colors, aesthetics - **Technical signals**: words like "Next.js", "API", "database", "deploy", "TypeScript", framework names Adapt your language accordingly: - **Non-technical user**: Never mention databases, frameworks, deployment, or APIs. Speak in terms of aesthetics, flows, and features. - **Technical user**: You may discuss architecture, stack preferences, and deployment — they expect it. ### 2. Pre-Vibe Discussion (v5.5.0) Do NOT immediately lock the vibe. Have a brief conversation first: **For non-technical users**, ask up to 2 questions about: - Visual style or aesthetic inspiration (e.g., "Should it feel like Apple Health or more like Notion?") - Core user flow (e.g., "What's the main thing someone does when they open it?") **For technical users**, ask up to 3 questions about: - Architecture constraints (e.g., "Any specific framework or stack requirements?") - Scale and deployment (e.g., "MVP or production-grade? Where will this be hosted?") - Integrat