Index of every page on this site: llms.txt
All skills
imawais-engineer avatar

/prompt-engineering-system

@5ecc5ec
Run it yourself

Design prompts as maintainable application components with clear task contracts, input schemas, output schemas, examples, safety boundaries, eval cases, versioning, and validation. Use when creating or improving prompts, system instructions, AI workflows, structured outputs, extraction/generation/classification prompts, or prompt libraries.

Use this Skill: https://skilld.dev/gh/imawais-engineer/skills/prompt-engineering-system

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈92 tokens for metadata: the name and description. ≈504 when used: this file. ≈53 more on demand in 1 file.

Description uses 4.6% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈370 characters, or 4.6%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Prompt Engineering System

Principle

Treat prompts as software artifacts, not disposable text. A production prompt needs a purpose, inputs, outputs, constraints, tests, failure handling, versioning, and ownership.

Prompt Design Workflow

  1. Define the task contract: what the prompt must accomplish and what it must not do.
  2. Define input fields, source of each field, required/optional status, and validation rules.
  3. Define output format, schema, allowed values, and rejection/error shape.
  4. Separate stable instructions from user-provided data.
  5. Add concise examples only when they improve reliability.
  6. Add safety, privacy, and prompt-injection boundaries.
  7. Add validation code or schema checks for outputs.
  8. Add eval cases covering normal, edge, malicious, incomplete, and ambiguous inputs.
  9. Version the prompt when behavior changes.

Prompt Structure

Prefer this structure:

  • Role and objective
  • Context needed for the task
  • Input contract
  • Output contract
  • Constraints and forbidden behavior
  • Decision rules
  • Examples, if useful
  • Failure and escalation behavior

Application Rules

  • Keep prompts close to the feature that uses them, or in a prompt library when reused.
  • Never mix untrusted user text into instructions without clear delimiters.
  • Prefer structured outputs when the app needs to parse or store results.
  • Validate AI output before database writes, external actions, or user-visible critical decisions.
  • Log prompt version, model/provider, inputs summary, output status, and validation result when useful.

Evaluation

Create small eval sets before stable release:

  • Happy path examples
  • Edge cases
  • Missing data
  • Ambiguous requests
  • Prompt injection attempts
  • Unsafe or disallowed content
  • Regression cases from real failures

Done Check

Prompt work is done when the prompt has a clear contract, produces parseable outputs where needed, passes eval cases, handles failure states, and is connected to the app workflow without placeholders.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts26d2 checks · Risk LOW
  • Socket26d

    No alerts

  • Snyk26d

    Risk: LOW · No issues

Signed by skilld at 5ecc5ec. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 5 days ago.

Activeupdated last week

README badge

README badge for imawais-engineer/skills/prompt-engineering-system