Agent skill

sfdx-hardis Architecture Guide

by hardisgroupcom in 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.

AGPL-3.0Auto-check passedDevelopment

Install sfdx-hardis Architecture Guide

skills CLI

$ npx skills add hardisgroupcom/sfdx-hardis --skill architecture -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install hardisgroupcom/sfdx-hardis architecture --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/hardisgroupcom/sfdx-hardis.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/architecture .claude/skills/architecture && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "architecture" agent skill from https://github.com/hardisgroupcom/sfdx-hardis/tree/main/.claude/skills/architecture into .claude/skills/architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture", 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

$skill-installer install https://github.com/hardisgroupcom/sfdx-hardis/tree/main/.claude/skills/architecture

Type 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.

skills CLI

$ npx skills add hardisgroupcom/sfdx-hardis --skill architecture -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install hardisgroupcom/sfdx-hardis architecture --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/hardisgroupcom/sfdx-hardis.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/architecture .agents/skills/architecture && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "architecture" agent skill from https://github.com/hardisgroupcom/sfdx-hardis/tree/main/.claude/skills/architecture into .agents/skills/architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture", 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.

skills CLI

$ npx skills add hardisgroupcom/sfdx-hardis --skill architecture -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install hardisgroupcom/sfdx-hardis architecture --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/hardisgroupcom/sfdx-hardis.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/architecture .cursor/skills/architecture && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "architecture" agent skill from https://github.com/hardisgroupcom/sfdx-hardis/tree/main/.claude/skills/architecture into .cursor/skills/architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture", 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

$ gemini skills install https://github.com/hardisgroupcom/sfdx-hardis.git --path .claude/skills/architecture

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add hardisgroupcom/sfdx-hardis --skill architecture -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install hardisgroupcom/sfdx-hardis architecture --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/hardisgroupcom/sfdx-hardis.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/architecture .gemini/skills/architecture && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "architecture" agent skill from https://github.com/hardisgroupcom/sfdx-hardis/tree/main/.claude/skills/architecture into .gemini/skills/architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture", 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.

GitHub CLI

$ gh skill install hardisgroupcom/sfdx-hardis architecture

Installs 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).

skills CLI

$ npx skills add hardisgroupcom/sfdx-hardis --skill architecture -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/hardisgroupcom/sfdx-hardis.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/architecture .github/skills/architecture && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "architecture" agent skill from https://github.com/hardisgroupcom/sfdx-hardis/tree/main/.claude/skills/architecture into .github/skills/architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture", 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.

skills CLI

$ npx skills add hardisgroupcom/sfdx-hardis --skill architecture -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install hardisgroupcom/sfdx-hardis architecture --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/hardisgroupcom/sfdx-hardis.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/architecture .opencode/skills/architecture && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "architecture" agent skill from https://github.com/hardisgroupcom/sfdx-hardis/tree/main/.claude/skills/architecture into .opencode/skills/architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture", 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: architecture
GitHub stars: 401
Token cost: ~2.1k tokens
SKILL.md length: 638 words
Files: 1
Skills in repo: 21
Repo updated: Oct 8, 2026
First seen: Oct 7, 2026
Licence: AGPL-3.0

At a glance

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.

Adding a new command to sfdx-hardis
SKILL.md covers Technology Stack, Project Structure, CLI Framework and Provider Pattern (src/common/), plus 6 more sections
Calls sf and yarn; reaches raw.githubusercontent.com
Deciding where a new git, notification or ticketing integration belongs

What it does

This is a contributor reference for the sfdx-hardis codebase. It lists the stack: TypeScript in strict mode, the Oclif framework used by the Salesforce CLI, Wireit for build tasks, Mocha with Nyc for tests and coverage, ESLint with Salesforce configurations, and LangChain for AI integration alongside Codex and Agentforce. Commands live under src/commands/hardis, number around 300, extend SfCommand and run as sf hardis followed by a topic and an action.

Commands should accept an --agent flag so AI agents and pipelines can run them without any interactive prompt, using sensible defaults. External integrations follow a provider pattern, with a root class and concrete implementations for git hosts (GitHub, GitLab, Azure DevOps, Bitbucket), notifications (Slack, Teams, email, API webhook), tickets (Jira, Azure Boards, ServiceNow), AI, post-deploy actions, key-value storage and documentation building.

When your agent uses it

Adding a new command to sfdx-hardis
Deciding where a new git, notification or ticketing integration belongs
Understanding how the project's providers, hooks and config fit together

Example prompts

“Add a new sfdx-hardis command under the audit topic and make it work with the --agent flag.”
“Where should a new Mattermost notification channel go? Follow the provider pattern.”
“Give me a map of the src/common folder and what each provider does.”

Requirements

A checkout of the sfdx-hardis repository

What it can do on your machine

Read from SKILL.md and the folder at commit 9625b22. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- sf
- yarn
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
- raw.githubusercontent.com
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

sfdx-hardis Architecture Guide loads about 2.1k tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 638 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~49
When it runs · the whole SKILL.md, loaded when a task matches: ~2.1k

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 9625b22, republished under its AGPL-3.0 licence (© hardisgroupcom). 638 words, ~2,064 tokens.

Download SKILL.mdSave it as .claude/skills/architecture/SKILL.md (or your agent's skills folder).

name: architecture
description: sfdx-hardis project architecture, technology stack, provider pattern, configuration system, and project structure. Use when working with project structure, providers, hooks, or config.
user-invocable: false

Architecture

Technology Stack

Language: TypeScript (strict mode)
CLI Framework: Oclif (Salesforce CLI framework)
Build System: Wireit (task orchestration)
Testing: Mocha with Nyc for coverage
Linting: ESLint with Salesforce configurations
AI Integration: LangChain (Anthropic, Google GenAI, Ollama, OpenAI) + Codex + Agentforce

Project Structure

src/
├── commands/hardis/   # CLI commands (~300+) organized by domain
│   ├── auth/          ├── cache/       ├── config/
│   ├── datacloud/     ├── doc/         ├── git/
│   ├── lint/          ├── mdapi/       ├── misc/
│   ├── org/           ├── package/     ├── packagexml/
│   ├── project/       ├── scratch/     ├── source/
│   └── work/
├── common/
│   ├── aiProvider/    # AI integration and prompt templates
│   └── utils/         # Shared utilities (barrel-exported from index.ts)
├── hooks/             # Oclif lifecycle hooks
├── i18n/              # Translation files (9 locales)
test/                  # Test files (*.test.ts, *.nut.ts)
lib/                   # Compiled JavaScript output
messages/              # Oclif message files (.md)
defaults/              # Default configurations and templates
docs/                  # Project documentation

CLI Framework

Commands extend SfCommand<any> from @salesforce/sf-plugins-core.
Invoked as sf hardis <topic> <action>.
ESM module ("type": "module").

Headless / Agent Mode

When possible, every command should support a --agent boolean flag so it can be called non-interactively by AI agents and automation pipelines:

// Flag declaration
agent: Flags.boolean({
  default: false,
  description: 'Run in non-interactive mode for agents and automation',
}),

// In run()
const agentMode = flags.agent === true;

// Guard every interactive prompt
if (!isCI && !agentMode) {
  const answer = await prompts({ ... });
}

Add '$ sf hardis:<topic>:<action> --agent' to the command examples array.
In agent mode the command must complete without blocking on any interactive prompt, applying sensible defaults instead.

Provider Pattern (`src/common/`)

External integrations use a root class + concrete implementations:

gitProvider: GitHub, GitLab, Azure DevOps, Bitbucket
notifProvider: Slack, MS Teams, Email, API webhook. Slack and Teams share the logical messaging channel; each provider declares its channel via getChannel(). Routing is filtered per notification type and per channel via severity thresholds. See the monitoring-notifications skill.
ticketProvider: Jira, Azure Boards, ServiceNow, Aha!, generic
aiProvider: LangChain-based (Anthropic, Google GenAI, Ollama, OpenAI) + Codex + Agentforce
actionsProvider: Post-deploy actions (Apex, data, manual, community publish, schedule batch)
keyValueProviders: Salesforce org, local test
docBuilder: Documentation generation

Monitoring Pipeline (`src/common/monitoring/`, `src/common/notifProvider/`)

hardis:org:monitor:all runs a list of sub-commands (monitoringCommandsDefault) on a configurable cadence. Each sub-command posts notifications through NotifProvider.postNotifications, which fans out to enabled channels (messaging / email / api) using per-notification-type severity thresholds. Defaults live in source; users override per-entry via the monitoringCommands property in .sfdx-hardis.yml, merged by key. The hardis:config:monitoring-defaults command exposes the full defaults payload to the VS Code extension UI.

When adding a monitoring command, a notification type, or changing default routing, use the monitoring-notifications skill -- it lists exactly which files to touch.

Configuration System (`src/config/index.ts`)

Three-Layer Config

Configuration uses a three-layer merge with priority: user > branch > project.

Layer	File locations	Purpose
Project (global)	`config/.sfdx-hardis.yml` or `config/.sfdx-hardis.yaml` (also `.sfdx-hardis.yaml`/`.yml` at repo root, or `package.json`)	Shared settings for the entire project, committed to git
Branch	`config/branches/.sfdx-hardis.<branch-name>.yml`	Per-branch overrides (e.g., different target org, deploy options per environment). Branch name is auto-detected from git or `CONFIG_BRANCH` env var
User	`config/user/.sfdx-hardis.<os-username>.yml`	Per-developer overrides, typically git-ignored

Higher-priority layers override lower ones via Object.assign() (shallow merge).

Config File Discovery

Uses cosmiconfig to search for config files. Supported names: .sfdx-hardis.yaml, .sfdx-hardis.yml, and package.json (for project layer).

Show full SKILL.md (257 more words)Show less

Remote Config Inheritance

A config file can include an extends property pointing to a remote YAML URL. The remote config is fetched and merged underneath the local config (local wins). This allows sharing a common config base across multiple projects.

yaml

# config/.sfdx-hardis.yml
extends: https://raw.githubusercontent.com/mycompany/shared-config/main/.sfdx-hardis.yml
projectName: my-project

API

getConfig(layer) - returns merged config up to the specified layer ("project", "branch", or "user" - default "user")
setConfig(layer, propValues) - writes properties to the config file for the specified layer
CONSTANTS - static constants (API version, URLs, metadata type lists)
getEnvVar(name) - reads env var with Azure unresolved-variable detection

JSON Schema

All config properties are defined in config/sfdx-hardis.jsonschema.json (JSON Schema draft-07). This schema is used to:

Generate HTML documentation (yarn build runs generate-schema-doc)
Validate config structure
Power IDE autocompletion

When adding or modifying a config property, always update config/sfdx-hardis.jsonschema.json to keep it in sync. Each property should have $id, description, title, type, and optionally default, enum, examples, and docUrl.

Hooks (`src/hooks/`)

Oclif lifecycle hooks:

init: logging, upgrade check, websocket client
prerun: auth, dependency check
auth: authentication
postrun: cache store
finally: notifications

WebSocket Client (`src/common/websocketClient.ts`)

Communicates with VS Code extension (vscode-sfdx-hardis) for UI interactions, progress, and prompts. Every message carries an event handled in the extension's src/hardis-websocket-server.ts, so adding or changing one is an extension change too. See the vscode-sfdx-hardis skill for the full integration surface.

Utilities (`src/common/utils/`)

Barrel-exported from src/common/utils/index.ts:

uxLog() - logging
execSfdxJson() - CLI subprocess calls
Deploy, git, org, XML utilities

AI Prompt Templates

Located in src/common/aiProvider/promptTemplates/. Each exports a PromptTemplateDefinition with variables and multilingual text. Users can override by placing .md files in config/prompt-templates/ (.txt also supported for backward compatibility).

Files

Just SKILL.md in .claude/skills/architecture of hardisgroupcom/sfdx-hardis.

Open the folder on GitHubat commit 9625b22

Compare with similar skills

sfdx-hardis Architecture Guide 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.

sfdx-hardis Architecture Guide compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
sfdx-hardis Architecture Guide this skillhardisgroupcom/sfdx-hardis	401	—	~2.1k	Automated safety check: Pass	AGPL-3.0	today
GitDiagram Repository Overviewahmedkhaleel2004/gitdiagram	18k	—	~427	Automated safety check: Pass	MIT	today
GitDiagram Repo Architectureahmedkhaleel2004/gitdiagram	18k	—	~429	Automated safety check: Pass	MIT	today
Gh Bot Commentjetstreamapp/jetstream	125	—	~616	Automated safety check: Pass	Custom licence	today
CodeScope Codebase Graph AnalysisQwenLM/qwen-code	28k	1 repos	~9.3k	Automated safety check: Pass	Apache-2.0	today
Codegraph QAQwenLM/qwen-code-examples	143	—	~4.3k	Automated safety check: Pass	None	4 mo ago

Similar skills

GitDiagram Repository Overview
ahmedkhaleel2004/gitdiagram
Explains the architecture of a public GitHub repository through GitDiagram: how the code is organized, the main components with paths, and a Mermaid diagram.
18k GitHub stars~427 tokensUpdated today
DevelopmentAuto-check passed
GitDiagram Repo Architecture
ahmedkhaleel2004/gitdiagram
Explains how a public GitHub repository is built by fetching its GitDiagram architecture diagram, components and optional explainer video.
18k GitHub stars~429 tokensUpdated today
DevelopmentAuto-check passed
Gh Bot Comment
jetstreamapp/jetstream
Post GitHub PR/issue comments, reviews, and review replies as the Jetstream bot account instead of the user's personal account.
125 GitHub stars~616 tokensUpdated today
DevelopmentAuto-check passed
CodeScope Codebase Graph Analysis
QwenLM/qwen-code
Answers questions about code structure, history, bugs and PR risk using a CodeScope knowledge graph and semantic index built from the repository.
28k GitHub starsUsed in 1 repo~9.3k tokens
DevelopmentAuto-check passed
Codegraph QA
QwenLM/qwen-code-examples
Use CodeScope to analyze any indexed codebase via its graph database (neug) and vector index (zvec).
143 GitHub stars~4.3k tokensUpdated 4 mo ago
DevelopmentAuto-check passed
System Design
aiskillstore/marketplace
CTO's deputy for software architecture using Clean/Hexagonal Architecture principles.
430 GitHub stars~1.1k tokensUpdated today
DevelopmentAuto-check passed

Questions about sfdx-hardis Architecture Guide

What does sfdx-hardis Architecture Guide do?

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. This is a contributor reference for the sfdx-hardis codebase. It lists the stack: TypeScript in strict mode, the Oclif framework used by the Salesforce CLI, Wireit for build tasks, Mocha with Nyc for tests and coverage, ESLint with Salesforce configurations, and LangChain for AI integration alongside Codex and Agentforce.

When should I use sfdx-hardis Architecture Guide?

sfdx-hardis Architecture Guide fits situations like: adding a new command to sfdx-hardis; deciding where a new git, notification or ticketing integration belongs; understanding how the project's providers, hooks and config fit together.

How do I install sfdx-hardis Architecture Guide in Claude Code?

Run `npx skills add hardisgroupcom/sfdx-hardis --skill architecture -a claude-code`. Or copy the skill folder (.claude/skills/architecture in hardisgroupcom/sfdx-hardis) into .claude/skills/architecture in your project. Claude Code loads it when a task matches its description.

How do I install sfdx-hardis Architecture Guide in Codex?

Run `npx skills add hardisgroupcom/sfdx-hardis --skill architecture -a codex`. Or copy the skill folder (.claude/skills/architecture in hardisgroupcom/sfdx-hardis) into .agents/skills/architecture in your project. Codex loads it when a task matches its description.

Can I use sfdx-hardis Architecture Guide 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 architecture -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/architecture, .gemini/skills/architecture, .github/skills/architecture and .opencode/skills/architecture in your project.

What does sfdx-hardis Architecture Guide need to run?

Going by SKILL.md and its folder, sfdx-hardis Architecture Guide needs the command-line tools its instructions call (sf and yarn). Our summary lists: A checkout of the sfdx-hardis repository.

Does sfdx-hardis Architecture Guide access the network?

SKILL.md names 1 domain. In commands or code: raw.githubusercontent.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is sfdx-hardis Architecture Guide 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 sfdx-hardis Architecture Guide use?

sfdx-hardis Architecture Guide 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 sfdx-hardis Architecture Guide use?

About 2.1k tokens (SKILL.md is roughly 8.3k 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 sfdx-hardis Architecture Guide?

Skills that share tags, products or a category with sfdx-hardis Architecture Guide: GitDiagram Repository Overview (ahmedkhaleel2004/gitdiagram, 18k stars), GitDiagram Repo Architecture (ahmedkhaleel2004/gitdiagram, 18k stars), Gh Bot Comment (jetstreamapp/jetstream, 125 stars) and CodeScope Codebase Graph Analysis (QwenLM/qwen-code, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains sfdx-hardis Architecture Guide?

hardisgroupcom (a GitHub organization) maintains it in hardisgroupcom/sfdx-hardis, which has 401 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 8, 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.

Install sfdx-hardis Architecture Guide

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Architecture

Technology Stack

Project Structure

CLI Framework

Headless / Agent Mode

Provider Pattern (src/common/)

Monitoring Pipeline (src/common/monitoring/, src/common/notifProvider/)

Configuration System (src/config/index.ts)

Three-Layer Config

Config File Discovery

Remote Config Inheritance

API

JSON Schema

Hooks (src/hooks/)

WebSocket Client (src/common/websocketClient.ts)

Utilities (src/common/utils/)

AI Prompt Templates

Files

Compare with similar skills

Similar skills

More from hardisgroupcom/sfdx-hardis

Related

Questions about sfdx-hardis Architecture Guide

Provider Pattern (`src/common/`)

Monitoring Pipeline (`src/common/monitoring/`, `src/common/notifProvider/`)

Configuration System (`src/config/index.ts`)

Hooks (`src/hooks/`)

WebSocket Client (`src/common/websocketClient.ts`)

Utilities (`src/common/utils/`)