Menu
Build a user-facing feature in the Reborn stack with the smallest existing contract surface.
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/nearai/ironclaw --skill reborn-featureThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Showing SKILL.md
Use when adding or changing a Reborn integration — a new extension, a channel surface, model-callable tools, or a shared auth provider — or when deciding whether something is "a channel", "an extension", or "a tool". Maps the unified extension model (NEA-25) to the exact manifest sections, crates, seams, and tests.
Use when creating or editing agent guidance in this repo — anything under .claude/ (skills, commands, rules), AGENTS.md or CLAUDE.md files, or the runtime skills/ directory — or when guidance is found citing files, branches, or checks that no longer exist.
Use when adding or reviewing tests for Reborn behavior — choosing a test tier, covering a bug fix, testing model/tool-choice behavior, touching tests/integration or tests/fixtures/llm_traces, or when a test needs Postgres, Docker, or a live LLM.
Based on SOC occupation classification
| name | reborn-feature |
| description | Build a user-facing feature in the Reborn stack with the smallest existing contract surface. |
Start by locating the existing ProductSurface descriptor, route, and caller test. Most WebUI features are already represented by one of these two paths:
read: WebUI handler -> ProductSurface::query -> ProductView descriptor
write: WebUI handler -> ProductSurface::invoke -> capability descriptor
-> query read-back when the result is durable state
The owning crates are:
ironclaw_assistant: product DTOs, the concrete ProductView and
command/capability descriptor instances, and product orchestration.ironclaw_product_contracts: the ProductSurface contract, the
ProductView/ProductSurfaceCommandDescriptor/ProductCapabilityDescriptor
types, and the ProductSurfaceCaller/BoundProductSurface caller binding.ironclaw_host_api: shared host-facing error vocabulary
(ProductAdapterError).ironclaw_webui: route descriptors, handlers, gateway/listener/auth, and
the Vite frontend under frontend/.ironclaw_composition: production assembly and dependency wiring.ironclaw_cli: boot and serve command wiring.Run the graph status check once. If it is missing or stale, use targeted
rg searches and verify the result against live code.
bash scripts/codebase-graph.sh status
rg -n "ProductSurface|ProductView|ProductSurfaceCommandDescriptor|ProductCapabilityDescriptor" crates/product/ironclaw_assistant crates/contracts/ironclaw_product_contracts crates/product/ironclaw_webui
rg -n "descriptor|webui_v2_routes|ProductSurface" crates/product/ironclaw_webui/src/webui_v2
Read the owning crate's AGENTS.md, then CLAUDE.md or CONTRACT.md when
present. Find the nearest existing descriptor and copy its narrow pattern.
ProductView<Params, Output> in
crates/product/ironclaw_assistant/src/reborn_services.rs or its owning submodule.ProductSurfaceCommandDescriptor for typed product
commands, or a ProductCapabilityDescriptor for API-only side effects.ironclaw_assistant or the owning
service. Keep authorization, approval, persistence, and runtime mediation
in their existing stages.ironclaw_webui. Handlers
receive ProductSurfaceCaller and use BoundProductSurface; they do not
reach into composition, stores, dispatchers, or runtime lanes.crates/product/ironclaw_webui/frontend/src and use
the existing API client and page patterns.Arc field when an existing surface can
carry the operation.Do not add a feature-specific port, facade method, DTO family, builder field,
or adapter by default. Add one only when it provides dependency inversion,
two production implementations, a real test seam, a required dyn injection
point, or an enforced security/ownership boundary. Record the reason in the
PR description and run the architecture test for dependency changes.
ProductSurface only. ironclaw_assistant imports in
WebUI are limited to wire DTOs and descriptors.cargo test -p ironclaw_assistant
cargo clippy -p ironclaw_assistant --all-targets --all-features -- -D warnings
cargo test -p ironclaw_webui --all-features
cargo clippy -p ironclaw_webui --all-targets --all-features -- -D warnings
cargo test -p ironclaw_architecture_tests # when ownership or dependencies change
pnpm --dir crates/product/ironclaw_webui/frontend test
Use a caller-level test for every new route or side effect. Add a whole-path integration test when the feature changes turn execution or cross-layer behavior. Do not add a new test tier solely because a recipe lists it.