Setup · Install or link JADO

How to use this routeCopy Anchor Link

Follow jado-install for the plan, semantic migration and access verification. Local and global setup give selected JADO skills priority with backups; external packages come from upstream. Linking updates project entry points. Apply updates through the CLI for the selected destination.

Stages: any (the route does not depend on design maturity). Work surface: as specified in the assignment. Involvement and budget come from the run's dials (shared rules).

MapCopy Anchor Link

Read from top to bottom. Labeled arrows show conditions; dashed arrows exist only in the stages they name; loops represent repairs within the budget. Instructions for each node appear below.

flowchart TD
  n_start(["Choose setup destination"])
  n_procedure["Read installation procedure"]
  n_read["Read instructions and configuration"]
  n_tools["Choose mode and tools"]
  n_existing{"Does an entry already exist?"}
  n_create["Prepare a JADO entry"]
  n_migrate["Prepare design migration"]
  n_files["Prepare the setup plan"]
  n_review["Review the setup diff"]
  n_apply["Apply authorized changes"]
  n_verify["Verify access and profiles"]
  n_gate{"Is setup verified?"}
  n_done(["Deliver verified setup"])
  n_stop(["Report remaining setup checks"])
  n_start --> n_procedure
  n_procedure --> n_read
  n_read --> n_tools
  n_tools --> n_existing
  n_existing -->|"No"| n_create
  n_existing -->|"Yes"| n_migrate
  n_create --> n_files
  n_migrate --> n_files
  n_files --> n_review
  n_review -->|"Approved diff"| n_apply
  n_apply --> n_verify
  n_verify --> n_gate
  n_gate -->|"Yes, checks complete"| n_done
  n_gate -->|"No, requirement or evidence missing"| n_stop

Input and outcomeCopy Anchor Link

• Input: JADO source and local or global destination; Existing instructions and configuration; Selected AI tools.
• Outcome: Installed method or linked project; Migrated design instructions and setup verification.

Work limitsCopy Anchor Link

Route cap: no new delegations; no additional repair batch. The effective budget is the lower of this cap and the budget dial; the stage sets the fix passes per artifact. Shared rules.

Step instructionsCopy Anchor Link

Choose setup destinationCopy Anchor Link

Locate the JADO source and choose local, global or linked setup.

ID: start.

Continue with «Read installation procedure».

Read installation procedureCopy Anchor Link

Follow jado-install. Setup is a separate assignment from product work.

Skill instructions jado-install ID: procedure.

Continue with «Read instructions and configuration».

Read instructions and configurationCopy Anchor Link

Inspect effective entries, overrides, linked Markdown, nested rules and Git state. For global setup inspect the tools' user-level instructions. Preserve product documents and existing UX artifact locations until migration is verified.

ID: read.

Continue with «Choose mode and tools».

Choose mode and toolsCopy Anchor Link

Reuse received choices. Local is self-contained; global manages the user-level method and upstream dependencies; linked setup adds a project entry. Claude Code, Codex and OpenCode have native adapters; other skills CLI targets receive skills only in local setup.

ID: tools.

Continue with «Does an entry already exist?».

Does an entry already exist?Copy Anchor Link

Inspect the effective instructions at the selected destination.

ID: existing.

• No → «Prepare a JADO entry».
• Yes → «Prepare design migration».

Prepare a JADO entryCopy Anchor Link

Prepare a concise method pointer while preserving project constraints.

ID: create.

Continue with «Prepare the setup plan».

Prepare design migrationCopy Anchor Link

Update the effective entry and reached files. Replace incompatible routers while preserving domain, design system, verification, Git and release rules.

ID: migrate.

Continue with «Prepare the setup plan».

Prepare the setup planCopy Anchor Link

Run install, link or update with --dry-run and retain the revision. The plan shows files, references and conflicts; router replacement also needs a semantic migration diff.

ID: files.

Continue with «Review the setup diff».

Review the setup diffCopy Anchor Link

Review proposed destination files and instruction changes before applying them. Honor authorization already supplied in the task.

ID: review.

• Approved diff → «Apply authorized changes».

Apply authorized changesCopy Anchor Link

Apply the reviewed plan with --yes and --revision HASH. The CLI checks collisions and hashes and retains backups. Apply the reviewed instruction diff with verified backup; commit or push needs its own authorization.

ID: apply.

Continue with «Verify access and profiles».

Verify access and profilesCopy Anchor Link

Check diff, links, catalog and instructions. For linked setup verify external reads in the AI session as well as the CLI. Use a local copy if external access is blocked. Verify route and available native profiles in a fresh session.

ID: verify.

Continue with «Is setup verified?».

Is setup verified?Copy Anchor Link

Distinguish completed checks from prepared files still awaiting load verification or a missing requirement.

ID: gate.

• Yes, checks complete → «Deliver verified setup».
• No, requirement or evidence missing → «Report remaining setup checks».

Deliver verified setupCopy Anchor Link

Return source, changed files and instructions with completed checks.

ID: done.

The route ends here.

Report remaining setup checksCopy Anchor Link

Return prepared setup and state missing requirements or verification; generated files alone do not prove native execution.

ID: stop.

The route ends here.

Method and sources