preview-verification
Skill0 starsChanged 10 days agoMITView on GitHub
Use after changing a FluxNative app or landing page, or when the user asks how a FluxNative screen looks or behaves, why it is blank or why a button does nothing: build the preview, then look, tap and read logs in the live preview, and report only what that evidence shows.
In this repository9 other files it gives its agents.
- app-sample-contentSkill
- app-workflowSkill
- design-referencesSkill
- mobile-app-designSkill
- mobile-design-briefSkill
- mobile-deslopSkill
- mobile-screen-reviewSkill
- paywall-onboardingSkill
- supabase-rls-auditSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Not a substitute for run_checks: compile errors, lint and tests come from there.
- Very specific: line 14
Every tool here takes the project's id as project, the same id on every call.
- Distinctive: line 49
Never report a screen as working because the build compiled or a write succeeded.
- Distinctive: line 50
Never claim native behavior (purchases, push, camera, sensors) from the web preview.
- Distinctive: line 51
Never type real personal data, real passwords or real payment details into the preview.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Check a FluxNative project in the live preview
When to use
- You changed a screen, a flow or styling and need to see the result.
- The user reports something visible: a blank screen, a broken layout, a control that does nothing, wrong data.
- Not a substitute for
run_checks: compile errors, lint and tests come from there.
Every tool here takes the project's id as project, the same id on every call; find it with list_apps (the app-workflow skill).
What the preview is
FluxNative runs the project's committed source in a real headless browser. An app runs as its Expo web build inside a phone or tablet frame; a landing page runs as the built site. The preview shows layout, navigation, copy, state and network calls. It does not run native modules (camera, push, in-app purchases, biometrics, native maps). For those, say what the preview could not show; a web fallback is not proof.
The preview runs the real app: a tap or a submitted form can reach the app's connected backend and change its data. Use test input the user gave you.
Procedure
- Build.
build_previewcompiles the current source and returns diagnostics. Fix compile errors before looking at anything. - Reach the screen the way a user would.
preview_viewwithroute(for example/login) opens a route directly. For a flow, start from its entry screen and tap through it withpreview_act. A screen that only works when opened by URL is not reachable. - Read the structure, then look.
preview_viewwithmodeelements(the default) lists the interactive elements withrefids. It leaves out headings and plain text.preview_viewwithmodetextreturns the visible text: use it for copy, empty states and error messages.preview_viewwithfindlocates an element by its label or role and returns itsref.preview_viewwithmodescreenshotreturns an image, which costs vision tokens. Take one per state you need to judge visually, not one per step;regionzooms into one part. Hosts that render MCP Apps show the preview inline.preview_viewwithinspect(aname,reforcoordinate) says where an element is written and how it is styled;sourcesadds file and line to the tree. Use them to go from screen to code.
- Act.
preview_actwithactiontap,double_tap,long_press,type,scroll,swipe,drag,keyorfill. Target byname(the visible label, preferred), thenref, thencoordinate; a swipe takes a target and adirection, a drag two points.preview_actwithactionnavigateand aroutemoves within the app. Read again after every action that should change the screen. - Set the state a screen needs.
preview_actwithactionreset_storageclears the preview's stored data (a first open);seed_storagewithentries(each akeyand a stringvalue) stores app data, never a session;set_clockwithat,advanceortimezonemoves the clock for a reminder, a streak or an expiry. The app restarts on its route, except after a clock advance. - Vary the device.
- An app:
preview_viewwithdeviceiphone-15-pro(the default),ipad-mini,pixel-8,iphone-duo(the foldable shut, a short screen) oriphone-duo-open(open, near-square); orpreview_actwithactionresizeandpresetmobile,tablet,android,foldableorfoldable-open,orientationlandscape,colorSchemedark. Check dark mode and a small phone for any screen you restyled; the open foldable ignores orientation locks, so check it in landscape too. - A landing page:
preview_viewwithdevicedesktop(the default),ipad-miniandiphone-15-pro; orpreview_actwithactionresizeandpresetdesktop,tabletandmobile. Nothing may scroll sideways at any width, and every link must land somewhere real.
- An app:
- When something is wrong, read the logs before the code.
preview_logswithkindconsoleanderrors_onlyshows runtime errors.preview_logswithkindnetworklists requests; pass arequest_idto get one call's status, headers and body. - Fix and repeat from step 1 until the screen and its states match the intent.
States worth checking
- Loading, empty and error states, not only the happy path with data.
- Long names and large numbers, so text wraps instead of clipping.
- Signed out and signed in, when the app has sign-in.
- Back navigation from a pushed screen, and switching tabs and coming back.
Never
- Never report a screen as working because the build compiled or a write succeeded.
- Never claim native behavior (purchases, push, camera, sensors) from the web preview.
- Never type real personal data, real passwords or real payment details into the preview.
Report
- What you checked, on which device and color scheme, and what you saw.
- Errors found in the console or network logs, and what you changed because of them.
- What the preview cannot verify and still needs a real device.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

