메뉴
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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | cli-first |
| description | 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. |
| user-invocable | false |
When interacting with third-party services, always prefer CLI tools over web dashboards, REST APIs, or connector plugins.
Before making API calls or using SDKs directly, check .env* files for existing credentials and project configuration.
# Check for environment files in this order:
# 1. .env.local , local overrides (gitignored, highest priority)
# 2. .env , shared project defaults
# 3. .env.development / .env.production, environment-specific
Look for:
Never hardcode credentials. If a needed credential isn't in .env*, ask the user to add it rather than creating one.
When these CLIs are available, use them instead of raw API calls:
| Service | CLI | Common Uses |
|---|---|---|
| AWS | aws | S3, Lambda, CloudFormation, IAM, ECR, ECS |
| Vercel | vercel | Deploy, env vars, domains, project settings |
| Supabase | supabase | DB migrations, edge functions, auth config |
| GitHub | gh | Issues, PRs, releases, Actions, repo settings |
| Stripe | stripe | Webhooks, test events, product/price setup |
| Google Cloud | gcloud | Compute, Cloud Run, IAM, storage, pub/sub |
| Firebase | firebase | Hosting, Firestore rules, functions |
| Cloudflare | wrangler | Workers, KV, R2, DNS |
command -v <tool> or which <tool>.env* files for project credentials and configurationwhoami or status commandextras/ for the dev tools installer) rather than working around it with raw HTTP calls# Instead of visiting the Vercel dashboard to add an env var:
vercel env add MY_SECRET production
# Instead of clicking through AWS console to upload to S3:
aws s3 cp ./dist s3://my-bucket/ --recursive
# Instead of using the Supabase web UI to run a migration:
supabase db push
# Instead of manually creating a GitHub release:
gh release create v1.0.0 --generate-notes
# Instead of configuring Stripe webhooks in the dashboard:
stripe listen --forward-to localhost:3000/api/webhooks
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.
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.