Public methodology · open recordHow we know a prompt is safe to ship.
Loddle does not run a prompt marketplace. Every prompt in the library passes four quality gates before publication: schema validation, automated citation-detection validation of every sample output, per-niche safety architecture embedded in every copy, and a transparency badge showing real generation metadata. This page describes what each gate actually does.
Quality gates
4
Schema · generation · safety · transparency
Model
Claude
Sample generation model
Prompts
150
Across 4 professional niches
Schema gate
CI
Every build, automatically
§ 01 · The four quality gates
Every prompt clears four gates before it ships.
The same four gates apply to a Basic admin-efficiency prompt and an Advanced equitable-adjustment letter. The difference is the height of the bar at each gate, not the number of gates.
Quality gate · empirical test01
Tested with a dedicated generation script — validated on every build.
Every Loddle prompt has a sample output generated by Claude using a niche-specific safety system prompt, produced by a dedicated generation script — not automatically on every build. Outputs that contain professional codes (CPT, ICD-10, FRCP, ASTM, and similar) are checked by an automated citation-detection validator on every build; where automated regeneration was not possible, the affected sample was manually redacted to a placeholder pending regeneration.
Sample generation · dedicated script; citation check · every build
Citation detection
Outputs containing professional code citations (CPT, ICD-10, FRCP, ASTM, etc.) are checked automatically on every build. Where automated regeneration was not possible, the affected sample was manually redacted to a placeholder.
Scope
Every prompt in the library — all 150 across all four niches — goes through the same generation pipeline.
Transparency
The model name and generation date are stored with each sample and displayed on every prompt page via the transparency badge.
Quality gate · contract & format02
Structured to a validated schema.
Every prompt is validated against a JSON schema enforced by the prebuild CI step. The schema requires role assignment, task definition, a constraints array, an uncertainty instruction, a disclaimer, and a minimum number of FAQ entries. A prompt that fails schema validation blocks the build — it cannot reach the library.
Schema validation · every build, automatically
Required fields
- ·Role — who the AI is being asked to play
- ·Task — what the user wants out
- ·Constraints — what the AI must not do
- ·Uncertainty instruction
- ·Professional disclaimer
- ·FAQ entries
Enforcement
JSON schema validation in the prebuild script. A prompt cannot reach the library without passing schema validation.
Gate
The validate-prompts.ts script runs automatically before every build via the npm prebuild lifecycle hook.
Format
Plain text. No model-specific syntax. Output is portable across model providers.
Quality gate · domain safety03
Per-niche safety architecture baked in — and embedded in what you copy.
Every prompt carries constraints written for its specific profession: a lawyer's billing-narrative prompt knows what a contingency arrangement is; a contractor's RFI prompt knows what a CCD is; a healthcare-admin patient-comms prompt knows what HIPAA permits in a status email. Those constraints, the uncertainty instruction, and the professional disclaimer are not just displayed — the Copy prompt button embeds them directly in the text you copy, so the model always receives them regardless of where you paste it.
Niche constraints · embedded in every copy
Scope locks
Every prompt declares its profession scope. Cross-domain use is flagged on the prompt page.
Embedded constraints
Safety constraints, uncertainty instruction, and disclaimer are prepended to the prompt text you copy — the model always receives them regardless of where you paste the prompt.
Direct handoff
Most prompt pages also offer "Open in Claude" / "Open in ChatGPT" links that pre-fill the prompt text directly — a shortcut, not a replacement for Copy prompt, since URL length limits mean the safety layer travels with the copy, not always with the link. There is no in-product execution: Loddle never sees your inputs or the model's output.
Out-of-scope flag
If your matter falls outside the prompt's declared scope, the prompt page tells you so before you copy.
Quality gate · transparency04
Confidence tiers reflect the stakes — with honest disclaimers.
Confidence tiers — Basic, Professional, Advanced — reflect the stakes of the task and are displayed on every prompt. Every prompt carries a profession-appropriate disclaimer; the language is consistent across the library to avoid drift. The transparency badge on each prompt page shows the model used, the generation date, and the confidence tier — all drawn from real data.
Confidence tier · displayed on every prompt
Confidence tiers
- ·Basic — routine, lower-stakes administrative tasks
- ·Professional — practice-grade tasks; review before use
- ·Advanced — high-stakes; use with professional review
Disclaimer
Each prompt carries a profession-appropriate disclaimer; the language is fixed across the library to avoid drift.
Transparency badge
Shows the model name (Claude), generation date, and confidence tier — sourced from the prompt data, not authored by hand.
Liability
Loddle's terms make clear: every output is informational; final professional judgement is required for every deliverable.
§ 02 · The pipeline
From authored prompt to published page.
Every prompt follows the same pipeline. Schema validation blocks the build on any failure; sample generation is run via a dedicated script, and its output is re-validated automatically on every build; nothing ships without passing both gates.
Step 1in pipeline
Prompt is authored and curatedDrafted with profession-specific constraints, an uncertainty instruction, and a professional disclaimer. Declared variables are enumerated so you can fill them in.
Curator · profession-focused
Step 2in pipeline
Schema validation gateThe validate-prompts.ts prebuild script checks every required field. Any failure blocks the build — the prompt cannot reach the library.
Automated · prebuild CI
Step 3in pipeline
Sample generation (dedicated script)Claude generates a sample output using the niche safety system prompt, run via a dedicated generation script. Outputs containing professional code citations are checked automatically on every build; where automated regeneration was not possible, the sample was manually redacted to a placeholder.
Manual run · generate-samples.ts
Step 4in pipeline
Published with transparency badgeThe prompt ships with its model name, generation date, confidence tier, and embedded constraints visible on the prompt-detail page.
System · CI / publishing
The library stays small because nothing ships until it clears every gate.
LoddleOpen any prompt. Read the metadata.
Every prompt-detail page shows the model, generation date, confidence tier, and embedded safety constraints. You can read exactly what the AI was told before you decide whether to trust it with client work.