Menu
Plan or review Flutter Navivox Telegram-like UI. Use for chat thread chrome, bubbles, composer, contacts, action sheets, voice affordances, or Telegram clone references.
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
| name | navivox-telegram-ui |
| description | Plan or review Flutter Navivox Telegram-like UI. Use for chat thread chrome, bubbles, composer, contacts, action sheets, voice affordances, or Telegram clone references. |
Make the Navivox Flutter app feel Telegram-like while keeping it Gormes-owned. Borrow navigation density, bubble rhythm, composer behavior, sheets, and contact-list scanning; do not import Telegram network assumptions, TDLib, MTProto, Telegram credentials, or consumer-messenger scope unless a future row explicitly authorizes it.
Do not use this for Gormes backend provider/runtime work unless UI changes require a typed Navivox API contract; then route backend work through gormes-tdd-slice or gormes-interface-designer.
The Navivox Flutter app is now a sibling repo, not an in-repo flutter-navivox/ tree.
/home/xel/git/gormes/navivox-apptest -d /home/xel/git/gormes/navivox-app and then cd /home/xel/git/gormes/navivox-app.flutter-navivox/app, ../navivox-app/app, or /home/xel/git/sages-openclaw/workspace-mineru/navivox-app/app; treat those as old evidence. For new work and tests, use the sibling repo path above.gormes-agent and Flutter implementation edits in navivox-app unless Juan explicitly scopes both repos.Treat references as design evidence, not dependencies.
Official Telegram repos to study for behavior patterns:
https://github.com/DrKLO/Telegramhttps://github.com/TelegramMessenger/Telegram-iOShttps://github.com/TelegramMessenger/Telegram-X-Androidhttps://github.com/telegramdesktop/tdesktophttps://github.com/morethanwords/twebhttps://github.com/tdlib/tdFlutter/community references to verify before adoption:
telware_cross_platformtelega2birukbr7telegram_ios_ui_kittele_web_appv_chat_bubblesBefore adding any package or copying an implementation, verify: source URL, license, maintenance status, platform support, API ownership, accessibility, and whether it introduces TDLib/API credential requirements. If not verified, use it only as visual inspiration.
| Telegram pattern | Navivox translation |
|---|---|
| Chat list | Profile contact list keyed by server_id + profile_id, with active-turn typing… state and Telegram-like search/filter |
| Chats bottom tab | Contact list may have top-level app nav; chat thread should not show bottom nav |
| Message bubbles | User right, assistant left, grouped tails, compact timestamps, assistant typing/streaming indicator |
| Read ticks | Local send/queued/streaming/done/error status, not read receipts |
| Attachment button | Telegram-style share tray for upload file, media, workspace file, approvals, tools, workspace/config, future files |
| Emoji/composer | Quick emoji strip inserts into the message field without leaving chat |
| Voice message | Device transcript bubble, explicit STT unavailable state, TTS/read-aloud action, tappable continuous voice banner, and voice control sheet |
| Long press | Selectable text, copy, forward to another profile/contact, retry, inspect event/tool, reveal redacted fields only when allowed |
| Telegram backend | Never: Navivox talks to Gormes gateway only |
Scope the surface
/home/xel/git/gormes/navivox-app for Flutter UI changes unless docs/tests require Gormes repo updates.Write/adjust widget tests first
flutter_test for shell and widget behavior.NavigationBar; contact list still has one.Keep chat immersive
Prefer small local widgets
SimpleChatAdapter; improve it incrementally.NavivoxChannel; UI widgets should not infer backend state from raw config.Validate
cd /home/xel/git/gormes/navivox-app && flutter test test/shared/app_shell_test.dartcd /home/xel/git/gormes/navivox-app && flutter testgormes-git before push.| Mistake | Fix |
|---|---|
| Adding Telegram/TDLib dependencies for UI polish | Use visual patterns only; Navivox backend is Gormes gateway. |
| Leaving bottom app nav inside mobile chat thread | Hide top-level nav on /chats/<server>/<profile> routes. |
| Treating Gormes profiles as Telegram accounts | Profiles are Gormes homes/config/runtime scopes. |
| Copying clone code without license/maintenance proof | Verify first; otherwise write local Flutter widgets. |
| Hiding broken STT/TTS controls | Keep voice controls visible with clear unavailable states, continuous voice status, and settings guidance. |
| Making UI pretty without tests | Add widget tests for the visible contract. |
Implement one selected repo-scoped Gormes row with tests. Use when next-work says decision=build. Do not use for decision=plan, broad parity audits, or untracked feature ideas.
Shape source-backed Gormes progress rows. Use for decision=plan builder handoffs, row splitting, feature maps, or parity planning. Do not use when decision=build or for runtime code.
Route Gormes work to the smallest repo-local skill chain. Use before substantial planning/building/refactor work, when unsure which Gormes skill applies, or when creating/improving repo-local skills.
Build one selected Gormes behavior with red-green-refactor. Use when the row or reproduced bug defines a test target. Do not use after decision=plan or for broad planning.
Move one bounded cmd/gormes command domain out of root files toward root main.go only. Use when thinning cmd/gormes, burning down loose root files, preserving CLI behavior, or catching refactor regressions during cmd moves.
Use when an agent is unfamiliar with a Gormes code area, a change crosses package boundaries, or a refactor needs a source-backed module map before edits.