Skills

A method for reviewing a codebase for the holes that actually matter — access control, tenant isolation, secret handling, and code that runs with privilege.

When: Before a release, or whenever you add anything that touches sign-in, money, secrets, or other people's data.

Write checks that prove what the software does, not that its source text matches a pattern — so they catch real breakage and survive a rewrite.

When: When you add a feature that must keep working, or change anything touching money, sign-in, or data that mustn't be lost.

The foundations that get a site crawled, indexed, and shown well — per-page metadata, one canonical URL, a sitemap, honest robots rules, and structured data.

When: When launching a site, or when pages aren't getting indexed or are showing the wrong title in search results.

Make a site readable and citable by AI assistants and agents — markdown versions of pages, an llms.txt index, plain-language summaries, and crawl permissions that say yes.

When: Alongside SEO, when you want AI assistants and coding agents to find, understand, and cite your site accurately.

Build UI that matches a brand, reads well on a phone, and works in both light and dark — using tokens, a real type hierarchy, and layout that never scrolls sideways.

When: When you add or restyle any page or component, so it fits the product instead of looking bolted on.