# AI use cases for Floorplan (haydenschmitty/floorplan)

Repo: [haydenschmitty/floorplan](https://github.com/haydenschmitty/floorplan) | Use cases: 3 | Page: https://dedupedai.com/use-cases/haydenschmitty-floorplan/

Floorplan is a Claude Code and Codex plugin that reads your codebase and draws an interactive map of it. Every part, file and web request gets a plain-English name and every connection is shown, across one repo or several. The map runs locally, has an Ask bar, a health check and a recent work view, and can also plan an app from a PRD.

This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL.

- Get a plain-English map of how your app fits together: https://dedupedai.com/use-cases/haydenschmitty-floorplan/map-your-app-in-plain-english/
- Map a codebase from Codex with no API key: https://dedupedai.com/use-cases/haydenschmitty-floorplan/use-floorplan-in-codex/
- See which parts an AI change touched, and keep the map current: https://dedupedai.com/use-cases/haydenschmitty-floorplan/check-what-an-ai-change-touched/

## How to get a plain-English map of how your app fits together with Floorplan

Repo: [haydenschmitty/floorplan](https://github.com/haydenschmitty/floorplan) | Difficulty: Beginner | Time: 15 minutes | Basis: From the README

Install the plugin and ask Claude Code for a Floorplan of your project.

**Who it is for:** A builder who shipped an app with AI and cannot say what happens at checkout.

**The problem:** Nobody drew the architecture, so it is unclear what breaks if you change something.

**The outcome:** An interactive map in floorplan/index.html with named parts, files, requests and connections.

### Steps

1. Run `claude plugin marketplace add haydenschmitty/floorplan`
2. Run `claude plugin install floorplan@floorplan`
3. Open your project (or the folder holding frontend and backend repos) in Claude Code
4. Ask: Make me a Floorplan of this app.
5. Explore the map, starting with its short tour

### Prompt to paste into your agent

```text
Install the Floorplan plugin with `claude plugin marketplace add haydenschmitty/floorplan` and `claude plugin install floorplan@floorplan`, then make me a floorplan of this app and tell me what happens when <user action>.
```

### Caveat

It only writes its own floorplan/ folder, which ignores itself in git.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/haydenschmitty-floorplan/map-your-app-in-plain-english/

## How to map a codebase from Codex with no API key with Floorplan

Repo: [haydenschmitty/floorplan](https://github.com/haydenschmitty/floorplan) | Difficulty: Beginner | Time: 15 minutes | Basis: From the README

Add the marketplace in Codex and type $Floorplan.

**Who it is for:** A Codex user who wants the same map with questions answered on their own sign-in.

**The problem:** Architecture tools often need another API key or a cloud upload.

**The outcome:** A local map whose Ask bar runs on your own Codex sign-in.

### Steps

1. Run `codex plugin marketplace add haydenschmitty/floorplan`
2. Run `codex plugin add floorplan@floorplan`
3. Start a new chat and type `$floorplan`
4. Use the Ask bar on the map to ask questions

### Prompt to paste into your agent

```text
In Codex, add the Floorplan plugin and run $floorplan on this repo, then use the map to list every web request and which part handles it.
```

### Caveat

This card is written from the haydenschmitty/floorplan README, not from a test run by Deduped. Before you start, make sure you have Claude Code or Codex. Check the repo for newer instructions before you rely on these steps.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/haydenschmitty-floorplan/use-floorplan-in-codex/

## How to see which parts an AI change touched, and keep the map current with Floorplan

Repo: [haydenschmitty/floorplan](https://github.com/haydenschmitty/floorplan) | Difficulty: Beginner | Time: 10 minutes | Basis: From the README

Update the Floorplan after each change and use Recent work and the Health check.

**Who it is for:** A developer letting Claude or Codex make changes who wants to see their blast radius.

**The problem:** After an agent edits many files it is hard to see which parts it touched and why.

**The outcome:** An updated map showing recent work and a health check, with secret values never stored or shown.

### Steps

1. Let the agent make its change
2. Ask: Update the Floorplan.
3. Open Recent work to see which parts were touched
4. Run the Health check; rename parts by asking, or edit floorplan/architecture.json

### Prompt to paste into your agent

```text
Update the floorplan for this repo, then list the parts the last change touched using Recent work and report anything the Health check flags.
```

### Caveat

This card is written from the haydenschmitty/floorplan README, not from a test run by Deduped. Before you start, make sure you have Claude Code or Codex. Check the repo for newer instructions before you rely on these steps.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/haydenschmitty-floorplan/check-what-an-ai-change-touched/
