Menu

Individual skill

project-architecture

0upvotes

Draw or explain the target project's software architecture and data flows with source-backed diagrams. Use when the user asks for a project architecture diagram, a subsystem walkthrough, or a visual explanation of a code change.

plugins/shared/loom/skills/project-architecture/SKILL.md

Read pinned source

Source commit 7cf9b229d22656ac28cb6fa47d26bb6230155b0a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,465
Repository last updated
Nov 3, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Project Architecture

Diagram the project Loom is delivering. Use its application, service, module,
scene, storage, and integration boundaries. Loom's planning stages, task results,
and review records belong to a delivery-evidence view, not the target system's
technical architecture.

## Establish the architecture

Start with the existing project context: architecture contracts, repository
context, documentation, manifests, and code already inspected for the task.
For an implemented system, use those records to locate the relevant code and
confirm key relationships. Fill gaps with focused file or symbol lookups;
use an existing code index or language server when available. Do not build a
Back to top