Ensure the current project has a docs/coding-standards.md checklist and use it to review code against the default stack (Bun, TypeScript, Drizzle, Biome, Bun-workspaces monorepo, red/green TDD) and quality principles — tidiness, separation of concerns, maintainability, stale assumptions, leftover experimental code, and doc drift. Use this skill whenever the user asks to check coding standards, review code quality, "is this tidy", "does this follow our standards", set up a coding standards doc, scaffold a new project's conventions, or before finishing/merging a change.
Interview the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.
Figma automation via the figma-use CLI (by dannote). Use when the user needs to create, modify, or inspect Figma designs programmatically. Triggers on requests to render components in Figma, sync design tokens, query or find nodes, export assets, manage variables/pages, compose screens from component instances, delta-sync web app CSS against Figma properties, or troubleshoot Figma CDP connections. Also triggers on mentions of "figma-use", "figma automation", "figma cli", "render to figma", "figma eval", or "design system sync". Never use computer-use (screenshot/click) for Figma — always use figma-use CLI.
Switch to Claude Opus 4.6 model
Fetch articles and save them to a local reading buffer, or compile all unsent articles into a Kindle-optimized PDF digest and email it to Kindle. Use when the user provides URLs to save for reading, or says "send" / "send to kindle" to compile and dispatch the digest.
Launch and control real Chrome Beta with persistent login sessions. Use when automating websites that detect Playwright (LinkedIn, etc.) or when running parallel browser sessions for job applications.
Sync Hyprnote call transcripts to the knowledge base. Finds new sessions in ~/Library/Application Support/hyprnote/sessions/, converts them to markdown (transcript + summary), and saves to calls/ in the knowledge base. Use when user wants to sync, import, or review call transcripts.
Set up and use a unified dev environment where all services, logs, and browser console stream into one place — so an agent can develop, observe, and QA without context-switching. Use when starting a new project and wanting this pattern, OR when already set up and needing the agent reference (log paths, browser attach commands).