policyengine-variable-patterns

Create PolicyEngine variables with parameterized values and legal citations.

31|6|Updated Oct 19, 2025
One-click install
npx skills add https://github.com/PolicyEngine/policyengine-claude --skill policyengine-variable-patterns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: policyengine-variable-patterns
Source: https://github.com/PolicyEngine/policyengine-claude/tree/main/skills/technical-patterns/policyengine-variable-patterns-skill
Command: npx skills add https://github.com/PolicyEngine/policyengine-claude --skill policyengine-variable-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill codifies naming conventions and patterns for PolicyEngine variables to support consistency and regulatory traceability.

Core Features & Use Cases

  • Prefix conventions: State/program-based prefixes for variables.
  • Standard components: Use adds, thresholds, and demographic variables consistently.
  • Use Case: Organize a complex program with multiple components (income, eligibility, resources) using unified naming.

Quick Start

Apply the standard {state}_{program} prefix to a new variable and its sub-variables.

Frequently Asked Questions about policyengine-variable-patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I name PolicyEngine variables consistently across state and federal programs?

Apply standard naming patterns using state and program prefixes to encode government benefit rules without hard-coded constants. This ensures consistency, regulatory traceability, and unified organization across eligibility calculations, deductions, resource limits, and metadata across multiple programs.

What naming conventions should I use for eligibility calculations and deductions in benefit programs?

Use prefix conventions based on state and program identifiers, then standardize components like adds, thresholds, and demographic variables. This approach parameterizes every numeric value, traces implementations to legal citations, and enforces architecture constraints for single-period simulation.

How do I organize complex benefit programs with multiple income and resource components?

Apply the {state}_{program} prefix pattern to your base variable and all sub-variables covering income, eligibility, and resources. This unified naming structure supports consistency across components while maintaining regulatory documentation and avoiding forbidden features.

Can I use variable naming patterns to enforce compliance requirements in government benefit calculations?

Yes. Standard naming patterns enable parameterization of all numeric values, document time-bound deduction limitations, and enforce single-period simulation constraints. This design supports regulatory traceability and compliance verification across federal and state programs.

What are the limitations of using fixed naming patterns for variables in benefit eligibility systems?

Patterns enforce single-period simulation and restrict certain architectural features to maintain compliance. Document any time-bound deductions and program-specific constraints within your naming structure to capture design limitations and ensure implementations remain traceable to legal citations.