x-ray

Generate a local HTML/SVG x-ray page with explanation lanes for bounded targets.

20|3|Updated May 14, 2026
One-click install
npx skills add https://github.com/cyberAlchemyAI/Arcanum --skill x-ray-cyberalchemyai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: x-ray
Source: https://github.com/cyberAlchemyAI/Arcanum/tree/main/.claude/skills/x-ray
Command: npx skills add https://github.com/cyberAlchemyAI/Arcanum --skill x-ray-cyberalchemyai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires yaml, and includes scripts (resource) components.

What problem does it solve?

Visualizing complex targets can be hard when structure is implicit. x-ray slices a target into explanation lanes (surface, properties, components, internal_dependencies, external_dependencies, flow, lifecycle, risk_questions, visual_composition) and assembles a local, self-contained HTML page that makes the structure inspectable without remote rendering.

Core Features & Use Cases

  • Lane-based explanations: surface, properties, components, internal_dependencies, external_dependencies, flow, lifecycle, risk_questions, visual_composition.
  • Local, self-contained HTML output: no external renderers required.
  • Mode-aware inspection: object, artifact, architecture, codebase, process, or mixed targets; supports selective lanes for clear narration.
  • Use cases include understanding a codebase architecture, documenting a system design, or explaining a business process with traceable evidence and inferences.

Quick Start

Provide a bounded context and run the x-ray workflow to generate a local HTML explanation.

Frequently Asked Questions about x-ray

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I visualize codebase architecture and dependencies in a local HTML file?

To visualize codebase architecture locally, you can generate a self-contained HTML page that dissects the target into explanation lanes like components, internal_dependencies, and flow. This local HTML output requires no remote rendering to inspect the implicit structure.

What is the best way to document a system design with traceable evidence and inferences?

Documenting a system design is best achieved by slicing the architecture into explanation lanes that separate evidence from inferences. This mode-aware inspection renders a local HTML page covering properties, lifecycle, and risk_questions for clear narration.

Can I generate a visualization for a business process or mixed targets without external renderers?

Yes, you can generate a visualization for a business process or mixed targets without external renderers. The tool supports mode-aware inspection for process targets and outputs a self-contained L0 HTML/SVG file that makes the structure inspectable locally.

How do I explain a complex system flow using layered HTML lanes?

To explain a complex system flow using layered HTML, you select specific explanation lanes such as surface, flow, and visual_composition. The workflow then assembles a local, self-contained HTML page that makes the implicit structure inspectable through these distinct layers.

Does the local HTML visualization require any specific dependencies to run?

The local HTML visualization requires the yaml dependency to process the bounded context. Once the x-ray workflow runs, it generates a self-contained L0 HTML/SVG output without needing any remote rendering dependencies to view the structure.

What are the limitations of using self-contained HTML for architecture visualization?

A limitation of using self-contained HTML for architecture visualization is that it requires a bounded target and manual lane selection to function correctly. The output is a static local HTML page, meaning it will not reflect real-time changes in the underlying system structure.