Audit schemas for looseness

Every loose type is an invitation the model will accept.

First time here? Paste the Context Pack first so the AI understands your project - open it from the header above.

Prompt Capsule

Audit all my tool schemas for constraint weakness. For each parameter record: current type, whether its real domain is narrower (a string that is actually one of 4 modes, a number that must be 1-100), whether it is truly required, whether its description would let a newcomer produce a valid value, and misuse evidence from transcripts (wrong shapes the model has actually sent). Rank the tools by misuse frequency. Deliver the audit table with a proposed tightened type for every weak parameter.

Paste into EmergentFull Build: complete implementation prompt with explicit requirements

Quick is short. Full Build is recommended for most steps. Strict forces real logic when the AI keeps faking output.

Actual change check

Expected after this step

A parameter-level audit with proposed tightened types.

Should NOT happen

An existing feature broke
A button only logs to console
Data disappears after refresh
Errors fail silently with no visible state

This is what should exist before you continue. If reality does not match, do not move on.

Your notes for this step

Track what changed, failed, or needs follow-up. Notes export with the flow.

Pass the Verify Gate to complete this step

Verify before continuing

Do not move on until every check is true. The complete button stays locked until then.

Every parameter assessed against its real domainTranscript misuse evidence attachedTightening proposals concrete

Do not continue if…

! Stringly-typed everything, inviting the model to improvise
! Optional parameters that are actually required, causing silent wrong behavior
! Extra invented parameters absorbed silently by permissive parsing
! Validation errors like 'invalid input' that teach the model nothing

If the AI messes this up

Use this when:

- it only made visual forms or placeholder UI
- buttons do nothing or only log to console
- data is not persisted - state disappears on refresh
- something that worked before is now broken

Use this when the AI fakes progress or breaks the feature. It forces a real fix.

The audit says everything is fine but misuse continues. Pull 10 failed tool calls from transcripts and work backwards - each failure traces to a constraint the schema failed to express.