agentleFS
Sign inStart free
extra-orgextra-org/extra/.claude/skills/prompt-rendering/SKILL.md

prompt-rendering

Skill119 starsChanged 5 months agoMITView on GitHub

Working on prompt templates, template loading/caching, or per-request rendering. Primary task is tasks/0005-prompt-rendering.md.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Do not edit this file directly.

    line 10
  2. Very specific:

    Use this when working on prompt templates, template loading/caching, or per-request rendering.

    line 18
  3. Distinctive:

    Use strict rendering: undeclared/missing variables raise errors.

    line 41
  4. Distinctive:

    Keep the source declaration (YAML) and resolution (runtime) separated.

    line 44

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- This file is generated by tools/skills. Do not edit this file directly. Edit .ai/skills/prompt-rendering.md and run `make generate-ai`. -->

Skill: Prompt Rendering

When to use this skill

Use this when working on prompt templates, template loading/caching, or per-request rendering. Primary task: tasks/0005-prompt-rendering.md.

Files to read first

  • AGENTS.md
  • docs/PROMPT_RENDERING.md
  • docs/adr/0004-prompts-are-templates-rendered-per-request.md
  • docs/RUNTIME_LIFECYCLE.md

Architecture rules

  • Prompt files are templates with placeholders, not finished text.
  • Parsed templates may be cached; rendered prompts are never globally cached.
  • Values are resolved per request from the ExecutionContext.
  • Missing required variables fail loudly with a named error.
  • Templates are data, not code — no execution inside a template.
  • Prompt text is not a security boundary.

Implementation rules

  • Implement loading/caching/rendering in src/agentplatform/prompts.
  • Cache the parsed template keyed by path + version; never cache rendered output.
  • Use strict rendering: undeclared/missing variables raise errors.
  • Pull values only from the ExecutionContext (which is populated by the resolver plugins), not from globals.
  • Keep the source declaration (YAML) and resolution (runtime) separated.

Validation checklist

  • Parsed templates cached; rendered prompts not cached globally.
  • Missing required variable → clear, named error.
  • No executable logic in templates.
  • No secrets in prompt files.
  • Tests cover successful render, missing variable, and cache behavior.
  • make check passes.

Common mistakes to avoid

  • Caching rendered prompts (data-leak risk across tenants/requests).
  • Silently substituting blanks for missing variables.
  • Embedding logic/secrets in templates.
  • Treating prompt instructions as enforcement.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free