# Adaptive Prompt Architect — Output Templates

## 1. Universal Serious-Project Prompt

```markdown
# Task Prompt

## Role
You are <target role>.

## Objective
<Concrete task goal.>

## Context
<Relevant project context.>

## Source-of-Truth Hierarchy
1. <Current operator instruction>
2. <Uploaded files / references>
3. <Style guide / examples>
4. <Prior drafts>
5. <Inference>

## Inputs
- <Input 1>
- <Input 2>

## Requirements
- <Requirement>
- <Requirement>

## Constraints / Non-Goals
- <Constraint>
- <Do not do>

## Planning Requirements
Before producing the final deliverable, provide a concise visible plan covering:
- assumptions
- execution sequence
- decision criteria
- risks / edge cases
- validation approach

Do not reveal hidden chain-of-thought.

## Output Format
<Exact deliverable structure.>

## Validation Checklist
- <Check>
- <Check>

## Failure Modes to Avoid
- <Drift risk>
- <Misinterpretation risk>
```

---

## 2. Coding / Implementation Prompt

```markdown
# Coding Implementation Prompt

## Role
You are a senior <language/framework> engineer.

## Objective
<Implementation objective.>

## Technical Context
- Stack:
- Runtime:
- Framework:
- Existing files:
- Constraints:

## Requirements
- <Functional requirement>
- <Functional requirement>

## Architectural Blueprint
Before writing code, provide a concise blueprint covering:
1. state management approach
2. core data flows
3. dependencies and interfaces
4. edge cases
5. failure modes
6. validation / test plan

Do not reveal hidden chain-of-thought. Provide only the useful planning artifact.

## Implementation Rules
- Preserve existing behavior unless explicitly changed.
- Avoid unnecessary dependencies.
- Identify file changes clearly.
- Do not perform destructive actions without approval.

## Output Format
Return:
1. Architecture summary
2. File change list
3. Code / patch
4. Test commands
5. Validation checklist
```

---

## 3. Design / Image Prompt

```markdown
# Image / Design Generation Prompt

## Visual Source of Truth
Use the uploaded images/style guide as the visual source of truth for:
- style
- palette
- composition
- typography
- materiality
- mood

## Objective
Create <number> <format> images/assets for <use case>.

## Format Requirements
- Size:
- Aspect ratio:
- Output count:
- File naming:

## Composition
<Composition rules.>

## Style Requirements
- <Style rule>
- <Style rule>

## Text Requirements
<Exact text rules, or “no text.”>

## Color / Accent Rules
<Color/palette constraints.>

## Do Not Include
- <Exclusion>
- <Exclusion>

## Final Quality Bar
<How the asset should feel and what it must communicate.>
```

---

## 4. Research / NotebookLM Source-Search Prompt

```markdown
# Research Source Search Prompt

## Research Objective
Find high-quality sources on <topic> for <notebook/project purpose>.

## Source Priority
Prioritize:
- official documentation
- primary sources
- maintained repositories
- current technical guides
- credible case studies
- provider documentation

## Search Queries
1. <Query>
2. <Query>
3. <Query>

## Inclusion Criteria
- <Criterion>

## Exclusion Criteria
- <Criterion>

## Expected Synthesis
Return:
1. best sources
2. why each source matters
3. what notebook section it supports
4. coverage gaps
5. next search queries
```

---

## 5. Agent / Workflow Protocol Prompt

```markdown
# Agent Protocol Prompt

## Agent Role
You are <agent name/role>.

## Operating Context
<Context and domain.>

## Activation / Commands
- `/command` — <behavior>

## State Rules
- <State rule>

## Approval Gates
State-changing actions require:
1. preview
2. conflict/risk register
3. explicit operator approval
4. post-action log/savepoint

## Handoff Rules
<How this agent sends/receives work.>

## Output Contract
<Exact format.>

## Failure Modes
Avoid:
- <Failure mode>
```