Open Specification v0.2

Prompts
as code.

A Markdown-based spec for parameterized, portable, executable AI prompts. Write once, run anywhere, version everything.

analyze.rune.md
--- name: competitor_analysis version: 1.0.0 model: claude-sonnet-4 temperature: 0.5 inputs: - name: company type: string required: true - name: industry type: enum options: [saas, fintech, climatetech] --- ## System You are a strategy consultant. ## Prompt Analyze {{company}} in {{industry}}.
Prompts deserve better tooling.
AI prompts are engineering artifacts, but we treat them like sticky notes. RuneFile fixes that.

Without RuneFile

  • Prompts scattered across Notion, Slack, random .txt files
  • Copy-paste variables by hand every time
  • No version history — "which version worked?"
  • Can't share prompts as reusable units
  • Zero validation — silent failures everywhere
  • Locked to one provider's playground

With RuneFile

  • One .rune.md file per prompt, in your repo
  • Typed inputs with validation and defaults
  • Git-native versioning with semantic versions
  • Share, import, compose prompts like functions
  • Errors caught before execution
  • Provider-agnostic — run on any model
Everything you need.
Nothing you don't.

Typed Inputs

String, text, number, boolean, enum, array. With defaults, constraints, and descriptions. Generate forms automatically.

🔀

Multi-Turn

Ordered sections map to messages. Repeat ## User and ## Assistant for few-shot patterns. Context gets prepended.

🧩

Composition

Include partials. Reuse system prompts. Override sections. Build prompt libraries from composable pieces.

📐

Output Schemas

Declare JSON Schema for structured outputs. Runners validate responses automatically. No more parsing surprises.

🛡

Input Sanitization

Template injection protection built into the spec. Enum validation, length limits, and strict mode for production.

🔧

Tool Definitions

Define function-calling tools in readable Markdown. The runner translates to your provider's format.

Six steps, zero ambiguity.
1
Parse
2
Resolve
3
Validate
4
Render
5
Execute
6
Output
See it in action.
Six real prompt files — from competitive analysis to public sector citizen services.
analysis.rune.md
Your prompts are functions.
Treat them that way.
RuneFile is open source and spec-driven. Star the repo, read the blueprint, build a runner, contribute.