jado-install

Installs JADO locally or globally, links a repository to the global method and guides migration of design instructions.

ID: jado-install.

What it does

Prepares the method in the selected .jado folder: a standalone copy in the repository or a global copy for the user. Linking adds only the project entry point. Existing external global skills remain with their current manager; native profiles are prepared for Claude Code, Codex and OpenCode when selected. The AI completes migration of old routers while showing the diff and preserving product contracts.

When to use it

When you want to adopt JADO in a repository or across all projects for your user, link a repository to the global setup or update the method and upstream skills with an explicit command.

How to use it

Ask for it by name, or invoke it with /jado-install in Claude Code or $jado-install in Codex. From the JADO checkout, use npm run jado -- install and choose the destination and tools. For AI use, specify --global or --local --target /repo, add --agents and prepare the plan with --dry-run --json; apply it with --yes --revision HASH. Use link --target /repo to link the project to the global setup. With update, choose the destination and, when needed, --component method or skills. Follow migration.md to resolve old instructions and verify an ordinary design request in a new session.

What it delivers

Plan with destination, tools, files and revision; backups of modified files
Local or global method copy, or linked project entry point
Skills and profiles only for the selected tools; instructions to migrate and checks still to complete

Example

Install JADO for Claude Code and Codex in this repository. Show me the plan, then complete migration of design routing in the files actually read, preserving domain, design system, verification, Git and release instructions.

Prerequisites

JADO checkout with installed dependencies and current artifacts
Accessible destination and explicitly selected tools; upstream access for missing skills or updates
When linking, AI session permissions to read the global method; files verified by the CLI do not prove native loading