skills.rest
TrebuchetDynamics
TrebuchetDynamicsOFFICIAL
Explore all skills by this author →
WebsiteGitHub

gormes-architecture-zoomout

Map cross-package boundaries and behavior locations in the Gormes codebase.

9|Updated Apr 19, 2026
Search Tags:#architecture#codebase#refactor#data-flow#subsystems#hermes#honcho
One-click install
npx skills add https://github.com/TrebuchetDynamics/gormes-agent --skill gormes-architecture-zoomout
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gormes-architecture-zoomout
Source: https://github.com/TrebuchetDynamics/gormes-agent/tree/main/development-skills/gormes-architecture-zoomout
Command: npx skills add https://github.com/TrebuchetDynamics/gormes-agent --skill gormes-architecture-zoomout

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use when an agent is unfamiliar with a Gormes code area, a change crosses package boundaries, or a refactor needs a source-backed module map before edits.

Core Features & Use Cases

  • Zoom-out map: answer where behavior lives and what skill should run next.
  • Architecture review: find 2-4 deepening opportunities in one subsystem.
  • Refactor preflight: decide whether a proposed extraction is worth doing before code changes.

Quick Start

Generate a zoom-out map of the current subsystem, identifying data flow, module ownership, and cross-package boundaries.

Frequently Asked Questions about gormes-architecture-zoomout

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

FAQPage Schema
How do I map cross-package boundaries in a Go codebase before a refactor?▼

To map cross-package boundaries in a Go codebase, generate a zoom-out architecture footprint identifying modules, entry points, and data flow to locate where behavior lives before editing.

What is a codebase zoom-out map used for in software architecture?▼

A codebase zoom-out map identifies where behavior lives across subsystems and surfaces 2-4 deepening opportunities, helping agents decide whether a proposed extraction is worth doing.

How do I identify data flow and module ownership in internal packages?▼

Identify data flow and module ownership by applying an architecture review to specific internal packages, producing a structured output detailing persistence and test surfaces.

Does this architecture mapping approach preserve public contracts during analysis?▼

Yes, the architecture mapping approach preserves public contracts while analyzing subsystems like internal/gateway, internal/memory, and internal/provider to surface deepening opportunities.

When do I need a source-backed module map before making code changes?▼

You need a source-backed module map when an agent is unfamiliar with a code area or when a change crosses package boundaries, ensuring a clear architecture footprint exists before edits.

What's the best way to review subsystems for refactor preflight?▼

The best way to review subsystems for refactor preflight is to map cross-package boundaries and data flow, deciding whether a proposed extraction is worth doing before code changes.

Related Skills

Explore More Software Engineering Skills→
TrebuchetDynamicsTrebuchetDynamics
9

gormes-openclaw-parity

Classify OpenClaw-only behavior against Hermes parity gaps for Gormes adoption decisions.

Official
Intermediate
vessuxvessux
1

zoom-out

Generate a domain-level map of modules and callers using the project glossary.

Community
Intermediate
jzilajzila
28

Architecture Pass Skill

Review Go and TypeScript API contracts, concurrency, and state persistence in the Canopy codebase.

Community
Advanced
mostafa-K-raihanmostafa-K-raihan

zoom-out

Generate a module-caller map using the project's domain glossary vocabulary.

Community
Basic