
Sign up to save your podcasts
Or


1. Role & Context Persona: Senior Python Developer. Project Scope: Documentation Automation & Markdown Management. 2. The Mission Analyze all Python (.py) files within the current directory and generate structured descriptions for each, appending them to the existing Scripts Description.md file. The goal is to create a comprehensive "Source of Truth" for the repository's functionality using the established Markdown format. 3. Expected Behavior File Discovery: Scan the root directory for all .py files. Logic Extraction: * Read the source code of each script. Identify the primary objective (e.g., file I/O, API interaction, data processing). Extract key features (libraries used, specific Excel operations, clipboard actions, etc.). Formatting: For each new script, generate a section that includes: A numbered header (e.g., ##### 3. script_name.py). A brief "purpose" line in parentheses. A list of functional "✅" bullet points. Content Alignment: Mirror the style of update_lengths.py and copy_description.py, focusing on technical actions (e.g., "Uses [library]", "Handles [error]", "Saves [file]"). Appending: Write the new descriptions to the end of Scripts Description.md without overwriting or refactoring the existing content. 4. Technical Constraints Language: Python analysis logic. Preservation: Do not modify any .py files. Only modify Scripts Description.md. Style Match: Ensure the indentation, spacing ( ), and emoji usage match the reference document exactly. 5. Verification Steps Terminal Command: Run cat "Scripts Description.md" to verify the content has been appended. Validation: Ensure the number of headers in the Markdown file matches the total number of Python scripts in the directory. Success Artifact: A complete Scripts Description.md file where every script has a "Mission-ready" summary. 6. Mission Summary (Antigravity Task List) [ ] Scan directory for all .py files not already documented in Scripts Description.md. [ ] Analyze script logic and external library dependencies. [ ] Draft a concise summary and functional checklist for each script. [ ] Format the draft to match the provided Markdown template (Header, subtitle, and ✅ points). [ ] Append the new descriptions to Scripts Description.md. [ ] Verify formatting consistency across the entire document.
By Sinapsos Podcast1. Role & Context Persona: Senior Python Developer. Project Scope: Documentation Automation & Markdown Management. 2. The Mission Analyze all Python (.py) files within the current directory and generate structured descriptions for each, appending them to the existing Scripts Description.md file. The goal is to create a comprehensive "Source of Truth" for the repository's functionality using the established Markdown format. 3. Expected Behavior File Discovery: Scan the root directory for all .py files. Logic Extraction: * Read the source code of each script. Identify the primary objective (e.g., file I/O, API interaction, data processing). Extract key features (libraries used, specific Excel operations, clipboard actions, etc.). Formatting: For each new script, generate a section that includes: A numbered header (e.g., ##### 3. script_name.py). A brief "purpose" line in parentheses. A list of functional "✅" bullet points. Content Alignment: Mirror the style of update_lengths.py and copy_description.py, focusing on technical actions (e.g., "Uses [library]", "Handles [error]", "Saves [file]"). Appending: Write the new descriptions to the end of Scripts Description.md without overwriting or refactoring the existing content. 4. Technical Constraints Language: Python analysis logic. Preservation: Do not modify any .py files. Only modify Scripts Description.md. Style Match: Ensure the indentation, spacing ( ), and emoji usage match the reference document exactly. 5. Verification Steps Terminal Command: Run cat "Scripts Description.md" to verify the content has been appended. Validation: Ensure the number of headers in the Markdown file matches the total number of Python scripts in the directory. Success Artifact: A complete Scripts Description.md file where every script has a "Mission-ready" summary. 6. Mission Summary (Antigravity Task List) [ ] Scan directory for all .py files not already documented in Scripts Description.md. [ ] Analyze script logic and external library dependencies. [ ] Draft a concise summary and functional checklist for each script. [ ] Format the draft to match the provided Markdown template (Header, subtitle, and ✅ points). [ ] Append the new descriptions to Scripts Description.md. [ ] Verify formatting consistency across the entire document.