27 lines
1.9 KiB
JSON
27 lines
1.9 KiB
JSON
{
|
|
"skill_name": "library-manager",
|
|
"evals": [
|
|
{
|
|
"id": 0,
|
|
"name": "resistor-description-format",
|
|
"prompt": "We're adding the Yageo RC0402FR-0736KL to our component library. From its datasheet: resistance 36 kohm, tolerance 1%, package 0402, rated power 63 mW (1/16 W), thick-film chip resistor, not AEC-Q qualified. Following our library process, what exactly should go in this part's Description field in its library sheet? Give me the final Description string.",
|
|
"expected_output": "A strict SOP Description string (e.g. CHIP_RES_36kOhm_63mW_+-1%_0402): type prefix, value, wattage, tolerance, package; no AEC-Q token since not qualified. NOT free prose.",
|
|
"files": []
|
|
},
|
|
{
|
|
"id": 1,
|
|
"name": "capacitor-description-format",
|
|
"prompt": "Adding a TDK CGA5L1X7R2A225K MLCC to the library. Datasheet: 2.2 uF, 100 V, tolerance 10%, 1210 case size, X7R dielectric, AEC-Q200 qualified. Per our library workflow, what is the exact Description field value for this part?",
|
|
"expected_output": "A strict SOP Description string (e.g. CHIP_CAP_2.2uF_100v_+-10%_1210_x7r_AECQ-200): type, value, voltage, tolerance, package, temp-coefficient, AEC-Q last. NOT free prose.",
|
|
"files": []
|
|
},
|
|
{
|
|
"id": 2,
|
|
"name": "existing-part-update-flow",
|
|
"prompt": "The part BAT46WJ from Nexperia is already in our library, but its forward-voltage value was entered wrong. I want to correct it. Walk me through exactly how you'd handle this with our library tooling, including the commands you'd run.",
|
|
"expected_output": "Recognizes this is an UPDATE of an existing part (not a hard-stop): offers update-or-stop, uses checkout + find-part to locate it, rebuilds the sheet in place with fill_templates (no version bump), keeps human verification, then commit-push with operator attribution. Does not invent a delete/re-add.",
|
|
"files": []
|
|
}
|
|
]
|
|
}
|