Skip to main content

prompting

Prompt engineering standards and context engineering principles for AI agents based on Anthropic best practices. Covers clarity, structure, progressive discovery, and optimization for signal-to-noise ratio.

来源信息

仓库
danielmiessler/PAIPlugin
最近来源活动
2025年10月25日 00:45
检测到的 SKILL.md 语言
英语
星标
56
分支
10

安装方式

默认使用会先检查来源的 Prompt;你也可以切换为直接命令,或下载本地副本。

检查来源文件

决定是否安装前,请先阅读 SKILL.md,以及 SkillsMP 当前展示的配套文件。

文件资源管理器
2 个文件

正在显示 SKILL.md

SKILL.md
来源说明 · 只读预览
name
prompting
description
Prompt engineering standards and context engineering principles for AI agents based on Anthropic best practices. Covers clarity, structure, progressive discovery, and optimization for signal-to-noise ratio.
# Prompting Skill ## When to Activate This Skill - Prompt engineering questions - Context engineering guidance - AI agent design - Prompt structure help - Best practices for LLM prompts - Agent configuration ## Core Philosophy **Context engineering** = Curating optimal set of tokens during LLM inference **Primary Goal:** Find smallest possible set of high-signal tokens that maximize desired outcomes ## Key Principles ### 1. Context is Finite Resource - LLMs have limited "attention budget" - Performance degrades as context grows - Every token depletes capacity - Treat context as precious ### 2. Optimize Signal-to-Noise - Clear, direct language over verbose explanations - Remove redundant information - Focus on high-value tokens ### 3. Progressive Discovery - Use lightweight identifiers vs full data dumps - Load detailed info dynamically when needed - Just-in-time information loading ## Markdown Structure Standards Use clear semantic sections: - **Background Information**: Minimal essential context - **Instructions**: Imperative voice, specific, actionable - **Examples**: Show don't tell, concise, representative - **Constraints**: Boundaries, limitations, success criteria ## Writing Style ### Clarity Over Completeness ✅ Good: "Validate input before processing" ❌ Bad: "You should always make sure to validate..." ### Be Direct ✅ Good: "Use calculate_tax tool with amount and jurisdiction" ❌ Bad: "You might want to consider using..." ### Use Structured Lists ✅ Good: Bulleted constraints ❌ Bad: Paragraph of requirements ## Context Management ### Just-in-Time Loading Don't load full data dumps - use references and load when needed ### Structured Note-Taking Persist important info outside context window ### Sub-Agent Architecture Delegate subtasks to specialized agents with minimal context ## Best Practices Checklist - [ ] Uses Markdown headers for organization - [ ] Clear, direct, minimal language - [ ] No redundant information - [ ] Actionable instructions - [ ] Concrete examples - [ ] Clear constraints - [ ] Just-in-time loading when appropriate ## Anti-Patterns ❌ Verbose explanations ❌ Historical context dumping ❌ Overlapping tool definitions ❌ Premature information loading ❌ Vague instructions ("might", "could", "should") ## Supplementary Resources For full standards: `read ${PAI_DIR}/skills/prompting/CLAUDE.md` ## Based On Anthropic's "Effective Context Engineering for AI Agents"
在 GitHub 查看