principles plugins

by leogallego

Display the Zen of Ansible principles and review Ansible code against them. Use when the user wants to see the Zen of Ansible, get philosophical guidance on their automation approach, or review code for simplicity, readability, and clarity. Use when user says "zen of ansible", "simplify my playbook", "is this too complex", or "clean code review". Do NOT use for strict rule compliance (use ansible-good-practices instead). Do NOT use for Ansible module reference or documentation lookups (use ansible-docs instead).

by Tom Mornini

The Church of Code scripture — a ranked hierarchy of commandments, articles of faith, abominations, and daily offices, bundled as a Claude Code skill in three context-size variants.

by Lauren Tan

if you want to go fast, go deep first. pstack helps you write less, but higher quality code. rigorous agent workflows you can parallelize with confidence. Ported from cursor/plugins.

by Patina Project

Patina Project's owned engineering workflows, forked from pstack.

by Viraj Patel

The principles-driven stack materializer — implements the vwf stack-adapter contract with a dispatch rule: a technology a shipped pack covers is copied from the pack; anything uncovered is generated (Context7 research → vwf's principles catalog → the stackgen-skill-reviewer gate). Both paths land directly in the repo's committed .claude/ tree — skills, agents, hooks and rules only, structured per a closed kind vocabulary, recorded in a lockfile — editable and plugin-independent for collaborators. Re-sync is explicit and diffed, never silent. Waves A–C landed 21 packs and 19 bundles across seven kinds; Wave D adds the eighth kind, deploy-target, whose container-image pack is the curated answer the container-generic bundle used to generate, assets/artifact-doctrine.md — the host rules deciding whether a generated skill, agent or hook is valid at all — and the ninth kind, design-tool, whose three packs land vwf's design adapters at fixed names in the repo's own .claude/. Two tool axes (design, cicd) let a pack be reached by the config token that selects it, which is what rescued a CI pack no menu could offer. The secrets-manager category then landed on the backing axis behind assets/contracts/secrets.md, where the whole decision is where the secret lives and what onboarding a teammate costs — and where devtools' Doppler doctrine went.

by Lauren Tan

if you want to go fast, go deep first. bleat helps you write less, but higher quality code. rigorous agent workflows you can parallelize with confidence. Codex port of the Claude Code plugin; skills are shared, tool names resolve via skills/just-bleat-it/references/codex-tools.md.

by chshin84

Team engineering discipline (SSOT principles) + per-domain design references + runtime LLM verification reviewers + spec/plan & doc review gates, for Codex. Mirrors the Claude Code plugin via shared skills and hook logic.

by kouko

Optional using-loom-design discovery routing and two stations — capture-intent, write-spec — turn a rough idea into a confirmed intent and a risk-declared spec, route non-blocking second-vendor suggestions, and provide product-principles and design-system tools. Reads loom-code's contract package. Claude Code, Codex + Antigravity CLI.

by Lauren Tan

if you want to go fast, go deep first. pstack helps you write less, but higher quality code. rigorous agent workflows you can parallelize with confidence. Third-party plugin by Lauren Tan, ported from Cursor.

by Lauren Tan (upstream), Théo Moura (Claude Code port)

if you want to go fast, go deep first. pstack helps you write less, but higher quality code. rigorous agent workflows you can parallelize with confidence. Claude Code port of cursor/plugins/pstack.