/copy

Make it your own.

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

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

What the agent does

1. Identify the decision each label or message supports and the legal or business meaning it must keep.
2. Make actions and errors specific, then check truncation, pluralization, missing-value variants and localization space before updating the authorized surfaces.

Inputs

• audience, intent, voice, and relevant product facts.

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

Scope

Reads

Labels, help text, error messages, and supplied marketing content; no invented guarantees or policy changes.

Writes

Apply: only the requested local changes and relevant isolated verification. Inspect/plan requests remain inspection/planning. External actions require their exact action and target in session authorization.

Mode

Apply to specified UI/docs; plan for alternatives only. Requires audience, intent, voice, and relevant product facts.

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

• Revised copy by affected state, with rationale, character constraints and unresolved policy wording.

How the work is checked

• A failure message gives an actionable next step; labels remain understandable without surrounding visual context.

When to stop or clarify

• Flag unverifiable product claims. Preserve legal or contractual wording unless the requested scope includes changing it.

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 user intent, action consequences, product terminology and message location/state.

Method

Write concrete labels and error recovery guidance without promising behavior the product lacks.

Pitfall

Friendly copy that says a failed operation succeeded or hides irreversible consequences misleads users.

Check

Check wording against actual success/error states, truncation and accessible naming, preserving meaning in short labels.

Situational decisions

When improving clarity would change a product promise: Surface that policy choice rather than quietly rewriting it.

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