Code
How storytold/photocraft is laid out, and where to start for common changes.
There is no import map for this report yet.
Where to start reading
- Repository root
- Repository root
- Likely public API
- Likely public API
- Likely start-up file
- Likely start-up file
- Suggested starting pointAI
- Suggested starting pointAI
Find files for a task
AIAdd a New Image Effect Filter
- Register the new effect as an action command in crates/engine/src/actions_cmds.rs.
- Add UI binding in the egui-based UI layer (crates/ui-egui or apps/photocraft).
Add Support for a New File Format
- Create a new crate in crates/ (e.g., crates/myformat/Cargo.toml) following the pattern of crates/codecs or crates/raw.
- Add fuzzing harness in crates/myformat/fuzz/ to validate parser robustness (reference: crates/format/fuzz).
Add a New Tool or Paint Brush Variant
- Register the tool as a command action in crates/engine/src/actions_cmds.rs.
Add a New Platform or Build Target
- Create platform-specific packaging script in packaging/ (reference: packaging/linux/AppRun, packaging/macos/Info.plist.in).
- Update xtask build orchestration in xtask/Cargo.toml and xtask/src to support the new target.
- Add CI configuration referencing scorecard/automation.toml if using GitHub Actions or similar.
- Test native bindings and platform-specific code paths in apps/photocraft or apps/photocraft-cli.
Change the public API
Trace runtime behavior
Add or update tests
Change build or automation
RepoPilot lists up to 500 files, so a file missing here may still exist.
- Files marked “likely” are guessed from their names.