kotlin-project-feature-implementation

Plan Kotlin Multiplatform feature implementation with architecture defaults and guardrails.

1|Updated Apr 22, 2026
One-click install
npx skills add https://github.com/cedric-champeix/SpoonFeeder --skill kotlin-project-feature-implementation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kotlin-project-feature-implementation
Source: https://github.com/cedric-champeix/SpoonFeeder/tree/main/.claude/skills/kotlin-project-feature-implementation
Command: npx skills add https://github.com/cedric-champeix/SpoonFeeder --skill kotlin-project-feature-implementation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Kotlin Multiplatform feature implementation can be error-prone without a clear plan; this skill codifies pre-coding inspections, KMP source-set discipline, state pipeline design, architectural defaults, security/performance guardrails, and implementation rules to guide implementation.

Core Features & Use Cases

  • Pre-coding inspection: ensures module boundaries, route ownership, and data ownership are clear before coding.
  • Architecture defaults: codifies common patterns to preserve consistency across multiplatform features.
  • State pipeline guidance: defines UI/state ownership, data flow, and error handling for new flows.

Quick Start

Apply this skill at the outset of a Kotlin Multiplatform feature to ensure architectural alignment and guardrails are established.

Frequently Asked Questions about kotlin-project-feature-implementation

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

FAQPage Schema
How do I plan architecture for a new Kotlin Multiplatform feature?

Kotlin Multiplatform feature implementation requires codifying pre-coding inspections, source-set discipline, and state pipeline design. This ensures module boundaries, route ownership, and data ownership are explicitly defined before coding begins.

What are the best practices for managing state in Kotlin Multiplatform?

State management in Kotlin Multiplatform involves defining clear UI and state ownership alongside structured data flow. Establishing architectural defaults early ensures consistent error handling and maintainable state pipelines across shared code.

When do I need to inspect module boundaries in KMP?

Inspect module boundaries in KMP during the pre-coding phase of new feature development or extension work. This inspection clarifies data ownership and route ownership, preventing integration errors across shared and platform-specific code.

How do I set up guardrails for Kotlin Multiplatform code quality?

Set up guardrails for Kotlin Multiplatform code quality by codifying security and performance rules alongside architectural defaults. Apply these guardrails at the outset of feature development to maintain consistent module boundaries and implementation standards.

Does Kotlin Multiplatform feature implementation work with existing platform-specific code?

Kotlin Multiplatform feature implementation applies to extension work across both shared and platform-specific code. It establishes pre-coding checks and source-set discipline that integrate new features with existing architectural boundaries.