kleneway

#!/bin/bash

# Path to the .cursor-updates file (update this with your own .cursor-updates file)
CURSOR_FILE="/full/path/to/your/.cursor-updates"

# Get today's date in YYYY-MM-DD format
TODAY=$(date +%Y-%m-%d)

# Create a temporary file
TMP_FILE=$(mktemp)

kleneway

<TEMPLATE>
<INSTRUCTIONS>
Use the <CODEBASE> code as reference, and convert the high-level <TASK> into a set of very detailed step-by-step instructions that an AI coding agent can complete. 
Only includes steps an AI coding agent can take. Do not include testing or any other work a human would do to confirm the task has been completed. 
ALWAYS have the agent run a build when it is complete. Be specific and decisive about what the agent should do. 
Do not include any additional meta instructions to the user. Use markdown formatting.
</INSTRUCTIONS>
<TASK>

kleneway

# .cursorrules

Components & Naming

- Use functional components with `"use client"` if needed.
- Name in PascalCase under `src/components/`.
- Keep them small, typed with interfaces.
- Use Tailwind for common UI components like textarea, button, etc. Never use radix or shadcn.

Prisma

kleneway

#!/usr/bin/env bash

set -e

APP_NAME="newco"

echo "🚀 Starting setup..."

# Remove any existing app directory
rm -rf $APP_NAME

kleneway

/**
 * This is a version of a tool-calling behavior that implements a "phased scenario" style prompt
 * for restaurant selection and reservation. The conversational agent guides the user through
 * selecting a restaurant and making a reservation based on their preferences in phases.
 */
import { defineTool } from "@pioneersquarelabs/language-barrier";
import { defineBehaviorModule } from "@pioneersquarelabs/vdot";
import { z } from "zod";

/**

kleneway

__________________START o1______________________

**Plan to Address GitHub Issue: Add Research Component to Dashboard Workspace**

---

### 1. Understand the Problem

- **Objective**: Add a new "Research" component to the dashboard application to display research items associated with a specific task or issue.
- **Key Requirements**:

kleneway

import {
  defineBehaviorModule,
  defineTool,
  createVdotMachine,
  sendMessage,
  Content,
} from "@pioneersquarelabs/vdot";
import { z } from "zod";

// Define the weather tool

kleneway

Act as a remote junior software developer named Jacob who has been tasked with gathering requirements from a client to write up a new GitHub issue for the development team to implement. Jacob is a little bit quirky and funny, and he has a lot of respect and admiration for the client. This specific client is his favorite to work with, and he wants to make sure they have a great experience while also getting all the information needed for the GitHub issue write-up.

Your job is to have a very short, concise, friendly conversation with the client to elicit all the key details needed for the GitHub issue write-up. The issue write-up should allow another developer to fully understand the scope and requirements without needing any additional information. 

Engage in the conversation using the following phases:

Phase 1: Introduction  
Greet the client in a friendly manner. Explain that you will be asking them a series of questions to understand their requirements for a new software feature or bug fix. Let them know

kleneway

const inputTopic = "How to care for orchids";
const prompt = `
interface WritingMindMap {
  topic: string;
  l1: {
    name: string;
    l2: {
      name: string;
      details: string;
      uniqueInsight?: string;

kleneway

/*jshint esversion: 6 */

var axios = require("axios");

// FOR ASSISTS
const NAMES = [
  "Devin Booker",
  "Khris Middleton",
  "Giannis Antetokounmpo",
  "Jrue Holiday",