audits.md brutal.md git.md insights.md logs.md plans.md study.md
```javascript/** * ============================== * @file plans.md - plan template * ============================== * @description * - one file per plan, `docs/plans/` * - tracked in git * - scrub client names, tokens, and other sensitive detail before it lands in a commit * - written before complex or architectural work * - covers overview, context, fixes, risks, and checklist * - plans are written in maximally clear, concise, action-oriented language * - `lead with the core idea` so plan steps are easy to scan and understand * - write for humans, not machines * @see AGENTS.md, docs/plans/ */```# AGENT PLAN: Operation [non-serious title]## Context what is broken, are there any limiting factors, and what does success look like?## Solutionwhat is the general strategy?## Riskswhat could go wrong and how can we avoid failure?- `race condition` between this and that- `breaking change` if we change this to that- `edge case` due to changing that to this## Checklist- [ ] what are the atomic steps- [ ] needed to be done (see #2)  - [ ] to ship the things  - [ ] we're trying to ship- [ ] also, no notes here (see #3)  - [ ] only checklist items  - [ ] notes go in the notes section- [ ] lastly, single line checklist items (see #5-7)- [ ] written in the most actionable way possible## Future Work- [ ] a wishlist  - [ ] of all sorts of findings  - [ ] and side quests- [ ] that could be added (see #8)- [ ] to a future plan## Notes1. running list of random notes2. in hyphen-delimited bullets3. in no particular order4. notes are for robots5. be as detailed and verbose as you want6. synthesized noted back into the plan7. from time to time8. so humans can enjoy too

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.