prompt-creation

Creates system prompts using Anthropic's 9-element structure and emphasis scale.

1|Updated Jul 29, 2026
One-click install
npx skills add https://github.com/fusengine/kimi-code --skill prompt-creation-fusengine
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prompt-creation
Source: https://github.com/fusengine/kimi-code/tree/main/plugins/prompt-engineer/skills/prompt-creation
Command: npx skills add https://github.com/fusengine/kimi-code --skill prompt-creation-fusengine

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Writing effective system prompts from scratch is error-prone: instructions end up ambiguous, guardrails get forgotten, and output formats are left unspecified. This Skill provides a proven structure and workflow so every prompt you write is complete, unambiguous, and testable. ## Core Features & Use Cases - 9-Element Structure: Covers task context, tone, rules, few-shot examples, input data, immediate task, scratchpad reasoning, output formatting, and prefill. - 6-Level Emphasis Scale: Calibrate rule strength from "Please do X" up to "CRITICAL - ZERO TOLERANCE". - 8-Step Creation Workflow: Move from objective definition through mental edge-case testing to iteration. - Specialized References: Load RAG patterns (chunking, citation injection, hallucination prevention) or multimodal prompting patterns (screenshot-to-code, diagram understanding) on demand. - Use Case: You need a system prompt for a customer-support classifier. Follow the workflow, apply the 9-element template, add few-shot examples for edge cases, and set critical rules at the right emphasis level. ## Quick Start Write a system prompt for a code review assistant using the 9-element structure with two few-shot examples and critical rules for security issues.

Frequently Asked Questions about prompt-creation

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

FAQPage Schema
How do I write a system prompt from scratch?▼

Follow the 8-step workflow: define the objective in one sentence, identify the audience, list constraints, choose techniques like chain-of-thought or few-shot, write using the 9-element structure, add guardrails, test mentally against edge cases, and iterate.

What is the Anthropic 9-element system prompt structure?▼

It covers task context, tone context, task description with rules, few-shot examples, input data, immediate task, precognition scratchpad, output formatting, and assistant prefill. Each element addresses a distinct aspect of prompt behavior.

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

Two to five examples are sufficient; more examples do not improve results. Prioritize diversity over quantity, include edge cases, and keep formatting consistent across all examples.

How do I prevent hallucination in RAG prompts?▼

Use explicit grounding instructions like answering only from provided context, add a confidence fallback phrase, ask the model to quote relevant passages before answering, and use temperature 0 for factual retrieval tasks.

When should I use XML tags versus markdown in prompts?▼

XML tags work well for structured instructions with nested rules, identities, and output specifications. Markdown headers suit simpler section separation. Both clearly delimit instructions, context, task, and expected format.

What are the limitations of multimodal image prompts?▼

Text below roughly 12px may be misread, handwriting accuracy varies, and dense diagrams over 20 nodes should be split into sections. Keep images between 768px and 2048px, since larger sizes add cost without quality gains.