mokata

Skills

26 in the Claude listing

• apimokata · API & interface design — contract-first, blast-radius on every change.
• brainstormmokata · Socratic pre-spec exploration — explore approaches WITH the user, one question at a time, and HARD-GATE the spec behind explicit approval.
• Browser testingmokata · Browser testing (DevTools) — live runtime captured via the existing MCP surface, fed to the test gate.
• bugmokata · Start from a reproducer and a failing test, then fix.
• Ci cdmokata · CI/CD & automation — the quality-gate pipeline + Scorecard posture, not a suggestion.
• debugmokata · Reproduce first, capture in a failing test, then fix.
• deprecationmokata · Deprecation & migration — remove nothing without walking its blast-radius first.
• developmokata · Implement the minimum to turn a failing test green.
• Docs adrmokata · Documentation & ADRs — an architecture decision is persisted to memory + the ledger, not lost.
• docsyncmokata · Keep the docs TRUE to the code — audit a doc (or sweep + drift-detect the docs) against the code, then reconcile the drift behind a human-gated, previewed write.
• Frontend a11ymokata · Frontend UI + accessibility — WCAG-AA checked in review, design-system conventions remembered.
• gitmokata · Git workflow & versioning — atomic commits + change-sizing riding the WriteGate, not habits.
• governmokata · See the governed state — rules, memory-by-kind, read/write ratio, pending proposals (read-only).
• Mcp repairmokata · Repair the mokata MCP server when its tools aren't connecting — check the registration, fix it, and tell you the one step left (restart Claude Code).
• onboardmokata · Guided capture of the project's rules, guardrails, conventions, domain context & docs into TYPED, human-gated memory the skills then reference.
• optimizemokata · Measure first; keep only proven, behaviour-preserving wins.
• performancemokata · Performance optimization — measure-first, before/after to the ledger, no guessing.
• playbookmokata · Run the full v1 story end-to-end on this repo (integration check).
• refinemokata · Deep, user-steerable review of EXISTING code → propose prioritized refinements → HARD-GATE a scoped set, then hand off to spec.
• review
• securitymokata · Security & hardening — OWASP items as HARD-enforced rules, not advice.
• sessionmokata · Portable / shareable tagged sessions — package this session and resume it on another machine or hand it to a teammate.
• shipmokata · Verify it's truly done, then let YOU choose how to land it.
• shippingmokata · Shipping & launch — a pre-launch checklist + staged rollout + rollback thresholds feed the ship-readiness gate.
• specmokata · Turn the problem into testable acceptance criteria; map each to a test.
• testmokata · Write failing tests first (RED); no implementation.