context-engineering

Guides writing custom modes and skills using context engineering principles.

1|1|Updated May 16, 2026
One-click install
npx skills add https://github.com/vanduc2514/hackathon-lablab-ibm-bob --skill context-engineering-vanduc2514
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: context-engineering
Source: https://github.com/vanduc2514/hackathon-lablab-ibm-bob/tree/main/.bob/skills/context-engineering
Command: npx skills add https://github.com/vanduc2514/hackathon-lablab-ibm-bob --skill context-engineering-vanduc2514

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing effective system prompts, custom modes, and skills is difficult: instructions are often too rigid and brittle, or too vague to guide model behavior. This Skill provides a structured methodology for finding the right balance between specificity and flexibility when authoring AI instructions. ## Core Features & Use Cases - Altitude Calibration: Helps you avoid overly prescriptive hardcoded rules and overly generic guidance by targeting the "Goldilocks zone" of instruction specificity. - Token-Efficient Prompt Design: Teaches how to minimize token count while maximizing signal, using canonical examples instead of exhaustive edge-case lists. - Structured Prompt Organization: Provides section templates (Background, Instructions, Tool Guidance, Output Format, Examples) and few-shot example structures for clear, maintainable prompts. - Use Case: When creating a new custom mode for a migration workflow, apply this Skill to define the expertise, core objective, constraints, and 2-3 canonical examples so the mode behaves consistently without brittle if-else logic. ## Quick Start Use the context-engineering skill to review and improve the system prompt for my new custom mode.

Frequently Asked Questions about context-engineering

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

FAQPage Schema
How do I write effective system prompts for custom modes?▼

Define the expertise, core objective, key constraints, and behavioral heuristics first. Then structure the prompt into clear sections like Background, Instructions, and Examples, and include 2-3 diverse canonical examples rather than exhaustive edge-case lists.

What is the right level of specificity for AI instructions?▼

Aim for the Goldilocks zone: specific enough to guide behavior with concrete signals, but flexible enough to provide strong heuristics. Avoid hardcoded if-else logic that breaks easily and vague directives like "be helpful" that assume shared context.

How many few-shot examples should a prompt include?▼

Provide 2-5 diverse, canonical examples, each demonstrating a different aspect of the desired behavior. Avoid redundant examples showing the same pattern, and keep each example minimal rather than verbose.

What are common prompt engineering anti-patterns to avoid?▼

Avoid listing every possible edge case, hardcoding complex branching logic, assuming the model knows your domain context, mixing multiple concerns without separation, and using vague language like "do your best."

When should I use sub-task architectures for long-horizon tasks?▼

Use sub-task architectures for complex research or analysis tasks that benefit from parallel exploration. The main task coordinates while specialized sub-tasks handle deep focused work, keeping each context window manageable.