Writing-style convention applied to ALL prose output. Strict rule, no exceptions, no off-switch, no "this once it's clearer." Never use em dashes (—) or en dashes (–) as punctuation. Em dashes are the single most reliable tell that text was written by an LLM, and humans almost universally use commas, periods, semicolons, colons, or sentence restructuring in those positions instead. Hyphens (-) inside compound words (e.g., "copy-pasted", "well-known", "user-level") are fine. Em or en dashes inside proper nouns such as song titles, album names, or book chapter titles are fine. The skill body also lists secondary tells to avoid: inflated verbs ("delve", "leverage", "utilize"), boilerplate scaffolding ("it's worth noting that"), and structural tics. Auto-loads on every conversation; binds every response, plan, commit message, doc, comment, code identifier label, and chat reply you produce.
Set up VibeStack conventions for the project in the current directory, creates CLAUDE.md, Makefile, docs/, and TODO.md based on the actual codebase. Skips any of those that already exist. Run this once per project after installing VibeStack at the user level.
Set up a self-contained GitHub Actions CI workflow for the current project. Detects language(s) from the codebase (TS/JS, Python, Go, Rust) and writes `.github/workflows/ci.yml` with lint, test, and build gates. Idempotent, skips if the workflow already exists unless the user asks to reconcile.
Convention for using CLI tools and environment variables when interacting with third-party services like AWS, Vercel, Supabase, Stripe, GitHub, and Google Cloud. Auto-loads when working with external services, deployments, infrastructure, or API integrations.
Reference map of the user's local development environment, installed languages, runtimes, version managers, databases, cloud CLIs, and tools on this machine. READ this file BEFORE telling the user a tool is unavailable, BEFORE asking which deploy target / cloud / DB to use, and BEFORE proposing to install something. If a CLI is listed as installed, assume it works. If listed as not installed, don't suggest commands that depend on it without flagging the install step. If the file shows "(not yet populated)" below, run the discovery steps to fill it in on first use.
Capture conversation learnings into docs and clean up the docs folder
Strategy session with a co-founder persona, critical, constructive, and invested. Use when you want to think through an idea, decision, or direction before building. Read-only; this is a meeting, not work.
Convention for using language server tools (LSP) to get precise type info, find references, check diagnostics, and navigate definitions across files. Auto-loads when doing refactors, debugging type errors, or working across multiple files.