kpkn-parity-auditor

Audit feature parity between KPKN PWA and Kotlin/Compose implementations.

Updated Feb 19, 2026
One-click install
npx skills add https://github.com/rotnitxe/KPKNFit --skill kpkn-parity-auditor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kpkn-parity-auditor
Source: https://github.com/rotnitxe/KPKNFit/tree/main/kpkn-parity-auditor
Command: npx skills add https://github.com/rotnitxe/KPKNFit --skill kpkn-parity-auditor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill prevents misleading “parity” conclusions by helping you audit real behavior differences between the KPKN PWA and the android-native Kotlin/Compose implementation.

Core Features & Use Cases

  • PWA-vs-Kotlin behavior auditing: verify feature route reachability, user workflow completion, and true state outcomes rather than relying on file presence.
  • Gap reporting and cutover evidence: produce actionable remaining gaps/drifts, distinguish intentional native adaptations from missing work, and recommend the smallest next step.
  • Evidence-driven validation guidance: select the minimum useful checks (type-checks, slice builds, tests) aligned to the risk of the claim being made.

Quick Start

Ask the AI to audit a specific feature slice by name and to compare the exact PWA anchors against the android-native landing zones, then return a compact parity report with statuses, evidence used, remaining gaps, and recommended next action.

Frequently Asked Questions about kpkn-parity-auditor

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

FAQPage Schema
How do I audit behavior parity between a PWA and an Android native app?

To audit PWA-to-Android parity, compare the PWA behavior oracle against the android-native Kotlin/Compose target by anchoring to actual code evidence. This verifies route reachability, workflow completion, and state outcomes rather than relying on file presence.

What is behavior drift in a PWA to Android migration?

Behavior drift occurs when the android-native implementation diverges from the PWA behavior oracle in logic, state persistence, or edge-case handling. A parity audit classifies these drifts to distinguish intentional native adaptations from missing work.

How do I prove migration readiness before cutting over from PWA to native?

Prove migration readiness by running a parity audit on a specific feature slice to identify cutover gaps. The audit produces actionable evidence on remaining drifts and recommends the smallest next step to achieve cutover confidence.

How do I validate logic and formula equivalence between web and Kotlin/Compose code?

Validate logic and formula equivalence by selecting minimum useful checks, like type-checks and slice builds, aligned to the risk of the claim. Evidence-driven validation anchors directly to PWA and android-native code to confirm true state outcomes.

What is the best way to classify native adapters vs missing features in a parity audit?

The best way to classify native adapters versus missing features is through evidence-driven status classification. Categories include parity, partial, native-adapter, missing, and behavior-drift, distinguishing intentional adaptations from unfinished work.