/carbon-content
Run focused CARBON Content testing and generate a branded content report.
Sophia · ContentExperience & accessibilityWhen to use it
Copy, links or product claims might mislead users.
Before you start
Follow the same fact through the page, FAQ, error messages and checkout. Record the exact conflicting text and source; visual consistency is not proof that a commercial claim is true.
Try this in your coding agent.
/carbon-content Check the pricing page for inconsistent plan names and unclear billing copy.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
Pricing-page copy
An expanded teaching example, not a recorded or live execution. The report stays visible while the replay explains how to read it.
- 01Read context
- 02Investigate
- 03Show evidence
- 04Report
Coding-agent conversation
I’m reviewing pricing-page copy. I’ll keep the scope and permissions explicit.
Follow the weakest evidence link and record what remains blocked.
Here is the evidence trail to inspect: Trace the same plan name and billing period across card, FAQ and checkout copy.
The plan card says monthly, while checkout help says annual. The billing configuration must be checked separately.
Example report
Illustration
TestBucks course screen with illustrative analysis. The screenshot supplies context; the demo does not establish a newly observed bug.
- User intent
- Visible content
- Meaning / consistency
Illustrated outcome
The plan card says monthly, while checkout help says annual.
Evidence to inspect
Trace the same plan name and billing period across card, FAQ and checkout copy.
Still untested / not established
The billing configuration must be checked separately.
Ready. Read the full example or play its steps.
What a useful result contains
A bounded claim
For pricing-page copy, state the target, revision, environment and actual work performed. Keep planned, executed, blocked and untested work separate.
An inspectable trail
Trace the same plan name and billing period across card, FAQ and checkout copy. In a real run, retain the source, trace, screenshot or fixture behind the conclusion.
The qualification
The billing configuration must be checked separately.
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
- Replace pricing-page copy with a real feature, path or decision in your project.
- State the expected rule and its source. Include safe fixtures, constraints and a budget where appropriate.
- Ask for exact evidence and remaining gaps. Approve consequential actions separately.
/jay Review the /carbon-content result. Separate observed evidence, assumptions and untested scope, then recommend the next useful check.Where to go next
/carbon-ux →/carbon-test →Content checked against the local command definition: skills/carbon-content/SKILL.md. Examples adapted from the homepage’s TestBucks walkthroughs. Availability is edition- and host-dependent.