Sf Datacloud
Jaganpro/sf-skills
Salesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows.
Design the solution and write a technical specification based on requirements analysis.
Install Design
$ npx skills add hardisgroupcom/sfdx-hardis --skill design -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install hardisgroupcom/sfdx-hardis design --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/hardisgroupcom/sfdx-hardis.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/design .claude/skills/design && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "design" agent skill from https://github.com/hardisgroupcom/sfdx-hardis/tree/main/.claude/skills/design into .claude/skills/design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/hardisgroupcom/sfdx-hardis/tree/main/.claude/skills/designType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add hardisgroupcom/sfdx-hardis --skill design -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install hardisgroupcom/sfdx-hardis design --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hardisgroupcom/sfdx-hardis.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/design .agents/skills/design && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "design" agent skill from https://github.com/hardisgroupcom/sfdx-hardis/tree/main/.claude/skills/design into .agents/skills/design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add hardisgroupcom/sfdx-hardis --skill design -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install hardisgroupcom/sfdx-hardis design --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hardisgroupcom/sfdx-hardis.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/design .cursor/skills/design && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "design" agent skill from https://github.com/hardisgroupcom/sfdx-hardis/tree/main/.claude/skills/design into .cursor/skills/design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/hardisgroupcom/sfdx-hardis.git --path .claude/skills/design--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add hardisgroupcom/sfdx-hardis --skill design -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install hardisgroupcom/sfdx-hardis design --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hardisgroupcom/sfdx-hardis.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/design .gemini/skills/design && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "design" agent skill from https://github.com/hardisgroupcom/sfdx-hardis/tree/main/.claude/skills/design into .gemini/skills/design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install hardisgroupcom/sfdx-hardis designInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add hardisgroupcom/sfdx-hardis --skill design -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/hardisgroupcom/sfdx-hardis.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/design .github/skills/design && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "design" agent skill from https://github.com/hardisgroupcom/sfdx-hardis/tree/main/.claude/skills/design into .github/skills/design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add hardisgroupcom/sfdx-hardis --skill design -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install hardisgroupcom/sfdx-hardis design --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hardisgroupcom/sfdx-hardis.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/design .opencode/skills/design && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "design" agent skill from https://github.com/hardisgroupcom/sfdx-hardis/tree/main/.claude/skills/design into .opencode/skills/design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
design- GitHub stars
- 400
- Token cost
- ~676 tokens
- SKILL.md length
- 321 words
- Files
- 1
- Skills in repo
- 21
- Repo updated
- First seen
- Licence
- AGPL-3.0
At a glance
Design the solution and write a technical specification based on requirements analysis.
- Works in 4 steps: Review analysis: Understand the… → Study existing patterns: Read similar… → Design the solution → …
- Sales & Support work in your project
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Design is an agent skill from hardisgroupcom/sfdx-hardis. Design the solution and write a technical specification based on requirements analysis. Second step of the contribution workflow, use after /analyze.
Its SKILL.md is about 680 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Sales & Support. It works with Salesforce. The repository describes itself as: French-army-knife Toolbox for Salesforce. Orchestrates base commands and assist users with interactive wizards to make much more than native Salesforce CLI + Allows you to define…. The licence is AGPL-3.0.
When your agent uses it
- Sales & Support work in your project
Example prompts
- “/design”
Requirements
- Pre-approved tools (allowed-tools): Read, Glob, Grep
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Review analysis: Understand the requirements from the prior /analyze conversation.
- Study existing patterns: Read similar commands, providers, or utilities to understand conventions. Check .claude/rules/ for coding and…
- Design the solution
- Write tech spec
What it can do on your machine
Read from SKILL.md and the folder at commit 971ac89. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadGlobGrep
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Design loads about 676 tokens when it runs. Until then it costs about 39 tokens; SKILL.md has 321 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from hardisgroupcom/sfdx-hardis at commit 971ac89, republished under its AGPL-3.0 licence (© hardisgroupcom). 321 words, ~676 tokens.
Download SKILL.mdSave it as
.claude/skills/design/SKILL.md (or your agent's skills folder).- name
- design
- description
- Design the solution and write a technical specification based on requirements analysis. Second step of the contribution workflow, use after /analyze.
- 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.
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.)
- 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)andconst 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
- Plan the vscode-sfdx-hardis side with the
vscode-sfdx-hardisskill and the extension's owndesignskill: which panel, command entry or WebSocket event changes, and which CLI flags or--jsonfields the UI needs so the terminal and the extension behave the same
- 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
- VS Code extension impact: Files to change in vscode-sfdx-hardis (following its
CLAUDE.md), CLI flags / JSON / events it relies on, minimum CLI version bump, or "none" with the reason - Risks: Potential issues or trade-offs
Do NOT implement anything. Produce only the design document for user review.
$ARGUMENTS
© hardisgroupcom, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/design of hardisgroupcom/sfdx-hardis.
Open the folder on GitHubat commit 971ac89
Compare with similar skills
Design next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Design this skillhardisgroupcom/sfdx-hardis | 400 | — | ~676 | Automated safety check: Pass | AGPL-3.0 | |
| Sf DatacloudJaganpro/sf-skills | 424 | — | ~2.7k | Automated safety check: Pass | MIT | |
| Sf Datacloud ActJaganpro/sf-skills | 424 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Sf Datacloud ConnectJaganpro/sf-skills | 424 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Sf Datacloud HarmonizeJaganpro/sf-skills | 424 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Consumer Goods Accruals Datakit Deployforcedotcom/sf-skills | 1.1k | — | ~5.1k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Sf Datacloud Act
Jaganpro/sf-skills
Salesforce Data Cloud Act phase. An agent skill from Jaganpro/sf-skills.
Sf Datacloud Connect
Jaganpro/sf-skills
Salesforce Data Cloud Connect phase. An agent skill from Jaganpro/sf-skills.
Sf Datacloud Harmonize
Jaganpro/sf-skills
Salesforce Data Cloud Harmonize phase. An agent skill from Jaganpro/sf-skills.
Consumer Goods Accruals Datakit Deploy
forcedotcom/sf-skills
A skill your agent uses to deploy the TPM Liability Accruals data kit end to end to a Salesforce org.
Platform Trust Archive Manage
forcedotcom/sf-skills
ALWAYS USE THIS SKILL for anything involving Salesforce Archive (also called Trusted Services Archive) — search, view, unarchive, analyze, mask, and erase (RTBF) archived records via the Archive…
More from hardisgroupcom/sfdx-hardis
All 21 skills in this repoPromotion Branches E2E Test
hardisgroupcom/sfdx-hardis
Runs a full end-to-end test of sfdx-hardis promotion branches and backpromote against real Salesforce orgs and a throwaway repository, then writes a report.
sfdx-hardis Training End-to-End Test
hardisgroupcom/sfdx-hardis
Walks the sfdx-hardis training course end to end as a learner would, against a real Developer Edition org and fork, fixing broken steps and screenshots that no longer match.
sfdx-hardis Architecture Guide
hardisgroupcom/sfdx-hardis
Explains how the sfdx-hardis Salesforce CLI plugin is built: its TypeScript and Oclif stack, command layout, agent-mode flag and provider classes for git, notifications and AI.
Changelog Style Rules
hardisgroupcom/sfdx-hardis
Style rules for adding CHANGELOG.md entries: short, user-facing bullets grouped by command under the beta section, each linking the command's docs page.
Documentation
hardisgroupcom/sfdx-hardis
Documentation standards for sfdx-hardis commands (description format with Command Behavior and Technical explanations sections, MkDocs site, build:doc).
Fix Jscpd
hardisgroupcom/sfdx-hardis
Decision framework for fixing jscpd (copy-paste detector) errors.
Related
Works with
Categories
Questions about Design
What does Design do?
Design the solution and write a technical specification based on requirements analysis. Design is an agent skill from hardisgroupcom/sfdx-hardis. Design the solution and write a technical specification based on requirements analysis.
When should I use Design?
Design fits situations like: sales & Support work in your project.
How do I install Design in Claude Code?
Run `npx skills add hardisgroupcom/sfdx-hardis --skill design -a claude-code`. Or copy the skill folder (.claude/skills/design in hardisgroupcom/sfdx-hardis) into .claude/skills/design in your project. Claude Code loads it when a task matches its description.
How do I install Design in Codex?
Run `npx skills add hardisgroupcom/sfdx-hardis --skill design -a codex`. Or copy the skill folder (.claude/skills/design in hardisgroupcom/sfdx-hardis) into .agents/skills/design in your project. Codex loads it when a task matches its description.
Can I use Design in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add hardisgroupcom/sfdx-hardis --skill design -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/design, .gemini/skills/design, .github/skills/design and .opencode/skills/design in your project.
What does Design need to run?
SKILL.md names no scripts, command-line tools or credentials: Design is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Glob, Grep.
Does Design access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Design safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Design use?
Design is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Design use?
About 676 tokens (SKILL.md is roughly 2.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Design?
Skills that share tags, products or a category with Design: Sf Datacloud (Jaganpro/sf-skills, 424 stars), Sf Datacloud Act (Jaganpro/sf-skills, 424 stars), Sf Datacloud Connect (Jaganpro/sf-skills, 424 stars) and Sf Datacloud Harmonize (Jaganpro/sf-skills, 424 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Design?
hardisgroupcom (a GitHub organization) maintains it in hardisgroupcom/sfdx-hardis, which has 400 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 7, 2026.
Source: hardisgroupcom/sfdx-hardis on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.