Analyze architectural seams and map dependencies to surface coupling problems.
npx skills add https://github.com/petekp/agent-skills --skill seam-ripper
Please help me install this Agent Skill. Skill: seam-ripper Source: https://github.com/petekp/agent-skills/tree/main/skills/seam-ripper Command: npx skills add https://github.com/petekp/agent-skills --skill seam-ripper
Ruthlessly analyze architectural seams—the interfaces, boundaries, and contracts between system components—to expose coupling problems, abstraction leaks, and design failures. Use when asked to review architecture, analyze coupling, find interface problems, improve module boundaries, audit dependencies, or redesign system structure. Produces uncompromising redesign proposals that prioritize correctness over backwards compatibility.
Request a seam-ripper analysis by providing the system's architecture or a codebase segment.
High-intent search queries and answers about installing and using this skill.
Mapping dependencies, interfaces, and data contracts across modules reveals architectural coupling problems and design flaws. This analysis exposes abstraction leaks and produces a structured transformation plan with actionable redesign recommendations.
Finding interface coupling problems requires auditing module boundaries and dependency directions to expose abstraction leaks. This identifies where contracts are violated and produces uncompromising redesign proposals that prioritize correctness over backwards compatibility.
Redesigning module boundaries requires mapping dependency directions and data flows to identify abstraction leaks. This produces a structured transformation plan with concrete migration steps, prioritizing architectural correctness over backwards compatibility to resolve design failures.
Auditing dependencies and data contracts across modules is supported by mapping interface boundaries and data flows. This comprehensive boundary mapping exposes design flaws and coupling problems, generating an evidence-based redesign plan with actionable recommendations.
When resolving architectural coupling problems and abstraction leaks, prioritizing correctness over backwards compatibility is recommended. This approach ensures uncompromising redesign proposals that properly fix design failures rather than preserving flawed boundaries.
Yes, providing the system's architecture or a codebase segment is sufficient for analysis. The process maps dependencies, interfaces, and data contracts to surface coupling problems and generate a structured transformation plan with concrete steps.
lekmanEnforce clean architecture principles for module design and boundary contracts.
grant-vineAnalyze codebase module boundaries and coupling to generate RFC migration plans.
yash-gargAnalyze software modules to design deeper interfaces and abstraction boundaries.
velesarAnalyze and visualize software dependencies to detect coupling, cycles, and architectural violations.
