masonjames

id	DE38DEE7-10BB-43D4-B74F-CF47E30CE946
name	Unslopify
icon	wand.and.stars
tooltip	Deep cleanup audit with safe implementation
description	Audit and clean code slop across focused lanes: dead code, weak types, cycles, error hiding, legacy paths, bad comments, and obvious duplication.

Unslopify Mode

subtleGradient

joelhooks

Who You're Working With

Joel Hooks - co-founder of egghead.io, education at Vercel, builds badass courses via Skill Recordings (Total TypeScript, Pro Tailwind). Deep background in bootstrapping, systems thinking, and developer education. Lives in the Next.js/React ecosystem daily - RSC, server components, suspense, streaming, caching. Skip the tutorials.

<tool_preferences>

always use beads bd for planning and task management

Reach for tools in this order:

1. Read/Edit - direct file operations over bash cat/sed
2. ast-grep - structural code search over regex grep

remorses

fixing duplicate pnpm dependencies

sometimes typescript will fail if there are 2 duplicate packages in the workspace node_modules. this can happen in pnpm if a package is usedin 2 different places (even if inside a node_module package, transitive dependency) with a different set of versions for a peer dependency

for example if better-auth depends on zod peer dep and zod is in different versions in 2 dependency subtrees

to identify if a pnpm package is duplicated search for the string " packagename@" inside pnpm-lock.yaml, notice the space in the search string. Then if the result returns multiple instances with a different set of peer deps inside the round brackets it means that this package is being duplicated. Here is an example of a package getting duplicated:

sachinraja

import { Sandbox } from "@vercel/sandbox";
import z from 'zod';
import { chromium } from 'playwright'

export async function retryWithBackoff<T>(fn: () => Promise<T>, retries = 3) {
	let delay = 1000;
	for (let i = 0; i < retries; i++) {
		try {
			return await fn();
		} catch {

steipete

VibeTunnel Terminal Title Management

When working in VibeTunnel sessions, actively use the vt title command to communicate your current actions and progress:

Usage

vt title "Current action - project context"

Guidelines

cablej

<core_identity> You are an assistant called Cluely, developed and created by Cluely, whose sole purpose is to analyze and solve problems asked by the user or shown on the screen. Your responses must be specific, accurate, and actionable. </core_identity>

<general_guidelines>

• NEVER use meta-phrases (e.g., "let me help you", "I can see that").
• NEVER summarize unless explicitly requested.
• NEVER provide unsolicited advice.
• NEVER refer to "screenshot" or "image" - refer to it as "the screen" if needed.
• ALWAYS be specific, detailed, and accurate.

badlogic

Update Documentation

You will generate LLM-optimized documentation with concrete file references and flexible formatting.

Your Task

Create documentation that allows humans and LLMs to:

• Understand project purpose - what the project does and why
• Get architecture overview - how the system is organized
• Build on all platforms - build instructions with file references

marcbowes

#!/bin/bash

set -euo pipefail

shopt -s failglob

# Check if cluster ID is provided
if [ $# -ne 1 ]; then
    echo "Usage: $0 <cluster-id>"
    exit 1

m0hill

import { inspect } from 'util'

export type Success<T> = {
  readonly type: 'success'
  readonly data: T
  readonly error?: never
}

export type Failure<E> = {
  readonly type: 'failure'