Best-practice dev-ops for an Effortless Rulebook (ERB) project: a rulebook-first pipeline promoted across up to **four tiers** — **dev** and **staging** on localhost (always fake/mock data), **beta/UAT** and **production** on a live remote server — governed by ONE migration ledger, a version that is always **derived** (never stored), and two independent axes (**DB migration version** + **code build**). Ships a **Deployment Management** admin console (the migration × environment matrix, drift/version grading, ERBVersions changelog, and the whole action rail), an environment/DB switcher, and the guardrails that keep staging & production reachable ONLY through ledger-tracked migrations. Triggers: "set up rulebook dev-ops", "deployment management page", "dev/staging/beta/production model", "promote a release", "cut a version / take a code snapshot", "migration matrix", "derive a migration from the diff", "environment switcher", "000-seed migration", "push code to production". This skill is HEAVY and meant to be i
Use when you need ERB naming conventions, DAG structure rules, PascalCase table names, primary key and foreign key patterns, the Name field requirement, or understanding why many-to-many relationships are not allowed. **Scope (load gate):** Effortless projects only — project root must contain `effortless.json` AND a CLAUDE.md identifying the project as ERB methodology. Do NOT load otherwise.
Top-level orchestrator for Effortless Rulebook (ERB) projects — rulebook-first schema-first business rules, `effortless.json` build pipelines, effortless-rulebook.json ontologies, rulebook-to-postgres code generation, or any project containing an effortless-rulebook/ directory or effortless.json file. Provides the ERB mental model, axioms, guardrails, token discipline, and routes to specialized sub-skills. Load this first on any ERB project. **Scope (load gate):** Effortless projects (project root has `effortless.json` + a CLAUDE.md identifying the project as ERB methodology), OR when the user explicitly asks to set up / install / update Effortless tooling.
Use when working with the ERB build pipeline — effortless.json configuration, transpiler catalog, effortless build commands, the -id flag, transpiler installation, or understanding how the build flows from the rulebook hub through to generated code. **Scope (load gate):** Effortless projects only — project root must contain `effortless.json` AND a CLAUDE.md identifying the project as ERB methodology. Do NOT load otherwise.
Use when querying an effortless-rulebook.json file — listing tables, extracting schema without data, finding FK relationships, inspecting calculated fields and formulas. Activates for any project with effortless-rulebook.json or effortless-rulebook/ directory. **Scope (load gate):** Effortless projects only — project root must contain `effortless.json` AND a CLAUDE.md identifying the project as ERB methodology. Do NOT load otherwise.
Use to understand the **structure** of effortless-rulebook.json — top-level keys, table objects, the field schema definition, field types (raw, calculated, lookup, relationship, aggregation), datatypes, formula syntax, and the `_meta` section. This skill is JSON-structure only; for naming / DAG / FK *rules*, use effortless-conventions. **Scope (load gate):** Effortless projects only — project root must contain `effortless.json` AND a CLAUDE.md identifying the project as ERB methodology. Do NOT load otherwise.
Use when making changes to an ERB project — modifying effortless-rulebook.json directly, editing via Airtable when connected, or running effortless build. `effortless-rulebook.json` is the hub/SSoT; Airtable, LLM-direct edits, and reverse-sync are peer input spokes. Covers the input-spoke options and permission checkpoints. **Scope (load gate):** Effortless projects only — project root must contain `effortless.json` AND a CLAUDE.md identifying the project as ERB methodology. Do NOT load otherwise.
Use ONLY for Airtable schema changes that the API cannot handle — formula fields, lookup fields, rollup fields, and new table creation (which requires the Name formula). All scalar field changes and CRUD operations go through the Airtable API directly. **Scope (load gate):** Effortless projects only — project root must contain `effortless.json` AND a CLAUDE.md identifying the project as ERB methodology. Do NOT load otherwise.