CARBON — Engineering ConfidenceUser Guide
CHAPTER 27 / 60 Pro

/carbon-load

Inspect code and server/deployment configuration read-only for likely load failure points, assess readiness, record approved browser journeys and generate replay workloads. Run staged load only after explicit target/traffic approval; distinguish static risk hypotheses from measured failures.

Tariq · PerformanceSecurity & resilience

When to use it

You need load readiness or a controlled capacity investigation.

Before you start

Start with source/configuration assessment. A URL alone does not authorize traffic. Approve the exact target, journey capture, traffic shape, limits and abort conditions before staged load execution.

Try this in your coding agent.

/carbon-load Review the search API code and configuration for load risks; do not generate traffic.

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

Search API load-risk review

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 search api load-risk review. I’ll keep the scope and permissions explicit.

Analyze

Analyze: Review the search API code and configuration for load risks; do not generate traffic.

Show evidence

Here is the evidence trail to inspect: Read source and configuration: no pagination limit; query scans product records.

Report

Unbounded results and a missing query index create a scaling risk. Read-only review: no load is generated and capacity is not measured.

CARBON

Example report

Illustration
Query → catalog → visible result
Query → catalog → visible result — TestBucks teaching screen

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

  1. Query intent
  2. Catalog / processing
  3. Visible result

Illustrated outcome

Unbounded results and a missing query index create a scaling risk.

Evidence to inspect

Read source and configuration: no pagination limit; query scans product records.

Still untested / not established

Read-only review: no load is generated and capacity is not measured.

Ready. Read the full example or play its steps.

What a useful result contains

A bounded claim

For search api load-risk review, state the target, revision, environment and actual work performed. Keep planned, executed, blocked and untested work separate.

An inspectable trail

Read source and configuration: no pagination limit; query scans product records. In a real run, retain the source, trace, screenshot or fixture behind the conclusion.

The qualification

Read-only review: no load is generated and capacity is not measured.

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 search api load-risk review 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-load result. Separate observed evidence, assumptions and untested scope, then recommend the next useful check.

Where to go next

/carbon-performance →/carbon-stress →

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