SDH Enterprise Standards

SDH Claude Skills

Enterprise-grade Claude Code plugin for a professional Software Development House.

A complete, audited system of skills, agents, and hooks that transforms Claude Code into a full SDLC partner — from requirements gathering through production incident response.

What This Is

This repository is a Claude Code plugin (sdh) that enforces enterprise development standards across the entire software development lifecycle. It is designed for teams building Rails API (Phlex views) + React Native mobile + ReactJS Vite SPA + Next.js App Router applications deployed on AWS and Vercel.

Instead of relying on ad-hoc prompting, this plugin provides:

• 58 skills — 37 workflow skills (/sdh:code-reviewer, /sdh:rails-architect, …), 20 std-* convention skills that auto-load by file path (e.g. std-rails-conventions, std-accessibility), plus the always-on sdh-engineering-standards skill
• 12 specialized agents (4 with team lead protocols) that handle complex tasks with constrained tool access
• 6 pre-defined agent team templates for coordinated multi-agent work
• Quality-gate hooks (PreToolUse blockers + a single PostToolUse dispatcher) with wrapper-agnostic framework detection
• A core sdh-engineering-standards skill carrying the stack + library conventions

Install

# Add this repo as a marketplace, then install the plugin
/plugin marketplace add Kaakati/sdh-claude-skills
/plugin install sdh@sdh-claude-skills

# Or test locally without installing
claude --plugin-dir /path/to/sdh-claude-skills

Skills are namespaced under the plugin: /sdh:code-reviewer, /sdh:rails-architect, etc. Run /plugin to manage it, and claude plugin validate . to validate changes.

What a plugin can't ship — add these to your project .claude/settings.json

A plugin cannot ship permissions, env, or worktree settings. Copy them from this repo's .claude/settings.json into your own project settings to get the secret/build-artifact Read denies, the agent-teams env flag, and worktree symlinks. See docs/monorepo-setup.md.

Project Directory Convention

The system auto-detects each framework — your wrapper directory can be named anything (backend/, api/, server/, web/, frontend/, next/, mobile/, or even the repository root). Conventions load from each framework's own layout and marker files, not from a forced top-level folder name.

How Detection Works

Detection uses two wrapper-agnostic signals:

1. Canonical internal structure — each framework's own conventional sub-paths, matched anywhere in the tree. app/models/*.rb is Rails whether it lives in backend/app/models/, api/app/models/, or app/models/. src/pages/ is a Vite SPA; src/screens/ is React Native — regardless of the wrapper.

2. On-disk project markers — when structure alone is ambiguous (e.g. a src/components/*.tsx that could be web or mobile), the hooks walk up the tree to the nearest marker file:

   Framework	Marker files
   Rails	Gemfile, config/application.rb, bin/rails
   Next.js	next.config.{js,ts,mjs,cjs}, "next" in package.json
   ReactJS (Vite)	vite.config.{js,ts}, index.html
   React Native	metro.config.js, app.json, "react-native" in package.json

So putting your Rails code in api/ instead of backend/ works fine — the Rails rules and hooks still activate.

What Convention Skills Auto-Load (wrapper-agnostic globs)

The std-* convention skills are path-scoped — they auto-load when you edit files matching their globs:

File you edit (under any wrapper)          std-* skills that auto-load
--------------------------------------     --------------------------------------
**/app/**/*.rb                           -> std-rails-conventions, std-clean-architecture
**/app/components/**/*.rb                 -> std-phlex-conventions
**/app/views/**/*.rb                      -> std-phlex-conventions, std-i18n
**/src/pages/**/*.tsx                     -> std-reactjs, std-accessibility
**/src/screens/**/*.tsx                   -> std-react-native
**/app/**/*.tsx + **/next.config.*        -> std-nextjs, std-accessibility
**/i18n/**, **/config/locales/**          -> std-i18n
**/migrations/**, **/migrate/**           -> std-database
**/*.tf, **/*.tfvars                      -> std-terraform-conventions, std-infrastructure, std-monitoring
**/*.test.*, **/*.spec.*                  -> std-testing

Hook Domain-Aware Limits (wrapper-agnostic)

The PostToolUse checkers apply a 200-line limit to models and UI components (300 elsewhere), matched by canonical structure under any wrapper: