Terminal
Terminal/Skill
Diagnoses why TurboSnap is enabled, disabled or unavailable in a Chromatic build, and recommends the smallest next step for customers and support.
By Chromatic
Works with
npx skills add chromaui/chromatic-skills --skill chromatic-turbosnap-debugPublic TurboSnap diagnostic contract for customers, support, and engineers.
This package is the single source of truth for:
reference/workflow-playbook.md and identify which workflow phase you are in.reference/diagnosis-taxonomy.md and identify the most likely diagnosis code from the evidence already provided.reference/evidence-ladder.md and decide whether you can diagnose immediately or need one more targeted artifact.reference/command-catalog.md only when evidence is incomplete or the repo is available and targeted proof is needed.reference/trace-minimization.md.reference/output-contract.md.reference/docs-map.md.Use one adaptive workflow:
triage: classify the current TurboSnap state from logs, config, and symptomsartifact-request: ask for the smallest next artifact when evidence is incompletetrace-validation: use changed files, a stats artifact, or trace output to validate the bail or minimize the fix pathrecommendation: return the smallest valid fix, a safer alternative if needed, and the exact next stepInfer the current phase from the evidence:
triageartifact-requesttrace-validationrecommendationPrefer evidence already in the conversation:
chromatic.config.json, package.json scripts, or CI snippets.chromatic/ as human-shareable referenceschromatic or chromatic trace command outputDo not jump to speculative fixes if the current evidence already maps cleanly to a diagnosis code.
Map the issue to one normalized diagnosis code from reference/diagnosis-taxonomy.md.
If the case includes multiple signals, choose:
TS_NEEDS_MORE_EVIDENCEUse the workflow in reference/workflow-playbook.md.
The default path is:
Do not skip directly to --untraced or repo surgery when the current phase is still classification.
The remediation posture is to restore or preserve TurboSnap where possible.
That does not permit hiding reality:
Then pivot to the exact fix path that restores TurboSnap on the next run.
Always return the diagnosis card from reference/output-contract.md.
Default tone:
bail reason, trace, and untraced when they improve precisionIf you cannot reach a confident fix:
Use template.md when:
The canonical prompt templates live in template.md so they stay versioned with the workflow.
Customer-facing snippets should still be shared as needed:
--externals, --untraced, --storybook-base-dir, or --storybook-config-dir unless the evidence points there.--untraced, keep the minimal technical set explicit and compress the safer recommendation into one monorepo-safe picomatch glob when possible.reference/workflow-playbook.mdreference/diagnosis-taxonomy.mdreference/evidence-ladder.mdreference/command-catalog.mdtemplate.mdreference/trace-minimization.mdreference/output-contract.mdreference/docs-map.mdexamples/internal-investigation.mdexamples/customer-guided-debug.mdevaluations/README.md