devopser-setup

DevOpser Setup

Expert guidance for bringing the DevOpser self-evolving software template up on a developer laptop. Reuses the repo's own scripts/setup.sh and run-migrations.sh — this skill does not introduce new scripts. The canonical playbook is AGENTS.md → "Quick setup (for AI agents)"; the README's "Opinionated variant (Bedrock, nothing to decide)" is the house style for rigor.

Rules

Rule	Description
prerequisites	Tool versions, port pre-flight, npm-cache ownership, aws sts get-caller-identity
llm-provider	Bedrock vs OpenAI vs Anthropic — ask once, never guess. MFA-session export pattern
email	Gmail SMTP vs SES vs leave-disabled (default for local dev)
verification	The four-check gate — do not report success without it

Key principles

• Defer to AGENTS.md. If this skill contradicts it, AGENTS.md wins — report the contradiction to DevOpser.
• Definition of done is the four-check verification gate, not "the process booted." See verification.md.
• Ask the user exactly once which LLM provider they want. Never guess, never default silently. See llm-provider.md.
• Relay prerequisite errors verbatim — do not paraphrase stack traces, exit codes, or port-conflict output. The setup script is designed to emit copy-pasteable fix commands.

Quick reference

Situation	Go to
Fresh clone, need to decide the provider	llm-provider.md
./scripts/setup.sh fails on Node / Docker / Postgres / port	prerequisites.md
npm install fails with EACCES on ~/.npm/_cacache	prerequisites.md → "npm cache ownership"
Bedrock chat fails with security token invalid	llm-provider.md → "MFA-protected IAM"
Gmail Missing credentials warning on boot	email.md
Before you say "done"	verification.md

Conflict resolution

If AGENTS.md contradicts this skill, AGENTS.md wins — report the contradiction to DevOpser.