Add dataset selection delegation pattern to API skill #23
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Documents the pattern of delegating dataset selection to policyengine.py by returning
Nonefrom the API, rather than hardcoding dataset paths in the API layer.Context
This pattern emerged from PR #2953 in policyengine-api, where we moved from explicitly specifying state-specific datasets in the API to delegating that responsibility to policyengine.py. This improves separation of concerns.
Changes
Added new "Dataset Selection Pattern" section to
policyengine-api-skillthat explains:Nonevs when to specify explicit datasetsWhy this matters
Future Claude sessions working on dataset selection will understand:
🤖 Generated with Claude Code