architecture-decisions
Skill0 starsChanged 7 months agoApache-2.0View on GitHub
Architecture decision guides for Kailash SDK including framework selection (Core SDK vs DataFlow vs Nexus vs Kaizen), runtime selection (Async vs Sync), database selection (PostgreSQL vs SQLite), node selection, and test tier selection. Use when asking about 'which framework', 'choose framework', 'which runtime', 'which database', 'which node', 'architecture decision', 'when to use', 'Core SDK vs DataFlow', 'PostgreSQL vs SQLite', 'AsyncLocalRuntime vs LocalRuntime', or 'test tier selection'.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- drvoss/everything-copilot-clitheir own version, first seen Oct 26, 2026
- nimadorostkar/Claude-Skills-collectiontheir own version, first seen Oct 13, 2026
- jwilger/agent-skillstheir own version, first seen Oct 11, 2026
- caiaffa/claude-code-ultimate-engineering-systemtheir own version, first seen Sep 14, 2026
- augments-labs/sdlc-skillstheir own version, first seen Aug 8, 2026
- lzx-Bill/Project-Factory-Coretheir own version, first seen Jul 15, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- drvoss/everything-copilot-cli★ 49same name
- nimadorostkar/Claude-Skills-collection★ 37same name
- caiaffa/claude-code-ultimate-engineering-system★ 17same name
- jwilger/agent-skills★ 4same name
- augments-labs/sdlc-skills★ 1same name
- lzx-Bill/Project-Factory-Core★ 0same 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
- frontend-integrationSkill
- testing-strategiesSkill
- 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
5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 72
NEVER use ORM when DataFlow can generate nodes
- Very specific: line 73
NEVER build API/CLI/MCP manually when Nexus can do it
- Distinctive: line 78
NEVER use LocalRuntime in Docker (causes hangs)
- Distinctive: line 79
NEVER mix runtimes in same application
- Distinctive: line 84
NEVER skip connection pooling config
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Kailash Architecture Decisions
Decision guides for selecting the right frameworks, runtimes, databases, nodes, and testing strategies.
Reference Documentation
| Decision | File | Quick Answer |
| Framework | decide-framework | Core SDK (custom), DataFlow (DB), Nexus (multi-channel), Kaizen (AI agents) |
| Runtime | decide-runtime | Docker/async -> AsyncLocalRuntime; CLI/Scripts -> LocalRuntime |
| Database | decide-database-postgresql-sqlite | Production -> PostgreSQL; Dev/Test -> SQLite |
| Node | decide-node-for-task | See node selection flow below |
| Test Tier | decide-test-tier | Unit (fast), Integration (real infra), E2E (full system) |
Framework Selection Matrix
| Need | Framework | Why |
| Custom workflows | Core SDK | Full control, 140+ nodes |
| Database CRUD | DataFlow | Auto-generated nodes |
| Multi-channel API | Nexus | API + CLI + MCP instantly |
| AI agents | Kaizen | Signature-based agents |
| All of above | Combine them | They work together |
Runtime Selection Flow
Deploying to Docker/async/Kubernetes?
YES -> AsyncLocalRuntime (async-first, no threads)
NO -> CLI/script?
YES -> LocalRuntime (sync execution)
NO -> Use get_runtime() for auto-detectionDatabase Selection Flow
Production deployment? -> PostgreSQL (scalable, enterprise)
Development/testing? -> SQLite (simple, fast setup)
High concurrency? -> PostgreSQL (better concurrency)Node Selection Flow
Custom Python logic -> PythonCodeNode
LLM/AI tasks -> LLMNode, OpenAINode, AnthropicNode
Database operations -> DataFlow auto-generated nodes
HTTP API calls -> HTTPRequestNode
File reading -> FileReaderNode
Conditional routing -> SwitchNode
Not sure? -> Check nodes-quick-indexTest Tier Flow
Individual function -> Tier 1 (Unit)
Workflow execution -> Tier 2 (Integration, real infrastructure)
Complete user flow -> Tier 3 (E2E)Critical Decision Rules
Framework
- NEVER use ORM when DataFlow can generate nodes
- NEVER build API/CLI/MCP manually when Nexus can do it
Runtime
- Docker/async -> AsyncLocalRuntime (mandatory)
- NEVER use LocalRuntime in Docker (causes hangs)
- NEVER mix runtimes in same application
Database
- Production -> PostgreSQL; NEVER SQLite for production high-concurrency
- NEVER skip connection pooling config
- Multi-instance -> One DataFlow per database
Related Skills
- 01-core-sdk - Core SDK fundamentals
- 02-dataflow - DataFlow framework
- 03-nexus - Nexus framework
- 04-kaizen - Kaizen framework
- 08-nodes-reference - Node reference
- 12-testing-strategies - Testing strategies
Support
decide-frameworkskill - Framework selection and architectureanalyst- Deep analysis for complex decisionspattern-expert- Pattern recommendations
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.

