deco-core-architecture

Explain Deco core architecture, resolution engine, block system, and runtime flow.

5|2|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/decocms/deco-start --skill deco-core-architecture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deco-core-architecture
Source: https://github.com/decocms/deco-start/tree/main/.cursor/skills/deco-core-architecture
Command: npx skills add https://github.com/decocms/deco-start --skill deco-core-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture reference for the Deco core framework, detailing the resolution engine, block system, and runtime flows to aid developers.

Core Features & Use Cases

  • Comprehensive overview of core modules (engine, manifest, decofile provider, blocks, runtime)
  • Guidance for porting Deco internals to TanStack Start and debugging resolution paths
  • Reference for understanding how changes ripple through resolvables, resolvers, and manifests

Quick Start

Review the engine.md, blocks.md, runtime.md, and deco-vs-deco-start.md to map how resolvables, resolvers, and blocks compose the Deco architecture.

Frequently Asked Questions about deco-core-architecture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How does the Deco resolution engine map resolvables and resolvers during runtime flow?

The Deco resolution engine maps resolvables to resolvers during runtime flow to dynamically compose blocks. This mechanism drives schema validation, import mapping, and routing across the generated manifest.

How do I debug resolution paths across the engine, manifest, and runtime in Deco?

Debug Deco resolution paths by tracing resolvables through resolvers into the DecofileProvider and manifest generation. This reveals routing mismatches and import mapping errors across the runtime architecture.

What is the best way to port Deco internal concepts to TanStack Start?

Port Deco internals to TanStack Start by mapping the resolution engine and block system to TanStack's routing. Review deco-vs-deco-start integration points to translate resolvables and manifest generation correctly.

How does Deco manifest generation handle schema and import mapping?

Deco manifest generation processes schema definitions and import mappings via the DecofileProvider to establish runtime routing. It links resolvables to resolvers for accurate block composition.

Why do changes in resolvers ripple through the Deco block system and manifest?

Changes in resolvers ripple through the Deco block system because resolvables depend on them for runtime composition. These dependencies alter manifest generation, schema validation, and import mapping outputs.