OrcaSlicer/AGENTS.md

CLAUDE.md

OrcaSlicer — open-source C++17 3D slicer. wxWidgets GUI, CMake build system.

Build Commands

# macOS
cmake --build build/arm64 --config RelWithDebInfo --target all --

# Linux
cmake --build build --config RelWithDebInfo --target all --

# Windows (replace %build_type% with Debug/Release/RelWithDebInfo)
cmake --build . --config %build_type% --target ALL_BUILD -- -m

Testing

Catch2 framework. Tests in tests/ directory.

cd build && ctest --output-on-failure           # all tests
ctest --test-dir ./tests/libslic3r              # individual suite
ctest --test-dir ./tests/fff_print

Code Style

• C++17, selective C++20. PascalCase classes, snake_case functions/variables
• #pragma once for headers. Smart pointers and RAII preferred
• Parallelization via TBB — be mindful of shared state

Key Entry Points

• App startup: src/OrcaSlicer.cpp
• Slicing pipeline: src/libslic3r/Print.cpp
• All print/printer/material settings: src/libslic3r/PrintConfig.cpp
• GUI: src/slic3r/GUI/
• Core algorithms: src/libslic3r/ (GCode/, Fill/, Support/, Geometry/, Format/, Arachne/)
• Printer profiles: resources/profiles/[manufacturer].json

Critical Constraints

• Backward compatibility required for .3mf project files and printer profiles
• Cross-platform — all changes must work on Windows, macOS, and Linux
• Profile/format changes need version migration handling
• Dependencies built separately in deps/build/, then linked to main app

Code review focus areas

• Changes must not cause regressions in existing functionality, defaults, profiles, or project compatibility.
• Features gated by options must not affect existing behavior when those options are disabled.
• Changes should follow the existing code style and architecture. Architectural changes should be justified in code comments and the PR description.
• Add helper functions or utilities only when existing code cannot reasonably be reused. Avoid duplication.
• Keep code concise and clear. Manually simplify AI generated bloated codes before review.
• Include targeted tests or documented verification for behavior changes, especially in slicing logic, profiles, formats, and GUI defaults.
• For translation changes (localization/i18n/**/*.po), check that recurring terms match the Localization glossary for that language.

Localization & translations

• Translation catalogs live in localization/i18n/<lang>/OrcaSlicer_<lang>.po.
• When creating or reviewing translations, use the Localization glossary as the source of truth for recurring terms, so the same English term is always rendered the same way within a language and terms that must stay in English (brand/product names, acronyms, file formats, G-code, macros/variables) are not translated.
• If a term's established translation changes, update both the affected .po files and the glossary so they stay in sync.
• Only edit msgstr (never msgid); keep placeholders (%s, %1%, \n), context (msgctxt), and file encoding/line endings intact.