audits.md brutal.md git.md insights.md logs.md plans.md study.md
```javascript/** * ================================================== * @file insights.md - opportunity report template * ================================================== * @description * - tracked in git, one insights file per day, appended across runs * - scrub client names, tokens, and other sensitive detail before it lands in a commit * - written by `@gitinsights` only, appended each run, many reports per file * - `reports` capture the opportunity surface at a moment in time, never edited after the fact * - `observations` are what the three streams found; `opportunities` are what to do about it * - `opportunities` sort onto the urgent/important matrix, and name the file they touch * - `lines` should contain a single clause/fact/action, limited to 100 characters * - skip the raw sidecar dump; keep the read of it, not the printout * - an opportunity that recurs across dated files is a finding; restate it, never edit the older report * - a Q1 entry that survives three reports has stopped being urgent in practice, say so * @see AGENTS.md, AGENTS/git/gitinsights.md, docs/insights/ */```# docs/insights/YYYY-MM-DD.md## Insight #1: YYYY-MM-DD HH:MM### sourceswhich streams fed this report, and the log range read*example:*> sidecar: 3 broken refs, 6 markers | docs reconciled: README, AGENTS.md | logs: 2026-07-24 to 2026-07-29### observationswhat the three streams actually surfaced:- hyphen-delimited list of bullets*example:*> `gitbrutal.sh` greps `content/**`, a path that no longer exists in this repo> README documents a `.gitkeep` scaffold that `.gitignore` no longer preserves> logs mention the same hook-testing gap on 3 separate days### opportunities**urgent and important:**- broken references, blockers, doc/code drift that misleads**urgent but not important:**- code markers, minor configuration fixes, trivial tool warnings**not urgent but important:**- refactoring, tech debt, architectural hygiene, core feature work**not urgent or important:**- overly ambitious refactors, nice-to-haves, out-of-scope ideas### carriedopportunities restated from an earlier report, with how many reports they have survived*example:*> hook test coverage — carried 3 reports, still Q1 on paper, evidently not urgent in practice## Insight #2: repeat the above format for each `@gitinsights` run on the same daynever edit an earlier report; a recurring opportunity is signal about what keeps getting skipped

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.