The permits API package needs conventions that should apply when working under src/api. What should the team create?
Select an answer to reveal the explanation.
Short Explanation
API house rules belong on the API floor, not taped to every department door. A path-specific rule aimed at src/api keeps permits API conventions where that package lives.
Full Explanation
The permits API package needs conventions that apply when working under src/api. The team should create a path-specific rule file scoped to the src/api path for that package so permits API standards load in the right place without polluting unrelated civic packages.
A path-specific rule scoped to src/api works because permits API conventions—routing, auth middleware, error envelopes, OpenAPI expectations—belong with API work. Engineers editing under that path receive the standards automatically; parks, transit, or docs packages do not inherit API-only rules. The rule remains versioned for the whole permits team.
A user-only sticky note that never enters the repository fails because shared package conventions must travel with the repo for every engineer and contractor. A root CLAUDE.md entry that also overrides parks and transit packages globally fails by broadening API rules into always-on or repo-wide instruction that fights package-local realities. An Explore subagent that rewrites API standards on every cold start fails by concept: Explore is for discovery summaries, not for owning durable package conventions; regenerating standards each start creates drift and nondeterminism.
Exam caveat: path-specific rules are configuration, not agents; do not use Explore or root CLAUDE.md as a substitute for scoped package rules. Operational check: edit under src/api and confirm permits API rules load; edit outside that path and confirm they stay out of context.