Skip to content
Agentmart
Submit a tool

document-architecture

Document the architecture of a frontend or backend service.

Skill by ernesto2108

IndexedMIT
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/ernesto2108-document-architecture

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Document the architecture of a frontend or backend service. Auto-detects project type and runs the appropriate pipeline. Use when user says "documenta arquitectura", "document service", "documenta frontend", "document architecture", or when orchestrate routes here.

Use cases: documents, frontend, backend, data

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/document-architecture

What's inside

Skill name
document-architecture
Description
Document the architecture of a frontend or backend service. Auto-detects project type and runs the appropriate pipeline. Use when user says "documenta arquitectura", "document service", "documenta frontend", "document architecture", or when orchestrate routes here.
License
MIT
Instructions
79 lines in SKILL.md · view on GitHub

Files (3)

  • SKILL.md
  • frontend-pipeline.md · guides/
  • service-pipeline.md · guides/

SKILL.md (first lines)

# Document Architecture

Unified entry point for documenting any project. Detects type, loads the matching guide, and runs the pipeline.

## Step 0 — Input & Detection

If invoked without arguments, ask the user (in Spanish):
1. **Que proyecto?** — nombre del repo
2. **Que tarea del backlog?** — ID. Si no hay, preguntar si crear una.

Resolve `<docs>` from `~/.claude/project-registry.md`.
Resolve `<repo>` from `~/projects/<project-name>`.

### Auto-detect

Run `ls <repo>/` and determine:

| Root contains | Type |
|---|---|
| `package.json` + `src/` with `.tsx`/`.jsx` | **frontend** |
| `go.mod` + `internal/` (NO `domain/`) | **service** (MVC) |
| `go.mod` + `domain/` + `usecase/` | **service** (Clean) |
| `go.mod` + `internal/` with `business/` | **service** (Hex) |
| Ambiguous | Ask: "Frontend o backend?" |

**Load the matching guide** from `guides/frontend-pipeline.md` or `guides/service-pipeline.md`.

## Step 1 — Verify output pattern

Check `<docs>/04-architecture/` for the expected file structure. The guide specifies which files to generate.

## Step 2 — Decide security

Ask yourself (NOT the user): does this project handle auth, payments, PII, or sensitive data?
- **Yes** → include security in pipeline
- **No** → skip security

## Step 3 — Scanner (deep, skeleton-aware)

Read the skeleton file specified in the guide. Inject INLINE into the scanner prompt. Launch `scanner` agent with `mode: deep` following the guide's scanner instructions.

- Model: **sonnet**
- **Target: <25 tool calls**
- After completion: **Read the context files** with Read tool.

## Step 4 — Architect (2 agents in parallel)

Launch TWO architect agents following the guide:
- **4a — Overview:** inject context-summary.md INLINE
- **4b — Detail:** inject template + context-detail.md INLINE

- Model: **sonnet**
- **Target: 0 Read calls** for detail agent (everything inline)

**Wait for both to finish before Step 5.** Read overview.md for security summary.

## Step 5 — Security [conditional]

Skip if Step 2 said no. Read `known-systemic-issues.md`, inject INLINE with context-risks.md + overview summary. Launch `security` agent following the guide's security instructions.

- Model: **sonnet**
- **Target: <10 tool calls**

## Step 6 — Close task

1. Update task status to `done`
2. Update board.md
3. Remove backlog duplicate if exists
4. Update sprint metrics

## Rules

- **All output in Spanish** — titles, descriptions, Mermaid labels. Code/paths in English.
- **Context injection MANDATORY** — each agent gets ONLY its segment INLINE.
- **Model: sonnet** for all agents.
- **Mermaid: NEVER use `|` inside labels or messages.** Use `/` instead.
- **Token budget: <50 tool calls total.**

From ernesto2108/forge, MIT.

More from ernesto2108/forge

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Apr 3, 2026 (6 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from ernesto2108

Cite this page

document-architecture skill. Agent Mart. https://agentmart.dev/skills/ernesto2108-document-architecture (last updated 2026-10-24)