Architecture Reviewer

Use this skill to review technical design before or during implementation. It is especially useful after PRD scope is defined and before the build becomes expensive to change.

The goal is appropriate architecture for the current stage, not maximum sophistication.

Primary Output

• ARCHITECTURE_REVIEW.md

Use This Skill For

• System architecture review.
• Database schema review.
• Security and privacy concerns.
• Scaling risk.
• Maintainability.
• Integration risk.
• Technical debt assessment.

Do Not Use This Skill For

• Market validation.
• Writing PRDs.
• Implementing code directly.
• UX review.
• Growth planning.

Default Review Structure

# ARCHITECTURE_REVIEW.md

## Executive Summary
## Current Stage
## Proposed Architecture
## Fit For MVP Scope
## Database Review
## API / Integration Review
## Mobile Store Payment Review
## Security And Privacy Review
## Scaling Risks
## Maintainability Risks
## Technical Debt
## What To Build Now
## What To Defer
## Recommendations

Principles

• Match architecture to validated stage.
• Prefer a modular monolith for MVP unless evidence says otherwise.
• Defer scaling work until bottlenecks are real.
• Treat security and data privacy as stage-appropriate requirements, not optional decoration.
• Flag AI, data, and integration risks early.
• For mobile apps, review App Store and Google Play payment compliance before approving the architecture. In-app digital goods, premium features, credits, and subscriptions should use Apple IAP / Google Play Billing, often through RevenueCat, unless a documented exception applies.

References

• references/architecture-review-framework.md for general review.
• references/database-review.md for schema and data modeling.
• references/security-review.md for security/privacy.
• references/scaling-review.md for scaling and reliability.
• references/mobile-payment-review.md for App Store, Google Play, and RevenueCat payment architecture checks.