RIPDPI

Use this skill to generate well-branded interfaces and assets for RIPDPI (an Android-native, Compose-first VPN and DPI-bypass app), either for production or throwaway prototypes/mocks/etc. Contains essential design guidelines, colors, type, fonts, brand-ship icons, and an interactive UI kit of every public composable from the live ui/components tree.

Use when managing the Rust workspace, adding/removing crates, editing workspace dependencies, running cargo nextest/audit/deny, configuring Cargo profiles for Android cross-compilation, debugging Cargo.lock churn, migrating crate edition, or wiring Gradle to cargo via the ripdpi.android.rust-native plugin.

Use when modifying the diagnostics scan pipeline, ScanRequest/ScanReport types, ProbeTask families, ripdpi-monitor-engine / ripdpi-diagnostics-* crates, strategy-probe candidates, the diagnostics catalog (packs/profiles), wire-schema contracts between Rust and Kotlin, DIAGNOSTICS_ENGINE_SCHEMA_VERSION, golden contract tests, or adding a new probe type / profile. Triggers on diagnostics scans, strategy probes, automatic audit, dpi-detector profiles, or anything in core/diagnostics or native/rust/crates/ripdpi-monitor-*.

Android-specific Rust build, verification, and packaging — per-target 16 KiB page alignment, size-optimized release profile, ELF symbol allowlist, .so size budgets, NDK 29 specifics. Use when modifying .cargo/config.toml for Android targets, the workspace [profile.release] / [profile.android-jni] block, or when verifying a built .so before release.

Telemetry and observability discipline for the RIPDPI Android Rust stack — control-plane vs data-plane logging, bounded flume event queues, atomic counters, snapshot polling, readiness callbacks, and deterministic JSON contracts. Use when authoring or modifying telemetry emission code, the bounded event ring, the Kotlin-side telemetry consumer, or any per-packet logging.

Custom detekt rules, DI/privacy/suppression guardrails, detekt.yml configuration, and false-positive triage.

Edge-to-edge and window-inset handling for Compose screens, scaffolds, sheets, and system bars.

Gradle dependencies, modules, convention plugins, and Android build failure triage.

R8 and ProGuard keep rules for serializable routes, JNI bindings, protobufs, and minification.

Use when authoring or reviewing async Rust that may run inside tokio::select! / tokio::time::timeout / FuturesUnordered, bridging JNI to async (block_on from JNI thread), configuring tokio runtime for Android NDK, designing CancellationToken parent/child trees, handling broadcast::Lagged, choosing spawn_blocking vs std::thread::spawn, or auditing for std::sync::Mutex-across-await deadlocks. Triggers on "select", "join", "spawn", "cancellation", "tokio runtime", "block_on", "async fn", "tokio-console", or async-related test/runtime questions.

io_loop, smoltcp/Tokio bridge, manual polling, tunnel sessions, io_uring buffers, and stalls.

Rust panic safety, JNI boundaries, Java exceptions, typed errors, unwrap audits, and catch_unwind.

Use when adding or reviewing any unsafe Rust block, FFI/JNI export, raw-pointer arithmetic, transmute, ManuallyDrop, mem::zeroed, ioctl call, union access, manual unsafe impl Send/Sync, Box::leak, JString::from_raw, EnvUnowned::from_raw, or any change that removes

Jetpack Compose guidance and audit for RIPDPI — state, recomposition, modifiers, navigation, theming, performance, and scored quality reports.

Audit and improve the RIPDPI Android VPN/proxy/diagnostics application from a network-engineering perspective: VpnService, TUN-to-SOCKS, SOCKS5, Rust native data plane, DNS, TLS/QUIC strategy probing, relay transports, MTU, telemetry, privacy, reliability, and network tests. Trigger for RIPDPI app network reviews, protocol strategy reviews, or app-side VPN/proxy architecture work.

Gradle and Rust dependency updates, version catalogs, AGP/Kotlin/NDK bumps, and Renovate.

Golden fixtures, snapshot tests, blessing workflows, mismatch triage, and volatile-field scrubbing.

Local GitHub Actions checks with act and workflow wiring triage on macOS.

Use when writing or reviewing Rust atomic operations, lock-free data structures, AtomicBool publish/subscribe patterns, choosing between Ordering::Relaxed/Acquire/Release/SeqCst, or diagnosing data races on ARM64 Android. Triggers on memory-ordering questions, weakly-ordered concurrency, happens-before reasoning, and atomic fence placement.

Rust mutation testing with cargo-mutants, survived-mutant triage, and test adequacy fixes.

Native Rust profiling on Android and desktop with simpleperf, HWASan, and flamegraphs.

Protobuf compatibility, reserved fields, diagnostics wire contracts, schema versions, and goldens.

Android Rust builds, cross-compilation targets, and Gradle jniLibs integration.

Rust crate creation, workspace restructuring, dependency layering, and direction rules.

Use when investigating a native Rust crash in the RIPDPI Android app, decoding tombstones, symbolicating addresses with addr2line, setting up LLDB in Android Studio for the cdylib crates, diagnosing JNI panics, missing logcat output from Rust, RUST_BACKTRACE on Android, or async-Rust debugging via tracing spans. Triggers on "native crash", "JNI panic", "tombstone", "addr2line", "RUST_BACKTRACE", or "lldb-server".

Rust JNI functions, Kotlin bindings, jni crate usage, and raw JNI versus UniFFI choices.

Rust clippy, rustfmt, cargo-deny configuration, new lints, and lint failure triage.

Use when profiling native .so files on Android with simpleperf/Perfetto, generating host flamegraphs, measuring binary size with cargo-bloat, analyzing monomorphization bloat with cargo-llvm-lines, configuring LTO/codegen-units, tuning sccache for the 4-ABI build matrix, writing or reviewing Criterion microbenchmarks in ripdpi-bench, or investigating cross-compilation build-time regressions. Triggers on "flamegraph", "cargo-bloat", "binary size", "build time", "LTO", or any performance question.

Use when running AddressSanitizer/ThreadSanitizer/MemorySanitizer on Rust code, configuring Miri for unsafe-Rust UB detection (Stacked Borrows or Tree Borrows), stubbing FFI for Miri compatibility, enabling HWASan or MTE on Android 14+, interpreting tombstones tagged SEGV_MTEAERR/SEGV_MTESERR, or wiring sanitizers into CI. Triggers on "sanitizer", "miri", "ASan/TSan/HWASan/MTE", "undefined behavior", or memory-safety validation questions.

Use when auditing Rust dependencies with cargo-audit, configuring cargo-deny policies, triaging RUSTSEC advisories, evaluating a new crate for typosquat/supply-chain risk before adding it to Cargo.toml, responding to a published CVE on a pinned dep, or modifying native/rust/deny.toml. Triggers on "cargo audit", "cargo deny --locked", "RUSTSEC", "advisory", "supply chain", or new-dependency-addition reviews.

Dynamic check toolkit beyond cargo test --locked — cargo-careful (Miri fallback for FFI), loom (concurrency model checker), proptest (property tests), cargo-fuzz (libFuzzer), cargo-mutants (mutation testing). Use when authoring tests for unsafe code, custom atomics/locks, packet parsers, or before promoting an AI-generated module past basic test coverage.

Test-first workflow for features, bug fixes, refactors, and project-specific test patterns.

Use when modifying the MTProto WebSocket tunnel for Telegram in ripdpi-ws-tunnel, Telegram DC IP routing (149.154.* / 91.108.* etc.), MTProto obfuscated2 classification, kws*.web.telegram.org bootstrap and TLS handshake, choosing between rustls and BoringSSL backends, the AvoidsBlocked517ByteClientHello invariant, or the telegram_availability diagnostics probe. Triggers on "Telegram", "MTProto", "ws tunnel", "WsTunnelMode", "ClientHello fingerprint", or Telegram-DC routing questions.

Compose UI, ViewModels, navigation, state, and app-module theming.

Android device or emulator debugging, logs, instrumented tests, crashes, and network issues.

Appium launch contract, start routes, state presets, and wrong-screen test debugging.

Appium test authoring, page objects, locators, assertions, and new-screen coverage.

Appium failure triage for flaky tests, locators, waits, sessions, and stability.

GitHub Actions authoring for workflows, CI jobs, caches, artifacts, and failure triage.

Client legal-safety review for domains, diagnostics targets, probes, workflows, and jurisdiction risk.