Skip to content

File Anatomy

A .prs file contains metadata, composition directives, content blocks, and modification operations. Syntax 1.5.0 applies top-level declarations in source order.

@meta {
id: "checkout-service"
syntax: "1.5.0"
}
# 1. Establish base layers.
@inherit @company/service
@use @team/backend
# 2. Declare local content.
@identity {
"""
You are working on the checkout service.
"""
}
@standards {
@header "Engineering Standards"
code: ["Use strict TypeScript"]
testing: ["Use Vitest"]
}
@restrictions {
- "Never expose payment data"
}
# 3. Modify values after composition.
@override standards.testing {
["Use Vitest", "Require integration tests"]
}
@extend standards {
code: ["Use named exports"]
}
Try in Playground

@meta should appear first. Imports normally come before local content. @extend and @override should appear after targets they modify.

Public Blocks

GroupBlocks
Core instructions@identity, @context, @standards, @restrictions, @knowledge, @local
Interaction@shortcuts, @guards, @params, @examples
Agent platform@skills, @agents, @workflows, @hooks, @mcpServers, @plugins
Prompt definitions@prompts
Composition@inherit, @use, @extend, @override
PresentationContextual @header entries inside supported owner blocks

@commands remains a compatibility alias for @shortcuts. @prompts holds prompt definitions with typed inputs. The validator checks it at syntax 1.6.0. Coding agent targets skip it, so it never changes their output, and the opt-in bundle and prompt-text targets compile it. See @prompts in the language reference and Application Prompts.