compose-multiplatform-patterns

Compose Multiplatform and Jetpack Compose patterns for KMP projects — state management, navigation, theming, performance, and platform-specific UI. Use when building Compose or Jetpack Compose UI, state, navigation, or theming in a KMP project.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/compose-multiplatform-patterns/SKILL.md

The canonical home for this skill is tdg-personal/compose-multiplatform-patterns

Quality

Content

76%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A high-quality, executable patterns reference with excellent actionability and efficient use of tokens. Its only real weakness is workflow clarity, which is inherent to its catalog nature — there is no sequenced procedure or validation loop to score against.

Suggestions

Add a short 'Decision workflow' subsection (e.g. pick state pattern → wire navigation → apply stability → verify recomposition) to give the catalog a light sequenced spine with a verification checkpoint, lifting workflow_clarity above 3.

Move the longer code exemplars (full ViewModel + navigation graph) into a references/ file and link from SKILL.md so the overview stays lean and progressive_disclosure can reach 5.

Tighten incidental commentary inside code blocks (e.g. remove 'Stateless composable — easy to preview and test') to push conciseness to 5.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean — brief lead-ins followed by code, assuming Compose competence — with only minor instances of over-explanation (e.g. "Stateless composable — easy to preview and test" comments) that could be trimmed.	4 / 5
Actionability	It provides fully executable, copy-paste-ready Kotlin patterns covering the common cases (ViewModel+StateFlow, collectAsStateWithLifecycle, type-safe navigation, slot APIs, expect/actual, @Stable, derivedStateOf, dynamic theming), with BAD/GOOD contrasts for recomposition pitfalls.	5 / 5
Workflow Clarity	As a patterns catalog rather than a procedural skill, it has no multi-step process to sequence and no validation checkpoints; content is well-organized by topic but lacks an explicit ordered workflow with feedback loops.	3 / 5
Progressive Disclosure	Good structure with clear section headers and one-level-deep, clearly signaled references to sibling skills (android-clean-architecture, kotlin-coroutines-flows); no bundle files exist, so all content is inline, which is reasonable at this size but leaves minor organization gaps.	4 / 5
	Total	16 / 20 Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-structured description that concretely states both capabilities and explicit activation triggers in third-person voice. It is comprehensive on completeness and only slightly shy of top marks on specificity, trigger synonyms, and distinctiveness.

Dimension	Reasoning	Score
Specificity	Names the domain and lists several specific capability areas — "state management, navigation, theming, performance, and platform-specific UI" — giving broad coverage, though these are pattern categories rather than discrete concrete actions, leaving minor gaps versus a fully comprehensive action list.	4 / 5
Completeness	It explicitly answers both what ("Compose Multiplatform and Jetpack Compose patterns for KMP projects — state management, navigation, theming, performance, and platform-specific UI") and when ("Use when building Compose or Jetpack Compose UI, state, navigation, or theming in a KMP project") with concrete trigger phrases.	5 / 5
Trigger Term Quality	"Use when building Compose or Jetpack Compose UI, state, navigation, or theming in a KMP project" surfaces natural terms a user would say (Compose, Jetpack Compose, UI, state, navigation, theming, KMP), but a few common synonyms (recomposition, composables, desktop/web) are absent.	4 / 5
Distinctiveness Conflict Risk	The Compose Multiplatform / KMP UI framing carves a clear niche with distinct triggers and minimal conflict risk, with only minor overlap potential against a generic Android-Jetpack-Compose skill.	4 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: skills/compose-multiplatform-patterns/SKILL.md
Commit: 06c5e11

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.