What problem does it solve?
The IronClaw repository's own documentation drifts out of date, making it hard to know where a new feature, fix, prompt, or doc belongs, which crate owns a subsystem, or how a request flows through the system. This Skill provides a verified, up-to-date architectural map so you stop routing work into deleted crates or stale locations.
Core Features & Use Cases
- Placement routing: Directs new features into the correct Reborn crate family (
app, contracts, domains, events, extensions, kernel, lanes, loop, product, substrates) and new prompt templates into the owning crate via include_str!.
- Request flow tracing: Documents the canonical path from the Vite frontend through
ironclaw_webui, product contracts, TurnRunScheduler, RebornTurnRunExecutor, and the agent loop down to runtime lanes.
- Drift detection: Explains that the v1
src/ monolith and crates like ironclaw_engine and ironclaw_gateway are deleted, and gives grep commands to verify any crate's real consumers.
- Use Case: You are about to add a new endpoint and a doc tells you to edit
ironclaw_gateway; this Skill tells you that crate no longer exists and routes you to the correct Reborn crate instead.
Quick Start
Ask the agent to orient you in the IronClaw repo and tell you which crate should own the feature you are about to build.
