kpkn-program-workout-flow

Translate KPKN program editing and workout logging from PWA to Kotlin/Compose.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Reduces regressions and behavior drift when translating KPKN training program, session editing, and live workout logging from the PWA into Android-native Kotlin/Compose.

Core Features & Use Cases

  • Behavior-preserving flow translation: Guides how to migrate business intent and data-flow semantics (program hierarchy, session editing, workout logging, history continuity, navigation argument contracts) without copying the PWA’s layout or interaction quirks.
  • Risk-aware implementation: Recommends the smallest viable seams (screens, ViewModels, ProgramRepository, and stable ID rules) and highlights common failure modes like route mismatches, wrong session persistence, stale ongoing workout state, and finish-workout incompleteness.
  • Validation and debugging workflow: Provides a targeted Android build/validation approach and manual smoke checks for program editor, session editor, and workout flow changes, especially when persistence or routing is involved.

Quick Start

Use the kpkn-program-workout-flow skill when migrating or debugging an Android-native regression in ProgramEditor, SessionEditor, or WorkoutScreen behavior, and ask it to produce a minimal, risk-aware change plan that preserves repository semantics and route/save contracts.

Frequently Asked Questions about kpkn-program-workout-flow

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

FAQPage Schema
How do I migrate PWA workout logging flows to Android Kotlin Compose without behavior drift?

Validate workout flow migrations in Android by running compile/assemble builds followed by targeted manual smoke checks on the program editor, session editor, and workout screens to ensure persistence and routing contracts remain intact.

How do I debug session editing persistence regressions in my Android workout logging app?

Common failure modes during session editing persistence include route mismatches, wrong session persistence writes, stale ongoing workout state, and finish-workout incompleteness, which require targeted manual smoke checks to resolve.

Why does my ongoing workout state become stale after migrating to Android-native Kotlin Compose?

Prevent stale workout state by maintaining stable entity IDs across program hierarchy edits, respecting navigation route argument contracts, and validating workout start, log, and finish history continuity through compile/assemble and manual smoke checks.

What is the best way to preserve program hierarchy structure when translating a PWA to Android-native?

Use the smallest viable seams across screens, ViewModels, and ProgramRepository to isolate program structure changes, then validate through targeted Android build approaches and manual smoke checks for regression analysis.

Can I use this approach for Android-native regression analysis of split selection and program structure edits?

Regression analysis requires checking that stable entity IDs are maintained, session editing persistence rules are respected, and workout history continuity is preserved across program editor and session editor screens.