spencerpauly
GitHub27 skills
accessibility-auditingspencerpaulyUse Cursor's browser aria snapshots to audit a page for accessibility issues — missing labels, broken tab order, contrast, and ARIA misuse.adding-e2e-testsspencerpaulySet up Playwright end-to-end testing in a project, including test configuration, example tests, and CI integration.api-smoke-testingspencerpaulyStart the dev server, discover API routes from the codebase, hit every endpoint, and report which ones return errors.architecture-decision-recordsspencerpaulyDocument technical decisions as Architecture Decision Records (ADRs) with context, options considered, and rationale.auditing-performancespencerpaulyAudit and optimize application performance, including bundle size, rendering, database queries, and Core Web Vitals.auditing-securityspencerpaulyPerform a systematic security audit of a codebase, checking for OWASP Top 10 vulnerabilities, secrets exposure, and insecure patterns.building-skills-from-patternsspencerpaulyWhen the same multi-step workflow repeats in Cursor (user corrections or agent redos), capture it as a new SKILL.md under .cursor/skills/ so future sessions load it automatically.codebase-onboardingspencerpaulyLaunch multiple explore subagents in parallel to investigate architecture, data models, auth, APIs, and deployment. Synthesize into an onboarding document.creating-prspencerpaulyCreate a clean, review-ready pull request with a good title, structured description, linked issues, and appropriate reviewers.database-designspencerpaulyDesign database schemas — tables, relationships, indexes, constraints, and ORM setup. Covers relational design, normalization, and common patterns.form-testingspencerpaulyUse Cursor's browser to fill and submit every form in the app with valid and invalid data, verifying validation, error states, and success flows.grinding-until-passspencerpaulyKeep iterating on code changes until the tests pass, the build succeeds, or linting is clean. Runs in a tight loop of fix → run → check → repeat. Use when you want the agent to autonomously grind through test failures or build errors.monitoring-terminal-errorsspencerpaulyWatch running terminal processes for crashes and stack traces. When an error appears, navigate to the failing file and line, diagnose, and fix it automatically.parallel-code-reviewspencerpaulyRun four parallel read-only subagents that each review the same diff from a different lens — security, performance, correctness, and readability — then merge findings into one report. Use before merging large or risky PRs.parallel-exploringspencerpaulyExplore a large codebase in parallel by launching multiple explore subagents that each investigate a different area simultaneously. Use when onboarding onto a new project, understanding architecture, or investigating a cross-cutting concern.responsive-testingspencerpaulyOpen the app in Cursor's browser at multiple viewport sizes, screenshot each, and report any layout breakage.reviewing-codespencerpaulyPerform a thorough code review focused on correctness, maintainability, performance, and best practices.saving-workspace-contextspencerpaulyAutomatically persist useful context — research, decisions, learnings, templates — to workspace files so knowledge survives across conversations.seo-auditingspencerpaulyAudit technical SEO — meta tags, structured data, Open Graph, sitemaps, robots.txt, performance, and accessibility signals.suggesting-cursor-hooksspencerpaulyWhen the user keeps asking for the same check to run (lint, tests, type-check), suggest a Cursor hook to automate it.suggesting-cursor-rulesspencerpaulyWhen the user repeats the same correction or convention multiple times, suggest a Cursor rule to encode it permanently.systematic-debuggingspencerpaulyStructured debugging methodology — reproduce, isolate, hypothesize, verify. Covers git bisect, binary search, logging, and minimal reproduction.using-ui-stackspencerpaulyEnforce a configuration-driven design system when generating UI. Ensures consistent spacing, colors, typography, dark mode, interactions, and accessibility across all AI-generated components.verifying-in-browserspencerpaulyAfter making code changes, start the dev server, open the app in Cursor's built-in browser, and verify everything works — check rendering, console errors, and network health. Use proactively after any UI or API change.visual-qa-testingspencerpaulyVisually QA a web application by launching it in Cursor's built-in browser, taking screenshots, checking console errors, and auditing network requests. Use after making UI changes to verify they look correct.writing-commit-messagesspencerpaulyWrite clear, conventional commit messages with proper type prefixes, scopes, and body content.writing-testsspencerpaulyAnalyze existing code and write comprehensive unit and integration tests for it. Detects the test framework, identifies untested code paths, and generates tests with proper mocking, edge cases, and assertions. Use when the user asks to add tests, improve coverage, or test a specific module.