By element22llc
An always-on engineering operating manual plus spec-workflow skills and templates. Org standards centralized so every product repo picks up changes via /plugin update.
Adopt an existing repo that never went through bootstrap (a "vibe-coded" app) into the standards — reverse-engineer the /spec from the code, triage productionization (Keep/Refactor/Rewrite/Reject per area), and sync the plugin's bundled scaffolding without clobbering working code.
Create a numbered ADR from the bundled template.
Repeatable, read-only audits of a managed repo: `code` mode (default) sweeps the whole repo against the standards dimensions, ranks findings by leverage, and files them in the tracker; `spec` mode compares the as-built /spec against the intended spec from the tracker and surfaces drift; `all` runs both. Repository-read-only — proposes spec changes and files issues but never edits code/spec or commits; defers correctness to /code-review and security to /security-review.
Guided flow for a non-technical product owner — idea → interview → approved spec → working local app → handoff for dev review, with Claude driving all tooling.
Detect and install the local prerequisites a managed repo needs before init/build/dev — git, mise (and the pnpm/uv/node it manages), and Docker — with per-OS guidance and confirmation-gated installs.
Executes bash commands
Hook triggers when Bash tool is used
Modifies files
Hook triggers on file write and edit operations
External network access
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Connects to servers outside your machine
Connects to servers outside your machine
An engineering-standards Claude Code plugin
marketplace. Its primary
plugin is steer, which carries org-wide engineering
standards so they live in one place and update centrally — instead of
being copied into every forked product repo and then frozen. The marketplace
also re-lists Anthropic's upstream frontend-design plugin (referenced
via a SHA-pinned git-subdir source, never vendored) so it can be installed from
the same catalog; it is not auto-enabled in product repos — install it
explicitly if a repo wants it.
Edit the rules once here; every product repo picks them up on the next
/plugin update.
This repo is the canonical source of the standards and of repository
bootstrap: the plugin bundles the full repo scaffold
(plugins/steer/templates/scaffold/) and the spec-spine templates, so
/steer:init and /steer:adopt stand a repo up without any external template.
The old static repository-template (a private repo, intentionally not linked
here) is replaced by this plugin-driven bootstrap — see
Migrating from repository-template.
steer ships| Component | Contents |
|---|---|
Always-on rules (rules/*.md) | Injected into every session by a SessionStart hook: PO/dev roles, stack defaults, monorepo layout, spec workflow, living documentation (natural-language → spec, action history, app docs), issue-tracker integration (client-agnostic), testing rules, Definition of Done, pre-merge drift gates, high-risk areas, secrets handling, audit-aligned delivery (SOC 2 / ISO 27001-aligned, not compliant), change-size model, baseline patterns/anti-patterns, design-sources summary, end-of-session checklist. |
Skills (on-demand, invoked as /steer:<skill>) | Grouped by area: Setup & maintenance — /steer:setup (the front door — detects repo state and routes to the right path below), /steer:doctor (detect + confirmation-gated install of the local prerequisites — git, mise, Docker — before init/build/dev; usually via setup), /steer:init (repo bootstrap from the bundled scaffold; usually via setup), /steer:adopt (adopt an existing "vibe-coded" repo; usually via setup), /steer:sync (bring a bootstrapped repo up to the current plugin; usually via setup), /steer:protect (verify/apply GitHub branch protection on main from policy/branch-protection.yml — the real PR gate, steer being advisory locally), /steer:tidy (sweep loose files into /spec; usually via audit).Spec authoring — /steer:build (PO-guided idea→working-app flow), /steer:spec (brainstorm + approve + validate a feature spec, no build), /steer:intake (absorb a PO's new/updated spec or roadmap document — docx/pptx/xlsx/pdf — by diffing it against the last version and folding the real changes into /spec), /steer:spec-scaffold (instantiate intent+contract — internal helper invoked by spec/build/init/adopt, hidden from the slash menu), /steer:questions (sweep open questions; usually via spec/issues), /steer:adr (ADR).Issues & execution — /steer:issues (GitHub Issues lifecycle), /steer:roadmap (generate a release-milestone timeline — viewable as a GitHub Projects v2 roadmap — from target features or a spec-gap from /steer:audit spec; usually via issues), /steer:work (execute an issue end-to-end; add --reviewed to wrap it in a review-gated loop — plan-gate + /code-review gate + bounded fix, vetted not first-draft), /steer:tracker-sync (the GitHub gateway — internal helper invoked by issues/work, hidden from the slash menu).Navigate & audit — /steer:next (cross-workflow "what next?"), /steer:help (browse the whole capability set as a plain-language menu — sourced from the router table, no repo state needed), /steer:audit (read-only repo audit — code whole-repo health, spec as-built-vs-intended conformance, all for both), /steer:report (file a defect in the steer plugin itself upstream — scrubbed, deduped, confirmation-gated; not for product bugs).Reference prose (materialized into /spec/reference/) — `/steer:reference [conventions |
| Templates | Bundled spec templates (feature-intent, feature-contract, adr, productionization, vision/users/glossary, history (action log), tracker, app-docs) and the full reference prose, so scaffolding always uses the latest org templates. |
npx claudepluginhub element22llc/e22-plugins --plugin steerHarness-native ECC plugin for engineering teams - 67 agents, 277 skills, 93 legacy command shims, reusable hooks, rules, MCP conventions, and operator workflows for Claude Code plus adjacent agent harnesses
Supergraph enforces a complete, evidence-based coding pipeline — scan → plan → TDD → fix → verify → review — grounded in real codebase analysis at every step. It combines AST dependency graphs, LSP-level code intelligence, and a structured skill chain so Claude never guesses about impact before making a change.
Claude harness - A harness for solo developers (Vibecoders) to handle full-cycle contract development.
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
Reliable automation, in-depth debugging, and performance analysis in Chrome using Chrome DevTools and Puppeteer
v9.44.1 — Patch release for Gemini environment/version detection and qwen auth gating. Run /octo:setup.