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 churchkeyStrongly-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
Encrypted secrets manager for Claude Code sessions backed by a private Git repo
Living Ontology for Claude Code - Captures and reuses knowledge across sessions
Encrypt and decrypt data with various algorithms
Secure coding, OWASP guidance, input validation, cryptography, authentication, and secrets management for secure application development.
Secret safety hooks: auto-load credentials via CLAUDE_ENV_FILE, redact secrets from CLI output. Powered by the nopeek CLI.
Use this agent when you need to analyze a service or codebase component and create comprehensive documentation in CLAUDE.md files. This agent should be invoked after implementing new services, major refactoring, or when documentation needs updating to reflect the current codebase structure. Examples: <example>Context: The user has just implemented a new authentication service and wants to document it properly. user: 'I just finished implementing the auth service, can you document how it works?' assistant: 'I'll use the codebase-documenter agent to analyze the authentication service and create detailed documentation in CLAUDE.md' <commentary>Since the user has completed a service implementation and needs documentation, use the Task tool to launch the codebase-documenter agent to create comprehensive CLAUDE.md documentation.</commentary></example> <example>Context: The user wants to ensure a newly added API module is properly documented for the team. user: 'We need documentation for the new payment processing API I just added' assistant: 'Let me use the codebase-documenter agent to analyze the payment processing API and create proper documentation' <commentary>The user needs documentation for a new API module, so use the codebase-documenter agent to create CLAUDE.md files with setup instructions and architectural notes.</commentary></example>