/help

Make it your own.

In Claude Code, use the slash command and add your context. In Codex, select help from the just-vibe skill picker, then send the same brief.

Version 0.11.0 also supports /jv help, /just-vibe help and /jv:help in Claude. See shortcut setup and context examples.

What the agent does

1. Use toolkit tools with the supplied scenario and the actual target host: codex, claude, or the editor adapter id, which lists just-vibe-<id> skill names. Read only the matching command contracts with toolkit show; do not load all skills.
2. Answer the immediate usage question with the smallest useful invocation for the best matching available workflow, preserving all user constraints. If a candidate is unknown or blocked, name the precise missing task evidence or integration.
3. If the user asks installation questions, use the installed setup skill or the bundled installer help. A help question is not permission to execute the recommended workflow.

Inputs

• optional command name, scenario, or question. Requires the shipped catalog and actual implementation status.

Optional context: scope, references, constraints, successCriteria, environment, mode, budget.

Scope

Reads

Explain usage and recommend workflows; inventory browsing belongs to `tools`.

Writes

No source changes in inspect/plan. Save only requested planning artifacts. A separately requested repair uses the relevant implementation workflow.

Mode

Inspect; optional command name, scenario, or question. Requires the shipped catalog and actual implementation status.

Prerequisites

Resolve the user brief and inspect the relevant project or supplied evidence. External capabilities are optional unless the selected action actually needs them.

Expected output

• Relevant usage instructions with availability and examples.
• Selected command, why it fits, required context and host-appropriate invocation.

How the work is checked

• A scenario finds the correct specialist command; a planned command is clearly identified as unavailable.

When to stop or clarify

• Do not execute the recommended workflow merely because help was requested. Fall back to installed capabilities when discovery is incomplete.

Handling missing context

Infer

Resolve the named files, existing scripts, current task and earlier corrections from the conversation and repository.

Assume

Use the narrowest interpretation that completes a reversible local task; state a consequential assumption once.

Ask

Ask when competing targets or incompatible success conditions would change the result; continue independent inspection first.

Technical guidance

Evidence

Resolve the user's task and whether they need discovery, invocation syntax or workflow details.

Method

Show a small relevant selection with appended-context examples and necessary prerequisites.

Pitfall

Dumping every command creates search burden; a lexical match does not establish capability availability.

Check

Confirm each suggested command exists and explain the boundary between near matches without starting the task implicitly.

Situational decisions

When the best workflow lacks required evidence: Explain the missing capability and a useful evidence-only alternative without falsely marking it available.

The coding agent follows this workflow using its available tools. Installation does not grant service access or guarantee an outcome. Read the compatibility notes.

Keep exploring