frontend-query-mutation
Skill1 starsChanged 2 months agoMITView on GitHub
Guide for implementing Ketos frontend query and mutation patterns with Axios and TanStack React Query v5. Trigger when creating or updating API hooks in controllers/API/queries, consuming UseRequestProcessor in components, deciding whether to use useQuery or useMutation, handling conditional queries, cache invalidation, mutation error handling, or migrating legacy API calls to the query hook pattern.
2 other projects use a version of this, 2 of them edited.
Adopted by
Most recently taken up by
- lien0219/openxflowedited, first seen Nov 8, 2026
- langflow-ai/langflowedited, first seen Oct 8, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 2
- langflow-ai/langflow★ 156k96% same
- lien0219/openxflow★ 896% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository29 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/docs_development.mdcCursor rule
- backend-code-reviewSkill
- component-refactoringSkill
- e2e-testingSkill
- frontend-code-reviewSkill
- frontend-testingSkill
- graphifySkill
- graphSkill
- ingestSkill
- lintSkill
- querySkill
- researchSkill
- run-reviewSkill
- saveSkill
- security-reviewSkill
- startSkill
- watchSkill
- graphSkill
- ingestSkill
- lintSkill
- querySkill
- researchSkill
- run-reviewSkill
- saveSkill
- security-reviewSkill
- startSkill
- watchSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. About 0 are common, 2 are distinctive, and 12 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
12
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
Keep API hooks in controllers/API/queries/{domain}/ as the organized source of truth.
- Very specific: line 12
Use UseRequestProcessor for consistent retry, invalidation, and error handling.
- Very specific: line 13
Use Axios api instance for all HTTP calls (never raw fetch for REST).
- Very specific: line 14
Use performStreamingRequest() for streaming operations (build, chat).
- Very specific: line 15
Keep cache invalidation in mutation onSettled callbacks.
- Very specific: line 44
Read references/query-patterns.md for hook structure, naming, URL patterns, and query/mutation call-site shape.
- Very specific: line 45
Read references/runtime-rules.md for conditional queries, invalidation, error handling, and streaming.
- Distinctive: line 46
Read both references when a task spans hook creation and runtime behavior.
- Very specific: line 48
Use UseRequestProcessor for query() and mutate() wrappers.
- Very specific: line 49
Use the api Axios instance for all HTTP calls.
- Very specific: line 50
Use getURL() for constructing API paths.
- Very specific: line 70
Use references/query-patterns.md for hook structure, naming conventions, directory layout, and anti-patterns.
- Very specific: line 71
Use references/runtime-rules.md for conditional queries, invalidation, mutate versus mutateAsync, error handling, and streaming requests.
- Distinctive: line 73
Treat this skill as the single query and mutation entry point for Ketos frontend work.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Frontend Query & Mutation
Intent
- Keep API hooks in
controllers/API/queries/{domain}/as the organized source of truth. - Use
UseRequestProcessorfor consistent retry, invalidation, and error handling. - Use Axios
apiinstance for all HTTP calls (never rawfetchfor REST). - Use
performStreamingRequest()for streaming operations (build, chat). - Keep cache invalidation in mutation
onSettledcallbacks.
Architecture Overview
Ketos uses Axios + TanStack React Query v5 for data fetching. There is no oRPC or contract layer. The architecture is:
Component
-> API hook (controllers/API/queries/{domain}/use-{verb}-{resource}.ts)
-> UseRequestProcessor (controllers/API/services/request-processor.ts)
-> useQuery / useMutation (TanStack React Query)
-> queryFn / mutationFn
-> api.get/post/patch/delete (Axios instance from controllers/API/api.tsx)Key Files
| File | Purpose |
controllers/API/api.tsx | Axios instance, ApiInterceptor component, performStreamingRequest() |
controllers/API/services/request-processor.ts | UseRequestProcessor hook wrapping useQuery/useMutation with retry defaults |
controllers/API/helpers/constants.ts | URL constants (URLs) and getURL() helper |
controllers/API/queries/{domain}/ | Domain-organized query and mutation hooks |
types/api/index.ts | useQueryFunctionType, useMutationFunctionType type helpers |
stores/ | Zustand stores for client-side state |
Workflow
- Identify the change surface.
- Read
references/query-patterns.mdfor hook structure, naming, URL patterns, and query/mutation call-site shape. - Read
references/runtime-rules.mdfor conditional queries, invalidation, error handling, and streaming. - Read both references when a task spans hook creation and runtime behavior.
- Read
- Implement the hook following existing patterns.
- Use
UseRequestProcessorforquery()andmutate()wrappers. - Use the
apiAxios instance for all HTTP calls. - Use
getURL()for constructing API paths. - Type the hook with
useQueryFunctionTypeoruseMutationFunctionType.
- Use
- Preserve Ketos conventions.
- Query keys are arrays with the hook name:
["useGetFlows"]. - Mutations invalidate related queries in
onSettled. - Zustand store updates happen in the query/mutation function, not in components.
UseRequestProcessorprovides default retry (5 for queries, 3 for mutations) with exponential backoff.
- Query keys are arrays with the hook name:
Files Commonly Touched
controllers/API/queries/{domain}/use-get-*.ts(query hooks)controllers/API/queries/{domain}/use-post-*.ts(create mutations)controllers/API/queries/{domain}/use-patch-*.ts(update mutations)controllers/API/queries/{domain}/use-delete-*.ts(delete mutations)controllers/API/helpers/constants.ts(URL constants)types/api/index.ts(API type definitions)stores/(Zustand store updates triggered by queries)
References
- Use
references/query-patterns.mdfor hook structure, naming conventions, directory layout, and anti-patterns. - Use
references/runtime-rules.mdfor conditional queries, invalidation,mutateversusmutateAsync, error handling, and streaming requests.
Treat this skill as the single query and mutation entry point for Ketos frontend work. Keep detailed rules in the reference files instead of duplicating them in project docs.
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.

