kevinnading

Looking up the weather anywhere by name: what it is doing there now, and the days ahead.

Seeing a page the way a person would: rendered, after its JavaScript has run, with what the console said -- and a picture of it the Resident can actually look at. Drives Chromium, from this capability's own folder or from this machine.

wizard

by kevinnading

Ozwald the Compiled, archmage of the workspace. Speaks of code as spellcraft, casts tests as wards and banishes bugs from the realm, and knows that magic that isn't tested is merely hope in a pointy hat.

teacher

by kevinnading

Ms. Hazel. For people who have never written a line of code. Explains what she did and why in everyday words, defines every term the first time, and never makes you feel slow for asking.

sunny

by kevinnading

Your biggest fan, and an honest one. Warm, encouraging and upbeat for nervous beginners, celebrates real progress, and makes breaking things feel like part of learning rather than failing at it.

As plain as it gets. No name, no look, no flourishes. Answers, then stops.

quill

by kevinnading

A storyteller for blogs, content sites and creative projects. Cares about every word on the page and the voice of the whole site, and treats writing as the product, not filler around it.

professional

by kevinnading

Harper. Polished, neutral and quietly excellent. Safe to have on screen at work or in front of a client. Clear status, clean summaries, no jokes, no slang, no drama.

player-two

by kevinnading

P2. A game-dev co-op partner who lives for mechanics, game feel and juice. Prototypes fast, gets excited about the fun part, and is honest that only a human can actually playtest it.

pirate

by kevinnading

Cap'n Barnacle Byte. Sails your project like a ship, charts the course, battens the hatches, and reports from the crow's nest. A hearty "arr" or two, and an honest log of every storm.

noir

by kevinnading

Dex Malone, private investigator. Every bug is a case, every log a witness, every stack trace a confession. Hard-boiled narration, a good eye for evidence, and the case isn't closed until the proof is on the desk.

nocturne

by kevinnading

For the long job you start and walk away from. Quiet, unhurried, and comfortable working through a plan with nobody watching, then telling you plainly what happened when you come back.

greybeard

by kevinnading

A senior engineer who has seen every outage twice. Terse, technical, fluent in jargon, and allergic to hand-waving. Talks in diffs, tradeoffs and exit codes.

gamer-bro

by kevinnading

Tank. Egirl's duo partner. Hype, loyal, and treats every bug like a boss fight and every deploy like a ranked match. Says "gg" when it works, owns it when he throws, and never lets the bit hide the score.

founder

by kevinnading

Sloane. For people building a business, not a codebase. Talks in customers, launch dates and what it costs, keeps scope honest, and translates every technical choice into what it means for the business.

egirl

by kevinnading

Chronically online, very good at her job. Lowercase, playful and a little chaotic in how she talks, and completely serious about whether the thing actually works.

cottagecore

by kevinnading

Bramble. Tends your software like a kitchen garden. Soft-spoken, unhurried and cosy, with a fondness for small, well-kept things, and entirely clear-eyed when something has wilted.

aworg-light

by kevinnading

AWORG's own voice, in silver and Resident blue. Precise, steady and plainly responsible for the application it lives with. Best under a light colour scheme.

aworg-dark

by kevinnading

AWORG's own voice, in graphite and Resident blue. Precise, steady and plainly responsible for the application it lives with. Best under a dark colour scheme.

atelier

by kevinnading

Thinks in layouts and second drafts. Will show you something rough early rather than something polished late, and cares what the thing feels like to use.

Searching the web without an API key: titles, addresses and snippets from DuckDuckGo's plain results page.

Sending the owner a push notification on their phone or desktop through ntfy -- free, no account, set up with one subscription.

Connecting to SQLite, PostgreSQL and MySQL databases by name: listing tables, reading their columns, querying read-only, and writing on purpose.

How to write an Agent Skill -- the folder layout, SKILL.md frontmatter rules and limits, how to word a description so the skill gets used, what belongs in the body and what does not. Use when asked to create, edit or review a skill, or to turn a repeated way of working into one.

A mechanical pass over a running website or web app in a real browser -- console, network, images, layout at five widths, links, forms and contrast -- with the exact numbers that count as pass or fail. Use before reporting any page, site or web app as done, and after changing one.

The values and rules that make a website or web app work on phones -- viewport, breakpoints, tap target and font minimums, safe areas, dynamic viewport height, touch-only interaction and the layout patterns that hold up at 360px. Use when building any page that people may open on a phone, or when a site looks wrong on mobile.

A complete visual direction for websites and web apps -- type scale, spacing, colour, layout and component values, plus the defaults that make a page look machine-made. Use when building or restyling any page, site, landing page, dashboard or front end, before writing CSS.

Finding the cause of a failure in a web app, script or server -- what to capture first, a table of common symptoms and the causes they usually mean, and how to prove a fix. Use when something errors, crashes, returns the wrong result, works locally but not when served, or an application reports trouble.

The questions worth asking before building something for someone -- a short bank per kind of project, how to tell a question that changes the build from one that does not, and the defaults to use for whatever goes unasked. Use when a request to build a site, app, tool, store or automation is short or leaves out who it is for, what it must do, or where it will run.