create-enaible-prompt

To generate deterministic prompts from templates, you supply a required template key and a discovery-time payload containing fields like prompt_id and purpose, which renders consistent layouts and guardrails into a shared prompts directory.

The best way to version shared prompts is to re-run the generation process using a template registry, producing deterministic outputs that can be diffed and version-controlled when underlying templates change across projects.

Yes, jinja2 is a required dependency to automate prompt creation, acting as the rendering engine that integrates with the template registry to write final outputs to shared/prompts.

Required payload fields for automating shared prompt generation include prompt_id, template_key, purpose, summary_line, artifact_slug, required_vars, optional_vars, derived_vars, extra_instructions, workflow_steps, output_sections, and output_attachments.

Yes, you can use template variables to enforce consistent output structure by defining required_vars, optional_vars, and derived_vars in the payload, ensuring the rendered prompt maintains deterministic generation and layout.