Plugin
distributed-architect
A reasoning framework that helps Claude analyze distributed system code changes for correctness before writing code. It provides an always-on boundary detector that recognizes when changes cross component boundaries (state mutations, data serialization, failure handling, new interactions), then loads targeted reasoning checklists on demand. Three slash commands cover the full development lifecycle: /dist-check for coding-time two-pass analysis, /dist-design for architecture trade-off eval...
- Analysed
- Last observed
What the code does
Static analysis found none of the capabilities we track, such as shell commands, network requests or file writes, in the latest version.
Having a capability is not wrongdoing; many tools need these to do their job. It tells you what to check before you install.
This is public metadata, not a safety certification or complete assessment. Static analysis cannot establish what a tool does at runtime.
Risk
Sign in to see this tool's overall risk level and what drives it. Free.
Coverage
Detailed report
1 finding from automated static analysis of the latest version, with severities and explanations.
Using this tool across your team? We can assess your whole inventory.
Request an inventory assessment