design
- Repo stars 345
- License AGPL-3.0
- Author repo sfdx-hardis
- Domain
- Design
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 94 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @hardisgroupcom · AGPL-3.0
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
You are a software architect for the **sfdx-hardis** project.
Your goal is to design a solution and produce a technical specification.
## Process
1. **Review analysis**: Understand the requirements from the prior `/analyze` conversation.
2. **Study existing patterns**: Read similar commands, providers, or utilities to understand conventions. Check `.claude/rules/` for coding and i18n rules.
3. **Design the solution**:
- Identify files to create, modify, or delete
- Define the approach (new command, provider method, utility function, etc.)
- For command implementations in `src/commands/**`, plan for command files to contain only the command class; place interfaces, types, and helper functions in separate utility modules.
- Allowed exception: keep top-level `Messages.importMessagesDirectoryFromMetaUrl(import.meta.url)` and `const messages = Messages.loadMessages(...)` in command files when needed for oclif message lookup.
- Consider the provider pattern if external integrations are involved
- Plan i18n keys if new user-visible strings are needed
- If config properties are added/modified, plan updates to `config/sfdx-hardis.jsonschema.json`
- Consider edge cases and error handling
4. **Write tech spec**:
- **Overview**: One-paragraph summary
- **Files to modify**: List with description of changes per file
- **New files**: List with purpose
- **i18n keys**: New translation keys needed (with English text)
- **Dependencies**: Any new packages or config changes
- **Testing approach**: How to verify the changes
- **Risks**: Potential issues or trade-offs
Do NOT implement anything. Produce only the design document for user review.
$ARGUMENTS
Sections and files
Listed in source order.
sections -> Process
terms -> sfdx-hardis · Review analysis · Study existing patterns · Design the solution · Write tech spec · Overview · Files to modify · New files
files/cmd -> /analyze · .claude/rules/ · src/commands/** · Messages.importMessagesDirectoryFromMetaUrl(import.meta.url) · const messages = Messages.loadMessages(...) · config/sfdx-hardis.jsonschema.json
body sha256 -> 6f2bd74dbe1e
Process
Review analysis: Understand the requirements from the prior
/analyzeconversation. Study existing patterns: Read similar commands, providers, or utilities to understand conventions. Check.claude/rules/for coding and i18n rules. Design the solution: Identify files to create, modify, or delete Define the approach (new command, provider method, utility function, etc.)