How do I install the Architecture Decisions skill?

Run npx skillmds@latest add tomevault-io/architecture-decisions in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Architecture Decisions safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Architecture Decisions?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Architecture Decisions free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Architecture Decisions?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Architecture Decisions by tomevault-io

Name: Architecture Decisions
Author: tomevault-io

Architecture Decisions

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'. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

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-detection

Database 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-index

Test 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-framework skill - Framework selection and architecture
analyst - Deep analysis for complex decisions
pattern-expert - Pattern recommendations

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: architecture-decisionsdescription: 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'. Use when this capability is needed.---# Kailash Architecture DecisionsDecision guides for selecting the right frameworks, runtimes, databases, nodes, and testing strategies.## Reference Documentation| Decision | File | Quick Answer || --------- | ------------------------------------------------------------------------- | --------------------------------------------------------------------------- || Framework | [decide-framework](decide-framework.md) | Core SDK (custom), DataFlow (DB), Nexus (multi-channel), Kaizen (AI agents) || Runtime | [decide-runtime](decide-runtime.md) | Docker/async -> AsyncLocalRuntime; CLI/Scripts -> LocalRuntime || Database | [decide-database-postgresql-sqlite](decide-database-postgresql-sqlite.md) | Production -> PostgreSQL; Dev/Test -> SQLite || Node | [decide-node-for-task](decide-node-for-task.md) | See node selection flow below || Test Tier | [decide-test-tier](decide-test-tier.md) | 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-detection```## Database Selection Flow```Production deployment? -> PostgreSQL (scalable, enterprise)Development/testing? -> SQLite (simple, fast setup)High concurrency? -> PostgreSQL (better concurrency)```## Node Selection Flow```Custom Python logic -> PythonCodeNodeLLM/AI tasks -> LLMNode, OpenAINode, AnthropicNodeDatabase operations -> DataFlow auto-generated nodesHTTP API calls -> HTTPRequestNodeFile reading -> FileReaderNodeConditional routing -> SwitchNodeNot sure? -> Check nodes-quick-index```## Test 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](../../01-core-sdk/SKILL.md)** - Core SDK fundamentals- **[02-dataflow](../../02-dataflow/SKILL.md)** - DataFlow framework- **[03-nexus](../../03-nexus/SKILL.md)** - Nexus framework- **[04-kaizen](../../04-kaizen/SKILL.md)** - Kaizen framework- **[08-nodes-reference](../../08-nodes-reference/SKILL.md)** - Node reference- **[12-testing-strategies](../../12-testing-strategies/SKILL.md)** - Testing strategies## Support- `decide-framework` skill - Framework selection and architecture- `analyst` - Deep analysis for complex decisions- `pattern-expert` - Pattern recommendations---> Converted and distributed by [TomeVault](https://tomevault.io/claim/integrum-global) — claim your Tome and manage your conversions.

Frequently asked questions