tempest
01Plugin Claude Code
tempest — a cross-harness software factory: opinionated build workflows as portable Agent Skills for Claude Code and pi.
2 2mo ago A
tokens not measured
original MIT
Instructions file CodexOpenCode
Instructions for mtthsnc/tempest, covering agents.md, what this repo is, golden rules, layout and working here.
2 2mo ago A 1,009 tokens
original MIT
Instructions file
Instructions for mtthsnc/tempest, a project described as: Tempest — a cross-harness software factory: opinionated build & QA workflows as portable Agent Skills for Claude Code and pi.
2 2mo ago A 3 tokens
copy · 100% MIT
tempest
04Plugin Claude Code
A software factory for AI coding agents: opinionated plan -> build -> review -> test -> ship -> reflect workflows, shipped as portable Agent Skills that run identically on Claude Code and pi.
2 2mo ago A
tokens not measured
original MIT
bcp
05Command
Set up or operate a Brand Context Protocol (BCP) — capture brand truth, produce on-brand output, score it.
2 2mo ago A 24 tokens
original MIT
bench
06Command
Measure Core Web Vitals and page performance for a page or change against a budget or baseline.
2 2mo ago A 18 tokens
original MIT
build
07Command
Execute an approved plan increment with discipline — follow patterns, verify, commit atomically.
2 2mo ago A 16 tokens
original MIT
office-hours
08Command
Reframe a raw idea or feature request with forcing questions before planning.
2 2mo ago A 13 tokens
original MIT
plan
09Command
Produce a reviewed implementation plan for a task before writing code.
2 2mo ago A 11 tokens
original MIT
qa
10Command
Verify a change works through the real browser UI with screenshot and assertion evidence.
2 2mo ago A 14 tokens
original MIT
review
11Command
Audit a diff or PR for correctness and security bugs and simplification opportunities, classifying findings and optionally fixing the safe ones.
2 2mo ago A 24 tokens
original MIT
ship
12Command
Land a reviewed change cleanly — tests, changelog, PR, green CI, verified deploy.
2 2mo ago A 19 tokens
original MIT
verify
13Command
Verify a change works by running the app and observing real behavior.
2 2mo ago A 12 tokens
original MIT
bcp
14Skill Claude CodeCodex
Use when brand or marketing work needs to be on-brand and traceable — set up a Brand Context Protocol (BCP) for a business, capture brand truth, or produce/score a deliverable (landing page, deck, email, ad copy) against the brand. Triggers on "set up a brand", "make this on-brand", "scaffold a BCP", "brand context…
2 2mo ago A 118 tokens
original MIT
bench
15Skill Claude CodeCodex
Use when you need to measure front-end performance or Core Web Vitals — LCP, CLS, INP/TBT, page load and hydration timing — for a page or a change, and judge it against a perf budget or baseline to catch regressions. Reach for it when a page feels slow, before/after a UI change, or when you must prove a perf budget…
2 2mo ago A 91 tokens
original MIT
office-hours
16Skill Claude CodeCodex
Use when you have a raw, vague, or unexamined idea or feature request and you want to pressure-test it with forcing questions BEFORE any planning or design — to make sure you build the right thing. Produces a sharpened problem statement and scope boundaries you can hand to the plan workflow. Skip when the problem is…
2 2mo ago A 77 tokens
original MIT
plan
17Skill Claude CodeCodex
Use when a coding task is non-trivial — a new feature, a multi-file change, a refactor, or anything with more than one reasonable approach — and you want a reviewed implementation plan before writing code. Produces a concrete, criticised plan you can hand to a build step. Skip for typo-level or single-obvious-line…
2 2mo ago A 71 tokens
original MIT
qa
18Skill Claude CodeCodex
Use when you must verify a change actually works through the REAL browser UI — acceptance, end-to-end, smoke tests, form interactions, navigation, login flows — driven by the agent-browser tool. Invoke when "click through it", "does the UI work", "smoke test the page", or browser-level evidence (screenshots…
2 2mo ago A 94 tokens
original MIT
review
19Skill Claude CodeCodex
Use when you have a diff, a PR, or a set of changed files and want a staff-engineer-level audit before it merges — correctness and security bugs, error handling, and simplification/reuse opportunities — with findings classified by severity and confidence and high-confidence fixes optionally applied and verified. Skip…
2 2mo ago A 68 tokens
original MIT
ship
20Skill Claude CodeCodex
Use when a change has been reviewed and you are ready to land it — merge the PR, cut the release, or push to production. Drives the change out the door: tests in place, changelog updated, a tight PR description, CI green, and the deploy verified end-to-end. Skip while still building or before review; this is the last…
2 2mo ago A 80 tokens
original MIT
verify
21Skill Claude CodeCodex
Use when you need to confirm a code change actually works by running the app and observing real behavior — not by trusting green unit tests. Triggers — verify a PR or fix, confirm a feature works, manually validate a change before shipping, start the app/server/CLI and exercise the specific behavior the change…
2 2mo ago A 88 tokens
original MIT