project-mapper

Scan a repository to detect tech stack and output a Mermaid C4 diagram.

1|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/hjemmesidekongen/ai --skill project-mapper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-mapper
Source: https://github.com/hjemmesidekongen/ai/tree/main/plugins/smedjen/skills/project-mapper
Command: npx skills add https://github.com/hjemmesidekongen/ai --skill project-mapper

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you quickly understand the technology stack, module dependencies, and architectural overview of any codebase, especially when onboarding to new projects.

Core Features & Use Cases

  • Tech Stack Detection: Identifies languages, frameworks, databases, and CI/CD tools used.
  • Module Mapping: Maps out distinct project modules and their interdependencies.
  • Architecture Diagram: Generates a visual C4 context diagram for clarity.
  • Use Case: When joining a new project, use this Skill to generate a project-map.yml and a Mermaid diagram to grasp the project's structure and technologies before writing any code.

Quick Start

Use the project-mapper skill to scan the current repository and generate a project map.

Frequently Asked Questions about project-mapper

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

FAQPage Schema
How do I generate an architecture diagram for a new codebase?

You can generate an architecture diagram by scanning the repository to detect its tech stack and map module boundaries. This process outputs a Mermaid C4 context diagram and a project-map.yml file for visual structural clarity.

What is the best way to map module dependencies in a monorepo?

Mapping module dependencies in a monorepo involves scanning the repository to identify distinct project modules and their interdependencies. This analysis reads configuration files like package.json and tsconfig.json to build a comprehensive project map.

How do I detect the tech stack of an existing repository?

Detecting the tech stack of an existing repository requires scanning configuration files like package.json and prisma/schema.prisma. This identifies languages, frameworks, databases, and CI/CD tools used within the codebase.

Can I use a repository scan to prepare for agent-based task dispatch?

Yes, scanning a repository generates a project-map.yml that maps module boundaries and dependencies. This structural overview provides the necessary context for preparing agent-based task dispatch.

Does codebase analysis work without reading configuration files?

No, comprehensive codebase analysis requires reading configuration files like package.json, tsconfig.json, and prisma/schema.prisma. These files provide essential metadata to detect the tech stack and map file dependencies accurately.