Skip to content

Builds Folder

Purpose

Documentation for Path of Exile character builds, organized by class.

Folder Structure

builds/
├── marauder/
├── duelist/
├── ranger/
├── shadow/
├── witch/
├── templar/
└── scion/

Naming Conventions

File Names

  • Format: [build-name].md (kebab-case)
  • Pattern: [main-skill]-[ascendancy].md or [archetype]-[ascendancy].md

Examples:

  • rf-juggernaut.md (Righteous Fire Juggernaut)
  • poison-pathfinder.md
  • lightning-conduit-elementalist.md
  • glacial-hammer-berserker.md

Folder Organization

Each class has its own subfolder with builds for that class's ascendancies.

Template Requirements

Required Template: templates/build-template.md

Required Frontmatter Fields:

yaml
template: "templates/build-template.md"
document_type: "build"
title: "[Build Name]"
status: "draft|review|published|outdated"
author: "[Your Name]"
created: "YYYY-MM-DD"
updated: "YYYY-MM-DD"
tags: ["tag1", "tag2"]
league: "3.25"
patch: "3.25.1"
class: "Marauder|Duelist|Ranger|Shadow|Witch|Templar|Scion"
ascendancy: "[Ascendancy Name]"
main_skill: "[Primary Skill]"

Creation Workflow

1. Check Class Folder

bash
# Verify class folder exists
Read("builds/[class]/index.md")

2. Get Template

bash
Read("templates/build-template.md")

3. Create Build Document

bash
Write("builds/[class]/[build-name].md", content)

Content Guidelines

What to Include

  • Build overview and playstyle
  • Skill tree and passive allocation
  • Ascendancy choice and lab order
  • Skill gems and links
  • Gear requirements and recommendations
  • Flask setup
  • Pantheon choices
  • Leveling guide
  • Budget considerations

Path Conventions

Always use absolute paths:

CORRECT:

yaml
relationships:
  requires:
    - path: "mechanics/items/the-brass-dome.md"
      title: "The Brass Dome"

INCORRECT:

yaml
relationships:
  requires:
    - path: "../mechanics/items/the-brass-dome.md"

Relationship Types

Common Relationships

  • requires - Essential items/mechanics for the build
  • synergizes_with - Complementary builds or mechanics
  • alternative_to - Similar builds with different approaches
  • derived_from - Based on another build or guide

Build Status Lifecycle

  • draft - Work in progress, may be incomplete
  • review - Ready for testing and feedback
  • published - Tested and viable for current league
  • outdated - Needs updates for current patch/league

Tags Guidelines

  • Damage types: physical, fire, cold, lightning, chaos, minion
  • Defense types: armour, evasion, energy-shield, life, low-life, ci
  • Playstyle: melee, ranged, caster, summoner, totem, mine, trap
  • Budget: league-start, budget, mid-tier, high-investment
  • Content: mapping, bossing, delve, heist, sanctum

Example Tag Set

yaml
tags: ["fire", "life", "armour", "league-start", "mapping", "bossing", "righteous-fire"]

Quality Checklist

Before creating a build document:

  • [ ] Read this index.md for conventions
  • [ ] Read class-specific folder index.md
  • [ ] Used templates/build-template.md
  • [ ] Included template: field in frontmatter
  • [ ] Followed naming pattern: [skill]-[ascendancy].md
  • [ ] Set correct class and ascendancy
  • [ ] Added current league and patch version
  • [ ] Used absolute paths for all relationships
  • [ ] Added appropriate tags
  • [ ] Set appropriate status

Examples

Good File Names

  • rf-juggernaut.md
  • boneshatter-slayer.md
  • spectral-helix-champion.md
  • toxic-rain-pathfinder.md

Bad File Names

  • my-build.md (not descriptive)
  • RF Build.md (has spaces, not kebab-case)
  • juggernaut-rf.md (wrong order - skill should come first)
  • build1.md (meaningless name)

Additional Resources

poe-aio - Path of Exile All-in-One