This repository contains plugins for Tomitribe's open source libraries and team workflow commands.
Add the Tomitribe marketplace to Claude Code:
/plugins → Marketplace → +Add Marketplace → tomitribe/claude-plugins
Then enable the plugins you want from the list.
Skills that auto-activate when you're working with Tomitribe libraries:
| Plugin | Library |
|---|---|
churchkey | Cryptographic key parsing/export (PEM, JWK, OpenSSH, SSH2) |
crest | Annotation-driven CLI framework |
pixie | Lightweight dependency injection, configuration, and events |
jaws | Typed S3 proxy interfaces |
tomitribe-util | Encoding, I/O, duration/size, templates, collections, reflection |
tomitribe-util-dir | Strongly-typed filesystem manipulation with Dir proxies |
archie | Streaming archive transformation |
checkmate | Fluent validation |
http-signatures | HTTP message signing (HMAC, RSA, ECDSA) |
swizzle | Stream manipulation and lexing |
java-conventions | Tomitribe Java coding standards (final keyword, etc.) |
Commands for working effectively with Claude Code. Enable via workflow@tomitribe.
/design [topic]Starts a structured design session. Claude discusses, tracks decisions, captures
rejected alternatives, and documents open questions — all before any code is written.
Creates a working document at docs/dev/<topic>-working-doc.md.
Use for problems that cross system boundaries, have multiple interconnected decisions, or where the first solution that comes to mind probably isn't the best one.
/improveReviews recent git history and proposes CLAUDE.md improvements based on what actually happened. Identifies three categories:
Run after completing significant work to make Claude permanently better for the next session.
/handoffBefore /clear, dumps session state to HANDOFF.md so the next session picks
up cleanly. Covers what was done, decisions made, what's next, gotchas, and
how to continue.
/recapQuick "where was I?" for when you return to an open session. Summarizes what you were working on, what got done, where you left off, and what's next.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
npx claudepluginhub tomitribe/claude-plugins --plugin checkmateStrongly-typed filesystem manipulation with Dir proxy interfaces
Tomitribe utility library reference — encoding, I/O, duration/size, templates, collections, reflection, and more
Pixie lightweight dependency injection, configuration, and event library reference
JAWS (Java AWS S3) typed proxy library reference
Swizzle stream manipulation and lexer library reference
Validate API schemas with JSON Schema, Joi, Yup, or Zod
Validates Claude Code configuration files for security, structure, and quality. Reviews CLAUDE.md, skills, agents, prompts, commands, and settings with comprehensive validation checklists.
Deterministic linting hooks, semantic code validators, and a multi-LLM advisory council. Enforces coding rules mechanically — not by suggestion.
Enforce mandatory pre-action verification checkpoints to prevent pattern-matching from overriding explicit reasoning. Use this skill when about to execute implementation actions (Bash, Write, Edit) to verify hypothesis-action alignment. Blocks execution when hypothesis unverified or action targets different system than hypothesis identified. Critical for preventing cognitive dissonance where correct diagnosis leads to wrong implementation.
Pre- and post-implementation validation with parallel subagents: /replan validates plans before execution, /recheck verifies implementations match the plan
DevsForge JSON validator with schema validation, formatting, JSONPath queries, diff comparison, and comprehensive error reporting