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.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Read README.md in this skill first — it covers the register, content
fundamentals, visual foundations, and iconography that the rest depends on.
Then open the other files as you need them.
README.md — the contract. Read first.colors_and_type.css — every token as a CSS custom property + @font-face
declarations for Geist Sans / Mono / Pixel Circle. Use this directly in
HTML artifacts.fonts/ — TTF files referenced by colors_and_type.css.assets/icons/ — the 6 brand-ship outline icons (SVG, 24×24) and the 6
brand-mark variants (clean / cracked / disintegrate / glitch / rubble /
stitch).assets/raw/ — Android vector drawable XML originals (kept for parity).preview/ — atomic design-system cards. Useful as references but not
meant to be linked from production HTML.ui_kits/android/ — the production UI kit. JSX recreations of every
public composable, wired into a 6-screen click-through. Read
RipDpiComponents.jsx to see the API; read index.html to see screens
composed.colors_and_type.css + fonts/ + any icons you need out of this
skill into the artifact folder.colors_and_type.css from your HTML and consume the tokens via
var(--rdp-…). Don't inline raw hex, raw px, or new font sizes.ui_kits/android/RipDpiComponents.jsx
into the artifact and import it. It self-contains everything: a theme
provider, every Compose-analog component, and the RDP token bundle.README.md for the rules.app/src/main/kotlin/com/poyka/ripdpi/ui/theme/
(in the user's codebase, not this skill) as authoritative. The CSS in
this skill is a mirror, not the contract.RipDpiExtendedColors, RipDpiTextStyles, RipDpiShapeMetrics,
RipDpi*Metrics, RipDpi*StateTokens, RipDpiSurfaceRoleMappings),
never by inlining a raw value.Ask the user what they want to build or design. Useful questions:
RipDpi* components, or is this a new
component that needs to plug into RipDpiThemeTokens?Then act as an expert designer who outputs HTML artifacts or production Compose code, depending on the need.
Connect not Tap to connect now.まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
RIPDPI's own Compose conventions: ViewModel pattern, Route/Screen split, DataStore->StateFlow, RipDpiThemeTokens. Use for how this app does Compose, not generic Compose API questions (see compose).
日本語の概要は準備中です。原文の説明を表示しています。
ADB-based RIPDPI device/emulator debugging: build/install/launch, logcat filtering, fixture port-forwarding, instrumented tests, crash/ANR triage. Use when debugging on a real device or emulator.
日本語の概要は準備中です。原文の説明を表示しています。
RIPDPI Appium launch-contract reference: start routes and permission/service/data presets. Use when a test launches to the wrong screen or a new automation route is added. General flakiness: appium-test-debug.
日本語の概要は準備中です。原文の説明を表示しています。
RIPDPI Appium test authoring: page objects, resource-id locators, assertions, wait tiers. Use when writing a new Appium test or page object, or adding coverage for a new screen.
日本語の概要は準備中です。原文の説明を表示しています。
RIPDPI Appium failure triage: flaky tests, locator/session/wait issues, screenshot and element-tree debugging. Use when an Appium test fails or is flaky.
日本語の概要は準備中です。原文の説明を表示しています。
Add or modify a GitHub Actions job. Use when editing a file under .github/workflows/. Not for running a workflow locally (local-ci-act) or release signing (release-signing).
日本語の概要は準備中です。原文の説明を表示しています。