Sorry, your browser does not support inline SVG.

Assembly tools

The aspect-selection door: turn a plain-language requirement into a complete CRUD resource by SELECTING pre-authored, proven behaviour aspects (ownership, search, soft-delete, status filter, ordering) — validated and composed into clean owned Laravel, never generated.

These tools live in the on-demand catalog rather than the default tool list, keeping the connected client's context small. Discover them with search_tools (e.g. search_tools(queries: ["assembly"])) and run them with execute_tools — or call them directly if your client has already loaded them.

Build Resource From Requirement

build_resource via execute_tools

Build a complete CRUD resource (model + controller + migration + routes + list view) into the ACTIVE project from a plain-language requirement — by SELECTING pre-authored, proven behaviour "aspects", never by generating logic. This is the aspect-selection door: an AI classifies the requirement onto a resource spec + a set of catalogue aspects (e.g. ownership = per-user rows, search, soft_delete = recoverable deletes, by_status, recent_first), then the server validates the selection (requires/axis/capability contracts + a commutativity enforcement gate) and composes clean, owned Laravel as code-as-data that exports through the real pipeline.

The AI only ever SELECTS from the catalogue — it cannot invent behaviour. If the requirement needs a behaviour no aspect provides, the build fails and the gap is recorded on the reuse-demand board for a human to author a new unit; it is never improvised.

Pass requirement in plain English (e.g. "a personal task list each user can search, with recoverable deletes and newest first"). Set preview: true to get the composed files back WITHOUT writing anything (a dry run); omit it to persist the resource into the active project. Returns the resource spec, the selected aspect keys, and either the file map (preview) or the created unit UUIDs.

Parameters

  • Name
    requirement
    Type
    string
    Required
    required
    Description

    Plain-language description of the resource to build, e.g. "private notes each user can search, soft-deletable".

  • Name
    preview
    Type
    boolean
    Description

    When true, return the composed files without writing anything (a dry run). Omit to persist into the active project.