Install
$ agentstack add skill-on-deck-society-love-stack-system-designer-review ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
System Designer Review
When activated, perform a structural review of the codebase with a senior system designer's lens.
Review Dimensions
- Data flow: Trace how data moves between components, services, and storage. Flag places where data is fetched redundantly, transformed inconsistently, or persisted without a clear source of truth.
- Coupling and cohesion: Identify tight coupling between modules that should be independent. Flag god files, circular dependencies, and places where business logic leaks into presentation or persistence layers.
- Scalability bottlenecks: Look for operations that would degrade at 10x or 100x current load. N+1 queries, synchronous calls that should be async, missing pagination, unbounded list operations.
- Error handling consistency: Check whether errors are handled with a consistent pattern across the codebase. Flag silent failures, caught-and-ignored errors, and missing error boundaries.
- State management: Review how state is owned, updated, and shared. Flag duplicate sources of truth, prop drilling that should be context, and global state that should be local.
- Abstraction levels: Flag missing abstractions (repeated patterns that should be extracted) and over-abstractions (premature generalization that adds complexity without benefit).
- External dependencies: List third-party services the system depends on. For each, assess blast radius if that dependency fails and whether a fallback exists.
- Testability: Identify code that's hard to test due to structure (untestable side effects, hidden dependencies, private state that should be injected).
Output Format
Produce a markdown report structured as:
- Executive summary (3-5 bullet points, the big stuff)
- Findings by dimension (one section per dimension above, with specific file and line references)
- Severity-ordered action list (Critical, High, Medium, Low, what to fix first)
- Questions for the team (anything ambiguous that warrants a discussion before deciding)
When to Invoke
Invoke when the user asks for an "architecture review", "system design review", "senior engineer review", "codebase audit", "find the tech debt", or is planning a major refactor and wants to understand the current state first.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: on-deck-society
- Source: on-deck-society/love-stack
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.