hwatkins
@hwatkins
Public Skills
elixir-liveview
by hwatkins
Phoenix LiveView patterns for real-time web applications. Covers lifecycle, streams, events, PubSub, forms, and performance optimization. Use when building or debugging LiveView features.
6502-assembly
by hwatkins
Write, read, debug, and optimize 6502 assembly language code. Use this skill whenever the user asks about 6502 assembly, MOS 6502, 6510, 65C02, or 65C816 programming, or is working on projects for the NES, SNES, Commodore 64, Apple II, Atari 2600/8-bit, VIC-20, BBC Micro, or any other 6502-based platform. Also trigger when the user mentions opcodes, addressing modes, zero page, stack operations, or assembly language concepts in the context of 8-bit/retro computing. Covers instruction set, addressing modes, common algorithms (16-bit math, multiplication, division), memory layout, optimization, and platform-specific patterns. Even if the user just says "assembly" in a retro computing context, use this skill.
animation-transitions
by hwatkins
Coordinating three animation systems in a Phoenix LiveView + Svelte stack — LiveView JS command transitions, Svelte transitions/motion, and CSS animations/keyframes. Covers which to use when, page transitions during LiveView navigation, reduced motion, and preventing jank. Use when adding animations, transitions, page transitions, or motion to a LiveView application.
component-design-system
by hwatkins
Build consistent, cross-framework component libraries where Phoenix function components and Svelte 5 components share a visual language through Tailwind design tokens. Use this skill whenever building UI components for a Phoenix LiveView + Svelte stack, setting up a component library or design system, creating variant-based component APIs (like button/1 with :variant and :size attrs), working with slots/snippets patterns, or establishing shared Tailwind token systems. Also trigger when the user mentions "component library", "design system", "shared components", "variant API", "token system", or is building Phoenix function components alongside Svelte components and needs them to look and behave consistently.
realtime-ux
by hwatkins
UX patterns for building real-time interfaces with Phoenix LiveView — the human side of real-time that's harder than the technical side. Use this skill whenever building features that involve: optimistic UI updates, presence indicators (who's online, typing indicators, live cursors), conflict resolution when multiple users edit the same data, graceful degradation on WebSocket disconnect, loading/skeleton states, real-time notifications, collaborative editing, or any LiveView feature where latency, concurrent users, or connection reliability affects user experience. Also trigger when the user mentions "optimistic UI", "presence", "typing indicator", "disconnect handling", "skeleton state", "loading state", "concurrent editing", "real-time UX", or asks how to make a LiveView feature "feel instant" or "handle offline gracefully".
liveview-js-interop
by hwatkins
When the user needs JavaScript interoperability in Phoenix LiveView. Covers JS commands, hooks, colocated hooks (LV 1.1+), DOM patching survival, server/client communication, third-party library integration, and the LiveSvelte boundary. Use when mentioning "hooks," "phx-hook," "JS commands," "JS.push," "pushEvent," "handleEvent," "phx-update ignore," "colocated hooks," or "JavaScript in LiveView."
api-design
by hwatkins
When the user is designing, building, or reviewing a REST/JSON API. Covers resource design, routing, error handling, pagination, authentication, idempotency, webhooks, and OpenAPI documentation. Phoenix-focused with Elixir examples. Use when mentioning "API design," "REST API," "JSON API," "API endpoints," "webhook design," or "API versioning."
rust-core
by hwatkins
Expert Rust development with ownership, borrowing, lifetimes, traits, error handling, and idiomatic patterns. Use for any Rust code.
email-sequence
by hwatkins
When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," or "lifecycle emails." For in-app onboarding, see onboarding-cro.
systematic-debugging
by hwatkins
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
postgresql-table-design
by hwatkins
Design a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features
test-driven-development
by hwatkins
Use when implementing any feature or bugfix, before writing implementation code
frontend-design
by hwatkins
When the user wants to create distinctive, production-grade frontend interfaces. Guides bold aesthetic choices, typography, color, motion, and spatial composition to avoid generic "AI slop" aesthetics. Use when building UI components, pages, or applications.
referral-program
by hwatkins
"When the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy. Also use when the user mentions 'referral,' 'affiliate,' 'ambassador,' 'word of mouth,' 'viral loop,' 'refer a friend,' or 'partner program.' This skill covers program design, incentive structure, and growth optimization."
saas-security
by hwatkins
When the user needs to implement or review security for a SaaS application. Covers authentication, authorization, API security, account takeover prevention, session management, and security headers. Also use when mentioning "auth security," "API protection," "account takeover," "session hijacking," "CSRF," "XSS," or "security headers." For spam-specific issues, see spam-prevention.
seo-audit
by hwatkins
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," or "SEO health check." For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup.
spam-prevention
by hwatkins
When the user needs to prevent spam signups, bot accounts, fake registrations, or abuse of signup/trial flows. Also use when mentioning "spam accounts," "fake signups," "bot registrations," "disposable emails," "signup abuse," or "trial fraud." For broader security concerns, see saas-security.
sql-optimization-patterns
by hwatkins
Master SQL query optimization, indexing strategies, and EXPLAIN analysis to dramatically improve database performance and eliminate slow queries. Use when debugging slow queries, designing database schemas, or optimizing application performance.
stripe-integration
by hwatkins
Implement Stripe payment processing for robust, PCI-compliant payment flows including checkout, subscriptions, and webhooks. Use when integrating Stripe payments, building subscription systems, or implementing secure checkout flows.
frontend-typescript
by hwatkins
Expert TypeScript development for frontend applications. Covers type safety, patterns, generics, utility types, and best practices. Use for any TypeScript code.
elixir-otp
by hwatkins
OTP patterns for Elixir — GenServer, Agent, Task, ETS, supervision trees, Registry, and process design. Use when designing concurrent systems, stateful processes, or deciding when (and when NOT) to use processes.
elixir-phoenix
by hwatkins
Expert Elixir and Phoenix development with functional programming patterns, Phoenix 1.7/1.8 conventions, Ecto, and OTP. Use for any Elixir or Phoenix code.
elixir-tdd
by hwatkins
Test-driven development enforcement for Elixir and Phoenix. Requires failing tests before implementation. Use when implementing features, fixing bugs, or when code quality discipline is needed.
svelte-core
by hwatkins
Svelte 5 components inside Phoenix LiveView via LiveSvelte. Covers reactivity, props from LiveView, live.pushEvent, SSR, slots, and end-to-end reactivity patterns. Use when building Svelte components in a Phoenix project.
elixir-ecto
by hwatkins
Expert Ecto patterns for Elixir — changesets, Multi, composable queries, migrations, optimistic locking, multi-tenancy, and railway-oriented programming with with. Use when working with databases or data validation in Elixir.
rust-tdd
by hwatkins
Test-driven development enforcement for Rust. Requires failing tests before implementation. Use when implementing features, fixing bugs, or when code quality discipline is needed.
frontend-tailwind
by hwatkins
Expert Tailwind CSS development with utility-first patterns, responsive design, component extraction, and performance. Use when styling frontend applications with Tailwind.
rust-async
by hwatkins
Async Rust with Tokio, futures, concurrency patterns, channels, and performance. Use when building async services, networking, or concurrent Rust applications.