From rosary
Discover and document architecture seams — the interfaces, data flows, and integration points between projects or dependencies. Use when exploring how codebases connect, onboarding to a new ecosystem, or documenting service boundaries. Works on single projects or multi-project ecosystems.
How this skill is triggered — by the user, by Claude, or both
Slash command
/rosary:seam-discovery <path-to-project> [path-to-project-2 ...]<path-to-project> [path-to-project-2 ...]This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Discover how projects connect by analyzing their boundary surfaces, integration points, and failure modes.
Discover how projects connect by analyzing their boundary surfaces, integration points, and failure modes.
Given one or more project paths ($ARGUMENTS), produce a structured seam analysis.
For each project path:
For each pair of connected projects (or project ↔ dependency), document:
| Field | Description |
|---|---|
| Seam name | Human-readable label (e.g., "mache → ley-line UDS") |
| Direction | Who calls whom, or bidirectional |
| Protocol | UDS socket, CGO FFI, HTTP, CLI subprocess, shared file, etc. |
| Discovery | How they find each other (env var, well-known path, config) |
| Failure mode | What happens when the other side is down |
| Classification | hard (won't start), soft (degrades gracefully), build (compile-time only), optional (enhances when available) |
| Data contract | Types, schemas, or formats that cross the boundary |
| Source files | Files implementing this seam |
Use this priority order to find seams:
Non-obvious connections that are easy to miss:
~/.mache/default.sock)#[cfg(feature = "embed")])Produce a markdown document with:
# Architecture Seams: <project(s)>
## Projects
| Project | Language | Purpose |
|---------|----------|---------|
| ... | ... | ... |
## Seams
| Seam | From → To | Protocol | Classification | Failure Mode |
|------|-----------|----------|----------------|--------------|
| ... | ... | ... | ... | ... |
## Dependency Graph
<ASCII art>
## Failure Analysis
- If <project> is down: <what breaks>
## Recommendations
- ...
/seam-discovery ~/remotes/art/mache
→ Analyzes mache's boundaries: MCP server (HTTP/stdio), FUSE/NFS mount,
ley-line UDS (soft dep), SQLite readers, tree-sitter grammars
/seam-discovery ~/remotes/art/mache ~/remotes/art/ley-line ~/remotes/art/kiln
→ Cross-project analysis: how kiln bundles them (CGO FFI, entrypoint.sh),
how mache discovers ley-line (LEYLINE_SOCKET, ~/.mache/default.sock),
build dependencies vs runtime dependencies
/seam-discovery .
→ Analyzes current project
rsry_bead_create(
repo_path="/path/to/repo",
title="Architecture seam discovery: <project>",
issue_type="research"
)
rsry_dispatch(bead_id, agent="architect-agent")
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub agentic-research/rosary --plugin rosary