app-workflow
Skill0 starsChanged 10 days agoMITView on GitHub
Use when the user wants to build, change, fix or explain a FluxNative app or landing page through the FluxNative connector: find or create the project, then read, edit, check and preview its source by its id. Not for an Expo project on this machine.
- Reads credentials
In this repository9 other files it gives its agents.
- app-sample-contentSkill
- design-referencesSkill
- mobile-app-designSkill
- mobile-design-briefSkill
- mobile-deslopSkill
- mobile-screen-reviewSkill
- paywall-onboardingSkill
- preview-verificationSkill
- supabase-rls-auditSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 5 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Every project tool takes project, the project's id from list_apps, as its first argument.
- Very specific: line 20
Call list_apps, with query when the user named the project.
- Distinctive: line 21
When several projects match, or none, ask which one.
- Distinctive: line 58
When a write is refused:
- Very specific: line 80
Not available over MCP: native builds, store uploads, review, release and ZIP export.
- Distinctive: line 84
Never edit a FluxNative project with local file, shell or git tools, or edit a local copy and paste it back.
- Distinctive: line 85
Never mix up projects: pass the id of the project the user means on every call.
- Very specific: line 86
Never put a secret in source or .env: every EXPO_PUBLIC_* value ships inside the app.
- Distinctive: line 87
Never ask for a key or a password in chat.
- Very specific: line 88
Never retry a conflict without reading the file again, or overwrite paths held by agent_editing.
≈ “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
Work on a FluxNative project
One connection, every project
The plugin's fluxnative server, https://mcp.fluxnative.app/mcp, reaches every app and landing page the account can edit, in every workspace. There is nothing else to add or connect.
list_appsandcreate_appfind and make projects.- Every project tool takes
project, the project's id fromlist_apps, as its first argument. Pass the same id on every call about that project. - The design catalog searches (
search_flows,search_screens,search_services), FluxNative's skills (load_skill) and the landing-template library (search_landing_templates,get_landing_template) take noproject: they are the same for every project.
The source lives in FluxNative, not on this machine. Local file, shell and git tools cannot see it, and a copy on disk is not the app. Every source write becomes a revision the user can see and undo in the FluxNative builder. Backend tools and preview_act change live data, which no revision undoes.
1. Find or create the project
- Call
list_apps, withquerywhen the user named the project. Each row has anid, a name, akind(apporlanding) and a workspace, newest activity first; it marks an imported app and names the app a landing page presents. - When several projects match, or none, ask which one. Never guess between two.
- A workspace the result says is left out has a plan without remote MCP. Tell the user it needs a plan that includes it; do not look for another way in.
- Call
create_apponly when the user asks for a new project. Give it aname(up to 30 characters), thekind, adescriptionin the user's own words (the brief every build of it starts from) and, when they have several workspaces, aworkspaceid fromlist_apps. A landing page may name the app it presents asparent_project. It builds nothing and spends no credits; the plan's project limit still applies.
Say which project you are working on (name and id) before you change it, and keep using that id.
2. Read the project's contract
Each project carries its own contract at the root of its tree: read_file with project and path AGENTS.md. Follow it.
- An app is Expo + React Native source: Expo Router routes in
app/re-export one Screen each fromsrc/features/<feature>/, data goes throughsrc/services/<domain>/index.ts,src/themeis the only token source, andsrc/platform/**is never edited. In an unfamiliar app, also readREADME.mdand.fluxnative/app-spec.json; the spec lists screens, navigation and flows with their status. - An app's identity is its design DNA:
.fluxnative/memory/design-dna.md, withdesign-screens.md,design-components.mdandproduct-dna.mdbeside it when the app has them. Read them before designing a screen. - An app's
AGENTS.mdis written for FluxNative's built-in assistant. Its<app_map>and<kernel_api>arekernel_api: every kernel component's props and token's name, used without opening their files. What it calls finishing is your final report, afterrun_checks. Read the skills it names withload_skill. Nothing here holds back a UI kit or NativeWind, so follow its Libraries rule yourself. - A new app (the starter screen is still there, no
.fluxnative/app-spec.json):kernel_api, then its component folders. Before the theme,search_flowsfor the journey andsearch_screensfor each kind of screen: their images are the bar for looks (type scale, spacing, surfaces, colour use), not layouts to copy, since this app's features decide its screens. Write the lead reference's look intodesign-dna.mdwith their ids, build each screen in it from kernel components, and judge every screenshot beside those images before your report. - An imported app (marked in
list_apps) is the customer's own Expo app; itsAGENTS.md, if any, is theirs. Locate withgrepandcode_graphbefore reading, follow its conventions, change the minimum, and never restructure it toward the template. - A FluxStore or FluxNews migration keeps the owner's settings in
src/config/and the Home layout insrc/features/home/home.sections.ts; data comes throughsrc/services/commerce. Never print, copy or ask for the WooCommerce keys in.env. - Notes in
.fluxnative/memory/taggeddecisionare the owner's standing rules, right after the user's request; save a lasting rule the user states as one. - A landing page is a static Vite, React and Tailwind site: facts and shared copy in
src/content.ts, sections insrc/sections/(one laid out from a template reads its words, links and images from its<Name>.copy.ts), tokens insrc/index.css, only the packages inpackage.json. - Before designing a landing page or section:
search_landing_templates(an app's page: ask forapp-showcase),get_landing_template, thencopy_templatefrom the template's id tosrc/App.tsx, and write each<Name>.copy.tsfor this product, keys kept. Change markup only withedit_file(drop, repeat or reorder items); never retype a template section. No template image comes over this connection. - A landing page never invents contact details or URLs and never says "sample", "coming soon" or "to be confirmed": content the brief lacks is believable sample content, listed in your report. A page that presents an app takes its name, brand, icon and real features from the app's source (its id as
project). The owner deploys it from the page's Publish.
3. Read before you write
list_fileswith aglobsuch asapp/**/*.tsxmaps the tree;include_metadataadds each path's SHA-256 and size without reading it.grepfinds the exact text a person sees or the symbol named (pathorincludeto narrow,outputfilesorcountfor an overview).code_graph(apps) follows code across files: definitions, references, callers up to the screens.read_filereturns the content, the committed revision and the full-file SHA-256; a long file continues fromstart_line.
4. Change the source
edit_filereplaces an exactold_stringwithnew_string. Passexpected_sha256from your last read of that path.write_filecreates a file (expected_sha256null) or rewrites a whole file.apply_changescommits up to 50 create, update, delete, move and copy operations as one revision. It is the only way to delete, move or copy a path, and the safe way to rename a component together with its imports.copy_templatestarts from FluxNative's own code: a template id for a page or section,exemplar:<slug>for an app screen.- Studio theme files (
src/theme/brand.ts, shape, typography, elevation, motion, fonts) change one literal at a time withedit_file. uploadputs a file from this machine into the project.step: "begin"returns a single-use command that streams the file straight to FluxNative (it carries a short-lived upload credential); run it, thenstep: "commit"with itsupload_idwrites it at apath. When the command cannot run,step: "inline"sends up to 2 MB as base64 in one call. Both take the path'sexpected_sha256(null for a new file).- Hashes are checked per path, so edits to different files do not conflict and can run in parallel.
When a write is refused:
- Changed since you read it. Someone else wrote that file. Read it again, re-apply your change to the new content, and retry once.
agent_editing. FluxNative's built-in assistant is writing those paths right now. Work on other files or wait; never overwrite its work.- Protected paths. Anything under
.github/,.fluxnative/other thanmemory/, deleting or moving.fluxnative/app-spec.json, and a new top-level folder are refused..envis writable. - App-spec diagnostics in a write result: fix each one.
5. Check your work
run_checksruns TypeScript, ESLint, Jest and the iOS and Android JavaScript exports on the committed source (on a landing page, the typecheck and the static build). Run it after meaningful changes and fix what it reports. It does not prove native linkage or device behavior.- For anything visible or interactive, use the
preview-verificationskill:build_preview, thenpreview_view,preview_actandpreview_logs. Check a landing page at desktop, tablet and phone widths.
App-only tools
A landing page refuses these; call them only with an app's id.
- Backend:
connection_infonames the connected backend, the public.envvalues to write and the secret names. The backend tools run with credentials that stay on FluxNative. Each backend has one read tool (supabase_read,cloudflare_read,api_read,firebase_read,appwrite_read,revenuecat_read) and change tools (for Supabase,supabase_sqland its siblings). Read with the read tool; a change tool acts on live data no revision undoes, so confirm deletes and other destructive changes with the user first. A backend tool on an app without that backend is refused by name: ask the user to connect it with the project's Server button in the FluxNative builder. When a credential is missing, ask the user to add it there; never ask for its value. Before a Supabase app ships, use thesupabase-rls-auditskill. - Android signing:
signing_key readreturns the SHA-1 and SHA-256 fingerprints to register with Firebase, Google Sign-In or Maps.signing_key generatecreates the key when the app has none. A keystore the user already has is uploaded in the builder, never here, and you never create a local keystore. - Design references and recipes:
search_flowsandsearch_screens, by journey and by screen, each result naming its app (see thedesign-referencesskill), andsearch_servicesfor maintained implementation recipes for a capability such as auth, payments, push or storage. Read the recipe before wiring a provider. Start a screen from anexemplar_idwithcopy_template. - Kernel:
kernel_apilists what the app's kernel exports, props included (modulenarrows it, e.g.theme). - Skills:
load_skillreads FluxNative's design and release skills; read their tool words as this connection's instructions map them.
Not available over MCP: native builds, store uploads, review, release and ZIP export. The user starts those in the FluxNative builder (Build and Publish). Never claim one happened. No image renderer either: make an icon's PNG on this machine and upload it.
Never
- Never edit a FluxNative project with local file, shell or git tools, or edit a local copy and paste it back.
- Never mix up projects: pass the id of the project the user means on every call.
- Never put a secret in source or
.env: everyEXPO_PUBLIC_*value ships inside the app. - Never ask for a key or a password in chat.
- Never retry a conflict without reading the file again, or overwrite paths held by
agent_editing.
Report
- The project (name and id) and the files you changed, one line each.
- The checks and preview steps you ran with their results, and what you could not verify.
- Anything the user must do in FluxNative: connect a backend or add a credential with the Server button, build, or publish.
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.

