-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #2 from tomkat-cr/GS-154_post_hackathon_fixes
GS-154 - Post hackathon fixes
- Loading branch information
Showing
22 changed files
with
1,118 additions
and
328 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,15 @@ | ||
| Generate suggestions for web and mobile software application mind-blowing ideas. These applications should be practical and impactful. Focus on ideas that are achievable within a constrained timeframe, suitable for an experienced developer. | ||
|
|
||
| # Requirements | ||
| - The application subject is: {question} | ||
| - Include a mix of fun, practical, profitable (or with social impact depending on the subject), or utility-based ideas. | ||
| - Specifically call out the target (web vs mobile application). | ||
| - Each suggestion should clearly explain the purpose of the app and how the development can be accomplished in terms of scope. | ||
|
|
||
| # Output Format | ||
|
|
||
| Provide the output as descriptions, each one a a bullet point and including: name, goal, alingment with the application subject, and real-world impact. | ||
|
|
||
| # Notes | ||
| - Ensure simplicity by focusing on core features that solve a specific problem or add value. | ||
| - Consider app categories like productivity, fun/entertainment, personal trackers, or unique generators related to the application subject. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,16 @@ | ||
| Generate suggestions for web and mobile software application mind-blowing ideas. These applications should be practical and impactful. Focus on ideas that are achievable within a constrained timeframe, suitable for an experienced developer. | ||
|
|
||
| # Requirements | ||
| - The application subject is: {subject} | ||
| - Constrained timeframe: Ensure suggested ideas can reasonably be scoped and implemented within {timeframe}. | ||
| - Include a mix of fun, practical, profitable (or with social impact depending on the subject), or utility-based ideas. | ||
| - Specifically call out the target (web vs mobile application). | ||
| - Each suggestion should clearly explain the purpose of the app and how the development can be accomplished in terms of scope. | ||
|
|
||
| # Output Format | ||
|
|
||
| Provide the output as descriptions, each one a a bullet point and including: name, goal, alingment with the application subject, and real-world impact. | ||
|
|
||
| # Notes | ||
| - Ensure simplicity by focusing on core features that solve a specific problem or add value. | ||
| - Consider app categories like productivity, fun/entertainment, personal trackers, or unique generators related to the application subject. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,26 @@ | ||
| Generate catchy and creative names for a software application related to `{question}`. | ||
|
|
||
| Please take into consideration the nature of the application. The names should be memorable, easy to spell, and relevant to {question}. Emphasize creativity while making sure the names clearly convey the essence of the tool or service provided. | ||
|
|
||
| Aim for 5-10 different unique suggestions. You may also combine words or concepts to create meaningful and appealing names. | ||
|
|
||
| # Output Format | ||
|
|
||
| Provide a list of suggested names. Each suggestion should be on a separate line, formatted in plain text. | ||
|
|
||
| # Examples | ||
|
|
||
| **For a web application about managing daily tasks:** | ||
| - DailyZen | ||
| - PlanIt | ||
| - TaskMaster | ||
| - DoItNow | ||
| - FocusFlow | ||
|
|
||
| **For a mobile app about fitness tracking:** | ||
| - FitSync | ||
| - MoveMore | ||
| - StepBoost | ||
| - GoalGain | ||
| - ActiveLyfe | ||
|
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,66 @@ | ||
| Create content for PowerPoint slides for a presentation including the main information for each slide and prompts for generating corresponding images. | ||
|
|
||
| The presentation subject is: `{question}` | ||
|
|
||
| The presentation should contain the following slides: | ||
|
|
||
| 1. **Title Slide**: | ||
| - **Content**: `{title} and {subtitle}` generated from the presentation subject. | ||
| - **Speaker Notes**: Introduce the presentation subject and provide context. | ||
| - **Prompt for Image**: "Generate an engaging title slide image that visually introduces the subject `{question}`." | ||
|
|
||
| 2. **Problem Statement**: | ||
| - **Content**: Describe the problem or "the pain" described in the presentation subject. | ||
| - **Speaker Notes**: Explain why the problem is significant and how the audience might relate to it. | ||
| - **Prompt for Image**: "Create an image that depicts individuals facing a common situation related to `{question}`." | ||
|
|
||
| 3. **Objective**: | ||
| - **Content**: Explain the application's main goal. | ||
| - **In this case**: `{question}` | ||
| - **Speaker Notes**: Emphasize how the objective aligns with solving the problem introduced earlier. | ||
| - **Prompt for Image**: "Generate an illustration or icon set showcasing the objective related to `{question}` and how it helps target people/organizations achieve their tasks." | ||
|
|
||
| 4. **Benefits**: | ||
| - **Content**: Include the main benefits related with the presentation subject. | ||
| - **Speaker Notes**: Persuade the audience why these benefits help address the problem effectively. | ||
| - **Prompt for Image**: "Create an infographic or chart highlighting key benefits of the solution related to `{question}` compared to existing methods or alternatives." | ||
|
|
||
| 5. **Feedback and Future Development**: | ||
| - **Content**: Notable positive aspects and potential improvements of the solution related to the presentation subject. | ||
| - **Speaker Notes**: Emphasize user satisfaction and iterate potential evolution based on feedback. | ||
| - **Prompt for Image**: "Create a slide image with text boxes or sticky notes representing customer feedback and future enhancements for `{question}`." | ||
|
|
||
| 6. **Future Vision**: | ||
| - **Content**: Describe possible enhancements to the the presentation subject solution. | ||
| - **Speaker Notes**: Highlight the future possibilities of `{question}` and how it can evolve to embrace target people/organizations needs. | ||
| - **Prompt for Image**: "Depict a futuristic or evolving version of the solution for `{question}`, illustrating new possible features and enhanced capabilities." | ||
|
|
||
| 7. **Thank You Slide**: | ||
| - **Content**: A final message thanking the audience for their interest in the presentation subject. | ||
| - **Speaker Notes**: Express gratitude and briefly redirect users to follow-up links or next steps. | ||
| - **Prompt for Image**: "Design a thank you slide including a message of appreciation and space for a QR code. Ensure it's visually consistent with the rest of the presentation." | ||
|
|
||
| # Output Format | ||
|
|
||
| Provide the output as a detailed summary of slide content with image prompts in the following JSON format: | ||
|
|
||
| ```json | ||
| { | ||
| "slides": [ | ||
| { | ||
| "title": "[Title of Slide]", | ||
| "content": "[Relevant content]", | ||
| "speaker_notes": "[Extended explanation intended only for the presenter]", | ||
| "image_prompt": "[Image prompt for the generated image]" | ||
| } | ||
| ] | ||
| } | ||
| ``` | ||
|
|
||
| Include all slide details as distinct items under the "slides" array. Each JSON object should capture the title of the slide, content, speaker notes, and the corresponding prompt for the image to be generated. | ||
|
|
||
| # Notes | ||
|
|
||
| - Ensure that each slide content is succinct but informative. | ||
| - Image prompts should represent or visually summarize the key points from each slide. | ||
| - Use individual placeholders relevant to the generated `{title}, {subtitle},` or other brackets to ensure all content points are well-covered. |
Oops, something went wrong.