fmess-chat-check — Claude Code skill for chat checks
fmess-chat-check — a Claude Code skill that checks how chats render in the fMess app. It runs before shipping CSS or page-script changes that affect messages or chat styling.
MIT ★ 122 updated 2026-11-15
npx skills add toanbku/fmess --skill fmess-chat-check -a claude-codeWhat fmess-chat-check does
The skill checks chats in the installed fMess app and evaluates screenshots. It covers discovered chat types and Messenger themes in light and dark modes, including messages, quotes, emoji-only messages, and toasts. Checks include bubble visibility and text contrast, plus quote bars and toast close buttons.
On macOS, build the debug app first with npx tauri build --debug --bundles app. The tests/app/chat-check.sh script quits the running fMess app, runs a probe, then opens the app again. It saves results, images, and result.json to the output directory; chat content that wasn’t found is flagged for a manual check. Animations, zoom, and the fast-scroll flash still need manual testing.
What it helps with
- check message bubble visibility and text contrast
- catch unreadable quote text or quote bars
- compare chat themes in light and dark modes
- detect toasts with unreadable text or a hidden close button
Example prompts for the agent
- Check chat rendering in fMess before I ship these CSS changes.
- Run the fMess chat check after changes to the page script.
- Test how this theme renders quotes and toasts in fMess.
How to install fmess-chat-check
1Skills CLI (Vercel)
npx skills add toanbku/fmess --skill fmess-chat-check -a claude-code2Manually: put the files in place
~/.claude/skills/fmess-chat-check/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/fmess-chat-check/
1Skills CLI (Vercel)
npx skills add toanbku/fmess --skill fmess-chat-check -a codex2Manually: put the files in place
.agents/skills/fmess-chat-check/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add toanbku/fmess --skill fmess-chat-check -a cursor2Manually: put the files in place
.cursor/skills/fmess-chat-check/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install toanbku/fmess .claude/skills/fmess-chat-check2Manually: put the files in place
.github/skills/fmess-chat-check/SKILL.md1Skills CLI (Vercel)
npx skills add toanbku/fmess --skill fmess-chat-check -a gemini-cli2Platform CLI
gemini skills install https://github.com/toanbku/fmess --path .claude/skills/fmess-chat-checkManually: put the files in place
.devin/skills/fmess-chat-check/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about fmess-chat-check
How do I install fmess-chat-check in Claude Code?
Run npx skills add toanbku/fmess --skill fmess-chat-check -a claude-code. The skill is installed at ~/.claude/skills/fmess-chat-check/SKILL.md.
What does fmess-chat-check do?
It checks screenshots of chats in fMess, including message bubbles, quotes, emoji-only messages, and toasts across chat themes and display modes.
What does fmess-chat-check need to run?
It needs macOS and the fMess app. Build the debug app first with npx tauri build --debug --bundles app.
Source text
SKILL.md · MIT
---
name: fmess-chat-check
description: Check how chats look in the real fMess app before a change to the page script or a theme ships. Run it for any CSS or inject change that can touch messages, bubbles, quotes, the chat's background or colours (0.1.31 shipped bare bubbles because one chat kind was never looked at).
---
# Chat check
`tests/app/chat-check.sh [output dir] [max chats]` (macOS, debug build:
`npx tauri build --debug --bundles app` first). It quits the running fMess,
runs `tests/app/chat-check.js` as a probe, and opens the installed fMess again.
## What it covers
For one read chat of each kind found in the list, with each Messenger chat
theme found:
| Dimension | Values |
|---|---|
| Chat | encrypted (e2ee), not encrypted, group |
| Messenger chat theme | default, gradient, colour (and wallpaper) |
| fMess look | Messenger, Zalo, WhatsApp, Teams, and any other theme in `src-tauri/themes/` (CSS put in the page, nothing saved) |
| Mode | light, dark (Messenger's own setting, put back at the end) |
| Messages | text bubbles (yours, theirs), quotes, emoji-only ("icons") |
| Toasts | one of Facebook's own (`cometPushToast`) per look and mode, as a chat named `toast` |
It scrolls back up to 8 screens for a screen with a quote or an emoji message.
Notes at the end say what wasn't found (e.g. no emoji message): look for one
by hand then.
## What it checks (on the picture's pixels)
- a bubble is visible: beside its text differs from just outside it
- its text reads: contrast ≥ 2.5 (Messenger's own white on #0099FF is ~3)
- a quote's text (≥ 2) and bar (≥ 1.25) read on the bubble
- an emoji-only message has no bubble behind it
- `box gradient` per chat: whether the chat box still paints the theme's
gradient (the fast-scroll flash, #27, comes from it)
- a toast's text reads (≥ 3) and its close button's cross shows on its face
(≥ 2). Facebook draws toasts the other way round from the page, so a theme's
page colours leaking into them gave white on white (0.1.33, dark mode, all
three themes). A toast that never showed fails (`no toast showed`, with
whether the page was hidden: keep the window in view while it runs)
Skipped on purpose: text in links (shared posts) and buttons (the message a
reply quotes), see-through bubbles Messenger dims, bubbles drawn as a border
only (unsent messages), anything covered (pinned message, a theme's card).
## Reading the result
`PASSED`/`FAILED` and one line per problem; `result.json` and the pictures in
the output dir, plus `sheet-<chat>.png` per chat: Messenger, Zalo, WhatsApp,
Teams across, light above dark. Look at the sheets even when it passes.
Before trusting a new check, run it on a known-bad build (it must fail) and a
known-good one (it must pass).
## Still by hand
The fast-scroll flash, hover cards, pinch/zoom, anything animated: ask anh
to try it in the debug build (a recorder probe helps, see fmess-fast-iteration
in memory).
For what happens when the computer sleeps, the network drops, the encrypted
chats' worker dies or a notification rings, and for whether the search field
can be typed in and text selected (focus-check.sh), see the fmess-live-check
skill. A check that clicks or types should use real events (probe.rs,
`window.__fmessInputRequest`), described there.
© toanbku · MIT · toanbku/fmess