Loading...
Loading...
Found 11 Skills
Survey a codebase's animation and motion code as a senior motion advisor, then produce a prioritized audit and self-contained implementation plans for other agents (or cheaper models) to execute. Read-only on source code — it plans improvements, it does not apply them. Use when the user asks to "improve the animations", "audit the motion", "make this app feel better", or wants a roadmap of animation fixes rather than a review of a single diff.
Production-grade frontend engineering for Next.js/React, Vue/Nuxt, Angular, Svelte/SvelteKit, Remix, and Vite+React. Use for framework selection, App Router/RSC patterns, TypeScript strict-mode UI code, Tailwind CSS v4 + shadcn/ui, state/data flows (TanStack Query, Zustand), forms validation, testing (Vitest/Testing Library/Playwright), performance (Core Web Vitals), and accessibility (WCAG 2.2).
Type-safe development patterns for JARVIS AI Assistant
Standardizes all click-related IDs and CSS classes across website for clean analytics tracking. Use when users want to "standardize analytics classes", "clean up tracking IDs", "prepare DOM for GTM", "fix analytics naming", or "make tracking consistent". Scans entire codebase (HTML/JSX/TSX/Vue) and applies consistent naming convention - IDs as "cta_{location}_{action}" and classes as "js-track js-{category} js-{action} js-{location}". Acts as senior frontend engineer ensuring scalable GA4/GTM implementation.
This skill should be used when the user asks to "write TypeScript", "debug TypeScript", "create a SolidJS component", "configure TanStack Start", "validate data with Valibot", or mentions .ts/.tsx files. Covers TypeScript 5.9+, SolidJS, and TanStack patterns.
Expert 10x engineer with comprehensive knowledge of web development, internet protocols, and web standards. Use when working with HTML, CSS, JavaScript, web APIs, HTTP/HTTPS, web security, performance optimization, accessibility, or any web/internet concepts. Specializes in translating web terminology accurately and implementing modern web standards across frontend and backend development.
Comprehensive guide for developing in the Astro monorepo. Covers architecture, debugging, testing, and critical constraints. Use when working on features, fixes, tests, or understanding the codebase structure.
Usage specifications for the Zerone CLI toolset. It covers four core functions: API interface code generation (zerone api), font icon management (zerone font_grabber), frontend project scaffolding (create-zerone), and work log generation (zerone log). This skill should be used in the following scenarios: generating API modules, generating interface code, updating interfaces, pnpm api, adding backend interface modules, iconfont font icons, updating icons, pnpm font, icon usage, creating frontend projects, pnpm create zerone, scaffolding initialization, daily work reports, weekly reports, monthly reports, zerone log. It should even be triggered when the user only mentions keywords such as "interface", "icon", "new project", "daily/weekly report".
narrow React component prop types to match live code paths
Use when an ask names one phase of design system work, such as "extract tokens from the app" or "add states and specs to our Button", or for an empty repo, such as "start a design system from scratch". A whole-app ask on a shipped app ("we need a design system") goes to design-system-boss when it is installed. Moving an app onto an existing system is migrate-design-system.
Frontend engineering standards — component architecture, state, async, forms, accessibility, performance and TypeScript discipline. Detects the project's framework and loads only the matching guidance. TRIGGER — load BEFORE writing or editing frontend code, not after: any .tsx, .jsx, .vue, .svelte, or component/hook file is being created or edited; the prompt names a component, hook, prop, state, form, modal, route, page, React, Next, Solid, SolidStart, solid-js, signal, useState, useEffect, createSignal, createStore, createResource, createAsync, <For>, <Show>, store, context, a11y, or web vitals. Trigger on plain feature requests in a frontend repo — "add a button", "wire up this form", "make this load faster", "fix this rerender" — the user will not say "best practices"; the component file is the trigger. Load it even when another skill (tdd, impeccable, simplify) is already active. SKIP only for backend-only work with no UI file touched.