Dojo

A Claude Code plugin marketplace, providing an AI-assisted SDLC (Kaizen), motion design as code (Motion Studio) and presentation decks as HTML (Slide Studio).

Available plugins

Everything is in English. Claude still answers in the language you write in.

Installation

1. Add the marketplace

/plugin marketplace add Lingelo/dojo

Or interactively:

/plugin
# Go to the "Marketplaces" tab > "Add marketplace"
# Enter Lingelo/dojo

Installed under the marketplace's previous name? Remove it (/plugin marketplace remove <old name>),
add Lingelo/dojo, reinstall the plugins, and use @dojo in enabledPlugins / extraKnownMarketplaces.

2. Install the plugins

Interactive (recommended):

/plugin
# Go to the "Discover" tab and select the plugins to install

Direct installation:

/plugin install motion-studio@dojo
/plugin install kaizen@dojo
/plugin install kaizen-ops@dojo      # only if you deploy with Kaizen
/plugin install slide-studio@dojo

Team configuration

Add to your project's .claude/settings.json to configure every team member automatically:

{
  "extraKnownMarketplaces": {
    "dojo": {
      "source": {
        "source": "github",
        "repo": "Lingelo/dojo"
      }
    }
  },
  "enabledPlugins": {
    "kaizen@dojo": true,
    "kaizen-ops@dojo": true,
    "motion-studio@dojo": true,
    "slide-studio@dojo": true
  }
}

Managing plugins

Usage examples

Kaizen

/kaizen:help                                    # what it is, where the repo stands, which command to run
/kaizen:setup audit                             # what the project lacks (CI, secrets, deployment…), fixed by priority
/kaizen:setup                                   # config, profile (by the repo's stakes), detected deployment
/kaizen:constitution                            # the project's non-negotiable principles
/kaizen:brainstorm orders CSV export            # WHAT to build → docs/plans/…-plan.md
/kaizen:plan                                    # HOW → units, tests, rollback + plan review
/kaizen:work                                    # test first, quality gate, multi-agent review
/kaizen:ship                                    # reviewable PR, then /kaizen:watch-pr until "ready"
/kaizen:learn                                   # the learning, read back by the next plan
/kaizen:autopilot                               # or chain everything after the brainstorm
/kaizen-ops:deploy production                   # approved, watched production release, rollback ready (kaizen-ops)

Documentation: getting started ·
guides per skill ·
configuration ·
troubleshooting ·
how it works ·
CLI reference.

Motion Studio

/motion-video 8-second 16:9 teaser for our API launch, dark style, orange accent

Storyboard → HTML/CSS/SVG/Canvas composition → control stills → frame-by-frame MP4 render (virtual
clock, motion blur, supersampling) with synced sound effects, music, voice-over and subtitles.
Dependencies (Playwright, Chromium, ffmpeg) installed automatically on first use.

Slide Studio

/slides 10-minute talk for the team offsite on our move to smaller pull requests, paper theme

Brief → storyline (one assertion title per slide, a layout per message) → deck scaffolded from the
themed template → every slide audited at its real size (slides.mjs check) → contact sheet, PNGs and PDF.
The HTML file presents itself in any browser (← / →, O overview, N notes, F fullscreen).
Writing a deck needs nothing; Playwright and Chromium are installed automatically for check and export.

Structure

dojo/
├── .claude-plugin/
│   └── marketplace.json      # Marketplace registry
├── .github/workflows/        # CI (kaizen.yml: Kaizen tests on Linux, macOS, Windows; slide-studio.yml: same for Slide Studio)
├── docs/                     # This repo's own brainstorms, plans and learnings
├── plugins/
│   ├── kaizen/               # AI-assisted SDLC: skills, agents, hooks, zero-dependency CLI
│   ├── motion-studio/        # Motion design videos from HTML (Playwright + ffmpeg)
│   └── slide-studio/         # Presentation decks as one HTML file, audited and exported (Playwright)
├── CLAUDE.md
└── README.md

Contributing

1. Create a new plugin in plugins/your-plugin/
2. Add .claude-plugin/plugin.json with the metadata (name, version, description, author)
3. Add commands, agents, skills or hooks as needed
4. Register it in .claude-plugin/marketplace.json
5. Add a README.md documenting your plugin, in English

Test suites: node --test plugins/kaizen/tests/*.test.mjs (Kaizen) and
node --test plugins/slide-studio/tests/*.test.mjs (Slide Studio).

License

MIT