compress

<p align="center"> <img src="brand/roxabi-plugins-logo.gif" alt="roxabi-plugins logo" width="400"> </p>

<h1 align="center">Roxabi-plugins</h1>

<p align="center"> <img src="https://img.shields.io/badge/license-MIT-22c55e" alt="License"> <img src="https://img.shields.io/badge/Bun-runtime-FBF0DF?logo=bun&logoColor=black" alt="Bun"> <img src="https://img.shields.io/badge/Claude%20Code-plugins-CC785C" alt="Claude Code"> </p>

<p align="center">Open-source Claude Code plugins by <a href="https://github.com/Roxabi">Roxabi</a>. Context engineering tools for teams using Claude Code.</p>

Why

Every team using Claude Code ends up reinventing the same things: documenting their workflow in CLAUDE.md, writing custom slash commands for code review, figuring out how to structure CI setup prompts, syncing docs after a refactor. It works, but it's disposable — none of it is reusable across projects.

Roxabi plugins are the reusable layer on top of Claude Code. Each plugin ships opinionated, battle-tested skills and agents for a specific domain. Install what you need, skip what you don't, and get consistent AI-assisted workflows across every project without starting from scratch.

Quick Start

# 1. Add the marketplace (once per machine)
claude plugin marketplace add Roxabi/roxabi-plugins

# 2. Install the plugin you need
claude plugin install dev-core        # full dev lifecycle
claude plugin install web-intel       # URL research + analysis
claude plugin install compress        # token-efficient skill notation

Then trigger any skill by describing what you want — no slash commands to memorize:

"start working on issue #42"    → /dev
"improve readme"                → /readme-upgrade
"sync docs after this refactor" → /doc-sync
"scrape and summarize this URL" → /summarize

How it works

Each plugin is self-contained: it ships skills (trigger-phrase workflows), agents (specialized sub-processes), and optionally hooks (automated guardrails that run on every tool call). Claude Code discovers and loads them automatically on install.

flowchart LR
    A[claude plugin install] --> B[Skills loaded into Claude]
    B --> C{You describe a task}
    C --> D[Claude matches trigger phrase]
    D --> E[Skill runs — agents, tools, hooks]
    E --> F[Result in your repo]

Plugins are project-agnostic: they read your stack from .claude/stack.yml at runtime and adapt to your framework, package manager, and file layout. The same dev-core plugin works on a NestJS monorepo and a Django service.

Plugins

Development lifecycle

Research & analysis

Content & branding

Forge has moved to its own marketplace: Roxabi/roxabi-forge. Install: claude plugin marketplace add Roxabi/roxabi-forge

Career tools

Utilities

Endorsed marketplaces

External plugin marketplaces we endorse. Install them directly — no vendoring needed.

claude plugin marketplace add <source>

Wrapped plugins

High-quality external skills packaged as first-class installable plugins. Roxabi adds versioning, install support, and a README; the source is vendored via git subtree. Attribution is in each plugin's README.

Data storage

Data-producing plugins store user data in ~/.roxabi-vault/ — never in the repo. Override the location with the ROXABI_VAULT_HOME environment variable. Vault functionality is provided by roxabi-vault.

Marketplace architecture

Two kinds of plugins live in this repo:

Native plugins — built and maintained by Roxabi. We own the full lifecycle: dev-core, compress, 1b1, web-intel, cv, linkedin-post-generator, image-prompt-generator, get-invoice-details, linkedin-apply.

Wrapped plugins — high-quality external skills with no versioning or install mechanism in their source repo. Roxabi adds plugin structure and vendors the source (via git subtree or file copy) so they become installable. Existing wrapped plugins live in plugins/: frontend-slides, react-best-practices, composition-patterns, web-design-guidelines. New wrapped plugins go into external/.

External plugin marketplaces we endorse are tracked in `.claude-plugin/external-registry.json` (source of truth). `.claude-plugin/curated-marketplaces.json` mirrors the curated list for runtime discovery — the /dev-core ci-setup skill reads it and offers installation — no skill edits needed to add a new endorsed source.

Contributing

See CONTRIBUTING.md for how to add a plugin, wrap an external skill, or improve an existing one.

[!TIP]

The fastest way to add a plugin is to follow the step-by-step guide in CLAUDE.md — it covers directory structure, frontmatter, marketplace registration, and the commit format.

License

MIT