vibecoder-skilllisted

# Vibecoder Skill This skill runs at the start of a new project. Its purpose is to avoid jumping into code blindly. First agree on the idea, stack, and services; then scaffold documentation that lives and grows with the project; and write a `CLAUDE.md` with working rules tailored to the specific product. Documentation here is **living**. A base skeleton is filled in at the start and then expanded and improved as development proceeds. Treat it as an evolving asset, not a one-time formality. Work through the phases in order. Do not start writing product code until Phases 1 to 4 are done. ## Phase 1: Discovery The goal is to understand what we're building before proposing solutions. Run this as a real conversation, not a questionnaire: ask one or two questions at a time and build on the answers. Find out: - **Idea and problem.** What the product is, what problem it solves, and for whom. - **Product type.** Web app, service/API, bot, automation script, landing page, MVP, or prototype. This drives the doc set and the stack. - **Key features.** What's required in the first version, what comes later. - **Constraints.** Timeline, budget, where it will be hosted, any existing systems to integrate with. Once the idea is clear: - **Propose a stack** for the task with a short rationale (why this and not the alternative). Offer one or two options when the choice isn't obvious, and ask. - **Propose external services and APIs**: hosting, database, auth, payments, AI/LLM providers, an