raw-photo-lightroom-preset

RAW Photo Lightroom Preset v2

Core rules

• Judge color only from RAW files rendered by Lightroom/Camera Raw. Use ordinary camera JPGs only for composition, focus, and expression triage.
• Preserve originals and the user's master edit. Do not move, rename, delete, overwrite, or batch-edit photos unless the user asks.
• Treat a preset as a reusable starting point, not a finished edit.
• Separate technical correction from creative style. Never guess 30-50 sliders at once.
• Prefer a closed loop: inspect Lightroom state, render, adjust a small pass, render again, compare, then continue.
• Do not claim Lightroom import, visual fidelity, or manual QA passed unless it was actually performed.

Choose the route

1. Read references/workflow.md for every shoot.
2. Read references/style-library.md before choosing a style or reference direction.
3. If Lightroom MCP tools are available and Lightroom Classic is running, also read references/lightroom-mcp.md and use the closed-loop route.
4. Otherwise use Lightroom/Camera Raw neutral previews and the manual-preview route. State that Lightroom-side feedback is unavailable.
5. If provenance is missing or ambiguous, stop color work and mark the affected item 未分類.

Closed-loop route

Use one representative RAW per lighting cluster first.

1. Capture the current photo metadata and develop settings.
2. If the user has an approved historical look, list presets and read it with get_develop_preset. Use UUID or folder/scope to avoid duplicate-name ambiguity.
3. Export a baseline JPEG from Lightroom into a new empty review folder.
4. Apply one bounded pass at a time:
   • technical correction;
   • tonal shape;
   • color correction;
   • creative look;
   • detail/noise.
5. Export and inspect after each pass. Compare against the baseline and any user-approved reference image.
6. When the fork tools are available, create uniquely versioned checkpoints with create_develop_preset and diff them against the approved look with compare_develop_presets.
7. Keep a checkpoint log of settings and rendered files. Stop when the remaining difference needs masks, crop, healing, AI Denoise, or subjective user choice.
8. Ask for approval on representative before/after results before copying settings across a cluster.
9. Export an accepted custom/checkpoint preset with export_develop_preset; never overwrite an existing destination. Import it into Lightroom before claiming compatibility. Use Lightroom's UI for a visible canonical preset when needed. The bundled generator remains a fallback for a verified global-setting subset.