Skip to content

JetBrains/intellij-community / .claude/skills/compose-ui

compose-ui

Verified

Write or audit Compose Desktop UI state, effects, and boundaries.

FileKindSize
OWNERSHIPother20 B
SKILL.mdskill md637 B
architecture/GUIDE.mdmarkdown5.7 KB
architecture/evals/evals.jsonconfig6.5 KB
architecture/references/animation.mdmarkdown11.3 KB
architecture/references/component-api-lists-performance.mdmarkdown4.1 KB
architecture/references/desktop-seams-review-output.mdmarkdown1.5 KB
architecture/references/effects.mdmarkdown1.7 KB
architecture/references/state-boundaries.mdmarkdown5.4 KB
architecture/skill-source.jsonconfig2.0 KB
audit/GUIDE.mdmarkdown14.1 KB
audit/evals/evals.jsonconfig18.1 KB
audit/references/api-hygiene.mdmarkdown8.8 KB
audit/references/audit-search-patterns.mdmarkdown3.9 KB
audit/references/boundary-violations.mdmarkdown3.3 KB
audit/references/effects/derived-state-of-guide.mdmarkdown2.2 KB
audit/references/effects/effect-selection-guide.mdmarkdown2.7 KB
audit/references/effects/infinite-loop-patterns.mdmarkdown2.6 KB
audit/references/effects/overview.mdmarkdown7.7 KB
audit/references/lazy-layouts/animate-item.mdmarkdown2.0 KB
audit/references/lazy-layouts/cache-window-and-prefetch.mdmarkdown3.2 KB
audit/references/lazy-layouts/desktop-scroll-measurement.mdmarkdown2.0 KB
audit/references/lazy-layouts/keys-and-content-type.mdmarkdown2.2 KB
audit/references/lazy-layouts/nested-lazy-layouts.mdmarkdown1.6 KB
audit/references/lazy-layouts/overview.mdmarkdown7.5 KB
audit/references/measurement/benchmarking-methodology.mdmarkdown1.9 KB
audit/references/measurement/overview.mdmarkdown5.5 KB
audit/references/measurement/profiler-setup.mdmarkdown2.5 KB
audit/references/modifiers/custom-modifier-node.mdmarkdown3.4 KB
audit/references/modifiers/modifier-order.mdmarkdown2.1 KB
audit/references/modifiers/overview.mdmarkdown7.4 KB
audit/references/modifiers/phase-deferral.mdmarkdown2.6 KB
audit/references/reporting-guidance.mdmarkdown2.3 KB
audit/references/stability/ci-stability-gate.mdmarkdown2.0 KB
audit/references/stability/desktop-measurement.mdmarkdown2.2 KB
audit/references/stability/overview.mdmarkdown7.6 KB
audit/references/stability/reading-classes-txt.mdmarkdown2.1 KB
audit/references/stability/reading-composables-txt.mdmarkdown1.9 KB
audit/references/stability/stabilising-types.mdmarkdown3.1 KB
audit/references/stability/stability-config-syntax.mdmarkdown1.6 KB
audit/references/stability/stability-inference-algorithm.mdmarkdown3.4 KB
audit/references/stability/strong-skipping-escape-hatches.mdmarkdown2.6 KB
audit/references/subcomposition/desktop-subcomposition-measurement.mdmarkdown1.7 KB
audit/references/subcomposition/overview.mdmarkdown7.2 KB
audit/references/subcomposition/subcomposition-decision-tree.mdmarkdown1.8 KB
audit/references/subcomposition/swing-panel-subcomposition.mdmarkdown1.8 KB
audit/references/tracing-setup.mdmarkdown5.3 KB
audit/references/tracing-usage.mdmarkdown6.3 KB
audit/skill-source.jsonconfig2.5 KB

audit/references/boundary-violations.md

View on GitHub
# Boundary Violations — IO and Computation in Composition

This document describes the two most critical categories of boundary violation: IO in composition
and inline data work in composition. Both belong in the presenter/state-holder, never in a
composable body.

## Strictly forbidden: IO in composition

The following must **never** appear in a composable body, regardless of how they are wrapped
(even inside `remember { }` — see note below):

**Serialisation / deserialisation**

- JSON (Kotlinx, Gson, Moshi, Jackson/ObjectMapper)
- XML, Protobuf, CSV, or any format parsing/encoding

**Network access**

- HTTP calls (`HttpClient`, `OkHttp`, `Retrofit`, `URL(...)`)
- WebSocket sends, DNS lookups, socket operations

**Database**

- Database calls include SQLite, Room, Exposed, or any raw JDBC/DriverManager call.
- `prepareStatement`, `executeQuery`

**File system**

- `File(...)`, `Files.*`, `FileInputStream`, `BufferedReader`, directory listings
- Any `java.io` or `java.nio` call

**Subprocess / process I/O**

- `ProcessBuilder`, `Runtime.exec()`, RPC stdin/stdout pipes

**Exception:** Image loading delegated to a threading-aware library (Coil, Glide) via their
Compose integration APIs is fine — they manage the threading contract.

### Why `remember { }` does not fix this

`remember { }` still runs on the composition thread on first composition and whenever its key
changes. Calling `remember { File(...).readText() }` blocks the UI thread on every cold start and
key change. Move the work to the presenter or state-holder so it runs off the hot path before
composition.

## Inline data work — apply common sense

O(N) complexity is a reliable red flag, and nominally O(1) operations can still be expensive when they perform object
allocation, hashing, synchronisation, or any side-effectful initialisation.

### Always flag (O(N) or worse)

| Category | Examples |
|----------|---------|
| Text scanning | `lineSequence().count()`, `split("\n").size`, `lines().count()` |
| String transforms | `.replace(…)`, `.trimIndent()`, `.format(…)` — allocate proportional to input |
| Collection traversals | `.filter { }`, `.sortedBy { }`, `.groupBy { }`, `.sumOf { }`, `.maxOf { }` |
| Regex inline | `Regex(…)` constructed or executed in composition — compiles pattern every recompose |

### Flag with judgement (nominally O(1) but potentially expensive)

- Factory calls or constructors that do meaningful initialisation work, acquire locks, or touch
  global state.
- `hashCode()` on complex objects.
- `joinToString`, `mapIndexed`, `flatMap`, `associate` on large collections.

### Safe in composition

Simple field reads, comparisons, boolean checks, and property access on already-computed values.
Normal small allocations (data class instances, small literals) are fine.

## Fix pattern

Move the work to the presenter or state-holder:

```kotlin
// WRONG — file read in composition
@Composable
fun LogViewer() {
    val lines = remember { File(logPath).readLines() } // blocks composition thread
    LazyColumn { items(lines) { Text(it) } }
}

// RIGHT — file read in presenter
class LogPresenter {
    val lines: StateFlow<List<String>> = flow {
        emit(File(logPath).readLines())
    }.stateIn(scope, SharingStarted.Lazily, emptyList())
}

@Composable
fun LogViewer(lines: List<String>) {
    LazyColumn { items(lines) { Text(it) } }
}
```
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall