/profiles

Make it your own.

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

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

What the agent does

1. Run toolkit profiles with the full relevant query; for specific details run toolkit profile ID. Read [profile selection](../../references/profiles.md) for scope and precedence.
2. Return a focused comparison and useful examples. Search is lexical discovery, not an authority or competence score.
3. Role discovery lists priorities and concrete contributions; browsing a role does not activate it.

Inputs

• Optional role family, specialty, level or task description.

Optional context: query, comparison, task context.

Scope

Reads

The shipped profile catalog and supplied task context.

Writes

No changes to active profile, project files, global settings or external state.

Mode

Inspect only. Accept a role, discipline, level or task description as appended context.

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 role IDs, purpose, priorities and example use.
• Clear distinctions between close profiles and their suggested workflows.

How the work is checked

• Every listed profile exists in the installed catalog. Discovery leaves the active task selection unchanged.

When to stop or clarify

• Do not activate a role, install tools or execute suggested workflows from a discovery request.

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

Inspect role purpose, priorities, boundaries and candidate workflows relevant to the requested job.

Method

Compare roles by concrete decision focus, then link the workflows supplying technical methods.

Pitfall

A job title is neither a credential nor evidence that all specialty checks were performed.

Check

Explain how candidate roles would change priorities on the same task without widening permissions or claiming a team exists.

Situational decisions

When several profiles appear relevant: Compare primary responsibility and actual task evidence; show options without silently activating one.

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