rule-map

Rule lookup maps the applicable rule set for your current task so you can identify governing guidance quickly. It routes constraints based on task type, showing you which standards matter most without reading the full manual first.

Conflict resolution clarifies which always-on rules take priority when overlapping guidance appears to disagree. It checks precedence between operating constraints, helping you apply the correct rules and avoid policy conflicts during development.

Task-specific constraints apply when starting new code, switching task types, or touching unfamiliar files. You need to check them for React, async, testing, Zod schemas, and dependency injection to ensure your work follows the correct operating constraints.

Consulting the rule map before starting new work applies the correct naming, import, and error handling standards. It identifies always-on posture and agent-discipline rules alongside task-specific guidance so you can work within the right guardrails.

Rule-map works with file I/O, logging, and dependency injection constraints by mapping the applicable rule set for these task types. It identifies the specific operating constraints and standards that apply to your current work in the repository.

Rule precedence matters when touching unfamiliar code because overlapping guidance can create policy conflicts. Mapping the applicable rule set clarifies which always-on rules take priority, ensuring you apply the correct operating constraints and avoid violations.