code-templates
Skill0 starsChanged 7 months agoApache-2.0View on GitHub
Production-ready code templates for Kailash SDK including basic workflows, cyclic workflows, custom nodes, MCP servers, and all three test tiers (unit, integration, end-to-end). Use when asking about 'template', 'example code', 'starter code', 'boilerplate', 'scaffold', 'workflow template', 'custom node template', 'MCP server template', 'test template', 'unit test template', 'integration test template', or 'E2E test template'.
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
- frontend-integrationSkill
- testing-strategiesSkill
- architecture-decisionsSkill
- 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
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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 56
Keep core structure intact when customizing
- Distinctive: line 57
Never skip error handling or input validation
- Distinctive: line 58
Never remove resource cleanup
- Distinctive: line 60
Follow naming conventions from gold standards
≈ “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
Kailash Code Templates
Production-ready templates for common Kailash development tasks. All follow the canonical 4-parameter pattern from /01-core-sdk.
Sub-File Index
Workflow Templates
- template-workflow-basic - Standard workflow
- WorkflowBuilder setup, node addition, 4-param connections, runtime execution, result access, error handling
- template-cyclic-workflow - Iterative workflows
- CycleNode setup, convergence checking, state persistence, iteration limits
Custom Development
- template-custom-node - Custom node creation
- Extend BaseNode, parameter definition, execute method, input validation, output formatting, registration
- template-mcp-server - MCP server creation
- MCPServer init, tool/resource registration, transport config, auth, progress reporting
Test Templates
- template-test-unit - Tier 1: Unit tests
- Fixtures, mock setup (allowed in Tier 1), assertions, fast execution
- template-test-integration - Tier 2: Integration tests
- Real database setup, workflow execution, real infrastructure fixtures, resource cleanup
- template-test-e2e - Tier 3: End-to-end tests
- Full system setup, real HTTP requests, complete user flows
Template Selection
| Task | Template | Key Pattern |
| New workflow | template-workflow-basic | WorkflowBuilder + .build() + runtime.execute() |
| Iterative logic | template-cyclic-workflow | CycleNode + convergence check |
| New node type | template-custom-node | Extend BaseNode, implement execute() |
| MCP integration | template-mcp-server | MCPServer + tool registration |
| Fast tests | template-test-unit | Mocking allowed, <1s |
| Real infra tests | template-test-integration | Real DB/runtime, no mocks |
| Full system tests | template-test-e2e | Real HTTP, complete flows |
Usage
- Select the template matching your task
- Read the sub-file for the complete, copy-ready template
- Customize to your specific needs
- Test with real data
Template Rules
- Keep core structure intact when customizing
- Never skip error handling or input validation
- Never remove resource cleanup
- Maintain type hints and docstrings
- Follow naming conventions from gold standards
Related Skills
- 01-core-sdk - Core patterns
- 06-cheatsheets - Pattern examples
- 07-development-guides - Development guides
- 12-testing-strategies - Testing strategies
- 17-gold-standards - Best practices
Support
pattern-expert- Pattern selectiontdd-implementer- Test-first development
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.