app-review

Audit Luxury Yacht app subsystems and rank structural improvements.

411|21|Updated Dec 18, 2025
One-click install
npx skills add https://github.com/luxury-yacht/app --skill app-review-luxury-yacht
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: app-review
Source: https://github.com/luxury-yacht/app/tree/main/.agents/skills/app-review
Command: npx skills add https://github.com/luxury-yacht/app --skill app-review-luxury-yacht

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you identify major structural issues in the Luxury Yacht codebase—stability, complexity, performance, security-hardening, and refactoring opportunities—before they become ongoing product drag or recurring bugs.

Core Features & Use Cases

  • System-level architecture audits: Reviews whole subsystems and cross-cutting concerns rather than isolated bugs, grounded in repository evidence.
  • Inventory-driven improvement planning: Builds broad inventories for each review domain, then translates findings into concrete improvement directions.
  • Actionable output with phased plans: Produces ranked improvement areas (and can generate temporary phased plans in docs/plans when asked).

Quick Start

Ask for a broad structural review of the Luxury Yacht app, including exactly three system-level improvement areas with evidence and likely validation steps.

Frequently Asked Questions about app-review

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

FAQPage Schema
How do I perform a structural audit of my codebase to reduce instability and development drag?

An architecture review assesses whole subsystems and cross-cutting concerns rather than isolated bugs, evaluating frontend/backend integration, developer experience, and operations-impacting design to reduce overall development drag.

How do I plan refactoring opportunities for cross-cutting concerns in a large application?

Plan refactoring opportunities by generating ranked improvement areas with concrete improvement directions and likely validation steps, optionally creating temporary phased plans in your docs directory to guide execution.

What's the best way to inventory system-level issues across frontend, backend, and Kubernetes tooling?

Inventory system-level issues by performing a read-only first-pass analysis grounded in repository evidence, evaluating cross-cutting systems and operations-impacting design concerns across architecture and integration layers.

Can I request exactly three system-level improvement areas with evidence from a codebase review?

Yes, you can request exactly three system-level improvement areas, and the review will provide explicit improvement directions per ranked area with supporting repository evidence and validation steps.

When do I need a whole-subsystem architecture review instead of fixing isolated bugs?

You need a whole-subsystem architecture review when recurring bugs and development drag indicate structural flaws in stability, performance, or cross-cutting concerns that require broad, evidence-backed inventories to resolve.