Menu
Client legal-safety review for domains, diagnostics targets, probes, workflows, and jurisdiction risk.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
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.
| name | client-legal-safety |
| description | Client legal-safety review for domains, diagnostics targets, probes, workflows, and jurisdiction risk. |
Conservative review workflow for what an end user may be exposed to by running the app, enabling a feature, or executing built-in diagnostics.
This is a current-law task. Always verify with live sources before concluding that a host or workflow is safe enough to ship.
Prefer primary or official sources:
publication.pravo.gov.rugenproc.gov.ru, rkn.gov.ru, etc.)consultant.ru, garant.ru) when needed for the
current text of a lawUse secondary reporting only to locate a designation or enforcement event, then confirm with a primary or official source where possible.
safesensitiveunsafeneeds_local_counselunsafe for
client reachability probing.sensitive; move to unsafe when current law or current enforcement makes
client access materially risky.needs_local_counsel.Return a compact matrix with:
If code changes are requested, update all of the following together: