Build custom tools fast, secure, and truly yours.

I want to build an app that shows the documentation of my product with the feature of chat that connects to the LLM, gives the context of the entire documentation, and enables the user to chat with that documentation, ask questions, and so on. The site should have a header. In the header, we should have YouTube, LinkedIn, X, links to the social media profiles, there should be a search bar, and there should be a link to the website. There should be a sidebar where there are all sections of the documentation. There should be sections that are collapsible and each section has any number of pages in it. I should be able to expand the sections, collapse them, and whenever a page changes, I want to maintain the sidebar. So for example, if I expanded one section and I clicked on one of the pages, when the page loads, I still want to have that only one section opened in the sidebar. Then there should be a main content in the middle, and there should be a chat feature, so small chat box in the bottom right. If a user clicks on it, it should open a pop-up where a user can chat with the LLM. The user should have an input field and there should be speech bubbles by the LLM, let's call it Pythagora, assistant, and by the user so they can chat in that pop-up window. Add the button to clear the context of the conversation in that pop-up window and the loader while the LLM is generating the response. When you make this LLM request, I want to use Claude Haiku 3.5 by Entropic, and I want to use prompt caching and make sure that the entire docs are sent in a system message, and that system message needs to be cached on the Entropic API so that we don't spend a lot of money while making requests, and user message and LLM response should be all the messages. Then I want to, on the back end and the front end, I want to limit the size of each message that the user can send, so make sure that the user cannot send more than 200 characters and ensure that this is validated on the back end as well. Then add a counter with a maximum number of messages before clearing the context. Make sure that we can do maximum five messages, and if the five messages are hit, then the user should see a button, clear the context, or actually when a user enters the sixth message instead of the send button, there should be clear context and send button, and make sure to also verify the maximum number of messages on the back end as well. Finally, enable on the back end the limit of sending 20 messages by the same IP address within one hour, and that needs to be enforced so this cannot get more than 20 messages in one hour by one IP address, and if that limit is hit, during the next 24 hours I want to see a CAPTCHA whenever a user wants to send a message. Finally, we want to have an admin panel. In the admin panel we want to manage sections, so all the sections and all the pages within sections. I want to be able to create, delete, and manage pages, and for each page I want to be able to edit the content that can be a rich text editor, and on the back end I want to save it as a markdown file. Finally, there should be an admin login, and the admin should be able to add users along with their passwords, and that way he should be able to add the users, the admin users who can manage all these things, and make sure that the page, the markdown, when it is rendered, that it renders nice code, in a colorful way.

Build an app called PromptHub, which will enable me and my co-workers to manage our LLM prompts, and to share them with each other and basically manage all of that. I want to have three types of users, three roles, Viewer, Creator, and Admin. An admin should have admin settings where they can manage all the users, invite new users. When they invite them, they should get an email to sign up, to set a password, and to basically access the platform that way. And the admin should be able to change the role for each user. And while inviting a user, the admin should be able to choose the role for that specific user. Actually, it shouldn't be able to set the password, but they should just get an access. And logging in should be done through Google Login. And so, basically, when a user is invited, then they get access, and they should get an email with a link to log in, and they should log in with Google. On the homepage, there should be a search bar, a list of prompts, and a toggle for favorite prompts. Next to each prompt, I should have a star that, when clicked, this prompt is labeled for me as a user as favorite. And when I toggle favorite prompts, then I should see only my favorite prompts. And if I am an editor, if I'm a creator user, I should be able to edit the prompts, and I should have a button, edit, and that should take me to an edit prompt page. There should be also a page, my prompts, which is basically the same as homepage, but only with my prompts. And I should be able to edit all of my prompts, while for other prompts, I should be able to edit only the prompts that are set to, that anyone can edit the prompt. Then, on the prompts page, there should be all the data from the prompt. The button, add as favorite, like the star, just like on the homepage. The edit button, if this user should be able to edit this prompt. And the name of the person who created this prompt. And also add the person who created it on the homepage as well. Then there should be create or edit a prompt page. On it, I should be able to add a title to the prompt, a description, the actual prompt, which is basically text. This should be like big text fields. And I should be able to add any number of labels, so there should be an input field where I can start typing and search for all the existing labels, and I should be able to add a new label if it doesn't exist. I should be able to, I should have a toggle system prompt. If I toggle it, then there should be another input field for the system prompt that should be saved as well. And then there should be a toggle if this prompt should be available in the API. Then there should be a dropdown where I should be able to set if this prompt is editable only by me, by other creators, or by other creators with my approval. If a creator edits my prompt and if my prompt is set to edit with approval, I should get an email and I should get on the approval page. On the approval page, I should see all the changes in git style that has been changed, and I should see the name of the creator who is editing this prompt, and I should be able to accept changes or decline changes. And both editing or declining, the creator who edited this prompt should get an email that their changes have been accepted or denied. And finally, on this page, I should see a history of this prompt. It should be in a sidebar. I should be able to click a button that should expand the sidebar and I should see the entire history of changes, the time when the change was made, by whom the change was made, and I should be able to click it and it should open up a pop-up with all the changes for this change and I should be able to roll back the whole prompt to this specific version. For the labels, there should be a general label where I can basically add anything, recommended LLMs labels, and recommendations to use. In recommendations to use labels, I should also be able to add any kind of recommendation. This should be the most prominent label and it should have a separate section while looking at the prompt, while general label and recommended LLMs should have just small separate sections. And finally, there should be an API, so each user should have their own API key which they should get in settings and with this API key, I should be able to get all the prompts that were set to be, that were toggled to be available in the API, for that specific user that has access to those prompts.

Create a GitHub dashboard that will enable me to have a dashboard of all the GitHub metrics from my team. It needs to have three different pages. The first one should be a homepage and it should show expandable list items, one below each other, per week. And for each week in the collapsed view, it should show the number of releases. This should be the most prominent number. And the leaderboard, like the number one, number two, and number three, spots of developers who had the most PRs merged by them that week. The second page should be branches and it should show the number of active branches that we have right now and the number of stale branches. And the stale branch should be a branch that had the last commit more than one week ago. And stale branches should be the most prominent. The view on the top, there should be a number of total branches, number of stale branches, and below there should be two sections, a list of active branches and stale branches, and I should be able to click on each of those and open it up on GitHub. Also, next to each branch, I want to see who had the last commit in that branch, which developer, and their thumbnail or their avatar from GitHub. And finally, we have the charts view, the charts page. It should show four different charts, one below each other. First one is the number of merged PRs per week. So the x-axis should have weeks and the y-axis should be the number of merged PRs. Another chart is number of releases per week. The third one is number of closed PRs per week. That means a PR that was closed and not merged. And final chart should be time to close a PR. That means the time from when the PR was opened until the time when it was closed, and it should be per week. So for all PRs that were merged that week, how many of them, or the average time between the opening the PR and the closed PRs for the closed PRs that week. Also, I want to add on the top of the homepage, I want to add four different numbers, four different metrics. They should be the most prominent ones. The first one should be that the number of open PRs, the number of stale PRs, that is a PR that was opened more than one week ago. And inside that number there should be the number of draft PRs that are stale and number of active PRs that are stale. Then the number of branches and the number of stale branches by the formula that I already explained. And that's pretty much it. Also in the chart, time to close a PR, don't count the draft PRs between the opening and closing, but only PRs that were open.

‍

Create an OKR tracking tool. It should have three different roles. An admin role, manager role, and IC role. An admin should basically have only a user management page where they can create teams. Each team should have one manager and multiple ICs. The admin should be able to invite managers and ICs to the platform through an email. The user should be added to the system. They should be sent a page where they can change their password the first time. From then on, they should be able to log into the system. The manager should see all their teams that they are assigned to. For each team, they should view all the ICs and click on each of the ICs and open up an IC view. In the IC view, they should have a list of weeks. For each week, they should be able to expand the week. On the top, there should be a current week. It should be colored differently. For each week, when you expand it, there should be one section with results and one section with goals. Results is just a static text area. Goals should be a rich text box where the manager and the IC should be able to collaborate and add comments by selecting text and commenting on a specific part of the text, just like Google Docs. It should be basically a copy of Google Docs. Whenever a manager adds a comment, the IC should get an email notification that a comment has been added and they should be able to see all the comments and collaborate on specific parts of the text, just like Google Docs. On the results, results should be one text box and on the bottom, there should be a chat area. They should be able to chat with the results through an LLM. When an LLM request is being made, they should get all the results from that week for that specific IC and the manager should get answers from an LLM. A manager should be able to ask a specific question about the results for that week. Then the IC role should see a list of weeks. Again, on the top should be the current week and for each week they should be able to add goals. This is again the Rich Text Editor that has the ability to select parts of the text and comment and basically collaborate with the manager, just like Google Docs. They should be able to edit the goals and save them and they should be able to... Whenever they save the goals, the manager should get an email that the goals were set. And there should be a results area where they should just add results and submit them and then the manager should get an email with a short summary of the results for that specific week. And finally, an admin should also have settings where they can set up automations. When should the ICs get an email that should say that they should add their goals for next week. So for example, I might want to set it for Monday, 8 in the morning, UTC. Someone else might do it differently. So the admin should set when the email is being sent to the IC for that specific week. For email sending, use Postmark. And for the LLM, use OpenAI's GPT-5.

I want to create an app that will allow me to chat with all of my unread messages on Slack. So I want this app to connect to my Slack account, get all of the unread messages for me, show me all the unread messages, show me the number of unread messages. I want to have a refresh button right there on the homepage so that I can refresh it. And I want to be able to view all of the unread messages individually by channels. So just have a list of channels or maybe a dropdown, view all messages. Then inside it, there should be grouped by channels. And if I click on each one, I should see it should expand to actually all of the messages that are unread in that channel. And most importantly, I want to have on the bottom of the screen an input field to start chatting with AI with my messages. So I want you to use either GPT-5 or GPT-Audio LLM model. Actually, you can use GPT-Audio. And in it, I want you to send all of the unread messages and whatever audio that I sent. So I want to be able to click, record my voice, and I want to have some nice animation. All that's happening. And when I click send, that's when it sends the message to GPT-Audio. And I want a textual response about everything that LLM said. So use OpenAI's API. And also, when I start recording, I want to be able to cancel the recording so nothing happens.

I want to build an employee onboarding application that on the homepage should have all the added employees and the button to add a new employee. When I click on the button, add a new employee, I should be able to choose a department, customer support, development and marketing, add new employee's name, company email for that user, team lead email and their personal email where they will get a notification once all the accesses have been given. Customer support users should get access to Intercom, development users from development department should get access to AWS, GitHub, and PostHog, but when you assign a GitHub in PostHog, first send an email to the team lead to set repositories from this organization where original employee will get the access to, then that the team lead should get a link to a page where we should list all the available repositories from the current organization. Make sure to use requestSecret MCP to ask me for all needed credentials during the backend implementation. Once they check all the repositories, they can click done and after that continue with the flow. Then the next thing is to send an email to the employee's personal email to request their GitHub username. Once they get an email, they should open up a specific page to enter their GitHub username. Once they enter and click done, then we should give them the access to all these repositories. And also make sure that on each employee's page, when I open it up, I want to see the entire workflow that is triggered and I want to see all the accesses that they have been given the access to. And once all the accesses have been given, send an email to the employee's personal email with the list of all the accesses that they have been given. And also when I choose the department, I want to see the flow that will be triggered and all the accesses that will be given for that specific department for that user, the employee.

‍

I want to build an app that shows the documentation of my product with the feature of chat that connects to the LLM, gives the context of the entire documentation, and enables the user to chat with that documentation, ask questions, and so on. The site should have a header. In the header, we should have YouTube, LinkedIn, X, links to the social media profiles, there should be a search bar, and there should be a link to the website. There should be a sidebar where there are all sections of the documentation. There should be sections that are collapsible and each section has any number of pages in it. I should be able to expand the sections, collapse them, and whenever a page changes, I want to maintain the sidebar. So for example, if I expanded one section and I clicked on one of the pages, when the page loads, I still want to have that only one section opened in the sidebar. Then there should be a main content in the middle, and there should be a chat feature, so small chat box in the bottom right. If a user clicks on it, it should open a pop-up where a user can chat with the LLM. The user should have an input field and there should be speech bubbles by the LLM, let's call it Pythagora, assistant, and by the user so they can chat in that pop-up window. Add the button to clear the context of the conversation in that pop-up window and the loader while the LLM is generating the response. When you make this LLM request, I want to use Claude Haiku 3.5 by Entropic, and I want to use prompt caching and make sure that the entire docs are sent in a system message, and that system message needs to be cached on the Entropic API so that we don't spend a lot of money while making requests, and user message and LLM response should be all the messages. Then I want to, on the back end and the front end, I want to limit the size of each message that the user can send, so make sure that the user cannot send more than 200 characters and ensure that this is validated on the back end as well. Then add a counter with a maximum number of messages before clearing the context. Make sure that we can do maximum five messages, and if the five messages are hit, then the user should see a button, clear the context, or actually when a user enters the sixth message instead of the send button, there should be clear context and send button, and make sure to also verify the maximum number of messages on the back end as well. Finally, enable on the back end the limit of sending 20 messages by the same IP address within one hour, and that needs to be enforced so this cannot get more than 20 messages in one hour by one IP address, and if that limit is hit, during the next 24 hours I want to see a CAPTCHA whenever a user wants to send a message. Finally, we want to have an admin panel. In the admin panel we want to manage sections, so all the sections and all the pages within sections. I want to be able to create, delete, and manage pages, and for each page I want to be able to edit the content that can be a rich text editor, and on the back end I want to save it as a markdown file. Finally, there should be an admin login, and the admin should be able to add users along with their passwords, and that way he should be able to add the users, the admin users who can manage all these things, and make sure that the page, the markdown, when it is rendered, that it renders nice code, in a colorful way.

Build an app called PromptHub, which will enable me and my co-workers to manage our LLM prompts, and to share them with each other and basically manage all of that. I want to have three types of users, three roles, Viewer, Creator, and Admin. An admin should have admin settings where they can manage all the users, invite new users. When they invite them, they should get an email to sign up, to set a password, and to basically access the platform that way. And the admin should be able to change the role for each user. And while inviting a user, the admin should be able to choose the role for that specific user. Actually, it shouldn't be able to set the password, but they should just get an access. And logging in should be done through Google Login. And so, basically, when a user is invited, then they get access, and they should get an email with a link to log in, and they should log in with Google. On the homepage, there should be a search bar, a list of prompts, and a toggle for favorite prompts. Next to each prompt, I should have a star that, when clicked, this prompt is labeled for me as a user as favorite. And when I toggle favorite prompts, then I should see only my favorite prompts. And if I am an editor, if I'm a creator user, I should be able to edit the prompts, and I should have a button, edit, and that should take me to an edit prompt page. There should be also a page, my prompts, which is basically the same as homepage, but only with my prompts. And I should be able to edit all of my prompts, while for other prompts, I should be able to edit only the prompts that are set to, that anyone can edit the prompt. Then, on the prompts page, there should be all the data from the prompt. The button, add as favorite, like the star, just like on the homepage. The edit button, if this user should be able to edit this prompt. And the name of the person who created this prompt. And also add the person who created it on the homepage as well. Then there should be create or edit a prompt page. On it, I should be able to add a title to the prompt, a description, the actual prompt, which is basically text. This should be like big text fields. And I should be able to add any number of labels, so there should be an input field where I can start typing and search for all the existing labels, and I should be able to add a new label if it doesn't exist. I should be able to, I should have a toggle system prompt. If I toggle it, then there should be another input field for the system prompt that should be saved as well. And then there should be a toggle if this prompt should be available in the API. Then there should be a dropdown where I should be able to set if this prompt is editable only by me, by other creators, or by other creators with my approval. If a creator edits my prompt and if my prompt is set to edit with approval, I should get an email and I should get on the approval page. On the approval page, I should see all the changes in git style that has been changed, and I should see the name of the creator who is editing this prompt, and I should be able to accept changes or decline changes. And both editing or declining, the creator who edited this prompt should get an email that their changes have been accepted or denied. And finally, on this page, I should see a history of this prompt. It should be in a sidebar. I should be able to click a button that should expand the sidebar and I should see the entire history of changes, the time when the change was made, by whom the change was made, and I should be able to click it and it should open up a pop-up with all the changes for this change and I should be able to roll back the whole prompt to this specific version. For the labels, there should be a general label where I can basically add anything, recommended LLMs labels, and recommendations to use. In recommendations to use labels, I should also be able to add any kind of recommendation. This should be the most prominent label and it should have a separate section while looking at the prompt, while general label and recommended LLMs should have just small separate sections. And finally, there should be an API, so each user should have their own API key which they should get in settings and with this API key, I should be able to get all the prompts that were set to be, that were toggled to be available in the API, for that specific user that has access to those prompts.

Create a CRM application that is a very simple app. I want for a user to manage their own CRM pipeline, add any number of columns. It should be like a Kanban board and in it I should be able to add cards. Each card should be a new lead. When I open the card I want to have a title, description, and in each card I want to be able to add any number of conversations that I had with the lead. And when I add a conversation I should be able to add a link to Fireflies and some notes on my end. And whenever I add that I want to be able to set a reminder. The default reminder should be in three days from the day that I talked. If I don't add any new conversation with that lead into the CRM with after those three days I should get an email notification that to ping that user, that lead. I should be able to name the columns and I want to be able to color code each card with a label, just like in Trello. I should be able to name the columns and I want to be able to color code each card with a label, just like in Trello.

Create an OKR tracking tool. It should have three different roles. An admin role, manager role, and IC role. An admin should basically have only a user management page where they can create teams. Each team should have one manager and multiple ICs. The admin should be able to invite managers and ICs to the platform through an email. The user should be added to the system. They should be sent a page where they can change their password the first time. From then on, they should be able to log into the system. The manager should see all their teams that they are assigned to. For each team, they should view all the ICs and click on each of the ICs and open up an IC view. In the IC view, they should have a list of weeks. For each week, they should be able to expand the week. On the top, there should be a current week. It should be colored differently. For each week, when you expand it, there should be one section with results and one section with goals. Results is just a static text area. Goals should be a rich text box where the manager and the IC should be able to collaborate and add comments by selecting text and commenting on a specific part of the text, just like Google Docs. It should be basically a copy of Google Docs. Whenever a manager adds a comment, the IC should get an email notification that a comment has been added and they should be able to see all the comments and collaborate on specific parts of the text, just like Google Docs. On the results, results should be one text box and on the bottom, there should be a chat area. They should be able to chat with the results through an LLM. When an LLM request is being made, they should get all the results from that week for that specific IC and the manager should get answers from an LLM. A manager should be able to ask a specific question about the results for that week. Then the IC role should see a list of weeks. Again, on the top should be the current week and for each week they should be able to add goals. This is again the Rich Text Editor that has the ability to select parts of the text and comment and basically collaborate with the manager, just like Google Docs. They should be able to edit the goals and save them and they should be able to... Whenever they save the goals, the manager should get an email that the goals were set. And there should be a results area where they should just add results and submit them and then the manager should get an email with a short summary of the results for that specific week. And finally, an admin should also have settings where they can set up automations. When should the ICs get an email that should say that they should add their goals for next week. So for example, I might want to set it for Monday, 8 in the morning, UTC. Someone else might do it differently. So the admin should set when the email is being sent to the IC for that specific week. For email sending, use Postmark. And for the LLM, use OpenAI's GPT-5.

A visual dictionary that instantly translates complex English phrases and idioms into illustrative GIFs or images. By providing immediate visual context, it helps users grasp the true meaning of language beyond literal definitions.

I want to create an app that will allow me to chat with all of my unread messages on Slack. So I want this app to connect to my Slack account, get all of the unread messages for me, show me all the unread messages, show me the number of unread messages. I want to have a refresh button right there on the homepage so that I can refresh it. And I want to be able to view all of the unread messages individually by channels. So just have a list of channels or maybe a dropdown, view all messages. Then inside it, there should be grouped by channels. And if I click on each one, I should see it should expand to actually all of the messages that are unread in that channel. And most importantly, I want to have on the bottom of the screen an input field to start chatting with AI with my messages. So I want you to use either GPT-5 or GPT-Audio LLM model. Actually, you can use GPT-Audio. And in it, I want you to send all of the unread messages and whatever audio that I sent. So I want to be able to click, record my voice, and I want to have some nice animation. All that's happening. And when I click send, that's when it sends the message to GPT-Audio. And I want a textual response about everything that LLM said. So use OpenAI's API. And also, when I start recording, I want to be able to cancel the recording so nothing happens.

I want to build an employee onboarding application that on the homepage should have all the added employees and the button to add a new employee. When I click on the button, add a new employee, I should be able to choose a department, customer support, development and marketing, add new employee's name, company email for that user, team lead email and their personal email where they will get a notification once all the accesses have been given. Customer support users should get access to Intercom, development users from development department should get access to AWS, GitHub, and PostHog, but when you assign a GitHub in PostHog, first send an email to the team lead to set repositories from this organization where original employee will get the access to, then that the team lead should get a link to a page where we should list all the available repositories from the current organization. Make sure to use requestSecret MCP to ask me for all needed credentials during the backend implementation. Once they check all the repositories, they can click done and after that continue with the flow. Then the next thing is to send an email to the employee's personal email to request their GitHub username. Once they get an email, they should open up a specific page to enter their GitHub username. Once they enter and click done, then we should give them the access to all these repositories. And also make sure that on each employee's page, when I open it up, I want to see the entire workflow that is triggered and I want to see all the accesses that they have been given the access to. And once all the accesses have been given, send an email to the employee's personal email with the list of all the accesses that they have been given. And also when I choose the department, I want to see the flow that will be triggered and all the accesses that will be given for that specific department for that user, the employee.

‍

I want to build an app that shows the documentation of my product with the feature of chat that connects to the LLM, gives the context of the entire documentation, and enables the user to chat with that documentation, ask questions, and so on. The site should have a header. In the header, we should have YouTube, LinkedIn, X, links to the social media profiles, there should be a search bar, and there should be a link to the website. There should be a sidebar where there are all sections of the documentation. There should be sections that are collapsible and each section has any number of pages in it. I should be able to expand the sections, collapse them, and whenever a page changes, I want to maintain the sidebar. So for example, if I expanded one section and I clicked on one of the pages, when the page loads, I still want to have that only one section opened in the sidebar. Then there should be a main content in the middle, and there should be a chat feature, so small chat box in the bottom right. If a user clicks on it, it should open a pop-up where a user can chat with the LLM. The user should have an input field and there should be speech bubbles by the LLM, let's call it Pythagora, assistant, and by the user so they can chat in that pop-up window. Add the button to clear the context of the conversation in that pop-up window and the loader while the LLM is generating the response. When you make this LLM request, I want to use Claude Haiku 3.5 by Entropic, and I want to use prompt caching and make sure that the entire docs are sent in a system message, and that system message needs to be cached on the Entropic API so that we don't spend a lot of money while making requests, and user message and LLM response should be all the messages. Then I want to, on the back end and the front end, I want to limit the size of each message that the user can send, so make sure that the user cannot send more than 200 characters and ensure that this is validated on the back end as well. Then add a counter with a maximum number of messages before clearing the context. Make sure that we can do maximum five messages, and if the five messages are hit, then the user should see a button, clear the context, or actually when a user enters the sixth message instead of the send button, there should be clear context and send button, and make sure to also verify the maximum number of messages on the back end as well. Finally, enable on the back end the limit of sending 20 messages by the same IP address within one hour, and that needs to be enforced so this cannot get more than 20 messages in one hour by one IP address, and if that limit is hit, during the next 24 hours I want to see a CAPTCHA whenever a user wants to send a message. Finally, we want to have an admin panel. In the admin panel we want to manage sections, so all the sections and all the pages within sections. I want to be able to create, delete, and manage pages, and for each page I want to be able to edit the content that can be a rich text editor, and on the back end I want to save it as a markdown file. Finally, there should be an admin login, and the admin should be able to add users along with their passwords, and that way he should be able to add the users, the admin users who can manage all these things, and make sure that the page, the markdown, when it is rendered, that it renders nice code, in a colorful way.

Build an app called PromptHub, which will enable me and my co-workers to manage our LLM prompts, and to share them with each other and basically manage all of that. I want to have three types of users, three roles, Viewer, Creator, and Admin. An admin should have admin settings where they can manage all the users, invite new users. When they invite them, they should get an email to sign up, to set a password, and to basically access the platform that way. And the admin should be able to change the role for each user. And while inviting a user, the admin should be able to choose the role for that specific user. Actually, it shouldn't be able to set the password, but they should just get an access. And logging in should be done through Google Login. And so, basically, when a user is invited, then they get access, and they should get an email with a link to log in, and they should log in with Google. On the homepage, there should be a search bar, a list of prompts, and a toggle for favorite prompts. Next to each prompt, I should have a star that, when clicked, this prompt is labeled for me as a user as favorite. And when I toggle favorite prompts, then I should see only my favorite prompts. And if I am an editor, if I'm a creator user, I should be able to edit the prompts, and I should have a button, edit, and that should take me to an edit prompt page. There should be also a page, my prompts, which is basically the same as homepage, but only with my prompts. And I should be able to edit all of my prompts, while for other prompts, I should be able to edit only the prompts that are set to, that anyone can edit the prompt. Then, on the prompts page, there should be all the data from the prompt. The button, add as favorite, like the star, just like on the homepage. The edit button, if this user should be able to edit this prompt. And the name of the person who created this prompt. And also add the person who created it on the homepage as well. Then there should be create or edit a prompt page. On it, I should be able to add a title to the prompt, a description, the actual prompt, which is basically text. This should be like big text fields. And I should be able to add any number of labels, so there should be an input field where I can start typing and search for all the existing labels, and I should be able to add a new label if it doesn't exist. I should be able to, I should have a toggle system prompt. If I toggle it, then there should be another input field for the system prompt that should be saved as well. And then there should be a toggle if this prompt should be available in the API. Then there should be a dropdown where I should be able to set if this prompt is editable only by me, by other creators, or by other creators with my approval. If a creator edits my prompt and if my prompt is set to edit with approval, I should get an email and I should get on the approval page. On the approval page, I should see all the changes in git style that has been changed, and I should see the name of the creator who is editing this prompt, and I should be able to accept changes or decline changes. And both editing or declining, the creator who edited this prompt should get an email that their changes have been accepted or denied. And finally, on this page, I should see a history of this prompt. It should be in a sidebar. I should be able to click a button that should expand the sidebar and I should see the entire history of changes, the time when the change was made, by whom the change was made, and I should be able to click it and it should open up a pop-up with all the changes for this change and I should be able to roll back the whole prompt to this specific version. For the labels, there should be a general label where I can basically add anything, recommended LLMs labels, and recommendations to use. In recommendations to use labels, I should also be able to add any kind of recommendation. This should be the most prominent label and it should have a separate section while looking at the prompt, while general label and recommended LLMs should have just small separate sections. And finally, there should be an API, so each user should have their own API key which they should get in settings and with this API key, I should be able to get all the prompts that were set to be, that were toggled to be available in the API, for that specific user that has access to those prompts.

Create a CRM application that is a very simple app. I want for a user to manage their own CRM pipeline, add any number of columns. It should be like a Kanban board and in it I should be able to add cards. Each card should be a new lead. When I open the card I want to have a title, description, and in each card I want to be able to add any number of conversations that I had with the lead. And when I add a conversation I should be able to add a link to Fireflies and some notes on my end. And whenever I add that I want to be able to set a reminder. The default reminder should be in three days from the day that I talked. If I don't add any new conversation with that lead into the CRM with after those three days I should get an email notification that to ping that user, that lead. I should be able to name the columns and I want to be able to color code each card with a label, just like in Trello. I should be able to name the columns and I want to be able to color code each card with a label, just like in Trello.

Create an OKR tracking tool. It should have three different roles. An admin role, manager role, and IC role. An admin should basically have only a user management page where they can create teams. Each team should have one manager and multiple ICs. The admin should be able to invite managers and ICs to the platform through an email. The user should be added to the system. They should be sent a page where they can change their password the first time. From then on, they should be able to log into the system. The manager should see all their teams that they are assigned to. For each team, they should view all the ICs and click on each of the ICs and open up an IC view. In the IC view, they should have a list of weeks. For each week, they should be able to expand the week. On the top, there should be a current week. It should be colored differently. For each week, when you expand it, there should be one section with results and one section with goals. Results is just a static text area. Goals should be a rich text box where the manager and the IC should be able to collaborate and add comments by selecting text and commenting on a specific part of the text, just like Google Docs. It should be basically a copy of Google Docs. Whenever a manager adds a comment, the IC should get an email notification that a comment has been added and they should be able to see all the comments and collaborate on specific parts of the text, just like Google Docs. On the results, results should be one text box and on the bottom, there should be a chat area. They should be able to chat with the results through an LLM. When an LLM request is being made, they should get all the results from that week for that specific IC and the manager should get answers from an LLM. A manager should be able to ask a specific question about the results for that week. Then the IC role should see a list of weeks. Again, on the top should be the current week and for each week they should be able to add goals. This is again the Rich Text Editor that has the ability to select parts of the text and comment and basically collaborate with the manager, just like Google Docs. They should be able to edit the goals and save them and they should be able to... Whenever they save the goals, the manager should get an email that the goals were set. And there should be a results area where they should just add results and submit them and then the manager should get an email with a short summary of the results for that specific week. And finally, an admin should also have settings where they can set up automations. When should the ICs get an email that should say that they should add their goals for next week. So for example, I might want to set it for Monday, 8 in the morning, UTC. Someone else might do it differently. So the admin should set when the email is being sent to the IC for that specific week. For email sending, use Postmark. And for the LLM, use OpenAI's GPT-5.

I want to create an app that will allow me to chat with all of my unread messages on Slack. So I want this app to connect to my Slack account, get all of the unread messages for me, show me all the unread messages, show me the number of unread messages. I want to have a refresh button right there on the homepage so that I can refresh it. And I want to be able to view all of the unread messages individually by channels. So just have a list of channels or maybe a dropdown, view all messages. Then inside it, there should be grouped by channels. And if I click on each one, I should see it should expand to actually all of the messages that are unread in that channel. And most importantly, I want to have on the bottom of the screen an input field to start chatting with AI with my messages. So I want you to use either GPT-5 or GPT-Audio LLM model. Actually, you can use GPT-Audio. And in it, I want you to send all of the unread messages and whatever audio that I sent. So I want to be able to click, record my voice, and I want to have some nice animation. All that's happening. And when I click send, that's when it sends the message to GPT-Audio. And I want a textual response about everything that LLM said. So use OpenAI's API. And also, when I start recording, I want to be able to cancel the recording so nothing happens.

I want to build an employee onboarding application that on the homepage should have all the added employees and the button to add a new employee. When I click on the button, add a new employee, I should be able to choose a department, customer support, development and marketing, add new employee's name, company email for that user, team lead email and their personal email where they will get a notification once all the accesses have been given. Customer support users should get access to Intercom, development users from development department should get access to AWS, GitHub, and PostHog, but when you assign a GitHub in PostHog, first send an email to the team lead to set repositories from this organization where original employee will get the access to, then that the team lead should get a link to a page where we should list all the available repositories from the current organization. Make sure to use requestSecret MCP to ask me for all needed credentials during the backend implementation. Once they check all the repositories, they can click done and after that continue with the flow. Then the next thing is to send an email to the employee's personal email to request their GitHub username. Once they get an email, they should open up a specific page to enter their GitHub username. Once they enter and click done, then we should give them the access to all these repositories. And also make sure that on each employee's page, when I open it up, I want to see the entire workflow that is triggered and I want to see all the accesses that they have been given the access to. And once all the accesses have been given, send an email to the employee's personal email with the list of all the accesses that they have been given. And also when I choose the department, I want to see the flow that will be triggered and all the accesses that will be given for that specific department for that user, the employee.

‍

Build an app called PromptHub, which will enable me and my co-workers to manage our LLM prompts, and to share them with each other and basically manage all of that. I want to have three types of users, three roles, Viewer, Creator, and Admin. An admin should have admin settings where they can manage all the users, invite new users. When they invite them, they should get an email to sign up, to set a password, and to basically access the platform that way. And the admin should be able to change the role for each user. And while inviting a user, the admin should be able to choose the role for that specific user. Actually, it shouldn't be able to set the password, but they should just get an access. And logging in should be done through Google Login. And so, basically, when a user is invited, then they get access, and they should get an email with a link to log in, and they should log in with Google. On the homepage, there should be a search bar, a list of prompts, and a toggle for favorite prompts. Next to each prompt, I should have a star that, when clicked, this prompt is labeled for me as a user as favorite. And when I toggle favorite prompts, then I should see only my favorite prompts. And if I am an editor, if I'm a creator user, I should be able to edit the prompts, and I should have a button, edit, and that should take me to an edit prompt page. There should be also a page, my prompts, which is basically the same as homepage, but only with my prompts. And I should be able to edit all of my prompts, while for other prompts, I should be able to edit only the prompts that are set to, that anyone can edit the prompt. Then, on the prompts page, there should be all the data from the prompt. The button, add as favorite, like the star, just like on the homepage. The edit button, if this user should be able to edit this prompt. And the name of the person who created this prompt. And also add the person who created it on the homepage as well. Then there should be create or edit a prompt page. On it, I should be able to add a title to the prompt, a description, the actual prompt, which is basically text. This should be like big text fields. And I should be able to add any number of labels, so there should be an input field where I can start typing and search for all the existing labels, and I should be able to add a new label if it doesn't exist. I should be able to, I should have a toggle system prompt. If I toggle it, then there should be another input field for the system prompt that should be saved as well. And then there should be a toggle if this prompt should be available in the API. Then there should be a dropdown where I should be able to set if this prompt is editable only by me, by other creators, or by other creators with my approval. If a creator edits my prompt and if my prompt is set to edit with approval, I should get an email and I should get on the approval page. On the approval page, I should see all the changes in git style that has been changed, and I should see the name of the creator who is editing this prompt, and I should be able to accept changes or decline changes. And both editing or declining, the creator who edited this prompt should get an email that their changes have been accepted or denied. And finally, on this page, I should see a history of this prompt. It should be in a sidebar. I should be able to click a button that should expand the sidebar and I should see the entire history of changes, the time when the change was made, by whom the change was made, and I should be able to click it and it should open up a pop-up with all the changes for this change and I should be able to roll back the whole prompt to this specific version. For the labels, there should be a general label where I can basically add anything, recommended LLMs labels, and recommendations to use. In recommendations to use labels, I should also be able to add any kind of recommendation. This should be the most prominent label and it should have a separate section while looking at the prompt, while general label and recommended LLMs should have just small separate sections. And finally, there should be an API, so each user should have their own API key which they should get in settings and with this API key, I should be able to get all the prompts that were set to be, that were toggled to be available in the API, for that specific user that has access to those prompts.

Create a GitHub dashboard that will enable me to have a dashboard of all the GitHub metrics from my team. It needs to have three different pages. The first one should be a homepage and it should show expandable list items, one below each other, per week. And for each week in the collapsed view, it should show the number of releases. This should be the most prominent number. And the leaderboard, like the number one, number two, and number three, spots of developers who had the most PRs merged by them that week. The second page should be branches and it should show the number of active branches that we have right now and the number of stale branches. And the stale branch should be a branch that had the last commit more than one week ago. And stale branches should be the most prominent. The view on the top, there should be a number of total branches, number of stale branches, and below there should be two sections, a list of active branches and stale branches, and I should be able to click on each of those and open it up on GitHub. Also, next to each branch, I want to see who had the last commit in that branch, which developer, and their thumbnail or their avatar from GitHub. And finally, we have the charts view, the charts page. It should show four different charts, one below each other. First one is the number of merged PRs per week. So the x-axis should have weeks and the y-axis should be the number of merged PRs. Another chart is number of releases per week. The third one is number of closed PRs per week. That means a PR that was closed and not merged. And final chart should be time to close a PR. That means the time from when the PR was opened until the time when it was closed, and it should be per week. So for all PRs that were merged that week, how many of them, or the average time between the opening the PR and the closed PRs for the closed PRs that week. Also, I want to add on the top of the homepage, I want to add four different numbers, four different metrics. They should be the most prominent ones. The first one should be that the number of open PRs, the number of stale PRs, that is a PR that was opened more than one week ago. And inside that number there should be the number of draft PRs that are stale and number of active PRs that are stale. Then the number of branches and the number of stale branches by the formula that I already explained. And that's pretty much it. Also in the chart, time to close a PR, don't count the draft PRs between the opening and closing, but only PRs that were open.

‍

Create a CRM application that is a very simple app. I want for a user to manage their own CRM pipeline, add any number of columns. It should be like a Kanban board and in it I should be able to add cards. Each card should be a new lead. When I open the card I want to have a title, description, and in each card I want to be able to add any number of conversations that I had with the lead. And when I add a conversation I should be able to add a link to Fireflies and some notes on my end. And whenever I add that I want to be able to set a reminder. The default reminder should be in three days from the day that I talked. If I don't add any new conversation with that lead into the CRM with after those three days I should get an email notification that to ping that user, that lead. I should be able to name the columns and I want to be able to color code each card with a label, just like in Trello. I should be able to name the columns and I want to be able to color code each card with a label, just like in Trello.

Create an OKR tracking tool. It should have three different roles. An admin role, manager role, and IC role. An admin should basically have only a user management page where they can create teams. Each team should have one manager and multiple ICs. The admin should be able to invite managers and ICs to the platform through an email. The user should be added to the system. They should be sent a page where they can change their password the first time. From then on, they should be able to log into the system. The manager should see all their teams that they are assigned to. For each team, they should view all the ICs and click on each of the ICs and open up an IC view. In the IC view, they should have a list of weeks. For each week, they should be able to expand the week. On the top, there should be a current week. It should be colored differently. For each week, when you expand it, there should be one section with results and one section with goals. Results is just a static text area. Goals should be a rich text box where the manager and the IC should be able to collaborate and add comments by selecting text and commenting on a specific part of the text, just like Google Docs. It should be basically a copy of Google Docs. Whenever a manager adds a comment, the IC should get an email notification that a comment has been added and they should be able to see all the comments and collaborate on specific parts of the text, just like Google Docs. On the results, results should be one text box and on the bottom, there should be a chat area. They should be able to chat with the results through an LLM. When an LLM request is being made, they should get all the results from that week for that specific IC and the manager should get answers from an LLM. A manager should be able to ask a specific question about the results for that week. Then the IC role should see a list of weeks. Again, on the top should be the current week and for each week they should be able to add goals. This is again the Rich Text Editor that has the ability to select parts of the text and comment and basically collaborate with the manager, just like Google Docs. They should be able to edit the goals and save them and they should be able to... Whenever they save the goals, the manager should get an email that the goals were set. And there should be a results area where they should just add results and submit them and then the manager should get an email with a short summary of the results for that specific week. And finally, an admin should also have settings where they can set up automations. When should the ICs get an email that should say that they should add their goals for next week. So for example, I might want to set it for Monday, 8 in the morning, UTC. Someone else might do it differently. So the admin should set when the email is being sent to the IC for that specific week. For email sending, use Postmark. And for the LLM, use OpenAI's GPT-5.

Create a CRM application that is a very simple app. I want for a user to manage their own CRM pipeline, add any number of columns. It should be like a Kanban board and in it I should be able to add cards. Each card should be a new lead. When I open the card I want to have a title, description, and in each card I want to be able to add any number of conversations that I had with the lead. And when I add a conversation I should be able to add a link to Fireflies and some notes on my end. And whenever I add that I want to be able to set a reminder. The default reminder should be in three days from the day that I talked. If I don't add any new conversation with that lead into the CRM with after those three days I should get an email notification that to ping that user, that lead. I should be able to name the columns and I want to be able to color code each card with a label, just like in Trello. I should be able to name the columns and I want to be able to color code each card with a label, just like in Trello.

Create an OKR tracking tool. It should have three different roles. An admin role, manager role, and IC role. An admin should basically have only a user management page where they can create teams. Each team should have one manager and multiple ICs. The admin should be able to invite managers and ICs to the platform through an email. The user should be added to the system. They should be sent a page where they can change their password the first time. From then on, they should be able to log into the system. The manager should see all their teams that they are assigned to. For each team, they should view all the ICs and click on each of the ICs and open up an IC view. In the IC view, they should have a list of weeks. For each week, they should be able to expand the week. On the top, there should be a current week. It should be colored differently. For each week, when you expand it, there should be one section with results and one section with goals. Results is just a static text area. Goals should be a rich text box where the manager and the IC should be able to collaborate and add comments by selecting text and commenting on a specific part of the text, just like Google Docs. It should be basically a copy of Google Docs. Whenever a manager adds a comment, the IC should get an email notification that a comment has been added and they should be able to see all the comments and collaborate on specific parts of the text, just like Google Docs. On the results, results should be one text box and on the bottom, there should be a chat area. They should be able to chat with the results through an LLM. When an LLM request is being made, they should get all the results from that week for that specific IC and the manager should get answers from an LLM. A manager should be able to ask a specific question about the results for that week. Then the IC role should see a list of weeks. Again, on the top should be the current week and for each week they should be able to add goals. This is again the Rich Text Editor that has the ability to select parts of the text and comment and basically collaborate with the manager, just like Google Docs. They should be able to edit the goals and save them and they should be able to... Whenever they save the goals, the manager should get an email that the goals were set. And there should be a results area where they should just add results and submit them and then the manager should get an email with a short summary of the results for that specific week. And finally, an admin should also have settings where they can set up automations. When should the ICs get an email that should say that they should add their goals for next week. So for example, I might want to set it for Monday, 8 in the morning, UTC. Someone else might do it differently. So the admin should set when the email is being sent to the IC for that specific week. For email sending, use Postmark. And for the LLM, use OpenAI's GPT-5.