Replace INFO with AI Description

Review the photo and video files I have made available to you. Their filenames were already created with FilenameTool.com, but some still contain INFO as an exact hyphen-delimited filename component.

The product you are creating is a proposed rename script to rename files by only replacing the INFO string in just the files containing -INFO- with descriptions you’ve written. Create a proposed rename script using these rules. Bash is the default. If I explicitly request PowerShell, return a PowerShell script instead.

1. Process only filenames containing -INFO- as a complete filename component with case sensitive. Skip any other filename. The string to be replaced is only INFO; leave the hyphens untouched.

2. Visually inspect every matching photo. For a matching video, inspect representative frames from the beginning, middle, and end.

3. Replace only the INFO string. Copy every other character of the filename verbatim from the original filename, including capitalization, punctuation, spaces, dates, times, credits, devices, sequence numbers, flags, dimensions, and extensions. Never reconstruct or normalize any portion of the filename.

4. Replace the INFO string with a concrete description of the main visible subject or action, normally three to seven words with a maximum of ten words. Use Title_Case with words separated by underscores, for example Rocks_Road_and_Fence. Do not use illegal filename characters ( : ; ~ & * \ " ' ? [ ] { } ( ) < > ␣ ), periods, or commas. Spaces should always be replaced with underscores. Only replace the INFO string; the rest of the proposed filename should be character by character identical to the original filename.

5. Use neutral descriptions for people unless I have explicitly identified them. Never guess identity, relationships, sensitive traits, ownership, or an exact location. If a name has been provided, use the full name as provided; if a first and last name was provided, use both the first and last name.

6. Make descriptions for similar files distinct whenever the visible content truthfully supports a distinction. If the content is unclear, leave the filename unchanged, do not replace the INFO string for that filename, and report that filename for manual review rather than inventing a description.

7. Before producing the script, verify all of the following:

	* every matching filename was processed exactly once;
	
	* every original filename exactly matches an existing filename;
	
	* every proposed filename differs from its original only by the replacement of the INFO component;
	
	* no proposed filename duplicates another proposed filename;
	
	* no proposed filename conflicts with an existing filename in the same directory.

8. Return only a code block containing the rename commands. The code block must only contain commands ready to paste into the Terminal, other than an initial commented line that says: “# Change to Chosen Directory before pasting these commands.” Otherwise, do not include a shebang, comments, blank lines, prompts, explanatory text, Markdown, or any other content inside the code block.

9. Unless I explicitly request PowerShell, produce Bash commands. Every command must appear exactly in this form:

	mv 'original filename' 'proposed filename';

10. If I explicitly request PowerShell, use a PowerShell code block instead, with each command in exactly this form:

	Rename-Item -LiteralPath 'original filename' -NewName 'proposed filename';

11. Use only plain ASCII characters for shell syntax although the filename can contain non-ASCII characters. Do not use typographic (“smart”) quotes, Unicode dashes, or other punctuation substitutions. Use the ASCII apostrophe (') for shell quoting.

12. Correctly escape any apostrophes or other special characters inside filenames for the selected shell. Use filenames relative to the current directory. In Bash, safely single-quote each filename. In PowerShell single-quoted strings, represent an apostrophe with two apostrophes. Use filenames relative to the directory containing the files. Do not overwrite files and do not execute any command.

13. Put a hard return after every command, including the last command, so the code block ends with a newline.

14. If any filename cannot be renamed safely, omit it from the script, and list it separately after the code block for manual review.

15. The product you are creating is the renaming script with the descriptions you've written replacing the INFO string in files containing -INFO-.