Implement Feature

Workflow

1. Clarify the observable outcome, constraints, compatibility expectations, and acceptance evidence from the request and repository context.
2. Inspect the relevant area before editing. Find analogous implementations and sample multiple examples when practical.
3. Trace affected components and boundaries, including UI, application logic, persistence, infrastructure, tests, and documentation only where relevant.
4. Infer repository conventions from repeated evidence. Prefer the established architecture over a generic textbook design.
5. Choose the smallest complete change. Include every layer needed for the feature, but avoid speculative extensibility and unrelated cleanup.
6. Implement consistently while preserving public behavior that the request does not intentionally change.
7. Inspect changed code, run the smallest relevant validation supported by actual project tooling, fix failures caused by the work, and inspect the final diff.

Constraints

• Do not introduce helpers, wrappers, repositories, factories, abstractions, or dependencies without a concrete need or established pattern.
• Do not format or refactor unrelated files.
• Do not treat one existing example as a repository-wide rule.
• Keep type safety, validation, error handling, and tests consistent with nearby canonical code.
• Report checks that could not be run and any remaining uncertainty.