zero-logement-vacant

Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.

Move issues through a state machine of triage roles — categorise, reproduce, grill if needed, and write agent-ready briefs.

Publish a French-language LOVAC import report to Notion after all subcommands and snapshots are complete. Reads snapshot-*-pre.json / snapshot-*-post.json and *.report.json files from the current directory.

ZLV production deploy summary workflow. Use when preparing a production release (mise en production): writing the GitHub deploy PR summary, finding Notion tickets, and creating the corresponding Notion release note page.

Use when adding or modifying a Dagster asset, job, schedule, or resource in `analytics/dagster/`. Enforces ZLV asset key conventions, the CustomizedDagsterDbtTranslator contract, retry/resource wiring, and a validate→materialize verification loop. Trigger phrases: "add a dagster asset", "new ingest pipeline", "schedule a refresh", "create a multi_asset".

Use when adding or modifying a dbt model in `analytics/dbt/`. Enforces ZLV layer/naming rules, ref()/source() discipline, schema.yml docs+tests, and a compile→run→test verification loop. Trigger phrases: "add a dbt model", "modify staging/intermediate/marts", "create stg_/int_/marts_…".

Use to onboard a new external dataset (data.gouv.fr, INSEE, DGFIP, DGALN, CEREMA, URSSAF, S3 Cellar) into the ZLV warehouse end-to-end: register the source, validate, materialize via Dagster, and expose to dbt. Trigger phrases: "add a new external source", "ingest a new dataset", "onboard data.gouv.fr file", "register a CEREMA file".

Use to investigate the ZLV data warehouse on MotherDuck (`dwh`) — list tables, inspect columns, run scoped queries, profile distributions, validate KPIs. Trigger phrases: "explore data", "check the warehouse", "how many rows", "what's the distribution of …".

ZLV feature development workflow orchestrator. Use when starting any frontend, backend, or fullstack feature. Inputs: optional Figma URL, optional PO ticket/instructions. Brainstorming is mandatory when no instructions are provided.