Prompt Recipes
Natural language prompts for common PromptWire workflows. No tool names to memorise.
You don't need to know PromptWire's tool names. Describe what you want in plain language and the agent selects the right tools, sequences the operations, and previews everything before applying.
Site inspection
Get an overview
Check the site health.
List all templates.
Show me the fields on the blog_post template.
Find content
Show me the page at /about/.
Find all pages using the blog_post template.
Search for pages containing "privacy policy".
Inspect schema
Export the full site schema as YAML.
Show me the details of the body field.
Content editing
Pull and edit
Pull the About page to a local file.
Pull all blog posts.
Rewrite the About page body to be more concise, then push the changes.
Push with preview
Push the About page changes. Show me what will change first.
Apply the About page changes.
Push all changes in the blog directory.
Push to production
Push the About page to production.
Push the About page to both local and production.
Page creation
Scaffold and publish
Create a new page called "FAQ" under /about/ using the basic-page template, with a title and a short body paragraph. Dry-run first.
Create three blog posts under /blog/posts/ with titles, summaries, and placeholder body content.
Publish the FAQ page to ProcessWire.
Build a section from scratch
Build a blog section at /blog/ with an index page and three sample posts. Posts should have a title, body, summary, and publish date. Dry-run everything first.
Schema management
Pull and compare
Pull the site schema.
Compare our local schema against production and flag anything that could cause problems if we pushed.
Show me the schema diff.
Push schema
Push the local schema to ProcessWire. Dry-run first.
Cross-environment workflows
Content deployment
Pull our About page, rewrite the body to be more concise, and push the changes to both local and production.
Validate all page references against production before pushing.
File sync
Sync files for the About page to production. Dry-run first.
Sync maintenance
Show me the sync status.
Reconcile the sync directory.
Tips
- Always use "dry-run first" when you're unsure. Every write operation supports it.
- The agent will choose tool parameters based on context. If you say "push to production", it sets
targets: "remote"automatically. - You can chain operations in a single prompt. "Pull, edit, push" works as a natural workflow.
- If a prompt doesn't do what you expect, be more specific about the path, template, or target.