CARBON — Engineering ConfidenceUser Guide
CHAPTER 60 / 60 Core + Pro

/carbon-pro

Open the CARBON Pro marketing page to explore Pro features, pricing, and upgrade options.

Jay · Your AI test managerTesting operations

When to use it

You want to compare deeper capabilities and support.

Before you start

This opens the marketing comparison only. It does not start checkout, purchase, install an edition or expose customer downloads. Model access and host charges remain separate.

Try this in your coding agent.

/carbon-pro Show the Pro features and pricing so I can compare upgrade options.

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

Edition comparison

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. 02Analyze
  3. 03Show evidence
  4. 04Report

Coding-agent conversation

Read context

I’m reviewing edition comparison. I’ll keep the scope and permissions explicit.

Analyze

Analyze: Show the Pro features and pricing so I can compare upgrade options.

Show evidence

Here is the evidence trail to inspect: Review included capabilities, support, host requirements and pricing link.

Report

The comparison explains which deeper commands Pro adds. No purchase or checkout is initiated by the walkthrough.

CARBON

Example report

Illustration
Project → decisions → retained evidence
Project → decisions → retained evidence — TestBucks teaching screen

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

  1. TestBucks project
  2. Command action
  3. Reviewable output

Illustrated outcome

The comparison explains which deeper commands Pro adds.

Evidence to inspect

Review included capabilities, support, host requirements and pricing link.

Still untested / not established

No purchase or checkout is initiated by the walkthrough.

Ready. Read the full example or play its steps.

What a useful result contains

A bounded claim

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

An inspectable trail

Review included capabilities, support, host requirements and pricing link. In a real run, retain the source, trace, screenshot or fixture behind the conclusion.

The qualification

No purchase or checkout is initiated by the walkthrough.

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 edition comparison 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-pro result. Separate observed evidence, assumptions and untested scope, then recommend the next useful check.

Where to go next

/carbon-help →/carbon →

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