Recipes

Display @googleCalendar events from the last 90 days in a new page called "all events" accessible from the sidebar. Display events in a table.

Add a table called Event types Allow the user to create event types and associate a color of calendar event for each event type. ex: Customer meeting => Sage - Make sure to use the google calendar color codes/names Add a settings page to create update and delete event types.

In the calendar events list, add a column displaying the event type based on the color matching.

In this homepage, display a pie chart of where I spend my time based on the meeting types. Add a filter: this week / last week / this month (to date) / last 30 days / last 90 days.

Create a 9 week past data overview with stacked bar graph groups by meeting type. Add this graph in the dashboard page.

Create a homepage that displays my Google Calendar events from the last 7 days. Use the @Google Calendar integration. Display the events in a table with columns for: Event name, Date & Time, Status (with color-coded badges), Location, and Actions.

Filter to only show events that: - Have attendees - Contain at least 1 external invitee (email domain different from the current user's domain)

In each row, add a button called "Add a transcript". this button opens a modal which allows the user to paste a meeting transcript. when confirming make sure to save the transcript in the database.

When validating the modal, run the transcript through OpenAI to auto detect action items and tasks. while this is running, display a work in progress UI. When done, display in a second modal the tasks that were extracted. Also save the transcript in the database.

For each task in the modal, add a button "Create Task in Attio". when clicked, create a task in @Attio. Include the calendar event name in the task content. numberOfLinkedRecords to 0 to avoid linking errors.

Create a search bar to search Salesforce opportunities by name, display results as cards showing amount, owner, and close date

Create a new object called "request" with: linked SFDC opportunity, request (text), due date, request status (requested/in progress/done), outcome (accepted/denied), Owner (which will be the logged user who created the request).

Add a "Create Request" button on opportunity cards that opens a modal Modal should allow user to add the text request and due date. Create request linked to the opportunity on submit and link to current logged in user.

Create a new page that displays all requests grouped by status. Add filtering tabs (All, Requested, In Progress, Done).

Display requests as cards with the following information: opportunity name / amount / owner / due date / request status / outcome. Do not add fields in the database, rather use the opportunity id to query that data from Salesforce and display it on the card.

When clicking on a request, open a drawer and display all details about the request. Allow editing of outcome and request status via a dropdown inline.

Add the ability to add comments on requests, linked to current logged in user - persist in database, display comments in a drawer with request details.

Pull all my @Linear issues and display them in the homepage in a table with the columns ID / Title / Status / Priority / Created_at.

Add a way to filter linear issues on the homepage.

On each row, allow the user to classify each issue in one of three buckets: Metrics Movers / Customer Requests / Delight. Persist that data in the database.

Add a new page called Dashboard. In that page, add a a few graphs representing how many issues are of each bucket.

In the dashboard page, add the same filters as the homepage.

Add tabs named VELOCITY, QUALITY, HYGIENE, SHIPPING, WORKLOAD.

Using github data, On the VELOCITY dashboard, show how quickly engineering work moves. Include PR lead time from open → merge, number of PRs opened and closed per week, and daily commit activity across repos. Highlight trends so we can spot improvements or slowdowns over time.

On the QUALITY dashboard, monitor CI reliability. Surface failing workflow runs, slow or long-running builds, and recent success/failure rates by workflow. Make it easy to identify flaky pipelines, unstable branches, or recurring failure patterns.

On the HYGIENE dashboard, flag work needing attention: stale issues with no updates, unassigned issues, PRs or branches with no recent activity, and anything that’s aging past our typical SLAs. Help us keep the backlog and active work clean.

On the SHIPPING dashboard, visualize release activity. Show releases per week or month, recent release notes, who authored each release, and any gaps in cadence. Give us a clear picture of how consistently we’re delivering new versions.

On the WORKLOAD dashboard, show how engineering time is distributed. Include commit volume per engineer, busiest coding days, and indicators of after-hours or weekend work. Help us monitor workload balance and spot signs of burnout early.

Add Tabs for hackathons, ideas, voting, results, teams, and settings.

Build a Hackathons data table with basic fields (name, dates,location), search, and full create/edit/delete actions. Display a table of Hackathons on the homepage.

Show a hackathon details drawer with editable fields.

Create a new object Participants (first name, last name, email) table linked to hackathons to manage who is part of a hackathon. Allow a user to add participants to a hackathon.

Create an Ideas data table linked to hackathons. Each idea has a one liner, description and a status. Each idea is also linked to a participant. Display a list of ideas in a new page, filtered per Hackathon. Allow a user to add, edit and delete ideas. Add a few seed data for ideas. Add a detailed drawer view for each idea.

Within the hackathon details view, show its ideas and allow adding new hackathon-specific brainstorm ideas.

Build a $100 voting interface that lets a participant allocate exactly 100 points across ideas for a selected hackathon.

Show a hackathon results table that aggregates votes per idea and ranks them by total allocation.

Create an Assignments table linking participants (builders) to ideas and show a team management view.

Configure a settings table that maps each hackathon to a Slack channel pulled from Slack.

When an idea is marked as shipped, automatically send a celebratory Slack message to the hackathon’s configured channel.

Pull @Jira issues into a table displayed on the homepage. Use JQL to only pull Jira issues created less than 20 weeks ago and only the issues in status "In progress".

Create a new object Questions: - Discussed Y/N // Linked Jira issue // Reporter - Display all questions in a new page.

In the issue row, add a button named "add question". It opens a modal where a user can ask a question about a specific issue. When confirming it then creates the question record, linked to this user and Jira issue.

Display all questions under the list of issues on the homepage. Group them by Discussed Yes or No and make that collapsible.

In the questions section on the homepage, add a button to mark as discussed.

Add field "Note" to the question object. Add a button View details in the question section and display the question, the description, and display the notes fields as input text. When closing the model, it should save the notes.

Pull @Linear projects and display them on the home page.

Group them by status and show KPIs at the top of the page.

On a new page display a list of @Linear issues using the search-issue function. Only pull the issues created in the last 3 months. For each issue display status and priority.

When I click on a project, I want to be redirected to a new page that shows the details of the projects including its associated issues.

On a new page, show the number of issue that have been done per week.

Create a database table for weekly goals with name and status (not-started, in-progress, completed). Show them in a table in the homepage with a create goal dialog.

Allow me to link a weekly goal to a @Linear project. Add a "Link" button in the table that lets me select from my Linear projects.

Allow me to link a weekly goal to a @Slack user. Add an "Owner" column showing the Slack user's name with ability to assign/unassign. Let me select the owner when creating a new goal too. Filter out bots and deleted users from Slack.

Add a database table for weeks with start_date and end_date. Link weekly goals to weeks and display goals grouped by week in cards showing completion rate.

Add a week filter dropdown at the top that defaults to the current week. Only show goals for the selected week. Include an "All weeks" option and mark the current week with "(Current)".

At the top of the page, display two metrics cards when a week is selected: how far we are along the week (as a percentage with progress bar) and % of goals achieved (with a progress bar that turns green at 100%).

On the homepage, allow the user to input 2 fields: Customer and Metric.

Add a button called "Generate QBR". When clicking on this button, use the template https://docs.google.com/presentation/d/1uFWjNbKmMOAqhi7hTyBSJd2sp6Zwt8ovpg40kPaYLuU/edit?slide=id.g3a469ea2ce1_0_0#slide=id.g3a469ea2ce1_0_0 and merge data with the 2 data provided Customer and Metric.

Display a clickable link of the duplicated presentation in a success toast.

Using the @ Google Calendar integration, display all calendar events from the past 30 days and next 30 days on the homepage

For each calendar event, when I click on an event open a modal. in this modal, I want to pick a source for the transcript of that meeting: I can pick from: - the description of calendar event - OR ability to copy paste a transcript of that meeting In both cases it should be stored in the database.

From the transcript upload modal. change the button to be called "Save and generate" when I click it generates a follow up email using OpenAI that will be sent to the organizers and attendees of the event. Display the generated email (recipients, subject, body) in a new modal

now instead of the button Copy email rename it to send email and use the @Gmail integration to send a draft email

after the email is sent I want to update a related contact and add a note on the @Salesforce instance.

Update the sidebar of this app - blue background #3905F5 - at the top, add the Vybe logo, centered in the sidebar: https://www.vybe.build/logos/vybe-full-logo-white.svg (edited)

Create a products table with columns for: name, description, and price. Add a page accessible from the top navbar which lists all the products. Allow the user to create delete and update products.

Build a quote builder on the home page. Let me select a product from a dropdown and choose a quantity. When I click "Add to Quote", add it to a list. Show the quote list in a table with: product name, quantity (editable), unit price, and line total Let me remove items from the quote.

Add a 'Generate Quote' button under the quote table. When clicked, open a dialog asking for: Company Name (required) // Contact Person (required) // Email (required) // Phone Number // Address.

When the user submits the customer form from the popup, create a new Google Doc using my connected @Google Docs connected account. The title of the google doc should be "Quote - [Company Name]". Insert the customer details at the top as regular paragraphs. Then display the quote data: insert a Google Docs table with headers (Product, Quantity, Unit Price, Line Total) and one row per quote item. Add a Subtotal row below the table..

After the Google Docs integration returns the created document URL: - Show a success toast confirming the quote was generated. - Display a “View Quote in Google Docs” link in the UI using the returned URL so the user can open the document.

Add navigation pages (empty for now): Calendar (homepage), Posts, Settings. Ensure consistent layout.

Create a new object called "Post": Title, Content, "Status" (pending, In Review, Ready, Posted), "scheduled at" (Date). List all posts in a table under the Posts tab. Allow a user to create update and delete a post.

Pull the list of users from the @Slack integration connected. Then display all Slack users in a table on a new page.

Update the Post object and add fields: "Owner" => links to a slack user. "Reviewer" => links to a slack user. Update the creation and update of a post according to this change.

When I click on a row of a Post, open a right drawer and display all the details about the post.

When a post in "pending" status, display a button "ready to review" which does 2 things: - update the status to "in review". - sends a message in the channel C09C75JQ44B on behalf of the user saying "[@reviewer] Post [title of the post] ready to review".

When a post in "to review" status, display a button "Update to Ready" which does 2 things: - update the status to "Ready". - sends a message in the channel [channelID] on behalf of the user saying "[@reviewer] [@owner] Post [title of the post] is ready to be posted on [scheduled_at]". Button is only clickable if scheduled_at date is not empty.

In the homepage, display all posts in a calendar view based on their "scheduled_at" value.

Create sidebar pages for Refund Inbox, Metrics, All refunds, and Settings with a consistent layout.

Pull all my open @stripe refunds requests and display them as a table in the All refunds tab. Display ID, Amount, Date created, Status,

Create a new object "Operator" in the database (First Name, Last Name, Email). In the settings page, allow a user to create, update and delete an operator.

Allow an operator to assign themselves to a Stripe Refund. Save that data in the database.

In the Refund Inbox Page, display all Stripe refunds which have not been yet assigned an operator. Add a button in each row "Assign to me" which assigns the operator matching the current logged in user to that Stripe refund.

When clicking on a row of a Stripe refund either in the All refunds or Refund Inbox pages, open a drawer with all details about this refund, including data about the linked Stripe customer and linked charge.

Add the ability to add and update notes in the drawer of a refund request and save it in the database.

Add a field "Outcome" (Accepted, Disputed) to the Stripe refund and save that in the app database. Allow a user to Update that field via dropdown. When clicking on Save in the drawer, it updates the refund in stripe as well and closes it. Log in the database the timestamp when the case was closed.

When clicking on Save, Send a @Slack message notifying of the outcome of a that refund. From the settings page, add the ability to pick the Slack channel it should be sent to from the list of all slack channels available.

In both All refunds and Refund Inbox pages, add filters, based on status, amount, date, outcome and operator.

In the page Metrics, add various metrics about the refund process: amount of requests handled per week, SLAs, filter per operator etc...

Pull my Google Forms response from the survey called "XXXXX", ID "XXXXXXX".

Display all survey responses in a table with the ability to see the detailed answers.

Add a setting page in which I can define a set of "Personas" for my product. Save personas in the database and add some seed data of personas.

Add a new page "Analysis". In that page add a table with all personas so I can set if they are target personas. Add % responses as well based on the survey response first question: Is Target Persona? (checkbox) | Persona | % Very Disappointed | % of Responses.

In the analysis page, add a Product Market Fit threshold slider (0-100%, default 40%) at the top of the analysis page. Below it, display two metrics: 1. 'Selected personas above: X% very disappointed → [status message]'. 2. 'All survey respondents: X% very disappointed → [status message]'. Depending on the threshold, in the status message, if percentage >= threshold: show 'You've achieved product/market fit 😃' in green, if not show 'No product/market fit 😞' in red.

In the analysis page, display a word cloud with the top words used in all the responses (remove common words). Add a filter to show responses from certain personas and Very/Somewhat/Not disappointed.

Add a new page called Roadmap. In this page, display a new object "Roadmap item" in the database: Feedback Theme / Feature One liner / Reach / Impact / Confidence / Effort Score (RICE).

Connect to @PostHog and display web visits per week.

- Create a new page where i'll be able to set utm source, medium,and campaign, all of them should be different tables in the database. - Create a link picking a source, medium and campaign (also persist in the DB) and make it copy friendly (base url being: www.vybe.build?). - Add a bunch of sample data for sources / medium / campaigns in the database.

Add a new chart to show me the weekly visits per week split by UTM.

Using @Slack integration, Send me a slack message every day at 9am PST in the channel #web-traffic that summarizes how we're performing this week in web traffic per UTM in comparison with previous weeks.