implement

Implement code changes per design specs in the sfdx-hardis project.

368|98|Updated Jan 25, 2021

Search Tags:#workflow #design #devops #contribution #code #implement #sfdx-hardis

Ready to run

npx skills add https://github.com/hardisgroupcom/sfdx-hardis --skill implement-hardisgroupcom

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/hardisgroupcom/sfdx-hardis/tree/main/.claude/skills/implement
Command: npx skills add https://github.com/hardisgroupcom/sfdx-hardis --skill implement-hardisgroupcom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides developers to implement code changes following the approved design specification within the sfdx-hardis project, ensuring alignment with repository rules and conventions.

Core Features & Use Cases

Follow the /design directives and project conventions to implement changes in the correct files and modules.
Consult .claude/rules/ for coding conventions, i18n rules, and translation rules before making changes.
Ensure changes are modularized per command file: only command class declarations remain in src/commands files; interfaces, types, and helpers moved to utility modules.

Quick Start

Review the prior design discussion and implement code changes following the project conventions.

Frequently Asked Questions about implement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I implement code changes following an approved design specification?▼

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.

What coding conventions do I need to follow for sfdx-hardis contribution workflows?▼

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.

How do I modularize command files when implementing code changes in a DevOps project?▼

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.

Do I need a prior design discussion before I can implement code changes?▼

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.

Why does my code implementation fail the repository rules check?▼

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.

When should I use the provider pattern 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.