check-platforms

Analyze feature implementation parity across iOS, Android, and backend repositories.

19|21|Updated Jul 22, 2024
One-click install
npx skills add https://github.com/vultisig/vultisig-windows --skill check-platforms
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-platforms
Source: https://github.com/vultisig/vultisig-windows/tree/main/.claude/skills/check-platforms
Command: npx skills add https://github.com/vultisig/vultisig-windows --skill check-platforms

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps ensure consistency and identify implementation gaps across different platform codebases (iOS, Android, Backend, Windows) when developing new features or porting existing ones.

Core Features & Use Cases

  • Cross-Platform Code Analysis: Searches sibling repositories for feature implementations.
  • Pattern Mapping: Identifies and maps native implementation patterns to TypeScript/React equivalents.
  • Use Case: Before implementing a new "token swap" feature in the Windows app, use this Skill to see how it's handled in iOS, Android, and the Go backend, ensuring a consistent user experience and leveraging existing logic.

Quick Start

Use the check-platforms skill to analyze the implementation of the "token swap" feature across all sibling repositories.

Frequently Asked Questions about check-platforms

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

FAQPage Schema
How do I check cross-platform feature parity across iOS, Android, and backend repositories?

Cross-platform feature parity is validated by searching commit histories and code snapshots in sibling repositories for specified keywords to identify implementation gaps. This ensures consistency across iOS, Android, and backend codebases during feature development.

What is the best way to map native iOS and Android implementation patterns to TypeScript and React equivalents?

Mapping native patterns to TypeScript and React equivalents involves analyzing sibling repository codebases to identify existing platform-specific logic. This allows developers to leverage existing implementations and maintain consistency when porting features.

How does searching commit histories help with feature porting across different platforms?

Searching commit histories facilitates feature porting by locating where and how a feature was implemented across sibling repositories. This reveals existing native logic and implementation details, ensuring the ported feature matches the expected cross-platform behavior.

Can I use this approach to validate a new feature implementation across Windows, iOS, Android, and Go backend codebases?

Yes, you can validate feature implementation across Windows, iOS, Android, and Go backend codebases. The process analyzes sibling repositories to ensure a consistent user experience and identifies implementation gaps before you finalize the new feature.

How do I identify implementation gaps when developing features for multiple platforms?

Implementation gaps are identified by analyzing and validating feature implementations across sibling repositories. By searching code snapshots for specified keywords, you can detect missing logic and ensure consistency across different platform codebases.

When do I need cross-platform code analysis for my repository?

Cross-platform code analysis is needed when developing new features or porting existing ones across different platforms. It ensures consistency and identifies implementation gaps by searching sibling repositories for existing feature implementations.