🧠
AI EngineeringShell

Using Strong Skipping Correctly

by skydoves

Using Strong Skipping Correctly is an AI Engineering skill for Claude Code, published by skydoves in compose-performance-skills.

492 stars17 forkson skydoves/compose-performance-skillsAdded 2026/08/26+1% in starsRepository updated 2026/06/16
agent-skillsandroidclaudeclaude-codecomposecompose-performancejetpack-composekotlinllm-toolsrecompositionskydoves
Install in seconds
Install Using Strong Skipping Correctly
Copy Using Strong Skipping Correctly into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.
terminal
npx degit https://github.com/skydoves/compose-performance-skills/tree/main/recomposition/using-strong-skipping-correctly ~/.claude/skills/using-strong-skipping-correctly

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/skydoves/compose-performance-skills.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file
recomposition/using-strong-skipping-correctly/SKILL.md in skydoves/compose-performance-skills
Installs to
~/.claude/skills/using-strong-skipping-correctly
Collection
One of 25 skills cataloged from this repository
Category
AI Engineering2451 skills

What Using Strong Skipping Correctly does

Using Strong Skipping Correctly explains Compose Strong Skipping Mode, including how skippability changes, when lambdas are auto-remembered, and when to use escape hatches like @DontMemoize or @NonSkippableComposable. It helps verify the mode is active and audit recomposition behavior during migration or debugging.

Using Strong Skipping Correctly is cataloged under AI Engineering on DirSkills. Using Strong Skipping Correctly comes from a repository tagged agent-skills, android, claude, claude-code and compose.

Documentation

README

Using Strong Skipping Correctly — make every restartable composable skippable, intentionally

Strong Skipping Mode is the Compose compiler behavior that became the default with the Kotlin Compose compiler plugin shipped in Kotlin 2.0.20. It changes two things at once: every restartable composable becomes skippable regardless of param stability (unstable params are compared with ===, stable params with equals), and every capturing lambda literal written inside a @Composable function is automatically wrapped in remember(captures) { ... }. Both behaviors are on by default; neither requires opt-in flags on Kotlin 2.0.20+. Lambdas with no captures are already compiler-emitted singletons and are NOT wrapped — only capturing lambdas need (and get) the auto-remember treatment.

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Using Strong Skipping Correctly

  • What else does skydoves publish alongside Using Strong Skipping Correctly?

    Using Strong Skipping Correctly is one of 25 skills that DirSkills catalogs from skydoves/compose-performance-skills, the repository it ships in. Its siblings there include Auditing Compose Performance, Avoiding Subcomposition Pitfalls and Choosing DerivedStateOf. Each one is a separate skill with its own page in this directory, installs the same way Using Strong Skipping Correctly does, and is maintained by skydoves in that same repository. The rest of the collection is listed on the skydoves/compose-performance-skills page.

  • How does Using Strong Skipping Correctly compare to other AI Engineering skills?

    Using Strong Skipping Correctly ranks #2183 by stars among the 2451 AI Engineering skills in this catalog. The most-starred ones next to it are Architecture Decision Records, AI-First Engineering and Agentic OS. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Using Strong Skipping Correctly against them. Open each page to compare what they document and how they install.

More from skydoves/compose-performance-skills

Using Strong Skipping Correctly is one of 25 skills cataloged on DirSkills from skydoves/compose-performance-skills.

See all 25 skills
🔍
5d ago

Auditing Compose Performance

Auditing Compose Performance runs a Measure → Diagnose → Fix → Verify workflow for broad Jetpack Compose slowdowns. Use it for perf audits, sprint kickoffs, and written reports when you need baseline metrics, causes, fixes, and verification.
Quality
49217
🧩
5d ago

Avoiding Subcomposition Pitfalls

Avoiding Subcomposition Pitfalls explains when SubcomposeLayout, BoxWithConstraints, or Scaffold cause repeated measure-phase composition in Jetpack Compose. Use it to replace unnecessary subcomposition with cheaper layout primitives or tune it when subcomposition is required.
Frontend
49217
🧩
5d ago

Choosing DerivedStateOf

Choosing DerivedStateOf helps decide when Jetpack Compose derivedStateOf reduces recompositions and when it is just overhead. It covers input-vs-output frequency, required remember wrapping, stale captures, and snapshotFlow for one-shot side effects.
Frontend
49217
🌊
5d ago

Collecting Flows Safely

Collecting Flows Safely helps migrate Compose screens from collectAsState() to collectAsStateWithLifecycle() and tame high-frequency flows with conflate(), distinctUntilChanged(), and snapshotFlow. Use it when background collection, unstable Flow parameters, or chatty streams are causing wasted work or extra recompositions.
Quality
49217
📜
5d ago

Configuring Lazy Prefetch

Configuring Lazy Prefetch tunes Jetpack Compose lazy-layout cache windows and nested prefetch for heavy scrolling. Use it when dropped frames come from composition work, especially with LazyLayoutCacheWindow or inner lazy layouts.
Frontend
49217
🛠️
5d ago

Configuring R8 For Compose

Configuring R8 For Compose explains how to set up minification for a Jetpack Compose app with R8 full mode, resource shrinking, and minimal keep rules. Use it when enabling release shrinking, fixing missing keeps, or checking why Compose does not need blanket keep rules.
DevOps
49217