CARBON — Engineering ConfidenceUser Guide
CHAPTER 15 / 60 Pro

/carbon-personas

Generate context-specific AI persona feedback for the current work or a named app, API, screenshot, document, design, or concept.

Mia · UsabilityExperience & accessibility

When to use it

Different user goals or contexts may reveal overlooked friction.

Before you start

Provide realistic goals, constraints and background. Compare agreements and disagreements across simulated perspectives instead of averaging them into an invented user-satisfaction score.

Try this in your coding agent.

/carbon-personas Review onboarding from the perspectives of a new user and a busy admin.

Replace sample paths with your project. Slash names are shorthand; your host may use a plugin prefix or a skill picker. Invocation help →

ILLUSTRATIVE WALKTHROUGH

Onboarding perspectives

An expanded teaching example, not a recorded or live execution. The report stays visible while the replay explains how to read it.

  1. 01Read context
  2. 02Investigate
  3. 03Show evidence
  4. 04Report

Coding-agent conversation

Read context

I’m reviewing onboarding perspectives. I’ll keep the scope and permissions explicit.

Investigate

Follow the weakest evidence link and record what remains blocked.

Show evidence

Here is the evidence trail to inspect: New user: unexplained workspace term. Admin: no visible bulk-invite route.

Report

The new-user and busy-admin perspectives reveal different friction. These are simulated perspectives, not interviews.

CARBON

Example report

Illustration
Meaning, price and presentation
Meaning, price and presentation — TestBucks teaching screen

TestBucks course screen with illustrative analysis. The screenshot supplies context; the demo does not establish a newly observed bug.

  1. User intent
  2. Visible content
  3. Meaning / consistency

Illustrated outcome

The new-user and busy-admin perspectives reveal different friction.

Evidence to inspect

New user: unexplained workspace term. Admin: no visible bulk-invite route.

Still untested / not established

These are simulated perspectives, not interviews.

Ready. Read the full example or play its steps.

What a useful result contains

A bounded claim

For onboarding perspectives, state the target, revision, environment and actual work performed. Keep planned, executed, blocked and untested work separate.

An inspectable trail

New user: unexplained workspace term. Admin: no visible bulk-invite route. In a real run, retain the source, trace, screenshot or fixture behind the conclusion.

The qualification

These are simulated perspectives, not interviews.

The next decision

Decide whether the evidence calls for a focused check, a reviewed fix or more context. Do not convert a plausible example into a verified finding.

Adapt the example to your project

  1. Replace onboarding perspectives with a real feature, path or decision in your project.
  2. State the expected rule and its source. Include safe fixtures, constraints and a budget where appropriate.
  3. Ask for exact evidence and remaining gaps. Approve consequential actions separately.
/jay Review the /carbon-personas result. Separate observed evidence, assumptions and untested scope, then recommend the next useful check.

Where to go next

/carbon-usability →/carbon-test →

Content checked against the local command definition: skills/carbon-personas/SKILL.md. Examples adapted from the homepage’s TestBucks walkthroughs. Availability is edition- and host-dependent.