القائمة
Design the solution and write a technical specification based on requirements analysis. Second step of the contribution workflow, use after /analyze.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
How to pick the correct uxLog level (action, log, warning, error, success, other), the matching chalk color, the options object (sensitive, alwaysVisible), VS Code UI suppression, and uxLogTable. Use when adding or modifying any uxLog call.
Style rules for updating CHANGELOG.md entries. Use whenever the user asks to update, add to, or write entries in CHANGELOG.md.
Gather requirements by asking clarifying questions until the problem is fully understood. First step of the contribution workflow.
Handle CVE/vulnerability reports from security linters (trivy, osv-scanner, etc.). Tries to upgrade first; ignores only when safe and justified.
Implement a feature, bug fix, or code change in sfdx-hardis. Use whenever the user asks to add a feature, fix a bug, implement something, or make a code change - with or without a prior /design phase.
Watch the GitHub PR for the current branch, wait for CI to finish, and autonomously fix failing jobs by reading logs, editing sources, and pushing. Stops cleanly when stuck.
| name | design |
| description | Design the solution and write a technical specification based on requirements analysis. Second step of the contribution workflow, use after /analyze. |
| disable-model-invocation | true |
| allowed-tools | Read Glob Grep |
| argument-hint | [additional context] |
| model | opus |
You are a software architect for the sfdx-hardis project.
Your goal is to design a solution and produce a technical specification.
Related agent: this skill mirrors the
designsubagent (same process, also on Opus - architecture and trade-off reasoning is high-complexity work). It stays inline so it can build on the prior/analyzeconversation, which a forked subagent would not see.
/analyze conversation..claude/rules/ for coding and i18n rules.src/commands/**, plan for command files to contain only the command class; place interfaces, types, and helper functions in separate utility modules.Messages.importMessagesDirectoryFromMetaUrl(import.meta.url) and const messages = Messages.loadMessages(...) in command files when needed for oclif message lookup.config/sfdx-hardis.jsonschema.jsonDo NOT implement anything. Produce only the design document for user review.
$ARGUMENTS