frontend-integration
Skill0 starsChanged 7 months agoApache-2.0View on GitHub
Frontend integration guides for React and Flutter with Kailash SDK workflows, including setup, API integration, state management, and best practices. Use when asking about 'frontend integration', 'React integration', 'Flutter integration', 'frontend developer', 'UI integration', 'React with Kailash', 'Flutter with Kailash', 'frontend workflow', 'API client', 'React query', or 'Flutter state management'.
- Sends data out
1 other project uses a version of this.
Adopted by
Most recently taken up by
- felvieira/claude-skills-fvtheir own version, first seen Sep 2, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- felvieira/claude-skills-fv★ 28same name
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 repository37 other files it gives its agents.
- .claude/rules/agents.mdAGENTS.md
- .claude/guides/claude-code/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- core-sdkSkill
- dataflowSkill
- nexusSkill
- kaizenSkill
- kailash-mcpSkill
- cheatsheetsSkill
- development-guidesSkill
- nodes-referenceSkill
- workflow-patternsSkill
- deployment-gitSkill
- testing-strategiesSkill
- architecture-decisionsSkill
- code-templatesSkill
- enterprise-infrastructureSkill
- validation-patternsSkill
- gold-standardsSkill
- security-patternsSkill
- flutter-patternsSkill
- interactive-widgetsSkill
- enterprise-ai-uxSkill
- conversation-uxSkill
- uiux-design-principlesSkill
- value-auditSkill
- ai-interaction-patternsSkill
- eatp-referenceSkill
- coc-referenceSkill
- 29-pactSkill
- claude-code-patternsSkill
- error-troubleshootingSkill
- kailash-mlSkill
- kailash-alignSkill
- co-referenceSkill
- managementSkill
- projectSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 119
Use this skill when you need to:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Kailash Frontend Integration
Guides for integrating Kailash workflows with frontend frameworks including React and Flutter.
Overview
Frontend integration patterns for:
- React applications with Kailash workflows
- Flutter mobile/desktop apps with Kailash
- API client setup and configuration
- State management patterns
- Real-time updates and streaming
Reference Documentation
React Integration
- react-integration-quick - React integration quick start
- Setup with Nexus API
- React Query integration
- TypeScript types
- Error handling
- State management
- Real-time updates
Flutter Integration
- flutter-integration-quick - Flutter integration quick start
- HTTP client setup
- Dart models
- State management (Riverpod/Bloc)
- Error handling
- Platform-specific code
General Frontend
- frontend-developer - Frontend development guide
- Architecture patterns
- API integration
- Authentication
- Error handling
- Best practices
Integration Patterns
React + Nexus
import { useQuery } from "@tanstack/react-query";
// Call Kailash workflow via Nexus API
const { data, isLoading, error } = useQuery({
queryKey: ["workflow", workflowId],
queryFn: () =>
fetch(`/api/workflow/${workflowId}`, {
method: "POST",
body: JSON.stringify({ input: "data" }),
}).then((res) => res.json()),
});Flutter + Nexus
import 'package:http/http.dart' as http;
// Call Kailash workflow
Future<Map<String, dynamic>> executeWorkflow(String workflowId, Map<String, dynamic> input) async {
final response = await http.post(
Uri.parse('$baseUrl/api/workflow/$workflowId'),
body: jsonEncode(input),
);
return jsonDecode(response.body);
}Architecture Patterns
Recommended Stack
React Applications:
- API Layer: Nexus (multi-channel platform)
- State Management: React Query / Zustand
- HTTP Client: Fetch API / Axios
- Type Safety: TypeScript with generated types
- UI Framework: Shadcn, Material-UI, or custom
Flutter Applications:
- API Layer: Nexus (multi-channel platform)
- State Management: Riverpod / Bloc
- HTTP Client: http package / Dio
- Type Safety: Dart with generated models
- UI Framework: Material 3 / Cupertino
Backend Architecture
Frontend (React/Flutter)
↓
Nexus API (Port 8000)
↓
Kailash Workflows
↓
DataFlow (Database)
↓
PostgreSQL/SQLiteWhen to Use This Skill
Use this skill when you need to:
- Integrate React with Kailash workflows
- Build Flutter apps with Kailash backend
- Set up API clients for Kailash
- Implement frontend state management
- Handle errors in frontend applications
- Configure real-time updates
- Generate TypeScript/Dart types
Best Practices
API Integration
- ✅ Use Nexus for auto-generated APIs
- ✅ Implement proper error handling
- ✅ Use type-safe clients (TypeScript/Dart)
- ✅ Cache responses appropriately
- ✅ Handle loading and error states
- ❌ NEVER expose API keys in frontend code
- ❌ NEVER skip input validation
State Management
- ✅ Use React Query for server state (React)
- ✅ Use Riverpod/Bloc for app state (Flutter)
- ✅ Implement optimistic updates
- ✅ Handle offline scenarios
- ❌ NEVER store sensitive data in client state
Performance
- ✅ Implement pagination for large datasets
- ✅ Use debouncing for search/filter
- ✅ Cache API responses
- ✅ Lazy load components
- ❌ NEVER fetch all data at once
Related Skills
- 03-nexus - Nexus API deployment
- 02-dataflow - Database backend
- 01-core-sdk - Workflow creation
Support
For frontend integration help, invoke:
react-specialist- React integration patternsflutter-specialist- Flutter integration patternsreact-specialist- Frontend architecturenexus-specialist- API configuration
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.

