@markllobrera This is an ideal blog post and I love the idea of doing the coding by hand. One idea would be that maybe something could do a one-time sizes calculation and store those values in a lookup table or asset media file. Should be enough For browser lazyloading and repaints.
@markllobrera I'm trying to have the Claude Code stuff build tools (like you describe) and think a lot more about pre-caching/caching/lookups that would be too complex of a script for me to write but zero time for that tool to write once.
@markllobrera Also: SO much to talk about with you at some point about Claude files. I've got a token-hygiene rule now that audits project level .claude/CLAUDE.md files that use @-level includes based on CMS, filetypes, etc. (e.g. is there ddev? backstop? a config/project/project.yaml file?)