Verified:GitHub

generate

Generate source-backed layered architecture and user flow specifications from a repository.

1|Updated May 19, 2026

Search Tags:#user flows #architecture documentation #repository scanning #frontend backend #implementation analysis #safety net #spec mirror

Ready to run

npx skills add https://github.com/edonghyun/donghyuns-agent-tools --skill generate-edonghyun

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: generate
Source: https://github.com/edonghyun/donghyuns-agent-tools/tree/main/plugins/spec-mirror/skills/generate
Command: npx skills add https://github.com/edonghyun/donghyuns-agent-tools --skill generate-edonghyun

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill turns a working codebase into a structured specification set that mirrors the current implementation, helping teams prevent drift, preserve behavior, and create a reliable safety net for future changes.

Core Features & Use Cases

Layered documentation: Captures frontend, backend, and domain behavior in separate markdown files with source-backed references.
Flow-based mapping: Breaks real user journeys into step-by-step flow docs that cross-reference the layered specs.
Repo bootstrap and guardrails: Creates a specs index, scaffolds human-curated refs folders, and enforces sourced claims and verification rules.
Use case: A team inheriting an evolving product can generate a current-state spec mirror before refactoring, so product, engineering, and QA share the same behavioral baseline.

Quick Start

Ask the skill to generate a spec mirror for the current repository so it analyzes the architecture and writes the layered and flow documentation set.

Frequently Asked Questions about generate

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

FAQPage Schema

What is spec mirror documentation and when do I need it for my codebase?▼

Spec mirror documentation captures frontend routes, backend handlers, domain rules, and user journeys into cross-linked markdown files with verified source references. It serves as a safety net that prevents drift and preserves behavior during future refactoring.

How to create a current-state specification set before refactoring an application?▼

Yes, you can document user flows by breaking real user journeys into step-by-step flow docs that cross-reference layered specs. This maps frontend routes and backend handlers directly to domain behavior within your architecture documentation.

Can I document user flows and map them to frontend and backend specs?▼

What limitations exist when generating living specs from a working codebase?▼

Repository scanning for architecture documentation enforces sourced claims by scaffolding human-curated refs folders and requiring verified file references. This ensures all generated specs trace back to actual implementation code rather than assumptions.

Does repository scanning for architecture documentation require manual file references?▼