PolicyEngine

Recharts chart patterns, formatting, and styling for PolicyEngine apps

PolicyEngine code writing style guide - formula optimization, direct returns, eliminating unnecessary variables

PolicyEngine parameter patterns - YAML structure, naming conventions, metadata requirements, federal/state separation

PolicyEngine code review patterns - validation checklist, common issues, review standards

PolicyEngine testing patterns - YAML test structure, naming conventions, period handling, and quality standards

PolicyEngine variable patterns - variable creation, no hard-coding principle, federal/state separation, metadata standards

Reference for the /create-dashboard and /deploy-dashboard orchestrated AI workflow

Mandatory frontend technology requirements for PolicyEngine dashboards and interactive tools — Tailwind CSS v4, Next.js (App Router), @policyengine/ui-kit theme, Vercel deployment

Sensitivity registry for PolicyEngine microsim results — maps {program × deviation signature} to the most likely calibration target or imputed variable driving the mismatch. The knowledge base that powers the calibration-diagnostics agent. Load when investigating why a microsim result differs from a prior score, or when reviewing whether a reform classification is calibration-sensitive. Triggers: "why does my reform not match", "policyengine cost off", "calibration mismatch", "imputed variable", "takeup rate", "non-filer", "itemizer share", "small state variance", "ECPS calibration target", "policyengine-us-data target", "calibration dashboard", "diagnose mismatch", "deviation signature".

Structured index of PolicyEngine's previously-published scored reforms. Use this skill to find an anchor for Stage 5 comparison in /analyze-policy, or any time you need a benchmark magnitude for a new policy analysis. Returns a queryable mapping of {reform name → (cost, poverty, distribution, year, methodology)} drawn from policyengine.org/{us,uk,canada}/research and blog.policyengine.org. Triggers: "prior PE score", "PolicyEngine has scored", "what did PE find", "PE benchmark", "anchor reform", "comparable reform", "EITC expansion scored", "CTC expansion scored", "SALT cap analysis", "state CTC analysis", "ARPA reform impact", "American Family Act score".

PolicyEngine API v2 - Next-generation microservices architecture with monorepo structure

ALWAYS LOAD THIS SKILL before setting up any Python environment or installing packages. Defines the standard: uv, Python 3.13, uv pip install, .venv at project root. Triggers: "set up python", "install python", "create a venv", "virtual environment", "pip install", "install packages", "uv pip", "uv venv", "python version", "VIRTUAL_ENV", "venv conflict", "which python", "activate", "deactivate", "run the script", "run with uv", "uv run", "pyproject.toml", "install dependencies", "install requirements", "install the package", "editable install", "pip install -e", "latest package", "latest version", "current version", "newest version".

ALWAYS USE THIS SKILL for PolicyEngine microsimulation, population-level analysis, winners/losers calculations. Triggers: microsimulation, share who would lose/gain, policy impact, national average, weighted analysis, cost, revenue impact, budgetary, estimate the cost, federal revenues, tax revenue, budget score, how much would it cost, how much would the policy cost, total cost of, aggregate impact, cost to the government, revenue loss, fiscal impact, poverty impact, child poverty, deep poverty, poverty rate, poverty reduction, how many people lifted out of poverty, SPM poverty, distributional impact, state tax, state-level, California, New York, UBI, universal basic income, flat tax, standard deduction, winners and losers, winners, losers, inequality, Gini, decile, SALT, marginal tax rate, effective tax rate. NOT for single-household calculations like "what would my benefit be" - use policyengine-us or policyengine-uk for those. Use this skill's code pattern; explore codebase for parameter paths if needed.

ONLY use this skill when users explicitly ask about the PolicyEngine Python package installation, REST API endpoints, API authentication, rate limits, or policyengine.py client library. DO NOT use for household benefit/tax calculations — ALWAYS use policyengine-us or policyengine-uk instead. This skill is about the API/client tooling itself, not about calculating benefits or taxes.

ALWAYS LOAD THIS SKILL FIRST before writing PolicyEngine-Canada code or answering household-level Canadian tax/benefit questions. Covers federal/provincial rules for household calculations. IMPORTANT: no representative population microdata; do NOT attempt microsimulation or population-level estimates. Only household-level analysis. Triggers: what would, how much would a, benefit be, eligible for, qualify for, single parent, married couple, family of, household of, if they earn, earning $, making $, calculate benefits, calculate taxes, benefit for a, what would I get, maximum, rate, income limit, benefit amount, compare provinces, CCB, Canada Child Benefit, GST credit, HST credit, GST/HST, OAS, GIS, CWB, Canada Workers Benefit, EI, CPP, Ontario Child Benefit, OCB, OTB, BC Climate Action, Alberta Child Benefit, Quebec, CRA, Canadian, Canada, Ontario, British Columbia, Alberta, Saskatchewan, Manitoba, Nova Scotia, New Brunswick, PEI, Newfoundland, Yukon, NWT, Nunavut, provincial tax, federal tax Canada.

Use when the user invokes $encode-policy-v2 or asks Codex to implement a new PolicyEngine-US state benefit program from official rules. Covers research, source collection, requirement extraction, scoped implementation, tests, validation, and draft PR preparation.

This skill should be used when the user asks about "local development setup", "how to run locally", "set up the project", "install dependencies", "start the API", "configure environment", "deploy to production", "production setup", "GCP setup", "Terraform setup", "GitHub secrets", "GitHub environments", "Modal setup", "Supabase setup", "seed the database", "initialize database", "docker compose", "workload identity federation", "WIF setup", "service account setup", "deploy pipeline", "staging environment", "custom domain", "environment variables", ".env setup", "rollback a deploy", "run tests locally", or needs to understand how to get the project running from scratch. Also relevant when onboarding a new developer or setting up a new deployment.

This skill should be used when the user asks about "database deployment", "how migrations run in production", "deploy.yml database step", "db-reset workflow", "why no create_all", "RLS policies deployment", "alembic in CI/CD", "lock_timeout", "seeding production", "init.py vs alembic", or needs to understand how schema changes reach the production Supabase database. Also relevant when modifying deploy.yml, db-reset.yml, alembic/env.py, or scripts/init.py.

This skill should be used when modifying the ui-kit's CSS theme, adding new design tokens, creating new component styles, or working on the ui-kit's build pipeline and package exports. Triggers: "add token", "design token", "theme.css", "tokens.css", "@theme", "ui-kit styling", "add color", "add spacing", "component style", "base styles", "ui-kit architecture", "how do Tailwind UI kits work", "authoring pattern", "@source", "package exports"