platform-dev

Implement Platform APIs with parity across Torch and MindSpore backends.

7|3|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/mindspore-ai/hyper-parallel --skill platform-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: platform-dev
Source: https://github.com/mindspore-ai/hyper-parallel/tree/main/.claude/skills/platform-dev
Command: npx skills add https://github.com/mindspore-ai/hyper-parallel --skill platform-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enables consistent cross-platform platform APIs development for HyperParallel, unifying PyTorch and MindSpore backend support, DTensor extensions, and shared platform utilities.

Core Features & Use Cases

  • Cross-platform API design and implementation across Torch and MindSpore backends
  • Support for platform-level features: FSDP, HSDP, Pipeline Parallelism, and Activation Checkpoint
  • DTensorBase extension and platform-agnostic operations
  • Workflow governance and testing guidance for platform-layer development

Quick Start

Add a new Platform API to the base class, implement corresponding backend logic for Torch and MindSpore, and validate parity with cross-backend tests.

Frequently Asked Questions about platform-dev

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

FAQPage Schema
How do I implement a cross-backend platform API for both PyTorch and MindSpore?

To implement a cross-backend platform API, add the new API to the base class, implement corresponding backend logic for Torch and MindSpore, and validate signature and return type parity with cross-backend tests.

What is cross-backend API parity and how is it validated?

Cross-backend API parity ensures aligned signatures, return types, and error behavior across PyTorch and MindSpore backends, validated through unit and cross-backend tests including stream and process group handling.

Does this platform development approach support DTensor extensions and distributed features?

Yes, platform development supports DTensorBase extensions and platform-agnostic operations, alongside platform-level features like FSDP, HSDP, Pipeline Parallelism, and Activation Checkpoint.

What's the best way to ensure signature and return type alignment across distributed backends?

The best way to ensure alignment is to define the API in the base class, implement corresponding logic per backend, and validate parity using cross-backend tests with stream and process group handling.

When do I need cross-backend testing for platform-layer development?

You need cross-backend testing for platform-layer development when adding new platform APIs to ensure signature, return type, and error behavior parity across Torch and MindSpore backends, including stream and process group handling.

Why does cross-backend platform API development require workflow governance?

Cross-backend platform API development requires workflow governance to maintain consistent implementation standards, testing guidance, and documentation updates across PyTorch and MindSpore backends.