Skip to main content
Back to Prompt Library
implementation

Build the application

Inspect the original prompt language first, then copy or adapt it once you know how it fits your workflow.

Linked challenge: Build a Robot-Cell Commissioning Acceptance Dossier Compiler

Format
Code-aware
Lines
85
Sections
11
Linked challenge
Build a Robot-Cell Commissioning Acceptance Dossier Compiler

Prompt source

Original prompt text with formatting preserved for inspection.

85 lines
11 sections
No variables
1 code block
## Build
Evaluate simulated robot-cell motion trials and axis limit margins using MoveIt kinematic profiles. Compile formal site acceptance test packets with verified reachability clearances and speed limits.

## User
Automation Commissioning Engineer

## Workflow
1. Ingest MoveIt joint trajectory execution records and nominal cell boundary extents.
2. Calculate axis velocity margin deviations and safety perimeter clearances.
3. Score test execution against predefined acceptance criteria for reachability and cycle time.
4. Synthesize an immutable site acceptance testing sign-off packet for engineering review.

## Interface
Web dashboard showing commissioning stage progress, joint margin deviations, and an acceptance dossier approval viewer.

## Data
Generate synthetic JSON records representing MoveIt joint trajectory execution logs with simulated kinematic offsets and cycle runtimes.
Starter examples below are synthetic. They are not downloaded records.

## Source
[MoveIt robotics](https://raw.githubusercontent.com/moveit/moveit2/main/README.md)
Applies MoveIt motion planning concepts, specifically joint limits and kinematic reachability envelopes referenced in MoveIt 2 documentation.

## Tools
pydantic-ai, fastapi, pytest.
Pydantic AI enforces strict type constraints on commissioning metrics and produces validated JSON acceptance dossiers.
Local or hosted LLM with structured output capabilities; requires fast schema validation for acceptance reporting.

## Deliverables
Submit runnable source, pinned dependencies, setup commands, a working interface, example outputs, and a recorded end-to-end demo. Include tests and an action log.

## Acceptance
- Validates all robot joints against prescribed velocity and position thresholds.
- Detects at least one clearance breach when given out-of-boundary tool coordinates.
- Outputs a valid JSON acceptance dossier with pass/fail attestation.

## Starter Examples
```json
[
  {
    "input": {
      "cell_id": "CELL-01",
      "trajectory_points": [
        {
          "joint_1_rad": 0.5,
          "joint_2_rad": -0.2,
          "velocity_rad_s": 1.2,
          "clearance_mm": 250
        },
        {
          "joint_1_rad": 1.1,
          "joint_2_rad": -0.4,
          "velocity_rad_s": 1.4,
          "clearance_mm": 210
        }
      ],
      "cycle_time_target_s": 12,
      "actual_cycle_time_s": 10.8
    },
    "expected_output": {
      "cell_id": "CELL-01",
      "acceptance_status": "APPROVED",
      "min_clearance_mm": 210,
      "max_velocity_rad_s": 1.4,
      "acceptance_notes": "All axes within speed envelope and minimum safe clearance maintained."
    }
  },
  {
    "input": {
      "cell_id": "CELL-02",
      "trajectory_points": [
        {
          "joint_1_rad": 2.8,
          "joint_2_rad": 1.9,
          "velocity_rad_s": 3.8,
          "clearance_mm": 35
        }
      ],
      "cycle_time_target_s": 10,
      "actual_cycle_time_s": 14.5
    },
    "expected_output": {
      "cell_id": "CELL-02",
      "acceptance_status": "REJECTED",
      "min_clearance_mm": 35,
      "max_velocity_rad_s": 3.8,
      "acceptance_notes": "Safety clearance dropped below 50mm buffer limit; velocity exceeds 3.0 rad/s."
    }
  }
]
```

## Safety
Read-only trajectory verification; simulated acceptance evaluation without physical machine enablement.
Use mock external writes. Require human review before any real deployment.

Adaptation plan

Keep the source stable, then change the prompt in a predictable order so the next run is easier to evaluate.

Keep stable

Hold the task contract and output shape stable so generated implementations remain comparable.

Tune next

Update libraries, interfaces, and environment assumptions to match the stack you actually run.

Verify after

Test failure handling, edge cases, and any code paths that depend on hidden context or secrets.