prompt-engineering
Skill2 starsChanged 6 months agoMITView on GitHub
Prompt engineering knowledge base — technique taxonomy with decision tree, prompt template patterns and formatting conventions, OWASP LLM Top 10 security checklist, eval frameworks and testing guide, context engineering, structured output contracts, multi-agent orchestration patterns, cost optimization. Use when designing prompts, reviewing prompt quality, building AI features, creating AI assets, or auditing LLM security.
89 other projects use a version of this.
Adopted by
Most recently taken up by
- AtilaMedeiros/skillstheir own version, first seen Nov 16, 2026
- exmarin/claude-skillstheir own version, first seen Nov 16, 2026
- Ivan-propio/claude-skillstheir own version, first seen Nov 16, 2026
- niki914/zafirotheir own version, first seen Nov 15, 2026
- lengrufeng2008/dsh-skill-librarytheir own version, first seen Nov 15, 2026
- Muvon/octomind-taptheir own version, first seen Nov 12, 2026
Used with
Projects with it also use security-checklist, multi-agent-orchestration and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
atuljha23Skillsecurity-checklist
OWASP-style quick reference — authn/authz, injection, secrets, sessions, crypto, dependencies. Use during code review and before committing security-sensitive changes.
Also in 3 projects that use this
javalenciacaiSkillmulti-agent-orchestration
Design and coordinate multi-agent systems where specialized agents work together to solve complex problems. Covers agent communication, task delegation, workflow orchestration, and result aggregation. Use when building coordinated agent teams, complex workflows, or systems requiring specialized expertise across domains.
Also in 4 projects that use this
xfstudioSkillllm-evaluation
Implement comprehensive evaluation strategies for LLM applications using automated metrics, human feedback, and benchmarking. Use when testing LLM performance, measuring AI application quality, or establishing evaluation frameworks.
Also in 3 projects that use this
GoogleSkillcoding-principles
Enforces engineering, architecture, public API, and code quality standards distilled from human reviewer feedback across A2UI pull requests. Use when authoring new code, refactoring, addressing review feedback, or reviewing PR diffs. Don't use for release publishing or spec blueprint generation without code or PR changes.
Also in 3 projects that use this
pproencaSkillrefactoring
Code refactoring best practices based on Martin Fowler's catalog and Clean Code principles. This skill should be used when refactoring existing code, improving code structure, reducing complexity, eliminating code smells, or reviewing code for maintainability. Triggers on tasks involving extract method, rename, decompose conditional, reduce coupling, or improve readability.
Also in 6 projects that use this
mjunaidcaSkilltool-design
Design tools that agents can use effectively. Use when creating new tools for agents, debugging tool-related failures, or optimizing existing tool sets.
Also in 3 projects that use this
Other versions89 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 89
- trycompai/comp★ 2.1ksame name
- niki914/zafiro★ 371same name
- CodeAlive-AI/ai-driven-development★ 184same name
- grandamenium/cortextos★ 106same name
- nahid-sparktales/agent-dispatcher★ 59same name
- geekatron/jerry★ 37same name
- nimadorostkar/Claude-Skills-collection★ 37same name
- Bbar0n234/learnflow-ai★ 35same name
- sabahattink/antigravity-fullstack-hq★ 30same name
- VoDaiLocz/kilo-kit-mcp★ 27same name
79 more not listed
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 repository40 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- ai-skillsSkill
- analyze-localSkill
- analyze-prodSkill
- analyzeSkill
- architectureSkill
- asset-validationSkill
- blog-postSkill
- bugfixSkill
- cloud-platformsSkill
- code-reviewSkill
- content-creationSkill
- context-engineeringSkill
- create-prSkill
- deployment-proceduresSkill
- deploy-productionSkill
- deploy-stagingSkill
- docsSkill
- feature-devSkill
- geo-writerSkill
- humanizerSkill
- infra-changeSkill
- marketing-operationsSkill
- marketingSkill
- ml-pipelineSkill
- planSkill
- pre-commitSkill
- productSkill
- project-initSkill
- qaSkill
- releaseSkill
- run-testsSkill
- security-scanSkill
- seo-reviewSkill
- social-media-managerSkill
- test-localSkill
- test-strategySkill
- ui-ux-designSkill
- worktree-isolationSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 78 edited versions we read keep these.
2
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 55
Grounding: Prefer citations and verifiable data over unanchored claims
- Distinctive: line 57
Cost awareness: Every token costs money and time.
“Common” is measured: kept by at least 6 in 10 of the 78 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
Prompt Engineering
Comprehensive prompt engineering knowledge base. Provides actionable patterns, checklists, and guides for designing, securing, evaluating, and optimizing LLM prompts and agent systems.
When to Use
- Designing or reviewing prompt templates (system, developer, user prompts)
- Building tool calling schemas and structured output contracts
- Evaluating prompt quality — accuracy, safety, cost, latency
- Auditing LLM security against OWASP LLM Top 10
- Designing multi-agent orchestration and handoff protocols
- Optimizing prompt cost and latency
- Creating or reviewing Codex AI assets (rules, workflows, skills — all are prompts)
- Setting up prompt versioning and observability
When NOT to Use
- Implementing backend/frontend code (use
software-engineerrole + stack-specific role) - Infrastructure and deployment (use
devops-engineerrole) - Writing code tests (use
qa-engineerrole +test-strategyskill) - Content writing (use
content-writerrole) - Context pipeline design, memory engineering, agent harness, RAG architecture, multi-agent orchestration, production AI checklists → use
context-engineeringskill
Key Concepts
Prompt as System
A prompt is not a string — it is a system composed of:
- Instruction hierarchy: System prompt > Developer prompt > User prompt > Retrieved content
- Context assembly: What enters the context window, in what order, with what priority
- Output contract: Schema, format, constraints, error handling, fallback behavior
- Tool interface: Available tools, their schemas, permissions, composition patterns
- Guard rails: Safety filters, refusal policies, output validators
- Versioning: Immutable versions, deployment tags, audit trail
Core Principles
- Eval-first: Define how to measure before changing anything
- Simplest technique: Zero-shot → few-shot → CoT → chaining. Escalate only when simpler fails
- Explicit over implicit: Spell out constraints, output format, edge cases. Never assume the model "knows"
- Separation of concerns: Instructions vs data vs examples — always delimited
- Grounding: Prefer citations and verifiable data over unanchored claims
- Least privilege: Minimal tool permissions per agent. HITL for high-impact actions
- Cost awareness: Every token costs money and time. Compress, cache, route
Resource Files
| File | Contents |
technique-guide.md | Technique selector overview and reading map |
technique-guide-core.md | Zero-shot, few-shot, CoT, self-consistency, constrained generation |
technique-guide-agentic.md | ToT, ReAct, chaining, reflection, RAG, meta-prompting, provider guidance |
prompt-template-patterns.md | Prompt structure overview and pattern index |
prompt-template-foundations.md | Delimiters, system prompt architecture, few-shot formatting, CoT formatting |
prompt-template-contracts.md | Output schemas, tool schemas, prompt registry, provider-specific adaptations |
security-checklist.md | OWASP LLM Top 10 mapped to prompt-level mitigations with checklist |
eval-and-testing-guide.md | Eval workflow overview and decision map |
eval-datasets-and-graders.md | Dataset curation, grader types, grader selection |
eval-deployment-and-monitoring.md | Regression gates, A/B testing, deployment rollout, monitoring |
Integration
- Follows rules:
prompt-engineerrole (prompt system architecture, security, eval-first quality) - Used by workflows:
ai-skillsskill (all assets are prompts),feature-devskill (AI features),code-reviewskill (prompt quality review) - Companion skills:
context-engineeringskill (context pipeline design, memory engineering, agent harness, RAG architecture, multi-agent orchestration, production checklists),asset-validationskill (AI asset format validation),code-reviewskill (review checklists) - Collaborates with roles:
software-engineerrole (prompt integration),qa-engineerrole (prompt regression tests),product-managerrole (success metrics)
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.

