---
id: "prereq-basic-prompting"
type: "prereq"
source_timestamps: ["00:01:14"]
tags: ["prompt-engineering", "fundamentals"]
related: ["framework-skill-anatomy"]
reason: "Writing the 'Instructions' section of a Skill requires the ability to write clear, constrained, and formatted prompts."
sources: ["alex"]
sourceVaultSlug: "claude-skills-content-automation-2026May14"
originDay: 1
---
# Basic Prompt Engineering

## What you need to know first

Foundational prompt engineering — the ability to author clear, constrained, well-formatted prompts. Without this, the Instructions layer of [[framework-skill-anatomy]] becomes the weakest link.

## Specific sub-skills assumed

- **Negative constraints** — phrasing what the model must *not* do (no emojis, no hedging, no marketing clichés).
- **Output formatting** — requesting specific structures (markdown tables, numbered lists, JSON blocks).
- **Multi-step reasoning** — chaining steps in a single instruction block.
- **Few-shot prompting** — providing input/output pairs to calibrate tone (this becomes the Examples layer of a Skill).
- **Role and tone setting** — concise persona framing.

## Why this matters

The Frontmatter of a Skill handles routing — see [[claim-description-importance]]. But once a Skill *fires*, the Instructions block is what actually drives output quality. A creator with strong prompt fundamentals will get materially better results from the same Skill template.