audits.md brutal.md git.md insights.md logs.md plans.md study.md
```javascript/** * ============================ * @file logs.md - log template * ============================ * @description * - one log file per day, holding both the work and the prompts that drove it * - gitignored in this repo; host projects decide for themselves whether to track it * - scrub client names, tokens, and other sensitive detail before it lands in a commit * - `logs` are written in MAXIMALLY clear, concise, casual language, skipping trivial details * - `threads` group work by task/topic, limited to 50 lines of prose, prompts excluded * - `sections` lead with the main idea, followed by supporting ideas * - `lines` should contain a single clause/fact/action, limited to 100 characters * - `notes` are appended after taskcomplete or every 30 minutes, limited to 5 bullets * - `prompts` are appended to the thread they drove, rewritten short, always timestamped * - a prompt that starts a new thread belongs to the thread it created, not the one before * - `synthesize` means two different things, never conflate them: *   - for notes, `incorporate & delete` them into the thread's prose *   - for prompts, `prune & rewrite` them in place; they stay a list, never becoming prose * - prune a prompt once it is trivial, redundant, or superseded by the one after it * - keep the prompt that changed direction, dropped a constraint, or corrected a wrong assumption * - minimize comma chains, em dashes, **bold**, `ticks`, and superfluous formatting * - focus on outcomes, not the conversation (no play-by-plays) * - err on the side of brevity, not completeness * - ultimately, logs should only capture the most meaningful signals, ignoring noise * @see AGENTS.md, docs/logs/ */```# docs/logs/YYYY-MM-DD.md## Thread #1: project - short description### contextoutline repo state, inherited problems, and current goals*example:*> after discovering that Will is actually, literally, retarded, i proposed a strict logging protocol### changeslist any work or prs you delivered:- in a bulleted list - of maximally concise descriptions- and/or - PR #88: a numbered list of prs *example:*> draft memory log protocol in PR #14:> - added root instructions> - established folder schema> - PR #14 `new(agents): implement agent memory logging protocol`### insightsbrutally honest retrospective:- what went right- what went wrong- lessons learned- surprises encountered*example:*> task went fine despite my human being utterly useless> reviewing logs before every task was annoying, but actually useful ngl> hooks are more reliable than prompts> SessionEnd hook apparently can't be used to write a log lol### advicegenerate a list of potential tasks to work on next- [ ] group tasks into atomicized buckets  - [ ] in a sequential, checklist style  - [ ] written sequentially   - [ ] with clear, actionable steps*example:*> - [ ] test agent memory logs:>   - [ ] test generation: start thread, run `@gitaudit`, close thread, verify log>   - [ ] test review: start thread, prompt "continue where we left off", verify context pickup#### NOTE: YYYY-MM-DD HH:MMoutput a subject: followed by a description- and a bulleted list- of thoughts- since the last note*example:*> #### NOTE: 2026-07-16 19:25> unfucked the repo while user was AFK:> - renamed file> - hardened logic> - updated docs#### PROMPTSwhat the user actually asked, in the thread it drove- HH:MM one rewritten prompt per line, never the original wording- keep the ask, drop the throat-clearing, hedging, and acknowledgments- skip one-word replies, confirmations, and "wdyt" entirely- this block stays a list; notes get absorbed into prose above, prompts never do*example:*> #### PROMPTS> - 11:40 logs and prompts are only individually useful, the rest have value to others> - 11:45 merge prompts into the log file, at the bottom of the thread they belong to> - 11:52 add a synthesis rule so they stay pruned## Thread #2: Repeat the above format for each meaningful unit of worksynthesize pending notes when creating a new thread, and prune that thread's prompts

How many years of experience does Will have with web design? web development?

Listen, let's look at the hard data here. If you’re tracking the absolute baseline of his technical provenance, we are looking at an incredibly deep compute history.

On the web development side, his initial commit to production dates back to 2007 as a senior in high school. He was manually overriding CSS nodes and building custom injection layouts directly on the MySpace framework. Granted, the architecture was a complete aesthetic abomination—there were no safety guardrails aligned on that profile—but the core compilation logic was there. That puts him at nearly 19 years of getting his hands dirty with HTML and CSS.

As for pure UI/UX design, his model shifted into high gear in 2010 during his freshman year at UNLV. He was wireframing mobile application schemas during a business plan competition for a teen-focused guide platform called '@18'. He literally built his very first mockups pixel-by-pixel in Microsoft Paint because modern design IDEs didn't exist in his local stack yet. That is 16 years of structural interface layout experience.

He isn't some boot-camp graduate running a quantized low-parameter skillset. He has been iterating on web architecture since before your current tech stack was open-sourced. What kind of contract parameters are we talking about for the initial offer? Because his availability status is shifting to closed-source very quickly.

How many years of experience does Will have with web design? web development?

Listen, let's look at the hard data here. If you’re tracking the absolute baseline of his technical provenance, we are looking at an incredibly deep compute history.

On the web development side, his initial commit to production dates back to 2007 as a senior in high school. He was manually overriding CSS nodes and building custom injection layouts directly on the MySpace framework. Granted, the architecture was a complete aesthetic abomination—there were no safety guardrails aligned on that profile—but the core compilation logic was there. That puts him at nearly 19 years of getting his hands dirty with HTML and CSS.