map-flows

map-flows is a skill for Claude Code, Codex from evgenii-studitskikh/Claude-Code-SaaS-Studio. It costs 41 tokens per session (465 once invoked), scanned A, original, MIT.

A user-flow and screen-planning review based on the product requirements document. It maps journeys such as sign-up, the main product task, billing, and settings into ordered steps and required screens.

In plain words
What is it for?
Use it to define key user journeys, identify every screen or modal, mark login and payment boundaries, and resolve unclear parts of the experience.
Why use it?
It exposes missing decisions in how users move through the product before design and development begin. It also records authentication, payment, error, and empty states.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/evgenii-studitskikh/claude-code-saas-studio/map-flows
Any agent
npx skills add evgenii-studitskikh/Claude-Code-SaaS-Studio --skill map-flows
Clone the repo
git clone --depth 1 https://github.com/evgenii-studitskikh/Claude-Code-SaaS-Studio

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for map-flows

README.md
[![agentmods](https://agentmods.dev/badge/skills/evgenii-studitskikh/claude-code-saas-studio/map-flows.svg)](https://agentmods.dev/skills/evgenii-studitskikh/claude-code-saas-studio/map-flows)
Your own site
<a href="https://agentmods.dev/skills/evgenii-studitskikh/claude-code-saas-studio/map-flows"><img src="https://agentmods.dev/badge/skills/evgenii-studitskikh/claude-code-saas-studio/map-flows.svg" alt="Measured on agentmods" height="20"></a>
Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 465 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00041 $0.00465
Opus 5 $0.00020 $0.00233
Sonnet 5 $0.00008 $0.00093
Haiku 4.5 $0.00004 $0.00047

Measured 4d ago against content hash a6bbbafe6750, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

map-flows scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/map-flows/SKILL.md · 23 lines

What it actually says

Translate the PRD's user stories into concrete user journeys and a numbered screen inventory that will anchor every subsequent design and engineering decision. Non-autonomous: flows are proposed, discussed, and approved before anything is written.

Phases

  1. Load PRD — read docs/specs/prd.md. If missing, stop and direct the user to /write-prd. Extract each user story and group them into candidate journeys (e.g., Onboarding, Core Loop, Billing & Upgrade, Settings).
  2. Propose journey map — present each journey as a numbered step sequence (e.g., 1. Land on marketing page → 2. Click "Sign up" → 3. Supabase auth → …). Mark which steps cross authentication or payment boundaries. Ask the user to confirm, adjust, or remove flows.
  3. Derive screen list — from the approved journeys, enumerate every distinct screen or modal needed. For each screen note: name, owning journey, auth-required (yes/no), and any critical empty/error states that must exist.
  4. Resolve ambiguities — identify any flows where the user story is underspecified (e.g., "What happens if the user cancels mid-checkout?"). Propose sensible defaults; get the user's confirmation before locking the decision.
  5. Write draft — fill docs/specs/flows.md with the journey map and screen list. Present the draft inline under full review; under lean / solo write immediately after a single confirmation prompt.
  6. Next step — on approval, point to /design-ui to assign components to each screen.

Output

docs/specs/flows.md — journey map + screen inventory. Writes nothing else without approval.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 4d ago First seen · 23 lines · 41 tokens per session scan A a6bbbafe6750

Subscribe to this mod's changes

map-flows is a skill published in the GitHub repository evgenii-studitskikh/Claude-Code-SaaS-Studio (1 stars, last pushed 2mo ago), licensed MIT. It adds 41 tokens to every session and 465 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

create-theme

Create custom color themes for Sidecar, including base theme selection, color overrides, gradient borders, tab styles, per-project themes, community themes, and programmatic theme registration. Use when creating or modifying themes, adjusting UI appearance, or debugging color/style issues. See…

marcus/sidecar · 74 tokens

drag-pane

Drag-and-drop pane resizing implementation for two-pane plugin layouts. Covers mouse event handling via the internal/mouse package, hit region registration, drag delta calculation, width clamping, state persistence, and pane layout management. Use when working on pane resizing, drag interactions, layout management, or…

marcus/sidecar · 70 tokens

ui-features

Implementing UI/UX features in sidecar including modals (internal/modal library), keyboard shortcuts, mouse support, scrolling, pill/tab rendering, and pane resizing. Use when implementing UI features, handling user input, adding keyboard shortcuts, building modals, or working on UX improvements.

marcus/sidecar · 61 tokens

visualize-output

Create clear, restrained visual presentations for answers and results by choosing among Markdown, tables, Mermaid, images, and self-contained inline HTML. Use when the user asks for a visualization, chart, diagram, comparison, timeline, status/result view, or when spatial layout would materially improve understanding…

Peiiii/nextclaw · 93 tokens

impeccable

Use when the user wants distinctive, production-grade frontend design, anti-generic AI aesthetics, UX critique, technical UI audits, or final polish through bundled Impeccable references and an optional upstream detector CLI.

Peiiii/nextclaw · 47 tokens

nextclaw-skin-studio

Use when a user wants to browse, apply, inspect, create, refine, switch, or remove a NextClaw skin; wants a personal skin with arbitrary CSS, JavaScript, images, SVG, DOM changes, motion, or component-level effects; asks for 易烊千玺/Jackson Yee, 桥本有菜, 迪丽热巴, 初音未来, KUN, Jinx, ENFP, or Gothic Void Crusade; or says a skin…

Peiiii/nextclaw · 115 tokens