Skip to content

ShipWithAI/shipwithai-plugins

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

65 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

shipwithai-plugins

Open-source Claude Code plugins. Build a real project harness — not another pasted CLAUDE.md.

Install this first: shipwithai-starter — CLAUDE.md, permissions, hooks (and more) via a ~5-minute interview.

License Claude Code plugin GitHub stars

Website · Issues · Claude Code Mastery (free course)


Prerequisites

  1. Claude Code installed and working
  2. A project directory you can write to (or an empty folder for greenfield)
  3. ~5 minutes for Essential tier (/shipwithai-starter:init)

Install shipwithai-starter (≈5 minutes)

# 1) Register this marketplace once
/plugin marketplace add ShipWithAI/shipwithai-plugins

# 2) Install the hero plugin
/plugin install shipwithai-starter@shipwithai

# 3) Run setup in your project
/shipwithai-starter:init

Marketplace name: shipwithai (see .claude-plugin/marketplace.json).

Done when

  • shipwithai-starter appears in your Claude Code plugin list / skills
  • After init: project has CLAUDE.md and/or .claude/settings.json (Essential+)
  • You can re-run /shipwithai-starter:review to audit the harness

What you get

  • Guided harness setup — tiers: Essential (~5 min) / Standard (~15 min) / Full (~30 min)
  • 13 skills (plugin v2.4.0): init, new-project, review, update-ssot, optimize-harness, and setup pillars (memory, permissions, hooks, MCP, agents, SSOT, observability, skills)
  • MIT, no build step, no runtime dependency — Markdown + JSON skills Claude Code loads directly

Plugins

Plugin In tree Marketplace Role Skills Install target
shipwithai-starter (v2.4.0) ✅ listed Start here — harness for any project 13 shipwithai-starter@shipwithai
shipwithai-auth (v1.7.1) ✅ listed Next.js auth (Better Auth / Firebase) 2 shipwithai-auth@shipwithai
shipwithai-harness (v2.0.0) ✅ listed Auto-detect stack → harness generator 2 shipwithai-harness@shipwithai

Secondary plugins (after starter)

Plugin One-liner Slash commands
auth Production auth for Next.js — Better Auth or Firebase, OAuth, UI, schema. /shipwithai-auth:setup · /shipwithai-auth:doctor
harness Scan project → CLAUDE.md, settings, safety hooks (Next.js / Laravel / Spring Boot and more). /shipwithai-harness:setup · /shipwithai-harness:doctor

Dogfood

We dogfood these plugins on real ShipWithAI / Mangala work. Source is readable Markdown and JSON before you run anything.


Links


Install other plugins (after starter)

After the marketplace is registered (step 1 above):

/plugin install shipwithai-auth@shipwithai
/shipwithai-auth:setup

/plugin install shipwithai-harness@shipwithai
/shipwithai-harness:setup

Local / development install

git clone https://github.com/ShipWithAI/shipwithai-plugins.git
claude --plugin-dir ./shipwithai-plugins/plugins/starter
# or: plugins/auth | plugins/harness

Repository structure

shipwithai-plugins/
├── plugins/
│   ├── starter/                 # shipwithai-starter v2.4.0
│   ├── auth/                    # shipwithai-auth v1.7.1
│   └── harness/                 # shipwithai-harness v2.0.0
├── .claude-plugin/
│   └── marketplace.json         # name: shipwithai
├── docs/
├── scripts/publish-plugin.sh
└── CLAUDE.md

No compiled code. Plugin content is Markdown (SKILL.md, references) and JSON (manifest, evals, settings).


Troubleshooting

  • Marketplace add fails — update Claude Code; check network / git access to GitHub
  • Skill not found — use the full slash with plugin prefix: /shipwithai-starter:init (not /starter:init)
  • Permission denied writing .claude/ — run init inside a project directory you can write to

Contributing

Open issues for bugs and feature requests. For new skills or providers, check open issues first.

  1. Read CLAUDE.md before authoring plugins.
  2. Add a directory under plugins/ with plugin.json / manifest.json, skills (SKILL.md + evals).
  3. If the plugin should be marketplace-installable, add it to .claude-plugin/marketplace.json and keep versions honest.
  4. Test on two real projects before opening a PR.
./scripts/publish-plugin.sh starter --dry-run

License

MIT — see LICENSE.

About

No description, website, or topics provided.

Resources

License

Stars

7 stars

Watchers

0 watching

Forks

Packages

 
 
 

Contributors