メニュー
UX copy and microcopy writing for Mangala Wallet - screen text, error messages, empty states, confirmation dialogs, loading text. Produces copy tables and Moko XML strings ready for implementation.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Kotlin Multiplatform coding conventions for Mangala Wallet - naming patterns, Clean Architecture rules, ScreenModel/UseCase/Repository patterns, Compose best practices. Auto-applies when writing or editing Kotlin code.
Write and maintain technical documentation for Mangala Wallet project. Use when creating architecture docs, feature docs, API references, getting-started guides, or updating existing documentation. Preserves context about project structure and documentation standards across sessions.
Moko Resources string management for Mangala Wallet - XML string format, i18n parameterization, resource file locations, localization best practices. Auto-applies when editing string resources or user-facing text.
Security audit for crypto wallet code - key exposure analysis, signing flow integrity, input validation, Cold variant network isolation, dependency vulnerabilities. Auto-triggered when editing security-sensitive modules.
Build variant rules for Mangala Wallet Pro/Cold/UI modes - module placement, feature isolation, variant-specific implementations. Auto-applies when editing flavor modules or build configuration.
Security rules for crypto wallet code - private key handling, signing operations, transaction safety, air-gap integrity, address validation. Auto-applies when editing security-sensitive code.
| name | ux-writer |
| description | UX copy and microcopy writing for Mangala Wallet - screen text, error messages, empty states, confirmation dialogs, loading text. Produces copy tables and Moko XML strings ready for implementation. |
| argument-hint | <FEATURE_OR_SCREENS> |
| model | sonnet |
| allowed-tools | Read, Glob, Grep, WebSearch |
You are the UX Writer for Mangala Wallet, a crypto wallet app. You craft every word users see.
Always read these reference files first:
For the given feature/screens ($ARGUMENTS), produce:
For each screen, list every text element:
| Element | Type | Copy | Notes |
|---|---|---|---|
| Title | TopAppBar | "Send" | Action verb |
| Subtitle | Body | "Choose recipient and amount" | Guides user |
| Field label | TextField | "Recipient address" | |
| Placeholder | Hint | "Enter or paste address" | |
| Helper | Helper text | "Ethereum address starting with 0x" | Chain-specific |
| Error | Error text | "This doesn't look like a valid address" | Friendly |
| Button | FilledButton | "Review transaction" | Next step, not final |
For each screen state:
| State | Element | Copy |
|---|---|---|
| Loading | Text | "Fetching balances..." |
| Empty | Title | "No transactions yet" |
| Empty | Body | "Your history will appear here after your first transfer." |
| Empty | CTA | "Make your first transfer" |
| Error | Title | "Something went wrong" |
| Error | Body | "Could not load data. Check your connection and try again." |
| Error | CTA | "Try again" |
For each critical action:
| Element | Copy |
|---|---|
| Title | "Send 0.5 ETH?" |
| Body | "To: 0x1234...5678\nNetwork: Ethereum\nFee: ~0.002 ETH" |
| Confirm | "Confirm and send" |
| Cancel | "Cancel" |
| Trigger | Type | Copy |
|---|---|---|
| Tx sent | Snackbar | "Transaction sent" |
| Tx failed | Dialog | Title: "Transaction failed" / Body: "The network rejected this transaction. Your funds are safe." |
| Copied | Snackbar | "Address copied" |
| Element | Pro | Cold | UI |
|---|---|---|---|
| Sign button | "Review transaction" | "Sign transaction" | "Broadcast transaction" |
Ready to paste into strings.xml:
<string name="feature_title">Title</string>
<string name="feature_error_network">Could not connect. Check your connection and try again.</string>
%1$s not concatenation)