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.

Keybase proof

I hereby claim:

I am amerine on github.
I am amerine (https://keybase.io/amerine) on keybase.
I have a public key ASDfxJQpdOkETeexQZ54B63DPKRY_LIQVzrk6zWu0oDhvQo

To claim this, I am signing this object:

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.

Do it with style

Mark Builds a k8s cluster.

Install kops

Last login: Wed Jul 13 14:08:05 on ttys020
~ % go get -d k8s.io/kops
~ % cd ${GOPATH}/src/k8s.io/kops/
kops [master] % make
GO15VENDOREXPERIMENT=1 go install -ldflags "-X main.BuildVersion=git-25d1e97" k8s.io/kops/cmd/...

Controller Actions	Corresponding Policy
describe_availability_zones	DescribeAvailabilityZones
describe_regions	DescribeRegions
describe_snapshots	DescribeSnapshots
create_snapshot	missing
delete_snapshot	missing
describe_key_pairs	DescribeKeyPairs
create_key_pair	CreateKeyPair
import_key_pair	ImportKeyPair

Keybase proof

I hereby claim:

I am amerine on github.
I am amerine (https://keybase.io/amerine) on keybase.
I have a public key whose fingerprint is CB4D 6A5C 4ADF 7D60 0BCD AB97 5751 DA93 F930 E3E6

To claim this, I am signing this object:

	- 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

	number of kegs = 9
	keg = 15.5 gallons
	size of pour = 12 US fl oz

	keg price = $550

	number of pours = (keg in US fl oz)/ size of pour

	number of pours => 165.3333

	- name: ensure openssl is the latest version
	apt: pkg=openssl state=latest update_cache=yes
	tags: openssl