Overview
This prompt aims to guide a programmer in enhancing a GUI by integrating new tabs based on user requests. Developers working on GUI applications will benefit from these structured instructions to ensure consistency and functionality.
Prompt Overview
Purpose: The goal is to enhance the existing GUI by integrating new tabs as requested by the user.
Audience: This information is intended for developers familiar with the existing script and GUI design principles.
Distinctive Feature: The new tabs will follow the same coding style and structure as the existing “loop dash” tab for consistency.
Outcome: The final result will be a functional GUI with all requested tabs properly integrated and tested for usability.
Quick Specs
- Media: Text
- Use case: Generation
- Industry: Development Tools & DevOps, Productivity & Workflow, Renewable Energy (Solar, Wind, Hydro)
- Techniques: Role/Persona Prompting, Self-Critique / Reflection, Structured Output
- Models: Claude 3.5 Sonnet, Gemini 2.0 Flash, GPT-4o, Llama 3.1 70B
- Estimated time: 5-10 minutes
- Skill level: Beginner
Variables to Fill
No inputs required — just copy and use the prompt.
Example Variables Block
No example values needed for this prompt.
The Prompt
You are tasked with enhancing an existing script by integrating new tabs into the main GUI window’s user interface. The user previously requested the addition of certain tabs and has now asked you to implement these additions properly into the GUI.
**Instructions:**
– Review the existing script to identify the new tabs that were mentioned but not yet added to the main GUI interface.
– Examine how the “loop dash” tab is implemented and imported into the GUI as an example.
– Using this example as a model, correctly add all the requested new tabs to the main GUI as distinct tabs.
– Ensure the integrations adhere to the same coding style, naming conventions, and structure as the existing tabs.
– Utilize the example file provided for UI elements to guide implementation details.
– Maintain clarity, consistency, and functionality within the GUI.
**Steps:**
1. Identify all the new tabs specified in the previous user instruction.
2. Analyze the existing “loop dash” tab implementation and its integration into the main GUI.
3. Implement the new tabs following the same method.
4. Test to confirm the new tabs appear correctly in the GUI’s tab bar.
**Output Format:**
– Provide the updated script or relevant code snippets that demonstrate the correctly integrated new tabs within the main GUI.
– Include comments where appropriate to describe the changes.
**Notes:**
– If any ambiguity arises concerning the tabs to add, explain your assumptions.
– Strive for neat, maintainable code that fits seamlessly with the existing application.
Your final response should contain the code modifications clearly demonstrating the addition of all requested tabs to the main GUI window as tabs, modeled on the “loop dash” example.
Screenshot Examples
How to Use This Prompt
- Copy the prompt for context and instructions.
- Review the existing script for new tab specifications.
- Examine the “loop dash” tab implementation for guidance.
- Add the new tabs using the same coding style.
- Test the GUI to ensure new tabs are visible.
- Provide code snippets and comments for clarity.
Tips for Best Results
- Identify New Tabs: Review user requests to list all tabs that need to be added.
- Analyze Existing Implementation: Study the “loop dash” tab for integration patterns and coding style.
- Implement New Tabs: Add the new tabs to the GUI using the same structure and conventions as the “loop dash” tab.
- Test Functionality: Ensure that the new tabs are visible and functional in the GUI after integration.
FAQ
- What are the steps to add new tabs to the GUI?
Identify new tabs, analyze existing implementations, integrate new tabs, and test functionality. - How should the new tabs be integrated?
Follow the coding style and structure of the existing 'loop dash' tab for consistency. - What should be done if tab specifications are unclear?
Clarify assumptions made about the tabs and document them in the code comments. - Why is testing important after adding new tabs?
Testing ensures that new tabs function correctly and appear as intended in the GUI.
Compliance and Best Practices
- Best Practice: Review AI output for accuracy and relevance before use.
- Privacy: Avoid sharing personal, financial, or confidential data in prompts.
- Platform Policy: Your use of AI tools must comply with their terms and your local laws.
Revision History
- Version 1.0 (February 2026): Initial release.
