ftm-diagram

Generates and synchronizes ARCHITECTURE.mmd and DIAGRAM.mmd files from your codebase structure using mermaid syntax.

Updated Aug 23, 2026

Search Tags:#architecture #mermaid #diagram #architecture-diagrams #code-architecture #module-relationships

Ready to run

npx skills add https://github.com/kkudumu/feed-the-machine --skill ftm-diagram

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ftm-diagram
Source: https://github.com/kkudumu/feed-the-machine/tree/main/ftm-diagram
Command: npx skills add https://github.com/kkudumu/feed-the-machine --skill ftm-diagram

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically generate and synchronize architecture diagrams across a codebase, reducing manual diagram maintenance and keeping module relationships up to date.

Core Features & Use Cases

Two-level diagram system: a root ARCHITECTURE.mmd for module relationships and per-module DIAGRAM.mmd for function-level graphs.
Incremental diagram updates: apply delta changes after code commits or module changes without recreating diagrams from scratch.
Graph-powered mode: optionally leverage a knowledge graph at .ftm-map/map.db to produce accurate diagrams.
Auto-invocation: integrated with ftm-executor to refresh diagrams after commits to reflect latest state.

Quick Start

Bootstrapping creates the root ARCHITECTURE.mmd and per-module DIAGRAM.mmd files from your codebase.

Frequently Asked Questions about ftm-diagram

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

FAQPage Schema

How do I automatically generate architecture diagrams for a multi-module codebase?▼

Automatically generate architecture diagrams by scanning your multi-module project structure to create a root ARCHITECTURE.mmd file for module relationships and per-module DIAGRAM.mmd files for function-level graphs using mermaid syntax.

Can I apply incremental updates to mermaid architecture diagrams after code commits?▼

Apply incremental delta updates to mermaid architecture diagrams after code commits or module changes, refreshing the existing diagram files to reflect the latest state without recreating them entirely from scratch.

What is the best way to visualize module relationships across a large software project?▼

Visualize module relationships across a large software project by generating a root ARCHITECTURE.mmd file that maps high-level dependencies, supplemented by per-module DIAGRAM.mmd files for detailed function-level context.

Do I need a knowledge graph to produce accurate code architecture diagrams?▼

A knowledge graph is optional for producing code architecture diagrams, but leveraging a local knowledge graph at .ftm-map/map.db through graph-powered mode significantly enhances the accuracy of the generated mermaid diagrams.

When should I not use automated mermaid diagram generation for my project?▼

Avoid automated mermaid diagram generation for projects that are not multi-module, as the two-level diagram system with root and per-module files is specifically designed for codebases requiring structured module relationship mapping.