kmm-app-skeleton

Bootstrap Kotlin Multiplatform Mobile projects with standardized templates and placeholders.

1|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/dimitriRemoiville/cc-mobile --skill kmm-app-skeleton
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kmm-app-skeleton
Source: https://github.com/dimitriRemoiville/cc-mobile/tree/main/plugins/cc-mobile-kmm/skills/kmm-app-skeleton
Command: npx skills add https://github.com/dimitriRemoiville/cc-mobile --skill kmm-app-skeleton

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The kmm-app-skeleton provides an authoritative blueprint to bootstrap a brand-new Kotlin Multiplatform Mobile project following this repository's conventions, ensuring consistency, templates, and placeholder handling across Android and iOS projects.

Core Features & Use Cases

  • Template registry consumed by /init-kmm-app and substituting placeholders such as APP_NAME, PACKAGE_ID, and APP_DISPLAY_NAME.
  • Includes every file template, placeholder list, feature-flag blocks, and the procedure to emit runnable splash screens on Android (Compose) and iOS (SwiftUI).
  • Enables rapid scaffolding for KMM projects with consistent structure and ready-to-use skeletons for native platforms.

Quick Start

Create a new KMM app scaffold using the kmm-app-skeleton template with the provided placeholders.

Frequently Asked Questions about kmm-app-skeleton

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

FAQPage Schema
How do I scaffold a new Kotlin Multiplatform Mobile project with consistent structure across Android and iOS?

To scaffold a Kotlin Multiplatform Mobile project, use a skeleton template that standardizes the structure across Android and iOS while substituting placeholders like APP_NAME and PACKAGE_ID to ensure runnable splash screens.

What placeholders do I need to configure when bootstrapping a KMM app skeleton?

You must configure placeholders including APP_NAME, PACKAGE_ID, and APP_DISPLAY_NAME to properly bootstrap the KMM app skeleton and ensure consistent project naming across native platforms.

Does the KMM app skeleton template generate runnable splash screens for both Android Compose and iOS SwiftUI?

Yes, the KMM app skeleton emits runnable splash screens on Android using Compose and on iOS using SwiftUI, ensuring immediate visual feedback after project scaffolding.

Can I use feature flags to control initialization when setting up a new Kotlin Multiplatform Mobile project?

Yes, the skeleton template includes feature-flag blocks that execute during KMM project initialization, allowing you to control which modules or configurations are applied during scaffolding.

Is this KMM skeleton template suitable for existing projects or only for new Kotlin Multiplatform initiatives?

This skeleton template applies exclusively to new KMM initiatives, providing a comprehensive blueprint for brand-new Kotlin Multiplatform Mobile projects rather than retrofitting existing codebases.

Why use a standardized skeleton template instead of manually creating a Kotlin Multiplatform Mobile project structure?

A standardized skeleton template ensures consistency, proper placeholder handling, and ready-to-use native platform skeletons, eliminating the structural inconsistencies that arise from manually scaffolding KMM projects.