AgentSkillsCN

c64-parity

在 C64 Commander 中，针对 Android、iOS 和 Web 各个渠道，全面审计并确保功能与行为的一致性。

SKILL.md
--- frontmatter
name: c64-parity
description: Audit/enforce feature/behavior parity across Android/iOS/Web routes in C64 Commander.
argument-hint: (optional) specific feature or module
user-invokable: true
disable-model-invocation: true

Skill: C64 Platform Parity Audit

Purpose

Ensure functional parity across:

  • •Android
  • •iOS
  • •Web

Android remains the reference implementation.

Execution Workflow

Step 1 - Inventory Features

Identify:

  • •Import flows
  • •Playlist management
  • •Disk mounting
  • •HVSC ingestion
  • •Share-target ingestion
  • •FTP browsing
  • •Configuration management

Step 2 - Detect Platform Divergence

For each feature:

  • •Compare platform-specific code paths.
  • •Identify Android-only logic.
  • •Identify iOS-only conditions.
  • •Identify Web-only fallbacks.

Document differences.

Step 3 - Classify Differences

Each difference must be categorized as:

  1. •Intentional platform constraint
  2. •Missing implementation
  3. •Behavioral inconsistency
  4. •UI-only variance

Step 4 - Remediation

If missing or inconsistent:

  • •Implement minimal parity correction.
  • •Add tests where behavior differs.
  • •Avoid duplicating tests for identical logic.
  • •Preserve Android as baseline.

Constraints

  • •Do not introduce speculative features.
  • •Do not refactor architecture unless required.
  • •Do not degrade Android route stability.
  • •Maintain deterministic Maestro and Playwright behavior.

Completion Criteria

  • •All core features aligned.
  • •No unintended platform drift.
  • •Platform-specific behavior explicitly justified.
  • •Tests updated where required.
  • •Clean working tree.