File Structure Auditor

Use this skill to review whether React Native files are placed, named, and grouped according to UHC Mobile maintainability standards.

Workflow

1. Locate the package, screen, or component boundary under review and read nearby files as a unit rather than judging a single file in isolation.
2. Check whether the main component file matches the exported component name and whether index.ts or index.tsx files are used only for aggregation.
3. Check related-file grouping: component, utils, hooks, types, tests, analytics, styles, fixtures, and stories should be grouped where the component has grown beyond a simple single file.
4. Check folder depth and reuse boundaries: prefer flat component-named folders, package-wide common code in common, screen-owned code under screens, and locally reused UI under components.
5. Check modal placement and route ownership, especially whether package-local modals and cross-package modals live in the right navigation area.
6. Report restructuring suggestions in small, behavior-preserving steps.

Review Focus

• Avoid index.tsx as the main component implementation file.
• Group related files with consistent Component.tsx, Component.utils.ts, Component.test.tsx, Component.analytics.ts, Component.types.ts, and Component.hooks.ts names.
• Keep folders flat enough to navigate and avoid deeply nested hierarchy for one feature.
• Extract reusable or testable logic into .utils.ts or focused hooks instead of leaving it inside large component files.
• Place cross-package modals in the shared core/navigation area and package-local modals inside the owning package.

Output

• Lead with findings ordered by severity, with file and line references when possible.
• Separate blocking issues from high, medium, and low priority recommendations.
• Explain impact in mobile-user terms: security exposure, broken rollout, jank, inaccessible flow, analytics drift, build/runtime failure, or maintainability risk.
• Include specific remediation guidance. Keep code snippets small unless the user asks for an implementation.
• If no issues are found, say so clearly and note any meaningful test or verification gaps.

References

• references/review-guide.md: Migrated detailed review guide from the original mobile-ai-skills agent definition. Read it when you need the full checklist, example report shape, or grep patterns.