project visualizer

    1

    Generate interactive, standalone HTML visualizations of project architecture, data flows, and component hierarchies.

    Free

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    project visualizer

    Example session with this skill installed

    Analyze the current directory's React frontend and generate a visualization showing the component hierarchy and how data flows through the context providers.

    • Read your context and instructions
    • Compiled the project visualizer
    • Generated the UI component

    I have analyzed the React project structure, identifying the core component hierarchy and the AuthContext and ThemeContext providers. A standalone visualization has been generated.

    Project Architecture Visualization

    The artifact includes a searchable component tree and a directed graph of the context provider subscriptions.

    <!DOCTYPE html>
    <html lang="en">
    <head>
        <meta charset="UTF-8">
        <title>Project Visualizer - React Frontend</title>
        <style>
            body { font-family: sans-serif; margin: 0; display: flex; height: 100vh; }
            #graph { flex: 1; background: #f9f9f9; overflow: hidden; }
            #inspector { width: 300px; border-left: 1px solid #ccc; padding: 20px; overflow-y: auto; }
            .node { fill: #fff; stroke: #333; stroke-width: 2px; }
            .edge { fill: none; stroke: #999; stroke-width: 1px; }
        </style>
    </head>
    <body>
        <div id="graph">
            <svg width="100%" height="100%" viewBox="0 0 800 600">
                <!-- Simplified SVG representation -->
                <g class="edges">
                    <path d="M400,50 L400,150" class="edge" />
                    <path d="M400,150 L200,300" class="edge" />
                    <path d="M400,150 L600,300" class="edge" />
                </g>
                <g class="nodes">
                    <circle cx="400" cy="50" r="30" class="node" /> <!-- App.tsx -->
                    <circle cx="400" cy="150" r="30" class="node" /> <!-- AuthProvider -->
                    <circle cx="200" cy="300" r="30" class="node" /> <!-- Dashboard -->
                    <circle cx="600" cy="300" r="30" class="node" /> <!-- Login -->
                </g>
            </svg>
        </div>
        <div id="inspector">
            <h3>Component Inspector</h3>
            <div id="details">Select a node to see source evidence and props.</div>
        </div>
        <script id="project-model" type="application/json">
        {
          "nodes": [
            {"id": "app", "label": "App.tsx", "type": "component"},
            {"id": "auth_prov", "label": "AuthProvider", "type": "context"},
            {"id": "dash", "label": "Dashboard", "type": "component"}
          ],
          "edges": [
            {"from": "app", "to": "auth_prov", "type": "contains"},
            {"from": "auth_prov", "to": "dash", "type": "provides"}
          ]
        }
        </script>
    </body>
    </html>
    

    Next steps

    • Open visualization/index.html in your browser to explore the interactive graph.
    • Use the Evidence tab in the inspector to see which lines of code define each component relationship.
    • Filter by Context to isolate state management flows from the UI hierarchy.

    index.html

    TSX · React component

    Generated

    Example file from a real run - the skill writes it into your workspace.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Generating clear architectural diagrams from source code is often a manual, tedious process that falls out of sync the moment a PR is merged. This skill automates the creation of standalone, browser-based visualizations that map your project's components, data flows, and dependencies without requiring heavy infrastructure or external SaaS tools.

    What it does

    • Architectural mapping: Generates directed graphs showing component hierarchies and relationships.
    • Data flow visualization: Maps data structures, producers, and consumers based on source evidence.
    • Interactive exploration: Builds an explorer with search, zoom, pan, and inspector panels for deep-diving into nodes.
    • Source grounding: Links every visual element to specific file paths and symbols to maintain technical accuracy.
    • Self-contained delivery: Produces a single HTML file with all CSS, JS, and model data embedded for offline use.

    How it works

    1. Analyze source: The skill inspects your repository, READMEs, manifests, and entry points to identify core responsibilities.
    2. Model generation: It builds an internal JSON model with stable IDs, typed edges, and source references.
    3. Render artifact: It injects the project model into a specialized visualizer template using inline SVG and safe DOM APIs.
    4. Local deployment: The file is saved to visualization/index.html or a custom path for immediate browser viewing.

    Frameworks & tools

    This tool uses standard HTML5, CSS3, and vanilla JavaScript. It is compatible with any project structure, including BlackBoxApproach projects using system.yaml.

    Why this beats prompting it yourself

    Generic prompts often result in static Mermaid diagrams that break with large datasets or lack interactivity. This skill enforces a strict data model that prevents infinite recursion in cycles and ensures every visual node is backed by verifiable source code evidence.

    Use cases

    • Onboarding new devs: Visualizing a complex codebase for a quick mental model.
    • Refactoring audits: Identifying tight coupling and circular dependencies before changing code.
    • Design proposals: Modeling a planned architecture to get stakeholder sign-off.

    Known limitations

    Does not perform runtime tracing or dynamic execution analysis. Large repositories may be presented as progressive subsystems rather than one giant graph to maintain readability.

    Visualizes static architecture only, not runtime traces. Large repos are split into subsystems. Requires modern browser for SVG rendering.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 20 days ago

    • Free with an Agensi account

    Permissions

    Read Files
    Write Files
    Listed20 days ago

    What's inside

    Frequently Asked Questions

    The Project Visualizer provides an interactive, standalone HTML file that allows for zooming, panning, and searching through complex hierarchies, whereas Mermaid produces static images or simple charts that often break with large datasets.

    This skill is designed to work with any standard AI agent capable of file-system access and code analysis, and it is fully optimized for BlackBoxApproach projects using `system.yaml`.

    No, the skill generates a single, self-contained HTML file with all CSS and JavaScript embedded, meaning you can view and share your project maps offline without any external SaaS subscriptions.

    The skill uses source grounding to link visual nodes to specific file paths, ensuring the diagram reflects your actual code rather than a generic hallucination of the architecture.

    For massive repositories, the skill automatically segments the architecture into readable subsystems or modules to prevent the graph from becoming an unintelligible 'spaghetti' diagram.

    New in Agents & Orchestration