Docs / Templates

Templates

Templates give new files and prompts a consistent starting point. File templates are stored globally and are available in every workspace.

File templates

When you create a file (⌘N or the New file button), you pick a file template. A template provides:

  • The initial file body — headings, structure, placeholder text.
  • A suggested filename (you can override it).
  • The correct frontmatter for the doc type (e.g. type: plans, status: draft).

Built-in file templates:

Template Type What you get
Rules rules # Constraints with “Always do / Never do / Important” sections
Plan plans # Plan with goal, tasks, and timeline sections
Architecture arch # Architecture with overview, components, and decisions
ADR adr # ADR-0001: Title with context, decision, and consequences
Notes notes Blank with correct frontmatter
Blank Empty file, no frontmatter

After choosing a template, type the filename and press Enter. The file opens ready to fill in.

Prompt templates

In the prompt card editor, the From template… dropdown fills the instruction with a saved prompt template (and its kind). Prompt templates can include {{variables}} — placeholders that become fill-in fields when you run the card.

Example prompt template:

You are reviewing the implementation of {{feature}} in {{file}}.

Check it against the rules in CLAUDE.md and the architecture in [[arch/overview]].
Flag any violations or improvements.

When you apply this template and run the card, Bedrock asks for feature and file values before sending.

The Claude Code pack

Bedrock ships with a bundled Claude Code pack — prompt templates optimised for working with Claude CLI: feature implementation, bug fix, refactor, write tests, explain code, review for quality, and generate docs.

These appear in the Library tab of the Prompts board.

Managing templates

Open Manage templates from:

  • The command palette: ⌘K → “Manage templates”.
  • Settings → Library.

The overlay shows built-in templates (read-only reference) and your own custom templates.

Creating a custom file template

  1. Open Manage templates and click New file template.
  2. Give it a name, pick a doc type, and write the body.
  3. Save it — it appears in the new-file dialog immediately.

Creating a custom prompt template

  1. Write a prompt card with the instruction you want to reuse.
  2. Click Save as template in the card editor.
  3. Give it a name and kind.
  4. It appears in the From template… dropdown on all future cards.

Variables

Any {{placeholder}} in a prompt template becomes a fill-in field. Good variables to parameterise: {{file}}, {{component}}, {{feature}}, {{issue}}.

Get release notes

An email when a new build ships or a major feature lands. A few times a quarter — never your inbox sold.

You're on the list — watch for a confirmation email.