#!/bin/bash# ==============================================# @file pretooluse.sh - pretooluse hook script# ==============================================# @description# - runs before a Bash tool call executes, can block it# - inspects the FULL command string, not just its prefix, so it#   catches destructive git flags that prefix deny-rules miss# - blocks force pushes and force branch deletes wherever the flag sits# - silent (exit 0) for everything else, never blocks non-git commands# @see AGENTS.md, .claude/settings.local.jsonCMD=$(jq -r '.tool_input.command // .toolInput.command // empty')# nothing to inspect[ -z "$CMD" ] && exit 0deny() {  jq -n --arg reason "$1" '{    hookSpecificOutput: {      hookEventName: "PreToolUse",      permissionDecision: "deny",      permissionDecisionReason: $reason    }  }'  exit 0}# force push: `git push` present AND a -f / --force[...] flag token anywhereif printf '%s' "$CMD" | grep -Eq '(^|[[:space:]])git[[:space:]]+push([[:space:]]|$)'; then  if printf '%s' "$CMD" | grep -Eq '(^|[[:space:]])(-f|--force[^[:space:]]*)([[:space:]]|$)'; then    deny "blocked by pretooluse hook: force push detected. run it yourself if you really mean to."  fifi# force branch delete: `git branch` present AND -D, or --delete together with --forceif printf '%s' "$CMD" | grep -Eq '(^|[[:space:]])git[[:space:]]+branch([[:space:]]|$)'; then  if printf '%s' "$CMD" | grep -Eq '(^|[[:space:]])-D([[:space:]]|$)'; then    deny "blocked by pretooluse hook: force branch delete (-D) detected. run it yourself if you really mean to."  fi  if printf '%s' "$CMD" | grep -Eq '(^|[[:space:]])--delete([[:space:]]|$)' \     && printf '%s' "$CMD" | grep -Eq '(^|[[:space:]])(-f|--force)([[:space:]]|$)'; then    deny "blocked by pretooluse hook: force branch delete (--delete --force) detected. run it yourself if you really mean to."  fifiexit 0

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.