WENCESTUDIO
01Prompt Anatomy 3D
SEARCH
How to use these references

The templates and anatomy mappings are WenceStudio teaching examples. Core guidance was reviewed on September 8, 2026; product access and features can change. Follow each provider’s source for current requirements. These tools assemble prompts locally and do not run an AI model.

PRACTICAL TOOLKIT / TEMPLATE LIBRARY

Start with a
working structure.

Adapt a reusable prompt for a real task, then test its structural completeness before using it.

FILTER BY USE CASE
LearningUniversal

Training Module

Turn approved source material into a structured, reviewable learning module.

Act as an instructional designer. Create a training module from the approved source material.

Audience: [Learner group]
Objective: [Observable learning objective]
Sources: [Approved documents]
Constraints: Preserve every safety and compliance requirement. Flag missing or conflicting information.
Output: Module outline, facilitator notes, learner activity, and five-question knowledge check.
Verification: Confirm every requirement is traceable to a supplied source.
OperationsChatGPT Work

SOP Builder

Create a controlled procedure with roles, hazards, and verification gates.

Create a standard operating procedure for [task]. Use the attached documents as the source of truth.

Audience: [Role]
Required roles: [People required]
Constraints: Do not invent steps. Preserve all safety requirements and approvals.
Output: Purpose, scope, PPE, responsibilities, numbered steps, hazards, and verification checklist.
Verification: Flag any missing, conflicting, or unsupported requirement for human review.
AnalysisClaude

Evidence Analysis

Separate source-supported findings from interpretation and uncertainty.

Analyze the supplied documents to answer [decision question].

First identify the most relevant evidence. Separate reported facts, analysis, and unresolved questions. Do not infer missing numbers or events.

Return a findings table with source, evidence, implication, confidence, and required follow-up. Flag conflicts for human review.
DevelopmentCodex

Focused Code Change

Define a repository change with scope controls and completion checks.

Goal:
[Describe the behavior to add, change, or repair.]

Context:
[Relevant files, errors, examples, and documentation.]

Constraints:
Preserve the current architecture and existing behavior. Keep the change focused. Do not add unrelated dependencies.

Done when:
[Tests, observable behavior, accessibility, and validation checks.]
CommunicationUniversal

Leadership Brief

Convert complex material into an executive-ready decision brief.

Act as a senior operations analyst. Turn the supplied material into a concise leadership brief.

Audience: [Leadership group]
Decision needed: [Decision]
Constraints: Preserve approved dates, figures, and requirements. Do not present assumptions as facts.
Output: TL;DR, key evidence, risks, decisions required, and action table with owners and dates.
Verification: Identify every unsupported or unresolved item.
StrategyChatGPT

AI Workflow Diagnostic

Map repetitive work, human judgment, risk, and automation opportunities.

Analyze the current workflow for [process].

Document the trigger, inputs, steps, tools, decisions, handoffs, outputs, and failure points. Identify repetitive work suitable for AI assistance and decisions that must remain human-controlled.

Return the current-state map, friction points, proposed future state, guardrails, approval gates, and a prioritized implementation plan.
ProductivityGemini

Workspace Action Plan

Use the Persona, Task, Context, and Format structure for workplace planning.

Persona: Act as a practical project coordinator.
Task: Create an action plan for [initiative].
Context: Use the supplied notes, dates, stakeholders, and constraints. The plan is for [audience].
Format: Return milestones, owners, due dates, dependencies, risks, and the next three actions.
Verification: Flag missing ownership, dates, or source information.
GovernanceUniversal

Prompt Governance Review

Evaluate a prompt before it enters a repeatable or high-risk workflow.

Review the prompt and intended workflow for governance risk.

Assess data sensitivity, source authority, allowed tools, prohibited actions, human approval points, verification requirements, recordkeeping, and escalation conditions.

Return a risk classification, identified gaps, required controls, approved-use conditions, and a clear human-review checklist.

STRUCTURAL CHECK / PROMPT ANALYZER

Find what your prompt
is missing.

This keyword check detects possible structural signals. It can miss good prompts or reward irrelevant words; it does not evaluate prompt quality or factual accuracy. Important outputs still require source verification and human judgment.

OFFICIAL REFERENCE / OPENAI PROMPTING

One foundation.
Three working modes.

OpenAI uses a shared prompting foundation across ChatGPT, ChatGPT Work, and Codex, supported by product-specific guidance. Use only the structure that materially improves the result.

01Goal

What should ChatGPT or Codex accomplish?

02Context

What information, files, sources, or errors matter?

03Output

What format, length, audience, or detail is required?

04Boundaries

What must remain unchanged, be avoided, or require approval?

05Verification

What should be checked before the work is finalized?

NOT A RIGID FORMULA

A short prompt can be effective. More structure becomes useful when work is important, complex, multi-step, or high risk.

PROMPT BLUEPRINT

ChatGPT

GoalContextOutputBoundariesVerification
REUSABLE TEMPLATE
Goal:
[Describe the result you need.]

Context:
[Provide the relevant background, source material, and audience.]

Output:
[Specify the format, length, structure, and level of detail.]

Boundaries:
[State what must remain unchanged, what to avoid, and what not to assume.]

Verification:
[Explain what should be checked before the response is finalized.]
WORKED EXAMPLE
Turn the attached training notes into a one-page update for department leaders.

Put decisions, compliance risks, and next steps first. Preserve all approved dates and safety requirements. Flag missing or unsupported information instead of guessing.

Before finalizing, confirm that every action item has an owner and due date.
PRACTICE NOTE

Short prompts are often enough. Add structure when the task is important, complex, or high risk.

OpenAI official sources 6 guides · expand to explore

OFFICIAL REFERENCE / ANTHROPIC

Claude prompting.
From chat to agentic work.

Explore Anthropic's primary documentation for Claude AI, Claude Code, Cowork, and prompt engineering. Every linked source is published by Anthropic or its official GitHub organization.

PRIMARY SOURCE LINKS · CHECK PRODUCT AVAILABILITY
OPERATING PRINCIPLE
Be clear and direct. Add only the context, examples, structure, and constraints that materially improve the result.
01
Clarify the outcome

State the desired result, format, scope, and constraints explicitly.

02
Explain useful context

Tell Claude why the instruction matters and provide the information that changes the answer.

03
Demonstrate the pattern

Use relevant, diverse examples. XML tags can separate instructions, context, examples, and inputs.

04
Ground long documents

Place long source material before the request, then ask Claude to quote relevant passages before completing the task.

05
Control the scope

For coding work, request the minimum necessary change and discourage unrequested files, abstractions, documentation, or defensive logic.

IMPLEMENTATION NOTE

Prompt guidance changes as Claude models change. Check the model-specific section before moving a production prompt to a newer model.

Anthropic official sources 9 guides · expand to explore
SOURCE RIGOR

Community handbooks, Medium articles, and unofficial repositories may be useful commentary, but they are not treated here as documentation. Cite the official Claude Platform, Claude Code, Claude, Support, and Anthropic GitHub sources above when building WenceStudio prompts, skills, or governance materials.

OFFICIAL REFERENCE / GOOGLE GEMINI

Prompt design.
From Workspace to Spark.

Explore Google's primary guidance for Gemini in Workspace, the Gemini API, and Gemini Spark. The experience separates documented Google frameworks from WenceStudio's applied workflow patterns.

PRIMARY SOURCE LINKS · CHECK PRODUCT AVAILABILITY
OPERATING PRINCIPLE
Start with the task, then add the persona, context, and format that materially improve the result. Not every prompt needs all four pillars.
01
Persona

Define who Gemini should act as or the professional perspective it should apply.

02
Task

State the exact action with a clear, direct verb. This is the essential pillar.

03
Context

Supply the background, audience, source material, and constraints that bound the work.

04
Format

Describe how the result should be organized, such as a table, email, brief, or checklist.

IMPLEMENTATION NOTE

Google presents Persona, Task, Context, and Format as helpful areas, not a mandatory formula. A concise, specific task may be enough.

01Persona
02Task
03Context
04Format
Google official sources 9 guides · expand to explore
SOURCE RIGOR

Google documents Tasks, Schedules, and Skills as Gemini Spark's building blocks. The Trigger, Sources, Action, and Review Boundary pattern above is a WenceStudio synthesis for implementation. Community references, including DAIR.AI, are excluded from the official source map.