Run a 5-phase post-completion audit with scored gap report and test scaffolds
npx claudepluginhub cure-consulting-group/productengineeringskillsThis skill is limited to using the following tools:
Multi-phase audit that runs after every feature completion across Android, iOS, Firebase, and Web. Produces a scored gap report with actionable fixes and missing test scaffolds.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Multi-phase audit that runs after every feature completion across Android, iOS, Firebase, and Web. Produces a scored gap report with actionable fixes and missing test scaffolds.
Before starting, gather project context silently:
PORTFOLIO.md if it exists in the project root or parent directories for product/team contextcat package.json 2>/dev/null || cat build.gradle.kts 2>/dev/null || cat Podfile 2>/dev/null to detect stackgit log --oneline -5 2>/dev/null for recent changesls src/ app/ lib/ functions/ 2>/dev/null to understand project structureBefore applying the audit framework, scan the codebase:
**/{feature}/**/*.kt **/{feature}/**/*.swift **/{feature}/**/*.tsxcatch|throw|Result in feature code (error handling gaps)try { } catch { } with empty catch blocks (swallowed errors)sealed class.*Error|enum.*Error (no error type hierarchy)**/{feature}/**/*.kt count**/{feature}/**/*Test.kt countsk-|pk_|ghp_|AIza|AKIAReport findings before proceeding to the framework phases.
Execute all 5 phases in order. Do not skip phases. Do not summarize — audit.
| Input | Required | Notes |
|---|---|---|
| Feature name | Yes | Short identifier |
| Feature description | Yes | 1-2 sentences |
| Android files/modules | Yes if Android | Screens, ViewModels, Repositories |
| iOS files/modules | Yes if iOS | TCA Features, Views, Clients |
| Firebase collections/functions | Yes if Firebase used | Firestore paths, callable names |
| Known concerns | Optional | Any suspected gaps |
If any required input is missing, ask for it before proceeding.
Map the complete surface area:
Action → Reducer → Effect chainUiEvent → ViewModel → Repository → DataSource chaintry/catch, .catch{}, sealed Result wrapper)viewModelScope, lifecycleScope)TaskResult, .run { } failure path)Effect.cancel(id:), .cancellable(id:)).none returns on meaningful actions)Validate end-to-end wiring across all layers:
Android: Hilt chain complete, StateFlow → Composable connected, navigation graph wired, lifecycle-aware Firebase listeners
iOS TCA: Store scoping correct, DependencyValues injection complete, all Actions handled, state-driven navigation, testValue defined for all live Dependencies
Firebase: Firestore schema matches both clients, Functions deployed to correct env, Auth UID scoped correctly, security rules consistent
Stripe: PaymentIntent lifecycle complete, webhooks idempotent, Customer/PaymentMethod associations correct in both Stripe and Firestore
Rate each item: ✅ Covered | ⚠️ Partial | ❌ Missing
Android: ViewModel with MockK/FakeRepository, Repository with fake data source, Hilt test modules, ComposeTestRule UI tests, navigation tests
iOS TCA: TestStore for ALL Reducer tests, every Action asserts exact State mutation, every Effect awaited and resulting Action asserted, withDependencies {} overrides, exhaustivity mode, cancellation tested
Firebase/Backend: Firestore rules via Emulator Suite, Firebase Functions unit tests, end-to-end happy path
Web: Component unit tests, integration tests, E2E tests for critical paths
═══════════════════════════════════════════════════════
FEATURE AUDIT REPORT
Feature: [NAME]
Date: [TODAY]
═══════════════════════════════════════════════════════
SUMMARY SCORECARD
┌─────────────────────────┬─────────┬───────────┬─────────┬────────┬────────┐
│ Category │ Android │ iOS (TCA) │ Backend │ Score │ Status │
├─────────────────────────┼─────────┼───────────┼─────────┼────────┼────────┤
│ Feature Boundary │ X/10 │ X/10 │ X/10 │ X/30 │ 🟢🟡🔴│
│ Logic Gap Detection │ X/10 │ X/10 │ X/10 │ X/30 │ 🟢🟡🔴│
│ Integration Wiring │ X/10 │ X/10 │ X/10 │ X/30 │ 🟢🟡🔴│
│ Test Coverage │ X/10 │ X/10 │ X/10 │ X/30 │ 🟢🟡🔴│
├─────────────────────────┼─────────┼───────────┼─────────┼────────┼────────┤
│ OVERALL │ │ │ │ X/120 │ │
└─────────────────────────┴─────────┴───────────┴─────────┴────────┴────────┘
Scoring: 🟢 >= 80% | 🟡 60-79% | 🔴 < 60%
CRITICAL GAPS (block ship — fix before merge)
1. [Platform] — [Gap] — [File/Layer] — [Fix]
HIGH PRIORITY GAPS (fix in next sprint)
1. [Platform] — [Gap] — [File/Layer] — [Fix]
MISSING TESTS
1. [Platform] — [Test description] — [Test type]
Scaffold: [Minimal code stub for the missing test]
WIRING ISSUES
1. [Platform] — [Issue] — [From layer → To layer] — [Fix]
CROSS-PLATFORM CONSISTENCY ISSUES
1. [Behavior or data contract that differs between Android and iOS] — [Risk] — [Fix]
RECOMMENDATIONS
- [Architectural or process improvement]
NEXT ACTIONS CHECKLIST
[ ] Fix all CRITICAL gaps before next PR/merge
[ ] Schedule HIGH PRIORITY gaps for next sprint
[ ] Add all MISSING TESTS to backlog with ticket references
[ ] Resolve WIRING ISSUES before QA handoff
[ ] Address CROSS-PLATFORM issues before dual-platform release
═══════════════════════════════════════════════════════