mojoai-king

by MojoAI

Splitting an oversized file without changing what it does: moving code rather than rewriting it, keeping every name and its callers, and ending in evidence a reader can check rather than a claim. Four cleanup skills were written for this pack and given an eval case each, run three times with the plugin and three times without it; this is the one whose runs beat their own baseline. The other three are recorded in docs/not-shipped with what was measured, because their cases could not tell the difference.

by MojoAI

Keeps the assistant's context small. A read guard hook refuses a whole-file read of a non-image file over 50KB with the reason, so the session reads a range or summarizes the file instead (enforced on Claude Code). A bounded session-start checklist hook, and a context-hygiene skill with the rules for large results, idle gaps, shell output (run checks through skilliton gate) and subagents. A separate, reversible setup script adds a status line that logs real quota; the config drift check is a manual diagnostic.

by MojoAI

Checks each shell command the assistant runs before it runs. Blocks force-pushes to protected branches (main and master by default), git hooks skipped with the no-verify flag, and staging or committing files or added lines that look like secrets; asks for confirmation before git commands that discard uncommitted work (Codex cannot ask from a hook, so there those commands are blocked with the reason). It reads the command text, so it catches ordinary and accidental commands, not deliberately hidden ones. A skill explains each rule and its settings.

by MojoAI

The team's way of working and the Skilliton runtime. Skills: task (a request becomes a tracked, recoverable piece of work), dispatch (many items become verified parallel lanes), handoff, maintain, review (plain-English review with a commit verdict) and security (evidence, not assurances). Agents: lane, locate and verify-item, each naming the model and effort it runs on. Runtime (skilliton on the shell path in Claude Code): prepare and migrate projects, task records and checkpoints, status, decision and lesson entries, project security evidence, release verification, the delivery gate, gate (a project's checks as a verdict with the output in a log) and dispatch (a lane plan becomes one Git worktree per lane, each with a brief that bounds it). Hooks: session start shows the handoff and project state; stop reminds to record a checkpoint, and names maintain when a batch has merged; a prompt that reads as six or more separate items gets one note suggesting dispatch; pre-compact and session end keep a local journal for recovery.