resource library
-
01 claude code course (for beginners)
a beginner's video walkthrough of claude code, one lesson at a time. The on-ramp to everything else here.
-
02 the loops build guide
three small skills turn claude code into a loop that specs, builds, reviews, and fixes its own work until it passes clean.
-
03 the prompt swipe file
15 copy-paste prompts from the claude code team: planning, architecture, and review, straight from boris cherny's thread.
-
04 the codvyn workflow guide
visual-first ui development with antigravity, stitch, and claude. One workflow, total design control.
-
05 the ai design workflow that doesn't ship slop
knox's playbook for turning one reference into a reusable design system and shipping it everywhere without drifting generic.
-
06 the vibe coder's web design guide
a beginner's cheat sheet of design vocabulary and copy-paste prompts for stitch, framer, or webflow ai.
-
07 make anything look beautiful
@rabinn.fx's 11 aesthetic principles for video editing. Beauty has a structure, and it's math, not talent.
-
08 nano banana prompts pack
a curated pack of portrait-photography prompts for nano banana, iterated and organized for practical use.
-
09 the dripstone hackathon ai playbook
27 free ai tools, rated and ordered the way you'd actually pick them during a 24-hour hackathon.
-
10 hack to hustle (h2h): chao.tech
kavisha mathur's 12-phase hackathon roadmap and episode series. Why 90% of teams fail, and how to not be one of them.
-
11 elu setup: find the unreasonable moment
install elu session-replay, then run two prompts that surface your users' real friction points and turn the top one into a build.
-
12 the landing page meta prompt
a notion page with a meta-prompt for generating landing page prompts. One template that pulls strong landing pages out of any agent.
-
13 github repositories to boost your hackathon
a curated list of github repos worth cloning before you start. Reference implementations and tools you would otherwise build yourself.
-
14 the gauntlet loop prompt
one prompt for claude code and opencode: build each subsystem against a reference, then let a blind critic judge it side by side and restart anything that loses.
no matches, try another word.