Looking up the weather anywhere by name: what it is doing there now, and the days ahead.
Explore
Everything in the store
Skills, tools and personas published for AWORG, all in one package system.
29 packages
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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'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'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.
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.