// Design new features, architectural changes, or refactors for the vscode-sfdx-hardis VS Code extension. Use when the user asks to plan, architect, or propose how to build something new or restructure existing code.
Implement features, bug fixes, or refactors in the vscode-sfdx-hardis VS Code extension. Use when the user asks to write code, fix a bug, add a feature, or make changes to the codebase.
Fix duplicate code issues reported by jscpd in the vscode-sfdx-hardis extension. Use when the user asks to fix, resolve, or address jscpd duplications, copy-paste detector findings, or MegaLinter COPYPASTE_JSCPD errors. Either factorizes the duplicates into shared helpers, or, when factorization would hurt clarity, adds jscpd ignore markers to silence them.
Fix security vulnerabilities reported by Trivy and OSV-Scanner in the vscode-sfdx-hardis extension. Use when the user asks to fix, triage, or address Trivy / OSV-Scanner / MegaLinter REPOSITORY_TRIVY / REPOSITORY_OSV_SCANNER findings. Tries upgrading the affected dependency first, then a yarn resolution override, and only ignores the finding if the vulnerability is genuinely non-exploitable in this extension's context.
Add a new monitoring command to the vscode-sfdx-hardis VS Code extension. Use when the user asks to add, register, or wire up a monitoring command (sf hardis:org:monitor:* or sf hardis:org:diagnose:* shown in the Org Monitoring menu and Monitoring Config Workbench).
Analyze code, architecture, data flow, or behavior in the vscode-sfdx-hardis VS Code extension. Use when the user asks to understand, trace, audit, or investigate how something works in this codebase.
Write or update documentation, tooltips, translations, and help text for the vscode-sfdx-hardis VS Code extension. Use when the user asks to document, describe, explain for users, or update README/translations.
| name | design |
| description | Design new features, architectural changes, or refactors for the vscode-sfdx-hardis VS Code extension. Use when the user asks to plan, architect, or propose how to build something new or restructure existing code. |
| compatibility | Designed for Claude Code (or similar products) |
| metadata | {"author":"cloudity","version":"1.0"} |
Design new features or architectural changes for the vscode-sfdx-hardis extension.
Understand requirements - Clarify what the feature should do and who it serves (beginner consultants vs expert developers vs both).
Map to existing architecture - Identify which components are involved:
hardis-commands-provider.ts, registration in src/commands/, icon in themeUtils.ts, i18n keys in all 9 locale filessrc/webviews/lwc-ui/modules/s/, panel command in src/commands/, message protocol designCONFIGURABLE_FIELDS + SECTIONS in src/utils/pipeline/sfdxHardisConfigHelper.ts, schema updatesrc/utils/gitProviders/ or src/utils/ticketProviders/ (interface + implementation)Address key design decisions:
command-runner.ts spawn) vs terminal vs LWC webview panelCacheManager) vs WebSocket real-timeen, fr, es, de, it, nl, ja, pl, pt-BR)Follow existing patterns:
sf hardis:category:action format (modern CLI, never legacy sfdx)TreeDataProvider pattern for tree viewsSharedMixin for all new LWC components (provides i18n + theme)Logger.log() + vscode.window.showErrorMessage()CacheManager for expensive operationsConsider integration points:
execSfdxJson() for JSON output, execCommandWithProgress() for progress UIsimpleGit() from simple-git for git operationssalesforce.salesforcedx-vscode).sfdx-hardis.yml (local or remote URL)Output a design document covering:
SFDX_HARDIS_WEBSOCKET_PORT env var).select (QuickPick) and text (InputBox). Design user input accordingly.sf hardis commands are allowed, no && chaining.