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에서 보기