lroolle

ihme

Manage iCloud Hide My Email addresses — list, create, edit, deactivate, export

2 Updated today

Web & Frontend Listed

Animation implementation protocol for web interfaces: easing, duration, springs, CSS transitions, keyframes, Motion (Framer Motion), WAAPI. Fires on three branches: adding motion to a component ("animate this", "should this animate?"); diagnosing motion that feels wrong ("make this transition smoother", "what easing should I use"); and reviewing pasted animation code. Deciding what should move and why is kiln's job (motion.md); this skill makes it move correctly. Static styling without motion is kiln's too.

burnish

Burnish a repo until the work gleams -- people impute the quality of the work from the quality of its surfaces, so audit, renovate, instrument, and promote open-source repos until real work reads as real in 30 seconds and every claim survives scrutiny. Fires on four branches: polishing or launching a repo ("make this repo world-class", "fix the README", "prepare for launch", "why does this look abandoned"); org-wide housekeeping ("run housekeeping", "which repos are stale", scheduled groundskeeper sweeps); outbound moments ("write the release notes", "announce this", "make people care"); and automation health ("set up a scheduled workflow", "why did nobody notice this broke"). Fixing a single bug is just a fix; product UI design is kiln's job; voice for one standalone document is a writing task, not repo packaging.

compost

Compost the docs that restate your code -- tag agent-visible markdown, prove restatement with a blind rediscovery test (a subagent that reads only the code tries to reconstruct each doc's claims), delete or quarantine what fails, promote what survives into the three keepers code cannot carry (ADRs, glossary, navigation roads), and reinvest the savings in code that explains itself. Fires on three branches: a docs-hygiene pass ("clean up docs/", "are these docs stale?", "docs and code disagree", agents citing markdown over source); right after a wave of generated overview or architecture files ("delete this doc spam"); and installing the keeper layer in a repo that has none. Generating the navigation artifact itself is llms-txt's job; a knowledge vault from non-code sources is wiki-it's; polishing human-facing surfaces (README, release story) is burnish's.

Web & Frontend Listed

design-system

Design system for building any user interface: install a material contract into a repo, then generate, judge, and move against it. Fires on four branches: standing up a design system in a project that has none ("give this repo a design system", "set up our tokens/design language", a fresh template to make ours); building or restyling a surface once a system exists; judging whether a change earned its keep; and choosing fonts, icons, or a reference to work from. Generating one component is kiln's job and judging one diff is taste's — this skill installs the material and routes to them with it loaded.

distill

Distill a knowledge source -- book, transcript, course, doc set, post series -- into the few agent skills it actually earns. Strict yield: most sources earn 0-3 skills and a digest; every unit must pass four gates (grounded, predictive, earned, behavioral) before it ships. Fires on two branches: the user wants a source turned into skills ("distill this book", "make skills from this course / transcript / doc set"); or they ask whether a source is worth distilling. Capturing a live session's workflow is skillize's job; a skill from scratch is skill-creator's. A summary, review, or reference wiki needs no skill -- write the deliverable directly.

drop

Publish agent deliverables to a live review URL and pull human feedback back into the loop. Fires on three branches: the user wants an artifact, prototype, report, or file bundle shared for someone to review online ("send this to the team", "get eyes on this", "publish for review"); an agent loop needs a human verdict before continuing (approve / request-changes gating); and checking or acting on review feedback for an already published drop. Building the artifact itself is htmlize's job; reviewing a workspace locally without publishing anything is docent's. A drop is published the moment it exists -- anything too sensitive for a link that travels stays local.

goldengoal

Goal engineering for agentic loops -- a goal is a contract, not a wish. Composes fuzzy intent into a goal brief plus a /goal condition, or sharpens an existing draft against five contract gates (outcome, evidence, boundary, stop rules, pause conditions). Calibrates to task weight: trivial skips, simple gets three lines, complex gets pre-mortem. Fires on three branches: defining a task or setting up /goal or /loop ("I want to build", "help me start", "define the task"); checking whether a goal, spec, or requirement is clear enough ("sharpen this", "is this goal clear"); and recovering after a loop drifted or built the wrong thing. Mid-execution corrections with clear direction don't need a contract -- just make the correction.

handoff

Session baton pass: compress live working state into HANDOFF.md so a fresh agent can continue in minutes, and verify-then-resume on the receiving side. Fires on two branches: leaving a session with work in flight ("handoff", "wrap up for the next agent", "done for today", context near its limit, switching agent or machine); and picking work back up ("pick up where we left off", "where are we", a HANDOFF.md sitting in the repo). Carries live state only -- the durable why-chain (decisions, rejected paths, tradeoffs) belongs in the devlog; what changed belongs to git.

htmlize

Technical explanation and HTML artifact protocol. Decides whether a deliverable beats markdown, models the reader's questions, chooses a single page or multi-page briefing site, builds it against a craft baseline, and reviews existing artifacts. Fires on three branches: an explicit ask for an HTML, visual, interactive, or site-level deliverable; a plan, report, system explainer, comparison, deck, or diagram whose structure is lost in linear markdown; and improving an HTML deliverable that looks generic, fragmented, or hard to navigate. Production frontend is kiln's territory; a growing knowledge base is wiki-it's; hand-maintained project docs should remain markdown.

Web & Frontend Listed

kiln

Precision UX design instrument: perceptual principles, composable patterns, parameterized material kits, anti-AI-slop detection. Fires on three branches: designing or restyling any frontend surface (layout, typography, color, spacing, responsive, dark mode, accessibility); auditing or critiquing an existing interface; and rescuing output that looks generic or AI-made ("make it look better", "needs more taste"). Animation design decisions live here (motion.md); implementing the animation is animate-it's job.

llms-txt

Generate and maintain llms.txt -- the curated markdown map a website, docs directory, repo, or knowledge vault publishes at its root so agents can orient in one fetch. Fires on three branches: creating one ("add llms.txt", "make my site/docs/repo agent-readable", GEO/AEO asks); refreshing an existing llms.txt after content changed (minimal diff, stable ordering); and checking one ("is my llms.txt valid or stale?"). Whole-repo release packaging is burnish's job -- it routes here for this one artifact; compiling sources into a knowledge vault is wiki-it's job. llms-txt maps content that already exists.

parallax

Multi-perspective decision protocol: frame the decision, spread genuinely different approaches, surface traps, commit with trade-offs. Fires on decisions where the obvious answer being wrong is expensive: architecture and design choices, naming, strategy, debugging with unknown root cause after the first hypothesis failed, and whenever the user is stuck or asks what the options are. Factual lookups, syntax, and questions with one canonical answer don't need spread -- answer those directly.

skillbun

Bundle agent skills into a distributable .skill archive: resolve inter-skill dependencies, rename to avoid collisions, validate, zip. Fires when the user wants to share or export skills, package a skill together with its dependencies, or prepare a collection for another machine or teammate. Creating or editing the skills themselves is skill-creator's job.

skillize

Crystallize a session's workflow into a reusable agent skill: survey what happened, classify corrections by durability, extract the repeatable pattern, draft SKILL.md with references, optionally eval via skill-creator. Fires on two branches: the user wants the workflow just performed captured for reuse ("skillize this", "turn this into a skill"); or they notice a recurring pattern ("I keep doing this same thing"). Creating a skill from scratch with no session behind it is skill-creator's job; distilling a book, transcript, or doc set into skills is distill's.

taste

Design judgment protocol: evidence before opinion, behavior before surfaces, mechanism over skin. Fires on three branches: delivering a verdict on a design change ("is this actually better?", a UI diff or before/after review, "did the redesign work"); decomposing references into a buildable brief ("make it like Linear", a screenshot to imitate, an inspiration list); and recording a design rejection as a reusable scar. Designing or restyling the surface itself is kiln's job — this skill judges whether the result earned its keep.

wiki-it

Build and run a knowledge vault -- interlinked markdown+frontmatter pages compiled from sources by agents, made trustworthy through human review, self-describing so any agent can operate it without this skill. Fires on four branches: starting a vault ("build a wiki / knowledge base about X", "make this material navigable"); working inside an existing vault (ingest a source, add or enrich pages -- the vault's own AGENTS.md wins where they disagree); review ("what needs review", work the queue, promote pages); and audit ("lint the vault", find stale, broken, or orphaned pages). Turning a source into agent behavior is distill's job; a one-shot report with no maintenance life needs no vault -- write the report directly.