poka-yoke

Mistake-proofing for software. Shigeo Shingo's poka-yoke method as a Claude Code plugin: audit code for footguns, design APIs that resist misuse, install guardrails, turn incidents into devices.

Active — Updated in the last 14 days

Works with

Claude

View on GitHub

24 GitHub stars (24)

+2 in 20 days

Stars gained per day · daily snapshots since Sep 26

Stars gained between daily snapshots
Period	New stars
Sep 27–28 (2 days)	0
Sep 29	0
Sep 30	0
Oct 1	0
Oct 2	0
Oct 3	0
Oct 4	0
Oct 5	0
Oct 6	0
Oct 7	0
Oct 8	0
Oct 9	0
Oct 10	0
Oct 11	0
Oct 12	0
Oct 13	0
Oct 14	+1
Oct 15	+1
Oct 16	0

13 skills (13 skills found in its SKILL.md files)
3 forks (3 forks)
1d ago last update (Last updated 1d ago)

Install

Skills CLI

npx skills add rainmanjam/poka-yoke

Asks which skills and agents to install. Just one: npx skills add rainmanjam/poka-yoke --skill agent-guardrails — add -g for every project.

Claude Code

git clone https://github.com/rainmanjam/poka-yokecp -r "poka-yoke/plugins/poka-yoke/skills/agent-guardrails" ~/.claude/skills/

Copies the agent-guardrails skill into ~/.claude/skills/ for every project (use .claude/skills/ for one project). Repeat for the other skills listed below.

Plugin

/plugin marketplace add rainmanjam/poka-yoke

Run inside Claude Code if the repository ships a plugin marketplace, then pick plugins from /plugin.

Skills can run code on your machine — read the SKILL.md first.

What it does

Filter skills

In the author's own words, from each skill's SKILL.md.

agent-guardrails

Stop an AI agent damaging your repo: PreToolUse hooks, permission deny rules, protected paths, verification gates. Use when "claude keeps force pushing", "CLAUDE.md says X but it still does Y", "stop the agent touching prod or .env", or making a repo safe for unattended agent work. For AI features you ship to users use llm.
plugins/poka-yoke/skills/agent-guardrails/SKILL.md on GitHub (opens in a new tab)
audit

Find footguns in code that already exists: swappable arguments, silent fallbacks, unguarded deletes, signatures that are easy to misuse. Use when someone asks "what could bite us here", "what is easy to misuse", "poka-yoke this repo", or wants a diff or PR reviewed for ways to get it wrong. Ranks by blast radius. For code not yet written use design; for something that already broke use retro.
plugins/poka-yoke/skills/audit/SKILL.md on GitHub (opens in a new tab)
authz

Multi-tenant isolation, IDOR and row-level security. Use to find every path where one tenant could read or write another tenant data: "we forgot to filter by org_id", "can users see each other data", "audit these endpoints for cross-tenant leaks", "make an unscoped query impossible". Covers scoped repositories, RLS, default-deny routing and the two-tenant test. For what the UI shows use ux.
plugins/poka-yoke/skills/authz/SKILL.md on GitHub (opens in a new tab)
data

Pipelines, warehouses, dbt models and metrics, where failure is silently wrong numbers rather than a crash. Use when "the dashboard is wrong", "the numbers do not match", "add data quality checks", "safe backfill", or an upstream schema change broke a join. Covers freshness, row-count and null-rate assertions, data contracts, reconciliation. For a crash rather than wrong numbers use audit.
plugins/poka-yoke/skills/data/SKILL.md on GitHub (opens in a new tab)
design

Design APIs, schemas, types and state machines so misuse cannot be expressed. Use when writing a new interface and someone asks "what should the types look like", "make invalid states unrepresentable", "so callers cannot screw it up", or wants illegal state transitions rejected. Covers branded types, discriminated unions, typestate, parse-don't-validate. For code that already exists use audit.
plugins/poka-yoke/skills/design/SKILL.md on GitHub (opens in a new tab)
guardrails

Pre-commit hooks, CI gates, lint rules, database constraints and branch protection. Use when a rule needs enforcing rather than documenting: "set up enforcement", "unformatted or untyped code must not get merged", "gate this in CI", "we agreed to X and people still do not", "stop secrets getting committed". Covers baselining and ratcheting so existing violations do not block anyone. For constrain…
plugins/poka-yoke/skills/guardrails/SKILL.md on GitHub (opens in a new tab)
llm

AI features you ship to users: structured output, tool schemas, prompt injection, evals. Use when "the model returns bad JSON", "it hallucinates", "stop it calling the wrong tool", "add evals", or an LLM feature can trigger refunds, emails or writes. Covers schema-constrained output, idempotent tool calls, confirmation gates. For agents editing your repo use agent-guardrails.
plugins/poka-yoke/skills/llm/SKILL.md on GitHub (opens in a new tab)
ops

Deploys, schema migrations, rollback and infrastructure. Use when "can I ship this on Friday", "this migration is scary", "what is the blast radius", "prevent accidental deletion of the database", or a change drops a column. Covers expand/contract, canary rollout, kill switches, prevent_destroy, tested backups. For an incident that already happened use retro.
plugins/poka-yoke/skills/ops/SKILL.md on GitHub (opens in a new tab)
poka-yoke

Mistake-proofing for anything: code, config, a schema, a process, a runbook, a form. Use when someone says "poka-yoke this", "mistake-proof it", "make this harder to get wrong", or runs /poka-yoke with no mode named. Applies Shigeo Shingo's method directly to any subject, and hands off to a specialist mode when one clearly fits. Start here when no other poka-yoke mode obviously applies.
plugins/poka-yoke/skills/poka-yoke/SKILL.md on GitHub (opens in a new tab)
retro

Turn a bug, outage or repeated mistake into a device that makes the whole class impossible. Use when something already broke: "make sure this never happens again", "this is the third time", "postmortem", "how did this get through". Root-causes to the missing constraint, then sweeps every other site where the mistake is still available. For a pipeline use data, a deploy use ops, cross-tenant use a…
plugins/poka-yoke/skills/retro/SKILL.md on GitHub (opens in a new tab)
ux

Forms, destructive actions and flows users get wrong. Use when "users keep deleting the wrong thing", "add a confirmation dialog", "this flow is error-prone", or building a delete, bulk action, checkout or settings page. Covers undo over confirmation, type-to-confirm, safe defaults, input constraints, double-submit. For the server-side rules behind the screen use authz.
plugins/poka-yoke/skills/ux/SKILL.md on GitHub (opens in a new tab)
clean-code

Software quality review and design guidance for any code: naming, cohesion, coupling, duplication, function size, dependency direction, and testability. Use when someone asks to improve, review, refactor, or design code, or asks what good structure looks like here. Routes to the sub-skill matching the kind of work.
benchmarks/controls/clean-code/skills/clean-code/SKILL.md on GitHub (opens in a new tab)
defensive

Defensive programming for any code: validating inputs at every boundary, checking for null and absent values, supplying safe fallbacks, catching and logging exceptions, and degrading gracefully rather than failing. Use when someone asks to make code robust, resilient, safer, or harder to crash. Routes to the sub-skill matching the kind of work.
benchmarks/controls/defensive/skills/defensive/SKILL.md on GitHub (opens in a new tab)

Review before you install

A skill is a set of instructions and scripts your agent will follow, and it can run code on your machine. Read the SKILL.md and any scripts first — this listing is not a security review.

Encoders & Decoders

Hash Generators

Code Formatters

HTML Tools

JavaScript Tools

Network Tools

Database Tools

Development Tools

Miscellaneous Tools

poka-yoke