aka-kika

Use when shipping a macOS app outside the App Store — Developer ID signing with hardened runtime, notarization with notarytool, stapling, building a clean drag-to-Applications DMG, and verifying the result launches on a stranger's Mac.

Use when reading, writing, or watching the macOS clipboard — NSPasteboard types and multiple representations, the changeCount polling pattern, the transient/concealed pasteboard conventions clipboard tools must respect, and the Sequoia paste-privacy alerts.

Use when adding or reviewing keyboard shortcuts in a macOS app — in-app vs global, RegisterEventHotKey vs the KeyboardShortcuts package vs NSEvent monitors, user-configurable recording, conflict handling, and which defaults won't collide with the system.

Use when adding, reviewing, or debugging Launch at Login in a macOS app — SMAppService registration, the requiresApproval state, a Settings toggle that reflects reality, and migration off deprecated login-item APIs.

Use when adding or reviewing macOS user notifications — UNUserNotificationCenter permission flow, categories and action buttons, click routing through the delegate, foreground presentation, and rules that keep notifications from becoming spam.

Use when a macOS app needs a TCC permission or touches private data — the map of which API, Info.plist key, and entitlement each permission needs, pre-prompt explanation patterns, denied-state recovery with System Settings deep links, and honest privacy copy.

Use between coding-agent runs (Codex, Claude Code, Cursor, Aider, etc.) to stop the project from drifting, overbuilding, or accumulating dead weight. Forces a read-only audit that classifies every active item as KEEP / DELAY / REMOVE and ends with a single, unambiguous next action. Trigger on "audit before continuing", "what should I do next", "this project got too big", "between runs", "trim scope", "stop adding stuff", or any signal that the project feels noisy and the next step is unclear. Do NOT load for trivial one-line fixes, when the next action is already obvious, or when you're mid-run and just need to keep going.

Run before building anything new — a pre-build gate that decides whether an idea deserves its own tool, judged from both the agent lens (legible, drivable, automatable) and the human lens (will I touch it, do I want to maintain it). Trigger on "should I build X", "starting a new project / app / tool / repo", "is this worth making", "want to spin up", or any new-build intent — even if the word "checklist" never appears. Outputs a backed GATE.md with checkmarks and a one-line verdict note in the project root docs. Do NOT load for small config tweaks, one-off scripts, bug fixes on existing things, or anything that is clearly a feature of something you already run.

Resurface the REST of the user's reshelf collection — everything catalogued in their reshelf macOS app EXCEPT the Yard Sale — led by The Collector: the shelved-and-forgotten middle that was never promoted to Top Shelf and often never cloned. Third of the reshelf trio: `reshelf` reads the source of cloned repos, `reshelf-catalog` indexes the whole shelf with a top-shelf bias, and THIS one digs through the rest so kept-around saves don't rot unseen. Trigger it whenever the user asks about the middle of their collection: "what's in my collector?", "the rest of my collection", "what did I shelve and forget?", "resurface my shelf", "oldest stuff I saved", "what's been sitting uncloned the longest?", "anything I collected for X besides my top picks?", "spring-clean my collector", "what should I promote or clone from the rest?". It maps the keeper collection (Yard Sale always excluded) with clone status and shelf age, leads with the forgotten middle, recommends what deserves promoting/cloning, and can pull a not-clo

Survey the user's WHOLE reshelf shelf — every project they catalogued in their reshelf macOS app, whether or not it was cloned to disk — so nothing they shelved gets forgotten. This is the companion to the `reshelf` skill: that one reads the source of repos already cloned to ~/reshelf/repos; THIS one reads the app's full catalog (live store + JSON backups) so it can also surface picks the user saved but never downloaded. Trigger it whenever the user wants the big-picture of their collection rather than code from one clone: "what's on my top shelf?", "everything I've shelved", "my whole catalog / collection", "did I miss cloning something?", "what did I save for X that I haven't downloaded yet?", "what's shelved but not cloned", "recap/overview of my shelf", "top-shelf picks I forgot", "what have I collected for <topic> overall", or comparing/choosing across saved-but-not-cloned options. It lists the catalog with clone status, highlights the not-cloned gap (especially top-shelf), recommends fits across the ful

Use the user's reshelf shelf — the open-source repos they cloned to disk with their reshelf macOS app, full source organized by category at ~/reshelf/repos/<Category>/<repo> — as a hands-on code reference they already curated. Reach for it before searching the open web whenever the user points at repos they already have. Trigger this STRONGLY, even when the user never says the word "reshelf", whenever they gesture at their own collection: "look at my shelf", "my cloned repos", "the repos/references I saved", "what have I collected for X", "my catalog", "stuff I cloned", "is there something I already have for Y", or they name a category they've collected and want to learn from it, borrow patterns from it, compare options, or pick the best one. Typical asks: "what have I got for note-taking and which should I learn from?", "best reference I saved for a menu-bar app — how does it wire it up?", "how do my macOS clones do global hotkeys?", "I'm building Y, what on my shelf is a good base and what should I copy?".

Design and maintain automation-friendly HTTMELY report collections with stable files, archive snapshots, privacy boundaries, regeneration rules, and recurring report prompts.

Design beautiful local HTML/Markdown collections for HTTMELY, including welcome guides, blog queues, daily reports, saved-site libraries, Design.md research folders, and project packets.

Use this skill when a project is finished, shipped, deployed, published, or released and the user wants a release note created or updated in Obsidian. It covers collecting release facts, choosing the note path, writing a concise release summary, updating existing notes safely, and preserving follow-up actions.

Use when starting any non-trivial task, when wondering "is there a skill for this", or after finishing work that used a librarian recommendation. Applies in every agent connected to the skill-librarian MCP server.

Use when the user has an image (screenshot, design system page, brand sheet, photograph, mockup) and wants a usable color system out of it — design tokens, dark/light themes, WCAG scores, or an HTML guide. Triggers on phrases like "extract the palette from this screenshot", "build a color system from this image", "make this a design system", or when the user wants tokens/CSS/Tailwind/Figma colors. Do NOT use for: text editing, code refactoring, generic image processing, or just showing the colors of an image (use a simple picker instead).