prompt-engineering-architect

Designs, audits, and optimizes production prompts for in-app LLM features.

1|Updated Aug 25, 2026
One-click install
npx skills add https://github.com/sabiscore/swarmxq --skill prompt-engineering-architect-sabiscore
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prompt-engineering-architect
Source: https://github.com/sabiscore/swarmxq/tree/main/.ai/skills/prompt-engineering-architect
Command: npx skills add https://github.com/sabiscore/swarmxq --skill prompt-engineering-architect-sabiscore

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI features embedded in applications often produce inconsistent outputs, hallucinated fields, or unreliable JSON because their prompts lack structure, examples, and explicit constraints. This Skill provides a systematic protocol for writing, testing, and versioning prompts so LLM features behave predictably in production. ## Core Features & Use Cases - Structured System Prompts: Builds prompts from four components (role, goal, constraints, format) with TypeScript templates for extraction, classification, summarization, RAG, and code generation tasks. - Few-Shot & Chain-of-Thought Patterns: Supplies ready-to-adapt examples for classification and multi-step reasoning, plus RAG context injection with boundary instructions that prevent hallucination outside provided context. - Prompt Versioning & Evaluation: Establishes a versioned prompt registry with changelogs and an eval harness that tests prompts against fixed input sets to measure accuracy over time. - Use Case: Your invoice extraction feature keeps inventing missing dates. Use this Skill to add explicit null-handling constraints, few-shot edge-case examples, and a Zod-schema-aligned output format, then verify the fix with an eval test suite. ## Quick Start Ask the AI to audit your existing system prompt for an extraction or classification feature and rewrite it using the four-component structure with few-shot examples.

Frequently Asked Questions about prompt-engineering-architect

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

FAQPage Schema
How do I write a better system prompt for an LLM feature?

Structure every system prompt with four components: role, goal, constraints, and output format. Use positive instructions like "respond only in JSON" rather than negative ones, and place key instructions at both the start and end of long prompts.

How do I make an LLM output JSON reliably?

Combine an explicit output schema with 2-3 few-shot examples covering edge cases, and instruct the model to respond with a single JSON object with no markdown or preamble. Use temperature 0 for deterministic extraction tasks.

How do I reduce hallucinations in a RAG application?

Add boundary instructions to your RAG prompt: answer only from the provided context, cite the section used, and respond with an exact fallback message when the answer is not in the context. Never allow the model to use outside knowledge.

When should I use few-shot examples versus instructions?

Few-shot examples are the strongest signal for format-sensitive tasks like extraction and classification, where 2-3 examples covering edge cases outperform written instructions. Use plain instructions for conversational or open-ended generation tasks.

How do I test whether a prompt change improved accuracy?

Build an eval harness with a fixed set of input cases and expected outputs, then run assertions against each case after every prompt change. Version your prompts with a changelog so regressions can be traced to specific edits.