claude

mokata

Spec-driven TDD framework: brainstorm -> provable completeness gate -> RED-before-GREEN -> review, with a codebase knowledge graph, self-healing memory, token governance, and human-gated writes. Local-first, Apache-2.0.

19 on GitHubby MoStackv0.0.27Apache-2.0updated 7 days ago
/

Plugin mokata from marketplace mostack in JasGujral/mokata-oss. Commands read from the repo's manifest — 7 days ago.

This plugin runs code on your machine — it starts local MCP servers. The exact commands are listed below; read them before installing.

What it installs

Skills (29)

  • api

    mokata · API & interface design — contract-first, blast-radius on every change.

  • backend-nestjs

    mokata · NestJS rule pack — impact-ordered rules for modules, guards, DTOs and providers, loaded by the spec's routing.

  • brainstorm

    mokata · Socratic pre-spec exploration — explore approaches WITH the user, one question at a time, and HARD-GATE the spec behind explicit approval. Runs standalone or as the front of mokata's pipeline.

  • browser-testing

    mokata · Browser testing (DevTools) — live runtime captured via the existing MCP surface, fed to the test gate.

  • bug

    mokata · Start from a reproducer and a failing test, then fix.

  • ci-cd

    mokata · CI/CD & automation — the quality-gate pipeline + Scorecard posture, not a suggestion.

  • debug

    mokata · Reproduce first, capture in a failing test, then fix.

  • deprecation

    mokata · Deprecation & migration — remove nothing without walking its blast-radius first.

  • develop

    mokata · Implement the minimum to turn a failing test green.

  • docs-adr

    mokata · Documentation & ADRs — an architecture decision is persisted to memory + the ledger, not lost.

  • docsync

    mokata · 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-a11y

    mokata · Frontend UI + accessibility — WCAG-AA checked in review, design-system conventions remembered.

  • frontend-perf

    mokata · Frontend performance for React web — measure, identify, fix, verify (keep or revert), guard; audit first, fix on request.

  • frontend-react

    mokata · React (web) rule pack — impact-ordered rules, loaded by the spec's routing, each with an Incorrect/Correct pair.

  • frontend-security

    mokata · Frontend security for React web — authorization first, then secrets in bundles, injection sinks and supply chain; audit first, fix on request.

  • git

    mokata · Git workflow & versioning — atomic commits + change-sizing riding the WriteGate, not habits.

  • govern

    mokata · See the governed state — rules, memory-by-kind, read/write ratio, pending proposals (read-only).

  • mcp-repair

    mokata · 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). Repair, not first-time setup.

  • onboard

    mokata · Guided capture of the project's rules, guardrails, conventions, domain context & docs into TYPED, human-gated memory the skills then reference.

  • optimize

    mokata · Measure first; keep only proven, behaviour-preserving wins.

  • performance

    mokata · Performance optimization — measure-first, before/after to the ledger, no guessing.

  • playbook

    mokata · Run the full v1 story end-to-end on this repo (integration check).

  • refine

    mokata · Deep, user-steerable review of EXISTING code → propose prioritized refinements → HARD-GATE a scoped set, then hand off to spec.

  • review

    mokata · Two-pass review: against the spec, then quality.

  • security

    mokata · Security & hardening — OWASP items as HARD-enforced rules, not advice.

  • session

    mokata · Portable / shareable tagged sessions — package this session and resume it on another machine or hand it to a teammate. Human-gated.

  • ship

    mokata · Verify it's truly done, then let YOU choose how to land it.

  • shipping

    mokata · Shipping & launch — a pre-launch checklist + staged rollout + rollback thresholds feed the ship-readiness gate.

  • spec

    mokata · Turn the problem into testable acceptance criteria; map each to a test.

MCP servers (1)

  • mokata

    runs: uvx --python >=3.12 --from mokata[full]==0.0.27 mokata-mcp

View source on GitHub mokata.ai

Similar plugins

Matt Pocock's agent skills for real engineering (grilling, spec/ticket flows, TDD, code review, domain modelling and more).

39 skills

mattpocock/skills 323,108

superpowers

claudecodex

Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques

15 skills · hooks

obra/superpowers 316,836

claude-mem

claudecodex

Persistent memory for Claude Code: the next session starts where the last one left off.

29 skills · 1 MCP server · hooks

thedotmack/claude-mem 116,618

AI-powered codebase understanding — analyze, visualize, and explain any project

9 skills · 10 agents · hooks

Egonex-AI/Understand-Anything 92,410

mem0

claudecodex

Cross-session memory and token savings for coding agents.

6 skills · 1 agent · 1 MCP server · hooks

mem0ai/mem0 68,893

mempalace

claudecodex

AI memory system — mine projects and conversations into a searchable palace. 47 MCP tools, auto-save hooks, guided setup.

3 skills · 6 commands · 1 MCP server · hooks

MemPalace/mempalace 60,536

Maintain mokata?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex pluginslisted