← ClaudeAtlas

prompt-craftlisted

Use when writing, tightening, evaluating, or repairing an LLM prompt or reusable prompt template for completion, agent dispatch, grading, structured extraction, tool use, or prompt-engineered workflows. Covers instruction hierarchy, message roles, context placement, few-shot examples, structured output, positive constraints, reasoning guidance, prompt-injection resistance, provider differences, and eval-driven iteration. Do NOT use for whole context-system design (use context-engineering), eval dataset or grader design (use agent-eval-design), reviewing generated code (use code-review), authoring SKILL.md files (use skill-scaffold), choosing which skill or agent should activate (use skill-router), or root-causing a deployed failure after outputs already exist (use debugging).
jacob-balslev/skills · ★ 0 · AI & Automation · score 73
Install: claude install-skill jacob-balslev/skills
# Prompt Craft ## Coverage This skill covers portable prompt design for LLM-backed tasks and agents: - Instruction hierarchy and message roles: where stable policy, developer rules, user requests, examples, and variable input belong. - Prompt anatomy: task statement, context, constraints, examples, input delimiters, output cue, refusal or escalation rule, and verification plan. - Context placement: what belongs in the prompt template versus the surrounding context, retrieval, memory, tool output, or runtime config. - Few-shot examples: choosing boundary examples, counterexamples, and diverse cases that teach the pattern without leaking private data. - Output-format discipline: schema-shaped responses, enum outputs, concise prose, tables, JSON, Markdown, validation, retries, and fallback behavior. - Positive constraints and negative boundaries: replacing vague prohibitions with explicit target behavior while retaining safety-critical refusals. - Reasoning guidance: when to ask for concise rationale or internal carefulness, when to avoid visible reasoning, and when provider effort controls are the better lever. - Adversarial-input resistance: separating instructions from user data, validating outputs, limiting tool authority, and routing security-sensitive controls to guardrails. - Iterative improvement: hold eval cases fixed, change one prompt surface at a time, measure behavior, and document the delta. - Provider differences: OpenAI, Anthropic, Gemini, and open-weight mode