OpenParable
Skip to content
← Back to skills

Articraft Viewer

Apps & Automation
articraft-viewer

Articraft Viewer is an Agent Skill for apps & automation published in the mattzh72/articraft repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Use when compiling Articraft records, opening the local viewer, inspecting articulated assets visually, or working on viewer API/web code.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/mattzh72/articraft/blob/HEAD/plugins/articraft/skills/articraft-viewer/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/articraft-viewer, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Articraft Viewer

Use this skill when the user asks to compile records, browse generated objects, inspect articulation, start the viewer, or work on viewer/api or viewer/web.

Compile Records

For one record:

uv run articraft compile <record_id>

Start The Viewer

Built viewer flow:

just viewer

Development viewer flow with API and Vite:

just viewer-dev

API only:

uv run uvicorn viewer.api.app:app --reload --host 127.0.0.1 --port 8765

Frontend-only commands:

npm --prefix viewer/web run dev
npm --prefix viewer/web run typecheck
npm --prefix viewer/web run lint
npm --prefix viewer/web run build

Visual QA

When inspecting an asset, verify:

  • all primary parts are visible and connected
  • articulations move the intended parts
  • no major unintended overlap or floating geometry is visible
  • link names and controls are semantic
  • materials and colors match the object prompt
  • history/lineage is preserved for forked records

If the viewer or frontend code changed, run the relevant frontend checks:

npm --prefix viewer/web run typecheck
npm --prefix viewer/web run lint

If API behavior changed, run focused viewer/API tests:

uv run --group dev pytest -q tests/viewer