System Design Reviewer
Software development skill, available on Zeplik
System Design Reviewer is a ready-to-run software development skill on Zeplik. Not for existing-code analysis (use architecture) or API rules (use api-design-principles). Ask in plain language and Zeplik applies the skill's method for you inside the conversation, on whichever AI model you prefer.
The System Design Reviewer skill loads automatically when your request matches it, or you can invoke it directly by typing /system-design in any chat. It works with attachments, connectors, and any model that supports the task, so you get the same expert method every time without setting anything up.
What the System Design Reviewer skill can do
- Gather functional and non-functional requirements before proposing components
- Produce component diagrams and data flow for new systems
- Design data models, caching, queues, and error handling in deep-dive sections
- Compare architecture options across cost, complexity, and scalability trade-offs
Try these prompts on Zeplik
Pick a prompt to open it in the Zeplik app. If you are not signed in yet, your prompt is waiting for you the moment you do.
How the System Design Reviewer skill works
/system-design
Help design systems and evaluate architectural decisions. Ask the user for requirements, constraints, and existing stack; deliver structured design documents with diagrams (ASCII or described), explicit assumptions, and trade-off analysis as chat artifacts. For understanding or documenting the architecture of an existing codebase, use architecture; for REST/GraphQL API style and contract conventions, use api-design-principles.
Framework
1. Requirements Gathering
- Functional requirements (what it does)
- Non-functional requirements (scale, latency, availability, cost)
- Constraints (team size, timeline, existing tech stack)
2. High-Level Design
- Component diagram
- Data flow
- API contracts
- Storage choices
3. Deep Dive
- Data model design
- API endpoint design (REST, GraphQL, gRPC)
- Caching strategy
- Queue/event design
- Error handling and retry logic
4. Scale and Reliability
- Load estimation
- Horizontal vs. vertical scaling
- Failover and redundancy
- Monitoring and alerting
5. Trade-off Analysis
- Every decision has trade-offs. Make them explicit.
- Consider: complexity, cost, team familiarity, time to market, maintainability
Output
Produce clear, structured design documents with diagrams (ASCII or described), explicit assumptions, and trade-off analysis. Always identify what you'd revisit as the system grows.
Usage
Walk the five framework stages in order, asking the user for missing requirements and constraints before proposing components. Deliver the design as a structured document artifact: context and requirements, high-level diagram, deep-dive sections for data model, APIs, caching, and queues, a scale/reliability plan with load estimates, and an explicit trade-off table with the decisions you would revisit as the system grows. When the user is choosing between two designs, compare them dimension by dimension (complexity, cost, familiarity, time to market, maintainability) and recommend one with reasoning. Defer codebase archaeology to architecture and API convention questions to api-design-principles.
/system-design $ARGUMENTS
How to use the System Design Reviewer skill
Sign in to Zeplik
Create a free Zeplik account or sign in. New accounts start with free credits, so you can try the System Design Reviewer skill right away.
Describe your software development task
Ask in plain language, or type /system-design to invoke the skill directly. Zeplik recognizes the System Design Reviewer skill and applies its method.
Review and refine the result
Zeplik returns a clear, structured answer. Ask follow-ups in the same chat to refine it or take the next step.
Source and credit
- Author
- anthropic
- License
- Apache-2.0
Adapted from the open-source anthropics/knowledge-work-plugins project and tuned to run natively on Zeplik. View source on GitHub.
Frequently asked questions
- What is the System Design Reviewer skill?
- System Design Reviewer is a ready-to-run software development skill on Zeplik. Not for existing-code analysis (use architecture) or API rules (use api-design-principles). Ask in plain language and Zeplik applies the skill's method for you inside the conversation, on whichever AI model you prefer.
- How do I use System Design Reviewer on Zeplik?
- Sign in to Zeplik and ask in plain language, or type /system-design in any chat to invoke it directly. The skill applies its method and returns a result you can refine in the same conversation.
- Which AI model does the System Design Reviewer skill use?
- Any model you choose. Zeplik works across every model in one chat, so the System Design Reviewer skill runs on your preferred model for the task.
- Where does the System Design Reviewer skill come from?
- The System Design Reviewer skill is adapted from the open-source anthropics/knowledge-work-plugins project (Apache-2.0) and tuned to run natively on Zeplik. The original source is linked on this page.
- How much does the System Design Reviewer skill cost?
- Using the skill is free to start. You only spend Zeplik credits when the assistant runs, and new accounts begin with free credits.
Related software development skills
- .NET BackendBuild ASP.NET Core 8+ backends with EF Core: auth, background jobs, production API patterns
- Advanced Git WorkflowsUse for advanced Git surgery: interactive rebase, cherry-pick, bisect, reflog recovery, and history cleanup before merging. Not for parallel worktree workflows (use using-git-worktrees).
- Adversarial Code ReviewHunt for bugs in code the user shares by assuming defects exist and attacking the code through several distinct lenses, then report severity-ranked findings with evidence. Use for "review this", "what could go wrong", "bug hunt", or pre-merge scrutiny of a change. Read-only, it reports problems and does not rewrite the code. Not for style cleanup (use simplify-code) or for writing new code.
- AI Agent FrameworksUse when building multi-agent systems or agent orchestration -- LangChain/LangGraph, agent team design, task coordination, pipelines. Not for authoring a Zeplik skill (use skill-creator).
- Algolia SearchAdd Algolia search: indexing strategies, React InstantSearch, relevance tuning, search-as-you-type
- Android CI/CDAutomate Android CI/CD to Google Play: keystore, GitHub Secrets, multi-stage release workflow for RN, Flutter, native
More on Zeplik
Try System Design Reviewer on Zeplik
Every model, one chat. Bring the System Design Reviewer skill into your next conversation and let the assistant do the work.