assets

Layerline Assets

Workflow for managing project assets in Layerline (mcp__layerline__* tools, asset domain).

What an "asset" is

An asset is a top-level production unit in a project — a character, prop, level, etc. It has:

• A name + asset tag (Characters, Props, Environments, …) → tags are also folder names
• A status (Not Started → In Progress → Review → Complete, configurable per project)
• Output tags representing pipeline stages (Modeling, Texturing, Rigging, …). Each output tracks its own completion based on linked tasks; you can also override per-output completion manually.
• A File Box (see layerline:storage) holding the files that belong to this asset
• An export config controlling FBX options for DCC exports (Maya/Blender)

Read tools

list_assets(projectId)                                  // all visible assets
get_asset(assetId)                                       // status, output statuses, task counts, thumbnail
get_working_assets(projectId, limit?)                   // assets linked to my tasks + recently modified
get_asset_activity_log(projectId, assetId?, limit?)
get_asset_statuses(projectId)

External users only see assets attached to tasks they're assigned to. If list_assets looks empty, double-check the user's role.

Create / update / archive

create_asset(projectId, name, assetTagName, assetTagFolder, outputFolders[])
update_asset(assetId, name?, description?, statusId?, metadata?)
archive_asset(assetId, reason)         // soft delete with reason
restore_asset(assetId)                  // unarchive
delete_asset(assetId)                   // permanent — confirm with user first

Picking assetTagName / assetTagFolder / outputFolders: these define the cloud folder layout. The user usually has conventions — check get_project or look at sibling assets via list_assets to match. Typical:

• assetTagName: "Characters", assetTagFolder: "Characters"
• outputFolders: ["Modeling", "Texturing", "Rigging"] for characters
• outputFolders: ["Modeling", "Texturing"] for props

statusId resolution: call get_asset_statuses(projectId), find the status by name, then pass the id.

Asset comments

Threaded discussion on an asset — supports @user mentions and #path/to/file references.

list_asset_comments(assetId)                            // threaded structure
create_asset_comment(assetId, content, parentId?)       // parentId for single-level reply
update_asset_comment(commentId, content)
delete_asset_comment(commentId)

Mentions are auto-parsed from content text. To mention [email protected], write @huelder in the body.

Output completion

Each output tag (e.g. "Modeling") has a status derived from the tasks linked to it. You can manually override:

mark_output_complete(assetId, outputTag)                // override → complete
unmark_output_complete(assetId, outputTag)              // remove override; revert to task-based
update_task_output_overrides(projectId, assetId, overrides[])
   // overrides: [{ taskId, excludedOutputs: ["Modeling", ...] }]

update_task_output_overrides is for when one task shouldn't contribute to a given output (e.g. a "Concept" task linked to a character but excluded from the "Rigging" calc).

Asset status options

get_asset_statuses(projectId)
update_asset_status(projectId, statusId, name?, color?, sortOrder?, isDefault?, isComplete?)

isDefault is the status given to new assets. isComplete flags the status as a "done" state for progress calculations.

Asset export config (FBX/DCC)

Layerline ships with per-asset export settings used by Maya/Blender exporters:

get_asset_export_config(assetId)
update_asset_export_config(assetId, defaultFbxOptions?, defaultExportGroupName?)
create_file_config(assetId, filePath, enabled?, fbxOverrides?, exportGroupName?, customOutputPath?)
create_animation_clip(fileConfigId, name, startFrame, endFrame, loop?)

A file_config overrides export options for one specific file inside the asset; animation_clip defines a frame-range clip on top of a file_config (used for batch animation export).

Project-level export settings live in the export-settings tools (get_export_settings, update_export_settings, list_export_filter_rules, create_filter_rule, list_export_overrides, create_export_override, list_script_templates).

Common workflows

"Create a character asset called Hero Knight"

1. list_assets(projectId) → confirm no duplicate name.
2. create_asset(projectId, name="Hero Knight", assetTagName="Characters", assetTagFolder="Characters", outputFolders=["Modeling","Texturing","Rigging"]).
3. Tell the user: created in Characters/Hero Knight/ with three output folders.

"Mark the modeling on Hero Knight as done"

1. list_assets(projectId) → resolve assetId.
2. mark_output_complete(assetId, outputTag="Modeling").

"Move Hero Knight to Review"

1. get_asset_statuses(projectId) → find the Review status id.
2. update_asset(assetId, statusId=<found id>).

"Comment on Hero Knight: 'sword feels too short, please bump scale'"

1. Resolve assetId.
2. create_asset_comment(assetId, content="sword feels too short, please bump scale @rigger #Characters/Hero Knight/Rigging/sword.fbx").

Pairings

• Want to upload files to the asset? → layerline:storage (file boxes + LS upload flow).
• Want to generate the asset with AI? → layerline:genstudio (generate with assetName + assetTagFolder + projectId auto-persists as a new asset).
• Want to review the asset? → layerline:reviews (create_review with asset_id).