design-native-extension-feature

Drafts PRD and ARCHITECTURE documents for third-party .ppmplugin native controls through iterative user review.

808|167|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/microsoft/power-platform-skills --skill design-native-extension-feature
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-native-extension-feature
Source: https://github.com/microsoft/power-platform-skills/tree/main/plugins/power-apps-mobile-extension/skills/design-native-extension-feature
Command: npx skills add https://github.com/microsoft/power-platform-skills --skill design-native-extension-feature

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Building a third-party .ppmplugin native extension for Power Apps mobile requires a precise product and technical specification before any code is written; without one, downstream scaffolding skills emit TODO placeholders instead of working iOS and Android code.

Core Features & Use Cases

  • Pitch-first PRD drafting: Captures a 2-3 line pitch (optionally seeded from a design doc or FRD URL) and infers a complete PRD.md covering identity, user scenarios, operations, UX requirements, and PCF surface.
  • Per-operation architecture walkthroughs: Produces ARCHITECTURE.md with opinionated iOS and Android implementation specs per operation, including framework choice, hosting, message contracts, error codes, and threading.
  • Iterative approval loop: Bundles clarifying questions, marks guesses explicitly, and iterates with the user until both documents are approved as the source of truth for downstream generate, build, and assemble skills.
  • Use Case: A developer wants to build a barcode-scanning native control for Power Apps mobile; this skill turns their short pitch into a complete PRD.md and ARCHITECTURE.md that the scaffold skill reads verbatim to generate working Swift and Kotlin code.

Quick Start

Ask the assistant to run the design-native-extension-feature skill and describe in two or three lines the native capability you want to build for Power Apps mobile.

Frequently Asked Questions about design-native-extension-feature

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

FAQPage Schema
How do I design a native extension for Power Apps mobile before writing code?▼

Run this skill with a 2-3 line pitch describing the device capability and maker scenario. It drafts PRD.md and ARCHITECTURE.md, asks bundled clarifying questions for gaps, and iterates until you approve both documents.

What is a .ppmplugin file and how does dispatch work?▼

A .ppmplugin is a native-only binary bundle containing manifest.json plus Android DEX and a flat iOS framework, with no JavaScript layer. Dispatch routes through the wrap proxy directly to NativeModules.<nativeModule>.<method> based on the manifest receivers[] contract.

Can I seed the design from an existing spec or FRD document?▼

Yes. Provide a local file path or web URL when prompted and the skill reads it before drafting. Auth-gated URLs like SharePoint may fail to fetch, in which case you paste the content directly.

Does this skill generate the native iOS and Android code?▼

No. It only authors PRD.md and ARCHITECTURE.md markdown documents. Downstream skills such as generate-native-extension read ARCHITECTURE.md section 3 verbatim to emit complete working code.

Why does the skill push back on generic class names like Device or Camera?▼

The derived native module symbol becomes a key in the shared NativeModules namespace, so generic names collide across plugins and may hit reserved-name validation rules. The skill recommends vendor-prefixed or qualified names that survive the validator.