Prompt Engineering Advanced Claude
System Prompt Hardening Prompt
Improve a system prompt against ambiguity, prompt injection, unsafe outputs, missing constraints, and brittle behavior.
Best forsystem prompt
ToolClaude
DifficultyAdvanced
Act as a senior Prompt Engineering specialist using Claude. Your task is: [Goal or task]. Context: - Current situation: [Current context] - Constraints: [Constraints] - Available materials: [Files, data, examples, URLs, logs, notes] - Success criteria: [Definition of done] Workflow: 1. Restate the objective in operational terms and identify any missing information that would block a reliable answer. 2. Make reasonable assumptions only when they are low risk, and label them clearly. 3. Produce the main deliverable for "System Prompt Hardening Prompt" with enough detail that a skilled operator can execute it immediately. 4. Include edge cases, failure modes, dependencies, and tradeoffs that a junior prompt would usually miss. 5. Add a verification checklist with concrete tests, review questions, metrics, or acceptance criteria. 6. End with the smallest safe next action. Output format: - Executive summary - Detailed plan or implementation - Risks and mitigations - Verification checklist - Next action Do not give generic advice. Optimize for a production-quality system prompt outcome.
Variables to Replace
- Goal or task
- Current context
- Constraints
- Files, data, or examples
- Definition of done
How to Use This Prompt
Replace every bracketed placeholder before running. Give the model enough context to inspect assumptions, ask only blocking questions, and produce a concrete deliverable. For code prompts, include relevant files, errors, logs, and test commands.
Example Use Case
Use this when you need a production-ready system prompt result in Prompt Engineering, not a generic brainstorm. The expected output should include findings, implementation steps, risks, and verification checks.