Crew Member Definitions

Prompt detail, context, and execution controls for real reuse instead of one-off copying.

planningDigital Twin Process Control for MoS2 FETs using CrewAI and Letta AIPublic prompt

Operator-ready prompt for reuse, tuning, and workspace runs.

This item is set up for developers who want to inspect the original language, fork it into Workspace, and adapt the evidence model without losing the source prompt structure.

Best for

Implementation handoffs, eval setup, and prompt tuning where you need the original structure intact.

Reuse pattern

Inspect first, copy once, then fork into Workspace when you want variants, notes, and model settings attached to the same run.

Before first run

Swap domain facts, examples, and any hard-coded entities for your own context.

Tighten the evidence or verification requirement if this is headed toward production.

Decide which failure mode you want to evaluate first before you branch the prompt.

Operator lens

This prompt already carries implementation detail, tool context, and a final-output instruction. Keep that structure intact when you tune it, or your comparison runs get noisy fast.

Best practice: keep one pristine source version, then branch variants around evaluation criteria, evidence thresholds, and output format.
Inspect linked challenge context
Run Profile

Open this prompt inside Workspace when you want a live iteration loop.

Copy for quick reuse, or run it in Workspace to keep prompt variants, model settings, and prompt-history changes in one place.

Structured source with 1 active lines to adapt.

Already linked to a challenge workflow.

Sign in to keep private prompt variations.

View linked challenge

Prompt content

Original prompt text with formatting preserved for inspection and clean copy.

Source prompt
1 active lines
1 sections
No variables
0 checklist items
Raw prompt
Formatting preserved for direct reuse
Define two CrewAI agents: 1) Fabrication_Engineer (Goal: Maximize Ion current density). 2) Metrology_Specialist (Goal: Identify process drift using historical data). Assign both agents to a Letta AI backend so they can store 'experiment logs' in long-term memory. Use the CrewAI 'Process.sequential' flow.

Adaptation plan

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

Keep stable

Preserve the role framing, objective, and reporting structure so comparison runs stay coherent.

Tune next

Swap in your own domain constraints, anomaly thresholds, and examples before you branch variants.

Verify after

Check whether the prompt asks for the right evidence, confidence signal, and escalation path.

Safe workflow

Copy once for a pristine source snapshot, then move the prompt into Workspace when you want variants, run history, and side-by-side tuning without losing the original.

Prompt diagnostics

Quick signals for how structured this prompt already is and where adaptation work is likely to happen first.

Sections
1
Variables
0
Lists
0
Code blocks
0
Reuse posture

This prompt is mostly narrative and instruction-driven, so you can adapt examples and output constraints first without disturbing the structure.

Linked challenge

Digital Twin Process Control for MoS2 FETs using CrewAI and Letta AI

Based on recent breakthroughs in gate structuring for bilayer MoS2 field-effect transistors, this challenge requires you to build an autonomous Digital Twin controller. You will use the CrewAI framework to orchestrate a 'Process Engineer' agent and a 'Metrology Specialist' agent. These agents will collaborate to optimize the gate deposition parameters (temperature, pressure, and time) to achieve ultrahigh current density. To manage the complex, stateful nature of microfabrication cycles, you will integrate Letta AI (formerly MemGPT). Letta AI will provide the agents with 'Archival Memory'—allowing them to store and retrieve historical run data, drift patterns, and sensor telemetry. This prevents the agents from repeating failed experiments and allows them to identify long-term degradation in the virtual manufacturing line.

Engineering
advanced
Prompt origin
Why open it

Use the challenge page to recover the original task boundaries before you tune the prompt. That keeps your variants grounded in the same evaluation target instead of drifting into a different problem.

Open challenge context