Prompt Guide

The fastest way to improve Alfrada outputs is to improve how you frame the task.

The Four-Part Formula

Strong prompts usually include:

1. Objective: what success looks like
2. Inputs: files, sources, accounts, or assumptions to use
3. Output: exact format, audience, and level of polish
4. Guardrails: constraints, risks, tone, and review standards

Prompting Patterns That Work

For analysis

Analysis pattern

Analyze [subject] using [sources/files]. Return the answer as [format]. Highlight assumptions, risks, and where the evidence is weak.

This encourages evidence-backed output instead of generic commentary.

For creation

Creation pattern

Create [deliverable] for [audience]. Use [inputs]. Match this tone: [tone]. Keep it within [constraints]. Give me a draft first, then suggest the highest-value improvements.

This creates better drafts and makes revision easier.

For automation

Automation pattern

Set up a repeatable workflow that checks [sources] on [cadence] and produces [output]. Escalate only if [trigger] happens.

Automation needs triggers, cadence, and output expectations to be explicit.

For coding

Coding pattern

Help me with [engineering task] in [repo/codebase]. First inspect the relevant files, explain the plan briefly, then implement or propose the change. Call out risks, testing needs, and edge cases.

This improves reasoning before execution and lowers the chance of low-quality blind edits.

Common Mistakes

• asking for "something good" without saying what good means
• mixing multiple unrelated jobs into one prompt
• forgetting to define the audience
• not naming the desired file or output format
• forcing long answers when you actually want a decision or a shortlist

One Great Habit

When a prompt works especially well, save it as a playbook. That turns a one-off success into a repeatable capability.