Mark Turner amerine

<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.

CLAUDE.md - Universal Development Principles

This document contains universal development principles and practices for AI assistants working on any project. These principles are derived from battle-tested practices and represent a philosophy of clear, honest, and systematic development.

Required Tools and Research Methods

1. Mandatory MCP Tool Usage

BEFORE ANY ACTION, you MUST use these tools. Tool names use double underscores between segments.

Make it real

Ideas are cheap. Make a prototype, sketch a CLI session, draw a wireframe. Discuss around concrete examples, not hand-waving abstractions. Don't say you did something, provide a URL that proves it.

Ship it

Nothing is real until it's being used by a real user. This doesn't mean you make a prototype in the morning and blog about it in the evening. It means you find one person you believe your product will help and try to get them to use it.

	- After making changes, ALWAYS make sure to start up a new server so I can test it.
	- Always look for existing code to iterate on instead of creating new code.
	- Do not drastically change the patterns before trying to iterate on existing patterns.
	- Always kill all existing related servers that may have been created in previous testing before trying to start a new server.
	- Always prefer simple solutions
	- Avoid duplication of code whenever possible, which means checking for other areas of the codebase that might already have similar code and functionality
	- Write code that takes into account the different environments: dev, test, and prod
	- You are careful to only make changes that are requested or you are confident are well understood and related to the change being requested
	- When fixing an issue or bug, do not introduce a new pattern or technology without first exhausting all options for the existing implementation. And if you finally do this, make sure to remove the old implementation afterwards so we d

	package main

	import (
	"bufio"
	"fmt"
	"os"
	"time"
	)

	const numWorkers = 3

	Host +
	ProxyCommand ssh $(echo %h \| sed 's/+[^+]$//;s/\([^+%%]\)%%\([^+]\)$/\2 -l \1/;s/:/ -p /') nc $(echo %h \| sed 's/^.+//;/:/!s/$/ %p/;s/:/ /')
	StrictHostKeyChecking no
	UserKnownHostsFile /dev/null

	## Rails App Template
	## Useful for Rails 3.0.x and Ruby 1.9.2
	## Run using $ rails new [appname] -JT -m tpl-basicapp.rb

	# ========
	# = Gems =
	# ========

	# pre-install spork, dydram and elastic_searchable
	run "gem install spork -v 0.9.0.rc --pre"

	# If your workers are inactive for a long period of time, they'll lose
	# their MySQL connection.
	#
	# This hack ensures we re-connect whenever a connection is
	# lost. Because, really. why not?
	#
	# Stick this in RAILS_ROOT/config/initializers/connection_fix.rb (or somewhere similar)
	#
	# From:
	# http://coderrr.wordpress.com/2009/01/08/activerecord-threading-issues-and-resolutions/

	# Use from console, was required as old messages were incorrectly encoded and placed on the failed queue
	# preventing us to view the failed queue.

	include Resque::Helpers

	Resque::Failure.count.times do \|index\|
	puts "Checking #{index}"
	begin
	decode Resque.redis.lindex(:failed, index)
	rescue Resque::Helpers::DecodeException