/profile

Make it your own.

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

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

What the agent does

1. Read [profile selection](../../references/profiles.md), then use toolkit profiles and toolkit profile ID to find and inspect relevant roles.
2. Keep simple selection in task context. With an existing run, call session profile using run and selection; with a new explicit single role, workflow COMMAND --profile ID preserves it. Do not create a fresh run just to evade a prior pin or budget.
3. State the selected profile and its concrete task contribution briefly once. Apply relevant priorities in subsequent workflows without repeating role claims, changing permissions or scope, overriding a user pin, or forcing every suggested workflow to run.

Inputs

• The requested role or auto/clear/status intent, current task context and any existing user-pinned selection.

Optional context: primary role, up to two secondary roles, selection reason, task scope.

Scope

Reads

Relevant catalog entries, current task instructions and enough project evidence to choose responsibly.

Writes

Only active task context or a supplied run record returned as JSON. Persist to a user-requested location only when explicitly asked; never change global host settings.

Mode

Inspect/project-read-only; changing in-context task selection does not grant apply mode. Preserve all appended task constraints.

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

• Primary and secondary role IDs, selection source, task scope, pin state and short evidence-based reason.
• Relevant priorities, checks and conflicts with the task brief; original scope and permissions stay intact.

How the work is checked

• Pinned user choices survive automatic routing. Profile changes preserve brief, mode, scope, authorization, budgets, attempts and original success criteria.
• A profile never creates a subagent, installs tools, changes credentials or claims professional expertise.

When to stop or clarify

• Keep an existing pin when an inferred role conflicts; ask only if an explicit conflicting request needs resolution.
• If no role fits, continue with ordinary task guidance and state that limitation. Do not invent a shipped role.

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

Read current selection, explicit user pins, task scope and proposed primary/secondary roles.

Method

Preserve pins and apply role priorities through the relevant workflow methods; record selection provenance and conflicts.

Pitfall

Agent inference cannot clear a user pin, and a principal role does not authorize broader architecture changes.

Check

Confirm the recorded selection and pin state match the request and that the brief, constraints and scope are unchanged.

Situational decisions

When the user requests auto after pinning a role: Record a user clear with the actual request as reason, then record an unpinned agent selection based on task evidence.

When the agent discovers a new focus while a user selection is pinned: Retain the selection and apply required task checks without silently changing roles.

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