implement

To implement code changes following an approved design specification, review the prior design directives and apply modifications to the correct files while strictly adhering to project conventions like modularization and i18n rules.

sfdx-hardis contribution workflows require consulting .claude/rules/ for coding and translation conventions, ensuring command files only contain class declarations while interfaces, types, and helpers move to utility modules.

To modularize command files when implementing code changes, keep only command class declarations in the src/commands files and move all interfaces, types, and helper functions into separate utility modules.

Yes, you need a prior design discussion before you implement code changes. The implementation process requires following approved design directives to ensure alignment with repository rules across the contribution workflow.

Your code implementation may fail repository rules if it lacks adherence to project conventions, such as proper modularization, i18n translation rules, or the provider pattern required for external integrations.

You should use the provider pattern for external integrations whenever your code implementation involves connecting to outside services, as it is a required project convention for maintaining modular and compliant architecture.