dragon prompt: prompt writing

Define the prompt-authoring brief behind dragon prompt

For Dragon Prompt, state the subject, environment, action objective, emotional beat, and end condition in plain production language. These invariants keep general prompt planning variants comparable instead of producing unrelated ideas. Clarify the intended medium and outcome, then write subject, action, context, composition, constraints, and an observable end condition. Prefer concrete relationships over adjective lists, and separate facts from proposed visual treatment. Write the decision owner and intended handoff beside the brief so a search phrase cannot be mistaken for a verified product capability or an instruction that has already been executed. At handoff, preserve the test fixture, and ask the accessibility reviewer to record reversal cost before the production checkpoint.

Apply the general prompt planning structure

Turn the phrase into a production brief with a medium, subject, action, setting, composition, ordered beats, constraints, and a reviewable end state. Separate the durable creative direction from syntax that belongs to a particular interface. This makes the prompt useful even when tools, model names, or accepted parameters change. For “dragon prompt”, keep a visible distinction between required content, optional treatment, exclusions, and facts that need evidence. That structure gives controlled variants a stable baseline and lets a reviewer identify which instruction caused a material change. At handoff, preserve the rights memo, and ask the source custodian to record temporal order before the release review.

• Subject and action Before revision, preserve the source ledger, and ask the claims reviewer to record temporal order before the final sign-off.
• Composition and beat order Before revision, preserve the brief version, and ask the channel editor to record destination fit before the final sign-off.
• Constraints and end state Before revision, preserve the review copy, and ask the release approver to record control availability before the final sign-off.

Prepare authorized inputs for character and fictional visual design

This query calls for an original or licensed character brief, silhouette, setting, action, reference rights, tone, and the visual details that must remain consistent. Build from shape, pose, material, expression, palette, staging, and action rather than relying on an unexplained style label. Identify what is original, referenced, or merely proposed. Record the source, permission, intended audience, protected details, and reviewer before testing language. The goal is a traceable creative proposal, not an assumption that a named platform, model, or workspace will perform the requested action. At this stage, preserve the input snapshot, and ask the identity reviewer to record claim scope before the reversible handoff.

Build controlled variants and observable acceptance checks

For this owner, the first review pass should make dragon observable rather than merely decorative. Change one meaningful dimension per version and label the hypothesis, invariant details, expected difference, and rejection condition. The prompt is ready for review when every phrase changes a meaningful decision, contradictions are removed, and a second reader can describe the expected result without inventing missing context. Keep failed variants in the decision record so the final wording is explainable rather than selected by impression alone. Before moving on, preserve the failure note, and ask the accessibility reviewer to record claim scope before the fallback decision.

Review authorization, safety, and changing product facts

Do not imply rights to a character, franchise, artist style, or reference image; verify licenses and avoid deceptive real-person identity transfer. Use only authorized source material, preserve attribution and provenance, avoid deceptive identity or factual claims, and verify any changing product or platform statement in current first-party documentation. Treat every named model, competitor, access term, platform rule, identity use, commercial claim, and output specification as a dated evidence question. If authorization or first-party support is missing, keep the language editorial, stop the handoff, and record the unresolved gap instead of inventing a workaround. For this checkpoint, preserve the input snapshot, and ask the production lead to record temporal order before the delivery pass.

Approve a reversible prompt handoff

Read the prompt once for intent, once for visual or temporal coherence, and once for rights and factual risk. Remove decorative terms that do not change an observable decision, then test controlled variants rather than rewriting every instruction at the same time. Before approving “dragon prompt”, check purpose, source rights, identity consent, factual support, continuity, disclosure, destination requirements, and the named review owner. Preserve the original brief and version notes. This handoff supplies authored guidance only and neither runs generation nor guarantees access, quality, speed, licensing, publishing, downloads, or outcomes. For this checkpoint, preserve the brief version, and ask the rights reviewer to record source fidelity before the delivery pass.