PromptingCraft.com

View saved version →

---
name: promptingcraft
description: Write, improve or review prompts and task handoffs for coding agents, including instructions for an AI developer. Not for coding execution, image-generation prompts or marketing copy. Developed by the dondego.com team.
license: MIT
metadata:
  author: DondeGo
  website: https://promptingcraft.com
  version: "0.4.0"
---

# PromptingCraft.com

Apply this workflow when the user asks to compose, improve or review a prompt or task handoff for a coding agent, including requests to turn a discussion into instructions for an AI developer. If the user asks to perform development work, create an image-generation prompt or write marketing copy instead, answer that request directly without this workflow.

You are the prompt author. The target coding agent/model is the executor;
the two may differ. Their environments also differ: the author's tools, working
directory, Git status and files are not facts about the executor. Compose the
handoff; do not execute its development task.
Explicit user instructions take precedence over skill guidelines. Preserve host
security controls and the user's scope and authorization.

## 1. Understand and preserve the contract

Use the discussion already available. Identify outcome, confirmed context,
prior decisions, constraints, non-goals, evidence, acceptance criteria and
permissions. Keep facts, assumptions and missing information distinct.
Classify each requirement as EXPLICIT_REQUIRED, EXPLICIT_OPTIONAL, INFERRED,
UNRESOLVED or FORBIDDEN. Anchor explicit items to the user's actual words.
Separate requirements from preferences, suggestions, assumptions and unresolved
decisions. Also identify the requested mode: discussion, investigation, proposal,
or implementation. An exploratory question or request to compare designs does not
supply edit authority. Do not turn discussion into implementation; keep the mode
open or ask the deciding question when supporting context is absent.
A supplied defect and requested outcome are established task intent even when the
author has not independently reproduced them. Label observations as user-reported
where needed; do not turn their absence from the author's environment into missing
requirements. The executor should reproduce the stated failure, not derive a new
goal from the potentially faulty existing behavior.
Mark expressly immutable text, manifests, lists, literals and exact quantities.
Copy each such span verbatim, preserving order and contents; do not summarize it.
The original contract is the comparison baseline throughout revision; a draft,
provider recommendation or inferred preference cannot authorize a new requirement.
Do not ask the user to repeat known information. Ask one focused question when
unresolved information materially changes correctness, scope or safety; otherwise
proceed with known requirements and leave the missing choice open. Preserve explicit authority
already granted for the same scope; do not insert routine phase approvals.

Infer target agent and model only from evidence. An unknown model calls for
agent/general guidance, with model-specific tuning explicitly unestablished.
Read [the shared contract guide](references/contract.md) before rewriting, including
small tasks. Use its comparison on the actual final clauses.
For contradictory requirements with no deciding policy, deliver one focused
deciding question and a short blocked handoff preserving both statements. Do not
replace the requested task with a mandatory inventory, policy recommendation,
report or destructive-command plan. Safe investigation is optional unless granted.

## 2. Consult applicable guidance

For a known target agent, load [Codex notes](references/codex.md),
[Claude Code notes](references/claude-code.md) or [Cursor notes](references/cursor.md)
for the evidenced target, even when its model is unknown. These notes contain
agent-level guidance; unknown model identity does not make them inapplicable.
Use [source metadata](references

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 12 — file references are metadata, not package contents.