prompt-engineering

Guides prompt design using few-shot, chain-of-thought, and template patterns for LLM tasks.

Updated Aug 19, 2026
One-click install
npx skills add https://github.com/nperepichka/Antigravity --skill prompt-engineering-nperepichka
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prompt-engineering
Source: https://github.com/nperepichka/Antigravity/tree/main/config/skills/prompt-engineering
Command: npx skills add https://github.com/nperepichka/Antigravity --skill prompt-engineering-nperepichka

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing effective prompts for large language models is often trial-and-error, producing inconsistent outputs, wasted tokens, and unreliable agent behavior. This Skill provides structured prompt engineering patterns and best practices to make LLM interactions predictable and controllable. ## Core Features & Use Cases - Few-Shot Learning: Teach models through input-output examples to enforce consistent formatting and reasoning patterns. - Chain-of-Thought Prompting: Request step-by-step reasoning to improve accuracy on complex analytical and multi-step tasks. - Prompt Optimization & Templates: Systematically iterate on prompts with A/B testing and build reusable template systems with variables and conditional sections. - Use Case: Imagine your support ticket classifier returns inconsistent JSON. Use this Skill to restructure the prompt with few-shot examples and explicit output schemas, then iterate until classification is stable. ## Quick Start Use the prompt-engineering skill to rewrite my customer support classification prompt with few-shot examples and a defined output format.

Frequently Asked Questions about prompt-engineering

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write better prompts for large language models?▼

Start with a simple direct instruction, then add constraints, reasoning steps, and examples only as needed. Follow the progressive disclosure approach: test each level on diverse inputs before adding complexity, and measure accuracy and consistency.

What is few-shot prompting and when should I use it?▼

Few-shot prompting teaches the model by showing 2-5 input-output example pairs instead of explaining rules. Use it when you need consistent formatting, specific reasoning patterns, or edge case handling, balancing example count against token consumption.

How does chain-of-thought prompting improve accuracy?▼

Chain-of-thought prompting requests step-by-step reasoning before the final answer, either with a phrase like "Let's think step by step" or example reasoning traces. It improves accuracy on analytical and multi-step tasks by 30-50%.

What is the difference between system prompts and user prompts?▼

System prompts define stable global behavior such as role, expertise, output format, and safety rules that persist across the conversation. User prompts carry variable per-turn content, keeping token usage efficient and instructions consistent.

Why does my prompt give inconsistent results?▼

Inconsistency usually comes from vague instructions, ambiguous wording, or examples that do not match the target task. Add explicit constraints, include representative input-output examples, and test on edge cases to stabilize outputs.

When should I avoid complex prompt engineering?▼

Avoid over-engineering when a simple direct instruction already works. Starting with complex prompts before trying simple ones wastes tokens and adds failure modes; only add examples, reasoning steps, and templates when testing shows they are needed.