SlayTheAmethystModded

Apply pragmatic Jetpack Compose implementation patterns for Android UI code, including state hoisting, unidirectional data flow, side effects, navigation boundaries, modifiers, theming, previews, accessibility, and testable composable structure. Use when asked to build, refactor, review, or explain Compose screens and components.

Design and review Android mobile frontend experiences with pragmatic attention to touch ergonomics, adaptive layouts, accessibility, state handling, and implementation handoff. Use when asked to design Android screens, improve mobile UI/UX, critique frontend flows, or translate product requirements into Android-ready interface guidance.

Audit Jetpack Compose performance by inspecting recomposition risk, state reads, stability, lazy layout keys, effects, derived state, allocation hotspots, and measurement evidence. Use when asked to diagnose slow Compose screens, review Compose code for performance issues, or propose targeted optimizations with verification steps.

Analyze SlayTheAmethyst feedback report bundles such as `sts-feedback-report-*.zip` or extracted `sts/` directories by prioritizing `sts/feedback/issue_body.md` and `request.json`, then `sts/jvm_logs/latest.log`, archived `jvm_log_*.log`, `launcher_settings.txt`, logcat, and optional crash artifacts to diagnose whether a problem is caused by the launcher, a mod, or the device/driver. Use when Codex needs to inspect a feedback package, interpret the project's diagnostics files, or write a concrete evidence-backed diagnosis and next step.