OpenParable
Skip to content
← Back to skills

Templ Syntax

Development
templ-syntax

Templ Syntax is an Agent Skill for development published in the Xe/site repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Learn and write templ component syntax including expressions, conditionals, loops, and Go integration. Use when writing .templ files, learning templ syntax, or mentions 'templ component', 'templ expressions', or '.templ file syntax'.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/Xe/site/blob/HEAD/.agents/skills/templ-syntax/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/templ-syntax, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Templ Syntax

Use this skill with progressive disclosure: start at Level 1, then read deeper sections only when needed.

Level 1: Fast Path

Use this skill when you need to write or fix .templ syntax.

  1. Define a component with typed params.
  2. Render values with { expr }.
  3. Compose components with @OtherComponent(...).
  4. Use Go control flow (if, for, switch) directly in markup.
  5. Keep business logic in Go helpers, not inline in templates.
package components

templ Greeting(name string, isAdmin bool) {
    <h1>Hello, { name }</h1>
    if isAdmin {
        <p>Admin mode</p>
    }
}

Level 2: Core Rules

  • Output: { value } auto-escapes text.
  • Dynamic attrs: class={ classes }, disabled?={ isDisabled }.
  • Children: accept with { children... }, pass with block syntax.
  • Composition: call components with @Component(...).
  • Safety: URLs should use safe helpers (for example templ.URL(...)) when appropriate.

Level 3: Common Patterns

templ Card(title string) {
    <section class="card">
        <h2>{ title }</h2>
        <div>{ children... }</div>
    </section>
}

templ UserList(users []string) {
    if len(users) == 0 {
        <p>No users</p>
    } else {
        <ul>
            for _, user := range users {
                <li>{ user }</li>
            }
        </ul>
    }
}

Escalate to Other Skills

  • Building reusable UI APIs: use templ-components.
  • Wiring templates to handlers/routes: use templ-http.
  • Adding dynamic interactions: use templ-htmx.

References