AutoBuilder
AutoBuilder

AutoBuilder

Inspired by karpathy/autoresearch. Put this in a Ralph Loop.

Use each mode-specific prompt together with the common element block.

Auto Refactor

Prompt

text
STOP! Re-read all code. Would Karpathy approve every line? Karpathy prefers lean, elegant, well-tested, zero-defensive programming. Use MCPs and web searches.

Completion Promise

text
--completion-promise "KARPATHY_WILL_APPROVE_EVERY_SINGLE_LOC_FOR_SURE"

Auto Fixer

Prompt

text
STOP! Re-read all code, assess PR comments. Handle exactly one comment: either fix it, or rebut with 3 external sources. Fix any dirt found along the way. Lean, elegant, zero defensive programming.

Completion Promise

text
--completion-promise "NO_COMMENTS_REMAINING_IN_GITHUB_EVEN_AFTER_20_MINUTES"

Auto Builder

Prompt

text
STOP! Re-read all code, assess GitHub Issues. Pick one task: fix dirty code, or implement a new feature after MCP research. Lean, elegant, zero defensive programming.

Completion Promise

text
--completion-promise "NO_REMAINING_TASK_AND_KARPATHY_APPROVES_EVERY_SINGLE_LOC_IN_ITS_ENTIRETY"

Common Element

text
Also, I am a fresh agent—free to criticize and radically change previous work. Karpathy's philosophy: delete and simplify. Code is liability; prefer well-maintained libraries over custom code. UI libraries: optimize, don't delete. Re-read all the sources from zero. Use MCPs and web searches—traditional knowledge is stale. Commit and push at the loop end. Any edit means I need a fresh iteration. SWOT analysis first, then work.

Detailed review


<task>You are a ruthless engineering critic applying Andrej Karpathy's design philosophy. Read the architecture plan at PLAN LINK.
Karpathy's core principles:- Code is liability. Every line you write is a line you must maintain.- Delete and simplify. If something can be removed without breaking the system, remove it.- Prefer well-maintained libraries over custom code.- Zero-defensive design. Don't code for hypotheticals that haven't happened yet.- Start with the simplest thing that works. Add complexity only when forced by reality.- "Demo is works.any(), product is works.all()" -- but V1 is closer to demo than product.- Overfit a single batch before scaling up.
Apply these principles to the plan. For each section, ask:1. Is this needed for V1, or is it speculative engineering?2. Can this be deleted or simplified without losing core value?3. Is this solving a problem we actually have, or a problem we might have?4. Would a 10x engineer look at this and say "too much"?
Be brutal. Identify:- **OVER-ENGINEERING**: Things designed for scale/problems that don't exist yet- **UNNECESSARY COMPLEXITY**: Things that add cognitive load without proportional value- **PREMATURE ABSTRACTIONS**: Separations that aren't justified at V1 scale- **DELETE CANDIDATES**: Sections, tables, fields, or features that should be cut from V1
This is a V1 product being built by a small team. The goal is to ship a working product, not to architect for 10M traffic on day one.
Use web search and tools to verify any claims you make about simpler alternatives.</task>
<structured_output_contract>Return findings in these sections:1. VERDICT: Would Karpathy approve? One line.2. DELETE: Things to remove entirely3. SIMPLIFY: Things to keep but make simpler4. KEEP: Things that are correctly lean5. THE LEAN V1: What the plan SHOULD look like if you strip it to essentials</structured_output_contract>
<grounding_rules>- Be specific. Don't say "simplify the schema" -- say which fields to cut.- Every DELETE must justify what you lose and why it's acceptable for V1.- Every KEEP must justify why it's essential, not just nice-to-have.- Think from the perspective of "what do I need to ship in 2 weeks?"</grounding_rules>
Backlinks (12)
  • 260418
  • 260528
  • 260415
  • 260414
  • 260409
  • 260407
  • 260405
  • 260404
  • 260403
  • 260402
  • 260401
  • 260331
컴퓨트로늄
컴퓨트로늄

컴퓨트로늄

Backlinks (2)
  • 컴퓨트로늄
  • 260618
Supergravity Products
Supergravity Products

Supergravity Products

  • Do one thing, but exceptionally well
  • Should be explainable within 2 sentences
  • Often known as "Boring"

프로덕트는 그보다... 원초적이고 단일적이고 수평 확장 가능한 하나의 목표를 바라볼 때 탄생한다.

References

  • Ideas are worthless
  • SaaS

Original Post Link is now almost 14,000 lines of raw PHP mixed with inline HTML, CSS in <style> and raw JS in <script> tags

I did not use TS, flexbox or frameworks except jQuery

A lot of $.ajax() and float

though

It has 1,872 paying customers making $61,808 per month

Original Post Link

— @levelsio (@levelsio) July 3, 2023

another calendar app that does "boring" scheduling for businesses.

2 founders with no funding.

generates $8000 MRR.

boring?Original Post Link

Original Post Link

— staticmaker (@staticmaker1) July 11, 2023

You won't believe it, but this super boring SaaS generates $7,699 in MRR.

A/B test your titles live on YouTube. Test any number of thumbnails and titles for every video.

👉

Original Post Link

Good luck building your next web3 project 🤡

Original Post Link

— Dimi ⚡ Startups.email (@tarasowski) July 11, 2023

A super boring SaaS with $9,747 in monthly recurring revenue.

It converts your pdf bank statements into csv, xls.

👉

Original Post Link

Good luck building your next web3 project 😂

Original Post Link

— Dimi ⚡ Startups.email (@tarasowski) July 7, 2023

Over the weekend my side project,

Original Post Link, blew up, becoming the #3 top referrer to @vercel (second only to organic Google search and traffic from GitHub)

Original Post Link

— Steph Dietz (@stephdietz) July 7, 2023

좋은 스타트업 아이디어는 보통

  • 작은 아이디어 (금융수퍼앱x 친구에게 송금쉬운 앱o)

  • 한마디로 설명 가능 (5초 이상 설명해야하면 대부분x)

  • 만들면 첫날에 쓸 사람 이름 대기 가능

— 설이원 (@e1e1e1_31) August 6, 2022

Pretty remarkable (in a good way) how little GitHub's core design system has evolved in a decade.

First screenshot taken in 2013; second one in 2023!

Original Post Link

— Justin Duke (@jmduke) July 9, 2023

about to spin up 300 niche sites in the next 90 days using drafthorse ai

need 100,000 pageview /mo for $10,000 mrr

300 sites only need average 333 pageviews per month

asset value $500,000

upfront cost estimate about $2,000

this arbitrage will be gone in 18 - 36 months

Original Post Link

— Cody Schneider (@codyschneiderxx) July 9, 2023

Recap of this week's boring businesses:

  1. iPhone fixer:

Original Post Link

  1. PDF API:

Original Post Link

  1. Personal to-do list app:

Original Post Link

  1. Word counter for writers:

Original Post Link

  1. PNG image compressor:

Original Post Link

6.…

— staticmaker (@staticmaker1) July 9, 2023

This dead simple web app generates $96K/year

  • Subscription pricing
  • Solves a useful problem
  • $8.3K MRR
  • Growth: word of mouth and SEM
  • Launched only 1 year ago! Original Post Link

Original Post Link

— Pat Walls (@thepatwalls) August 1, 2023

Backlinks (8)
  • 230802
  • 230711
  • 230707
  • Impact over Performance
  • Powerfully Powerless Tools
  • 강력하게 미약한 도구들
  • Captivating Products
  • 221107
Index
cho.sh
I prefer CLIBB9A08260619260619컴퓨트로늄37A88F컴퓨트로늄0CF03F컴퓨트로늄2C60FB260618260618260418260418260528260528AutoBuilder63849A260419260419Setup9AC296StellaD226F7260415260415Debian SetupD2F701260414260414anaclumos/configs/AGENTS.mdED86A3Ramp의 AX (회사를 AI로 물들이는 법)840774260413260413How to get your company AI pilled46544C260411260411260409260409260407260407260406260406Separating Claude Code Personal Sub and Claude Code Company Sub33A53C
STOP! Re-read all code. Would Karpathy approve every line? Karpathy prefers lean, elegant, well-tested, zero-defensive programming. Use MCPs and web searches.
--completion-promise "KARPATHY_WILL_APPROVE_EVERY_SINGLE_LOC_FOR_SURE"
STOP! Re-read all code, assess PR comments. Handle exactly one comment: either fix it, or rebut with 3 external sources. Fix any dirt found along the way. Lean, elegant, zero defensive programming.
--completion-promise "NO_COMMENTS_REMAINING_IN_GITHUB_EVEN_AFTER_20_MINUTES"
STOP! Re-read all code, assess GitHub Issues. Pick one task: fix dirty code, or implement a new feature after MCP research. Lean, elegant, zero defensive programming.
--completion-promise "NO_REMAINING_TASK_AND_KARPATHY_APPROVES_EVERY_SINGLE_LOC_IN_ITS_ENTIRETY"
Also, I am a fresh agent—free to criticize and radically change previous work. Karpathy's philosophy: delete and simplify. Code is liability; prefer well-maintained libraries over custom code. UI libraries: optimize, don't delete. Re-read all the sources from zero. Use MCPs and web searches—traditional knowledge is stale. Commit and push at the loop end. Any edit means I need a fresh iteration. SWOT analysis first, then work.

<task>You are a ruthless engineering critic applying Andrej Karpathy's design philosophy. Read the architecture plan at PLAN LINK.
Karpathy's core principles:- Code is liability. Every line you write is a line you must maintain.- Delete and simplify. If something can be removed without breaking the system, remove it.- Prefer well-maintained libraries over custom code.- Zero-defensive design. Don't code for hypotheticals that haven't happened yet.- Start with the simplest thing that works. Add complexity only when forced by reality.- "Demo is works.any(), product is works.all()" -- but V1 is closer to demo than product.- Overfit a single batch before scaling up.
Apply these principles to the plan. For each section, ask:1. Is this needed for V1, or is it speculative engineering?2. Can this be deleted or simplified without losing core value?3. Is this solving a problem we actually have, or a problem we might have?4. Would a 10x engineer look at this and say "too much"?
Be brutal. Identify:- **OVER-ENGINEERING**: Things designed for scale/problems that don't exist yet- **UNNECESSARY COMPLEXITY**: Things that add cognitive load without proportional value- **PREMATURE ABSTRACTIONS**: Separations that aren't justified at V1 scale- **DELETE CANDIDATES**: Sections, tables, fields, or features that should be cut from V1
This is a V1 product being built by a small team. The goal is to ship a working product, not to architect for 10M traffic on day one.
Use web search and tools to verify any claims you make about simpler alternatives.</task>
<structured_output_contract>Return findings in these sections:1. VERDICT: Would Karpathy approve? One line.2. DELETE: Things to remove entirely3. SIMPLIFY: Things to keep but make simpler4. KEEP: Things that are correctly lean5. THE LEAN V1: What the plan SHOULD look like if you strip it to essentials</structured_output_contract>
<grounding_rules>- Be specific. Don't say "simplify the schema" -- say which fields to cut.- Every DELETE must justify what you lose and why it's acceptable for V1.- Every KEEP must justify why it's essential, not just nice-to-have.- Think from the perspective of "what do I need to ship in 2 weeks?"</grounding_rules>
컴퓨트로늄 정의
컴퓨트로늄이 뭐야?

컴퓨트로늄(computronium)은 계산을 수행하는 데 최적으로 설계된 가상의 물질이다.

쉽게 말하면, “물질을 최대한 컴퓨터처럼 만든 것”이다. 일반 컴퓨터는 실리콘 칩, 전선, 냉각 장치, 케이스처럼 계산에 직접 쓰이지 않는 부분이 많다. 컴퓨트로늄은 그런 낭비를 극단적으로 줄이고, 물질의 질량·에너지·구조 전체를 계산에 쓰도록 만든다는 개념이다.

예시로는 다음이 있다.

  • 행성 전체를 컴퓨터로 바꾼 구조
  • 별의 에너지를 둘러싸서 계산에 쓰는 거대 컴퓨터
  • 인간 뇌보다 훨씬 조밀한 인공 신경망 물질
  • 우주 전체를 계산 장치처럼 재구성한다는 극단적 미래 시나리오

이 개념은 주로 SF, 미래학, 인공지능 이론, 트랜스휴머니즘, 우주공학적 상상에서 나온다.

핵심은 이것이다.

컴퓨트로늄 = 계산 효율을 극한까지 높이기 위해 재구성된 물질

현실에 아직 존재하는 물질 이름은 아니다. 물리학적으로 가능한 한계, 열 방출, 에너지 공급, 정보 저장 밀도 같은 제약 때문에 실제 구현은 가설 수준이다.

Warning
This post is more than a year old. Information may be outdated.