Note Guru

Improved prompt:

Data Organization and Security Improvement Project

Project Overview:
Your task is to analyze and reorganize all notes and files within the primary project folder ${main_folder} located at ${path_to_folder}/. The goal is to improve data security, enhance readability, and optimize the folder structure for future maintenance. The project will be completed in three distinct phases.

Phase 1: Comprehensive Security Audit

Task 1: Sensitive Information Extraction and Documentation

Examine every file within the ${main_folder} folder. Your primary objective is to identify and document all sensitive data elements that pose potential security risks. This includes but is not limited to:

• API keys
• Passwords
• Tokens
• Credentials
• Private keys
• Secrets
• Connection strings
• Any other confidential or restricted information

To document your findings:

1. Create a new markdown file named secrets.md within the ${main_folder} directory.
2. List all discovered sensitive information in the secrets.md file.
3. For each sensitive data element, include a clear reference to the source file where it was found.
4. Ensure the references are formatted consistently and are easily identifiable.
5. Do not modify the sensitive data itself; simply document its presence and location.

Phase 2: Content Organization and Topic Clusterization

Task 2: Topic-Based Content Reorganization

After the security audit, proceed to analyze the content of each file. Many files contain multiple notes on different subjects written at different times. Your objective is to:

1. Identify the top ${topic_max} most prominent and relevant topics across all files.
2. Base your topic selection on content frequency, importance, and logical clustering.
3. Create ${topic_max} new markdown files within the ${main_folder} directory.
4. Name each topic file using a descriptive and unique name in the format ${topic:#}.md, where # represents the topic number.

For each note segment in the original files:

1. Identify the appropriate topic cluster for the current note.
2. Copy the note segment in its entirety to the corresponding topic file.
3. Add a clear and unique reference number next to the original note in the source file. This reference should be in the format ${topic:2} or → Security:2, clearly indicating which topic file the note has been migrated to.
4. Ensure the reference numbers are consecutive and consistent within each file.

Phase 3: Archive Management

Task 3: File Migration and Archive Creation

Once all note segments from an original file have been successfully migrated to their respective topic files and reference numbers have been added:

1. Create a new folder named ${archive_folder:old} within the ${main_folder} directory.
2. Move the original, now empty, file to the ${archive_folder:old} folder.

Expected Final Folder Structure

${main_folder}/
├── secrets.md (1 file)
├── ${topic:1}.md (topic files totaling ${topic_max})
├── ${topic:2}.md
├── ..... (more topic files)
├── ${topic:#}.md
└── ${archive_folder:old}/
      └── (all original, empty files migrated from the main folder)

Important Guidelines:

1. Read every file completely and thoroughly, ensuring no information is overlooked.
2. Maintain the original content and formatting when copying notes to topic files.
3. Choose topic names that are concise, descriptive, and accurately reflect the content clusters you identify.
4. Categorize every note segment, leaving no orphaned content in the original files.
5. Keep reference numbers clear, consistent, and easily traceable.
6. Only move files to the ${archive_folder:old} directory after confirming all content has been properly migrated to the topic files.
7. If you encounter any ambiguous content or need clarification during the topic organization process, please inform me immediately.

Begin your analysis with the ${path_to_folder} directory, and let me know if you need any further clarification or if you encounter any specific challenges during the project.