with one click
onlytty
onlytty contains 6 collected skills from AndrewDryga, with repository-level occupation coverage and site-owned skill detail pages.
Skills in this repository
Design an opinionated, boring-by-default implementation plan before writing code. Use when a change spans more than one file or context, when the approach isn't obvious, or when asked to plan/design/think through a feature. Produces a small-step, verifiable plan to approve before /work.
Drain this repo's .agent/tasks/ queue autonomously and run-to-completion, taking EACH task to a ship-ready bar — claim a 00_todo/ task (`coop tasks claim`), build it, gate it green, self-review it against the .agent/rules KB and every hat, ITERATE until clean, COMMIT it on its own, then `coop tasks done` — without quitting early. Arms the Stop-hook sentinel. Use to "work all the tasks" / drain a backlog / run an unattended sweep.
Put on the product-manager hat for OnlyTTY — decide what to build, what to cut, and what order; define the smallest valuable slice and what "done" means. Use when a request is vague or oversized, when scoping a feature, prioritizing, or deciding whether something is worth building at all. Pairs with /spec.
Put on the SEO/marketing hat for the OnlyTTY site and positioning — clear honest value prop, crawlable server-rendered pages, titles/meta/structured data, internal linking, sitemap, and the /control/:slug long-tail tool pages. Use when editing server/lib/relay_web/site (page.ex, tools.ex), writing positioning/copy, or improving how pages rank and convert.
Put on the UI/UX + visual-design hat for OnlyTTY — the dark-first marketing site and the mobile terminal viewer. Make it beautiful, calm, fast, and trustworthy: protect the design system in site.css, design every empty/loading/error/offline state, and hold a Linear/Vercel/Stripe-grade aesthetic bar. Use when designing or critiquing any page, screen, component, or flow in server/lib/relay_web/site or server/priv/static (viewer.html, app.js, site.css).
Execute an approved plan step-by-step, with the repo's gate between steps and no scope creep. Use when implementing a planned change, working a checklist, or the user says "go" / "implement it" / "do the plan". Stops and reports on the first red gate.