skills.rest
2zcory
2zcoryCOMMUNITY
Explore all skills by this author →
GitHub

web-architecture-review

Clarify web application architecture decisions with constraints, tradeoffs, and residual risks.

Updated Mar 20, 2026
Search Tags:#architecture#deployment#api#rendering#decision#web#tradeoffs
One-click install
npx skills add https://github.com/2zcory/skills --skill web-architecture-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: web-architecture-review
Source: https://github.com/2zcory/skills/tree/main/web-architecture-review
Command: npx skills add https://github.com/2zcory/skills --skill web-architecture-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams make architecture decisions for web applications by clarifying constraints and boundaries, comparing rendering models, state ownership, API contracts, repository structure, and deployment implications, and delivering a concise recommendation with tradeoffs and residual risks.

Core Features & Use Cases

  • Define and document architecture questions and constraints for a project.
  • Compare rendering models (SSR vs CSR), state ownership, API contracts, and deployment boundaries.
  • Produce a concise recommendation with tradeoffs, residual risks, and verification steps.
  • Pair with product-management or dialectical-review when business or contradictory inputs require alignment.

Quick Start

Provide a decision-focused architecture review for the current web app and surface the strongest practical direction with next steps.

Frequently Asked Questions about web-architecture-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make web architecture decisions for rendering models and API contracts?▼

Web architecture decisions are made by clarifying constraints, pairing options, and evaluating fit and cost to yield a concise recommendation. This workflow surfaces tradeoffs between rendering models, state ownership, and API contracts to guide your application structure.

What is the best way to compare SSR vs CSR rendering models for my application?▼

Comparing SSR vs CSR requires evaluating deployment boundaries and state ownership constraints. A structured architecture review pairs these rendering options against your project requirements to deliver a practical recommendation with residual risks.

How do I structure a web architecture review before a major refactoring?▼

Structure a web architecture review by capturing constraints, clarifying boundaries, and comparing repository structures. This process evaluates deployment implications and API contracts to produce verification steps and a concise direction for your refactoring.

Does this architecture review workflow help with state ownership and deployment boundaries?▼

Yes, this architecture review workflow explicitly addresses state ownership and deployment boundaries. It evaluates these components against your application constraints to identify tradeoffs and residual risks before finalizing your architecture direction.

When should I evaluate tradeoffs and residual risks in web architecture decisions?▼

Evaluate tradeoffs and residual risks during initial architecture direction, boundary clarification, or refactoring reviews. Surfacing these constraints ensures your web architecture decisions account for API contracts and deployment impact before implementation.

Related Skills

Explore More Software Engineering Skills→
HechaoYannetHechaoYannet

create-architecture

Generate a master architecture document from GDDs, ADRs, and governance constraints.

Community
Advanced
patrickrmoorepatrickrmoore

sddp-plan

Generate implementation plans from feature specifications with architecture, data models, and API contracts.

Community
Advanced
OzeroHAXOzeroHAX
32

coder-system-design-perf-patterns

Select system-level performance patterns for latency, throughput, or cost constraints.

Community
Advanced
anderson-0anderson-0
4

architecture-map

Generate Mermaid architecture diagrams from source code with dependency analysis.

Community
Advanced