Publication date: October 27, 2026

Developer Hayden Smith has open-sourced Floorplan. The tool helps both individual developers and teams gain a clearer and more detailed view of a codebase. Floorplan shows how components are connected to one another and how the application works as a whole.

Installation

Floorplan is implemented as a plugin for Claude. Installation takes about 30 seconds and requires two commands. The commands are displayed on screen and are provided in the readme file of the repository on GitHub.

After installation, the plugin can be launched in any existing repository, in a multi-repository configuration, or in a separate part of a repository. Initialization is performed in one of two ways:

• with a command;
• with a request inside Claude, for example: "Make me a floorplan".

Generating the floorplan takes a few minutes.

How It Works

During generation, Claude performs two tasks:

1. Structural analysis. Pre-installed scripts map the entire codebase and identify most of the connections between components.
2. Semantic analysis. Claude determines the purpose of the system's components, the reasons for their interconnections, the nature of these connections, and the functions of the code blocks within the application.

Once generation is complete, Floorplan launches a web server with an interface built from the user's codebase.

Interface Overview

The fictional software development company Brewline is used as an example.

Overview

The Overview tab shows the most abstracted map of the system. The example includes:

• the online shop;
• the staff app;
• the main server;
• the services that the main server connects to.

The Start here tour is located in the lower left corner. It introduces the main parts of the application in sequence and describes the nature of the connections between them.

Details Panel

The right sidebar displays details of the selected element. On the Overview tab, it contains a general description of the system. When you select a server, such as the main server, the panel shows details of the components that make up that server.

Change Highlighting

Components with recent changes in the codebase are marked with a green indicator. When generating a diagram, Claude analyzes the latest changes and reports:

• why the component was changed;
• what exactly was changed;
• how the change affects the application as a whole.

Details of the changes are available in cards. In the example, the main server has several recorded changes.

Top Bar

Recent Work Tab

The Recent work tab contains a summary list of recent changes, indicating where they are located in the application. If the project has a frontend, elements are grouped by screen.

The example selects the subscriptions page. For it, the following are displayed:

• the interaction between the frontend and the backend;
• routes, their connections, and their locations;
• the name of each route.

Right-clicking a card provides access to:

• viewing detailed information;
• copying the endpoint name;
• copying the name;
• opening the file in the selected code editor.

Data Flows

Claude automatically generates flows, meaning the most significant user scenarios and data flows in the application. By default, three flows are created. The user can request a new flow if any scenario remains unclear. Claude will build a map for the requested flow.

The example shows the flow for sending a gift subscription. The flow steps are displayed in the upper part of the screen. Shop pages are linked to building blocks. Moving through the steps is accompanied by an explanation of how the flow is implemented in the application's code.

Drill-Down

Double-clicking an element opens a deeper level. The example opens the internal structure of the main server. At this level, the following are displayed:

• inputs;
• components that use this logic;
• the main logic components;
• components that this element uses.

Drill-down can be continued at any level.

Data Storage and Dependencies

• All maps are stored locally. Data is not transferred outside the user's computer.
• The work is performed through the existing Claude Code subscription.
• Floorplan has no external dependencies. No external API keys are required.

Questions to the System

When Claude Code CLI is available, the user can ask questions about the system. For example, a simple explain request on the overview page launches an isolated instance of Claude Code. Its context is formed through function calls that access the built code map.

The instance performs function calls and searches, after which it produces:

• a visual representation of the most significant elements;
• a text description.

The user can select a specific component and ask a question about it. This narrows the search to the area of interest.

Updating the Diagram

You can create the diagram anew or update it. To update it, simply ask Claude to update the diagram for the repository. Claude detects the changes and processes only those parts of the application that require updating.

The diagram can also be adapted to your team's terminology. For example, a request to rename the element "main server" to "back end server" changes the name in the diagram. This example is simple, but it illustrates the principle.

Sharing and file storage

Created files can be shared with other team members. The floorplan folder is added to .gitignore automatically, so it is not committed to the repository. All files are located in the same floorplan folder.

Summary

• Floorplan is distributed for free, as open-source software, under the MIT license.
• Installation takes two commands and about 30 seconds.
• Generating a diagram takes a few minutes.
• The tool can be applied to any existing project.