prompting
Skill9 starsChanged 7 months agoMITView on GitHub
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.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- LarsLrn/orcaitheir own version, first seen Nov 8, 2026
- samchon/ttsctheir own version, first seen Oct 17, 2026
- saffron-health/opencode-guitheir own version, first seen Oct 9, 2026
- cashew-labs/librettotheir own version, first seen Aug 18, 2026
- saffron-health/librettotheir own version, first seen Aug 18, 2026
- mj-deving/pai-skillstheir own version, first seen Apr 27, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- cashew-labs/libretto★ 898same name
- saffron-health/libretto★ 883same name
- samchon/ttsc★ 364same name
- saffron-health/opencode-gui★ 59same name
- LarsLrn/orcai★ 2same name
- mj-deving/pai-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository140 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- alex-hormozi-pitchSkill
- AlgorithmSkill
- AnnualReportsSkill
- ArtGeneratorSkill
- artSkill
- autoplanSkill
- autoresearchSkill
- benchmarkSkill
- brainstormingSkill
- brand-guidelinesSkill
- brightdataSkill
- browseSkill
- BugHunterSkill
- CallIntelligenceSkill
- canarySkill
- canvasSkill
- carefulSkill
- ceo-advisorSkill
- cfo-advisorSkill
- cmmcSkill
- codebase-indexerSkill
- codexSkill
- CodingAgentSkill
- company-valuesSkill
- connect-chromeSkill
- CORESkill
- system-createcliSkill
- CreateskillSkill
- csoSkill
- cto-advisorSkill
- CybersecurityPlaybooksSkill
- defuddleSkill
- design-consultationSkill
- design-reviewSkill
- DevTeamSkill
- DiscordAdminSkill
- document-releaseSkill
- document-writerSkill
- doraSkill
- dpdpaSkill
- EmailManagerSkill
- executing-plansSkill
- fabricSkill
- fedrampSkill
- ffuf-web-fuzzingSkill
- find-communitySkill
- first-customersSkill
- FirstPrinciplesSkill
- form-croSkill
- freezeSkill
- gdpr-complianceSkill
- git-worktreesSkill
- GovernanceSkill
- grow-sustainablySkill
- gstack-upgradeSkill
- guardSkill
- hipaa-complianceSkill
- investigateSkill
- iso27001Skill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 26
Every token depletes capacity
- Distinctive: line 27
Treat context as precious
- Distinctive: line 35
Use lightweight identifiers vs full data dumps
- Distinctive: line 41
Use clear semantic sections:
- Distinctive: line 64
Don't load full data dumps - use references and load when needed
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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"
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

