architecture

Document sfdx-hardis project architecture, technology stack, and configuration system.

368|98|Updated Jan 25, 2021
One-click install
npx skills add https://github.com/hardisgroupcom/sfdx-hardis --skill architecture-hardisgroupcom
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/hardisgroupcom/sfdx-hardis/tree/main/.claude/skills/architecture
Command: npx skills add https://github.com/hardisgroupcom/sfdx-hardis --skill architecture-hardisgroupcom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

sfdx-hardis project architecture, technology stack, provider pattern, configuration system, and project structure. Use when working with project structure, providers, hooks, or config.

The goal is to provide a consistent blueprint that reduces guesswork, accelerates onboarding, and ensures future contributions align with established patterns.

Core Features & Use Cases

  • Technology stack overview: TypeScript (strict), Oclif, Wireit, Mocha, Nyc, ESLint, LangChain integration with multiple AI providers.
  • Project structure blueprint: Clearly defined directories (src, test, lib, docs, defaults) and conventional file layout to improve maintainability.
  • Provider-pattern and config system: Describes how integrations (git, notif, ticket, ai, docBuilder) are modeled and configured.
  • Three-layer configuration: Global project config, per-branch overrides, and user-level overrides with remote inheritance.
  • Agent/Headless mode guidance: Patterns for non-interactive automation and agent-based execution.

Quick Start

Provide a baseline architecture overview for a new sfdx-hardis project by listing the stack, patterns, and file layout.

Frequently Asked Questions about architecture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize Salesforce project architecture using a provider pattern?▼

Standardize Salesforce project architecture by defining a consistent technology stack, provider pattern, and a three-layer configuration system to reduce guesswork and accelerate onboarding.

What is the three-layer configuration system in sfdx-hardis projects?▼

The three-layer configuration system manages global project config, per-branch overrides, and user-level overrides with remote inheritance to ensure extensible and consistent environment setup.

Does the Oclif CLI framework work with TypeScript and Wireit for project structure?▼

Oclif integrates with TypeScript strict mode and Wireit build tooling to define conventional directory layouts, improving maintainability for CLI tooling and headless automation.

How do I configure headless agent mode for non-interactive automation?▼

Configure headless agent mode by applying established provider patterns and integration points for git, notifications, and AI to enable non-interactive automation and agent-based execution.

Can I use LangChain prompts with multiple AI providers in a standardized CLI project?▼

LangChain integration supports multiple AI providers within the defined architecture, using TypeScript and Oclif to structure prompts and guide agent-based execution.

When do I need to document project structure for a new sfdx-hardis project?▼

Document project structure when working with providers, hooks, or config to ensure future contributions align with established patterns, required files, and conventional directory layouts.