Mermaid scout

Skill JarrydAdaens/agentic_rails_tooling/archived/skills/mermaid-scout

The right rail of Agentic Rails: Reusable skills, agent personas, rules, and workflows for agentic coding IDEs — the tooling rail of the Agentic Rails framework.

Install

npx -y skills add JarrydAdaens/agentic_rails_tooling --skill mermaid-scout

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use this skill when discovering files and filtering them to specific classes or types for a Mermaid relationship map. It writes scoutmap.md as a CSV-like work queue for scoped inventory or for the mermaid-mapper workflow.

SKILL.md

2.4 KB, as published. Nobody here has run it

Mermaid Scout

Build a scoped list of files and types to map. Output is always scoutmap.md in the workflow output directory when used as part of the mermaid-mapper workflow, or at a path the user specifies for standalone runs.

When to use

You need a file-to-type inventory for a feature area, naming family (for example *ViewModel), or named type.
You are running the discovery step before parallel mermaid mapping.
You want "all relevant view models under X" without drawing the graph yet.

Inputs

Target query: type name, feature keywords, folder hint, or pattern (for example types ending in ViewModel).
Repository root: the project whose code you are mapping.
Optional: folder constraints, glob hints, maximum row count (if the user caps scope).

Instructions

Translate the query into search tactics: Glob for paths, Grep for symbols and class declarations.
Open candidate .cs (or other supported) files and list declared types that are in scope.
Include classes that match the query: naming patterns, explicit names, or clear semantic fit (for example feature-specific view models).
Exclude unless explicitly targeted: struct, record, static-only helpers, constants-only types, generic noise, unrelated DTOs or persistence types, and declarations that are clearly out of scope.
Group types by file: one row per file in the output format.
Write scoutmap.md using references/scoutmap-format.md. New rows use the unassigned state marker in the first column.

Output contract

Destination (workflow): documentation/workflows/mermaid_mapper/scoutmap.md under the target repository root (always rooted at repo root).
Format: see references/scoutmap-format.md.

Standalone examples

Find all view model classes under src/UI/Resources and write scoutmap.
Build a scout map for types matching *Resource*ViewModel in an RTS UI folder.
Given "UnitViewModel", locate its file and related unit view models in the same feature area.