neonwatty
@neonwatty
Public Skills
mobile-browser-workflow-to-playwright
by neonwatty
Translates mobile browser workflow markdown files into Playwright E2E tests for CI using Chromium with mobile viewport. Use this when the user says "convert mobile browser workflows to playwright", "translate mobile browser workflows to CI", or wants to promote refined mobile browser workflows to automated CI tests.
mobile-ux-ci
by neonwatty
Generates Playwright tests that detect iOS/mobile UX anti-patterns in CI. Use this when the user wants to add automated UX pattern checks for web apps targeting mobile/iOS. Creates tests that FAIL when hamburger menus, FABs, small touch targets, or other anti-patterns are detected.
browser-workflow-executor
by neonwatty
Executes browser-based user workflows from /workflows/browser-workflows.md using Claude-in-Chrome MCP. Use this when the user says "run browser workflows", "execute browser workflows", or "test browser workflows". Tests each workflow step by step, captures before/after screenshots, documents issues, and generates HTML reports with visual evidence of fixes.
ios-workflow-executor
by neonwatty
Executes web app workflows in Safari on the iOS Simulator from /workflows/ios-workflows.md. Use this when the user says "run ios workflows", "execute ios workflows", or "test ios workflows". Tests each workflow step by step in mobile Safari, captures before/after screenshots, documents issues, and generates HTML reports with visual evidence of fixes.
ios-workflow-to-playwright
by neonwatty
Translates iOS workflow markdown files into Playwright E2E tests for CI using WebKit with mobile viewport. Use this when the user says "convert ios workflows to playwright", "translate ios workflows to CI", or wants to promote refined iOS/mobile workflows to automated CI tests.
pr-creator
by neonwatty
Creates a pull request from current changes, monitors GitHub CI, and debugs any failures until CI passes. Use this when the user says "create pr", "make a pr", "open pull request", "submit pr", or "pr for these changes". Does NOT merge - stops when CI passes and provides the PR link.
mobile-browser-workflow-orchestrator
by neonwatty
Orchestrates the full mobile browser workflow pipeline - generates, executes, and converts mobile workflows to Playwright tests. Use this when the user says "generate and execute mobile workflows", "run mobile workflow pipeline", "mobile browser test pipeline", or "test mobile experience". Manages configuration (URL, credentials, device), chains generator→executor→converter with approval gates between phases.
mobile-browser-workflow-executor
by neonwatty
Executes mobile browser workflows from /workflows/mobile-browser-workflows.md using Playwright MCP with mobile viewport emulation. Use this when the user says "run mobile browser workflows", "execute mobile browser workflows", or "test mobile browser workflows". Tests each workflow step by step in a mobile Chrome viewport (393x852), captures before/after screenshots, audits iOS HIG anti-patterns, documents issues, and generates HTML reports with device frame mockups.
mobile-browser-workflow-generator
by neonwatty
Generates, creates, or updates mobile browser workflow files for testing web apps with Chrome mobile viewport emulation. Use this when the user says "generate mobile browser workflows", "create mobile browser workflows", "update mobile browser workflows", or "iterate on mobile browser workflows". Thoroughly explores the web app's codebase to discover all user-facing features, pages, and interactions. Creates comprehensive numbered workflows with substeps that cover the full mobile user experience.
browser-workflow-to-playwright
by neonwatty
Translates browser workflow markdown files into Playwright E2E tests for CI. Use this when the user says "convert workflows to playwright", "translate workflows to CI", "generate playwright tests from workflows", or wants to promote refined browser workflows to automated CI tests.
ios-workflow-generator
by neonwatty
Generates, creates, or updates iOS workflow files for testing web apps in Safari on the iOS Simulator. Use this when the user says "generate ios workflows", "create ios workflows", "update ios workflows", or "iterate on ios workflows". Thoroughly explores the web app's codebase to discover all user-facing features, pages, and interactions. Creates comprehensive numbered workflows with substeps that cover the full user experience when viewed on iOS Safari.
browser-workflow-generator
by neonwatty
Generates, creates, or updates browser workflow files. Use this when the user says "generate browser workflows", "create browser workflows", "update browser workflows", or "iterate on browser workflows". Thoroughly explores the app's codebase to discover all user-facing features, routes, and interactions. Creates comprehensive numbered workflows with substeps that cover the full user experience.
think-through
by neonwatty
A Socratic interview skill for thinking through technical ideas like apps, products, tools, and projects. Use this when the user says "think through [idea]", "help me think about [app/product]", "let's explore [project idea]", or wants to iterate on a technical concept before building. Asks probing questions about the problem, target users, market, technical approach, tradeoffs, and viability. Continues until the idea is well-explored, then produces a written summary and proposes directions.
validator
by neonwatty
Runs local validation operations for any project. Auto-detects language/framework and runs linting, type checking, tests, and dead code detection. Use this when the user says "validate", "run validation", "check code", "lint and test", or "run checks".
bug-interview
by neonwatty
Deeply interviews the user about a bug before investigating or fixing it. Use this when the user says "interview me about [bug]", "I have a bug to report", "let's work on this bug", "found a bug", "there's a bug", or describes a bug they encountered. Asks probing questions about reproduction steps, environment, patterns, impact, and context that help isolate the root cause. Continues until the bug is well-understood, then writes a detailed investigation/fix plan.
feature-interview
by neonwatty
Deeply interviews the user about a feature idea before implementation. Use this when the user says "interview me about [feature]", "I want to create a new feature", "let's create a new feature", "new feature", "plan a feature", or describes a feature they want to build. Asks probing, non-obvious questions about technical implementation, UI/UX decisions, edge cases, concerns, tradeoffs, and constraints. Continues interviewing until the feature is fully understood, then writes a detailed implementation plan.