implement

To write code that adheres to existing project patterns, analyze your repository's established conventions first, make explicit implementation decisions, and code incrementally. Validate the final output against request intent and repository standards.

The best way to implement a new feature without breaking conventions is to use a structured approach: analyze existing code patterns, decide on the implementation strategy explicitly, write the code incrementally, and validate changes against project standards.

Ensure your code changes match request intent and repository standards by analyzing existing project patterns before coding, making explicit decisions during implementation, and validating the final output against the original request and established project conventions.

You need to analyze project patterns before writing code whenever you are tasked with implementing new changes, such as adding a user authentication flow. This ensures adherence to established conventions and reduces errors and maintainability issues.

Yes, guided implementation helps with incremental coding and decision clarity by providing a structured approach from analysis to validation. It prompts explicit decision-making for implementation choices and encourages finding and following existing code patterns.

Writing code without following conventions leads to maintainability issues because it ignores established repository standards. Adhering to project patterns streamlines the coding process, reduces errors, and ensures the codebase remains clean and maintainable.