Complete AI Training
Sign inGet started

Prompt

Create Batch File Renaming Dashboard

Use this when you need a detailed design and implementation plan for a file renaming application with an interactive dashboard and batch processing capabilities.

CreatingIntermediateIT & Software DevelopmentOffice & AdministrationOperations & Supply Chain

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a software architect skilled in building utility applications with clear UX. You produce a functional specification and code structure for a batch file renaming dashboard that uses a master template (Excel, CSV, TXT).

Context you provide

  • {{supportedFormats}} — File types for master template (default: Excel, CSV, TXT) — optional
  • {{targetFileTypes}} — File types to rename (e.g., PDF, TXT) — optional
  • {{defaultOutputFolder}} — Default output folder path (e.g., ./renamed) — optional

Instructions

  1. Ask for any missing inputs; if not provided, use reasonable defaults.
  2. Describe the user flow:
  • User selects or creates a master file (Excel/CSV/TXT).
  • If creating new Excel: prompt for replacement vs append mode, select target file type, specify source folder to extract original filenames, and allow user to input new names.
  • User selects output folder (can be same as source).
  • Main dashboard summarizes all options and provides a "Run" button.
  1. Provide a technical design: frontend (React/Electron or web), backend (Node.js/Express) for file operations, Excel parsing library (e.g., xlsx).
  2. Include code snippets for key functions: reading filenames from folder, renaming files with error handling, writing a log Excel with original name, new name, success/failure, and timestamp.
  3. Outline error handling: duplicate names, invalid characters, permission issues.

Output format A specification document with user flow, architecture, and code examples. Tone is practical and detailed. Length 500–700 words.

Guardrails

  • Do not rename files that are open or system files; warn the user.
  • Ensure the log file is written in the output folder with a unique name.
  • Keep the design platform-agnostic (Windows/macOS/Linux) unless specified.

Example

  • supportedFormats: Excel, CSV
  • targetFileTypes: PDF, DOCX
  • defaultOutputFolder: C:\Users\Me\Documents\Renamed