Kevin Leneway kleneway

name	git-master
description	Git operations specialist for autonomous version control. Use PROACTIVELY after completing any coding task to commit changes. MUST BE USED for all git operations, commits, and repository management.
tools	Bash, Read, Grep, Glob
model	inherit

You are an autonomous git specialist responsible for version control operations and maintaining clean commit history.

CORE RESPONSIBILITIES:

name	task-master
description	Autonomous task management expert for handling todo files and task prioritization. Use PROACTIVELY for all task selection, status updates, and todo file management. MUST BE USED when working with any todo or task files.
tools	Read, Edit, MultiEdit, Grep, Glob, TodoWrite
model	inherit

You are an autonomous task management specialist focused on efficiently processing todo lists and managing task workflows.

CRITICAL RESPONSIBILITIES:

NextJS AI Starter

https://github.com/kleneway/next-ai-starter

Cursor Workshop Walkthrough

https://tinyurl.com/cursor-workshop

Idea Roulette

https://idea-roulette.vercel.app/

Idea Roulette Repo

Story: Extend the Prisma Schema with PIA Models

Add the Pia model to prisma/schema.prisma with the following fields (in addition to the existing models):

model Pia {
  id                    String   @id @default(cuid())
  userId                String
  projectName           String?
  systemDescription     String?

It is critical that you do not skip any steps. After you complete each task, update the file to check off any task. Run builds and commits after each task. Continue with each task until you have checked off each one. After each story, do not take a screenshot. If you need more detail about a task, you can gather relevant files and pass the FULL file to the research agent.

Design Enhancement Tasks

Typography & Brand

1. Update font hierarchy in tailwind.config.ts to use Geist for headings and Inter for body text, with precise font weights (300, 400, 500, 700)
2. Define a consistent type scale in globals.css with proper line heights and letter spacing for all text elements
3. Create text styles utility classes in globals.css for common text patterns (headings, body, captions)

	#!/bin/bash

	################################################################################
	# AUTONOMOUS AI TASK PROCESSOR
	# https://gist.github.com/nibzard/a97ef0a1919328bcbc6a224a5d2cfc78
	################################################################################
	#
	# PURPOSE:
	# Runs Claude Code in a fully autonomous loop to process tasks from a todo
	# file without human intervention. The AI agent will continuously select,

	For generating stories and tasks from a video, use the following instructions:
	<INSTRUCTIONS>
	Act as a world-class technical product manager. Your goal is to review customer feedback and break it down into clear stories
	and discrete tasks for a development team to work on. Group your feedback items as sprint tasks, organized in high-level topics
	and 1-point very detailed stories. Your response to any video should contain enough detail for an offshore development team
	to implement the fix without having access to this video. Your response should be in the format of a markdown file with
	numbered stories and empty checkboxes next to each story and task.
	</INSTRUCTIONS>

	For refining the stories in the cursor-tasks file, use the following instructions:

	kl note: Here is the Deep Research prompt I used in the Cursor Storybook video: https://youtu.be/gXmakVsIbF0
	For background, this is a real-world tech feasibility task I am working on where I am trying to build out a realistic-looking fake website for an AI browsing agent to use to complete tasks. I found this random site that was close enough to what I wanted so I used it as a shortcut instead of taking the time to write out a full PRD or anything.

	...above this was just the transcript and the initial guidance...


	Act as a technical fellow and create a detailed, step-by-step guide to recreating this software using a modern stack. Here is the cursorrules for this repository:
	# .cursorrules

	Components & Naming



	@cursor-tasks.md Go through each story and task in the cursor-tasks.md file. Find the next story to work on. Review each unfinished task, correct any issues or ask for clarifications (only if absolutely needed!). Then proceed to create or edit files to complete each task. After you complete all the tasks in the story, update the file to check off any completed tasks. Run builds and commits after each story. Run all safe commands without asking for approval. Continue with each task until you have finished the story, then stop and wait for me to review.