human-made-standards

Plugin human-made-standards from marketplace hm-standards in humanmade/claude-code-standards. Commands read from the repo's manifest — 1 month ago.

Skills (8)

• altis-development

  Altis DXP projects — local server commands, mu-plugins architecture, asset handling and deploys. Use when a project has an Altis config or `composer server` scripts, or when asked to start or stop the local server, run WP-CLI, open a database shell, tail logs, or run a PHP script in WordPress contex

• css-scss-standards

  Human Made CSS and SCSS conventions — BEM class naming, custom properties, theme.json integration, Stylelint config. Use when writing or reviewing styles, adding a stylesheet or SCSS partial, naming classes, wiring theme.json tokens, or when asked whether some CSS follows HM standards.

• hm-coding-philosophy

  Human Made engineering principles — what to prioritise when evaluating tradeoffs between code quality and directness, why simple beats clever, and how to spot over-engineering. Use when choosing between implementation approaches, reviewing a design or PR for unnecessary complexity, justifying a simp

• javascript-standards

  Human Made JavaScript and TypeScript conventions — ES6+ patterns, module organisation, ESLint config, WordPress integration. Use when writing or reviewing JS or TS, adding a module, or when asked whether some JavaScript follows HM standards.

• php-standards

  Human Made PHP conventions for WordPress — namespaced procedural code, the bootstrap pattern, file naming, type hints, the HM-Minimum PHPCS ruleset, and input/output security. Use when writing or reviewing PHP in a plugin or theme, adding a feature namespace or bootstrap, or when asked whether some

• react-standards

  Human Made React conventions — functional components with hooks, semantic HTML, props and state, component organisation, block editor interfaces. Use when writing or reviewing a React component, structuring a component directory, or building WordPress block editor UI.

• run-linters

  Discover and run a project's linters — PHPCS, PHPStan, ESLint, Stylelint. Use when asked to lint, run the linters, check code quality, run static analysis, fix coding standard violations, or verify changes before opening a pull request. Prefers the project's own composer or npm script over calling t

• vip-development

  WordPress VIP projects — vip-cli commands, client-mu-plugins architecture, and VIP platform constraints. Use when a project has a VIP structure, or when asked to run vip-cli, reach WP-CLI or the database on a VIP application, tail logs, work with the local dev-env, or check whether something is perm