99-reference/app-review-checklist.md

App review checklist

App review checklist

Use this checklist when reviewing a Vroq app or a proposed change.

The goal is to verify that the app follows the Vroq house style, stays maintainable, and does not drift toward hacks.

Structure

• Does the app follow the standard bootstrap (index.html, App.js, store setup)?
• Are features grouped inside features/?
• Is shared code only used for truly reused logic?
• Are new files justified by clear responsibility boundaries?

Naming

• Are feature names clear and business-oriented?
• Are component and section names descriptive?
• Are reducer names aligned with owned state slices?
• Are action names explicit and feature-scoped?

Code organization

• Are files small and focused?
• Are components presentation-oriented?
• Are sections feature-local and store-aware?
• Do reducers own state transitions?
• Do API clients isolate remote calls?

Editing discipline

• Was the change made with focused edits?
• Was patching preferred over rewriting?
• Were good existing patterns preserved?
• Were hacks or symptom patches avoided?

Styling

• Does the app load ui.css?
• Are theme tokens used instead of ad hoc visual values?
• Are layout patterns simple and consistent?
• Is inline style used only for small local layout adjustments?

State and debugging

• Does state shape reflect feature ownership?
• Are actions explicit?
• Are reducers predictable and pure?
• Would the behavior be easy to debug through action and reducer flow?

APIs

• Are remote calls isolated in API client helpers?
• Are scripts small and well-named?
• Are request and response shapes predictable?
• Are errors clear and actionable?

Final question

Does this app or change make the next edit easier, or harder?

If it makes the next edit harder, it likely needs another pass.