All Skills

Plan and implement UI

Database design principles and decision-making. Schema design, indexing strategy, ORM selection, serverless databases.

Design thinking and decision-making for web UI. Use when designing components, layouts, color schemes, typography, or creating aesthetic interfaces. Teaches principles, not fixed values.

Apply operations across multiple files simultaneously. Pattern-based bulk modifications, search-and-replace across codebases, consistent changes to many files at once.

AI operational modes (brainstorm, implement, debug, review, teach, ship, orchestrate). Use to adapt behavior based on task type.

Advanced multi-agent orchestration with parallel workers, synthesis protocols, and coordinator lifecycle. Use when complex tasks require multiple agents working in parallel with intelligent result synthesis.

Red team tactics principles based on MITRE ATT&CK. Attack phases, detection evasion, reporting.

SEO fundamentals, E-E-A-T, Core Web Vitals, and Google algorithm principles.

Testing patterns and principles. Unit, integration, mocking strategies.

Lint and Validate Skill

Server management principles and decision-making. Process management, monitoring strategy, and scaling decisions. Teaches thinking, not commands.

Tailwind CSS v4 principles. CSS-first configuration, container queries, modern patterns, design token architecture.

Automatic agent selection and intelligent task routing. Analyzes user requests and automatically selects the best specialist agent(s) without requiring explicit user mentions.

React and Next.js performance optimization from Vercel Engineering. Use when building React components, optimizing performance, eliminating waterfalls, reducing bundle size, reviewing code for performance issues, or implementing server/client-side optimizations.

4-phase systematic debugging methodology with root cause analysis and evidence-based verification. Use when debugging complex issues.

Production deployment principles and decision-making. Safe deployment workflows, rollback strategies, and verification. Teaches thinking, not scripts.

Node.js development principles and decision-making. Framework selection, async patterns, security, and architecture. Teaches thinking, not copying.

Performance profiling principles. Measurement, analysis, and optimization techniques.

VR/AR development principles. Comfort, interaction, performance requirements.

Documentation templates and structure guidelines. README, API docs, code comments, and AI-friendly documentation.

2D game development principles. Sprites, tilemaps, physics, camera.

PC and console game development principles. Engine selection, platform features, optimization strategies.

Web browser game development principles. Framework selection, WebGPU, optimization, PWA.

Game audio principles. Sound design, music integration, adaptive audio systems.

Mobile game development principles. Touch input, battery, performance, app stores.

Use when triaging a study before any writing — stress-tests whether it clears Cell's bar (a complete, mechanistic, hypothesis-driven story with multiple converging lines of evidence) or belongs at a sibling. Use this first to decide Cell vs Molecular Cell vs Cell Reports vs Cell Reports Medicine before investing in framing or figures.

Use this first, before any writing, to stress-test whether a clinical study clears NEJM's bar — practice-changing clinical impact, methodological rigor, and generalizability. Decides NEJM vs Lancet/JAMA vs a specialty journal.

Use to build PNAS's Data Availability Statement and deposition plan — mandatory deposition of data in an approved repository at submission, accession numbers/DOIs, public + archived code, and materials sharing. "Available on request" is not sufficient for primary data.

Use to choose the PNAS submission track — Direct Submission (standard, editor-assigned, peer reviewed) vs Contributed Submission (an NAS member communicates their own paper). Covers eligibility, the editor/member role, the discontinued and legacy tracks, and how to pick. Unique to PNAS.

Use before any writing to stress-test whether a result clears Science's (AAAS) desk-reject filter — broad significance and general interest across disciplines. Decides Science vs Science Advances vs a specialist journal before you invest in prose.

Use when planning an ATC (ACM SIGOPS Annual Technical Conference, formerly USENIX ATC) campaign end to end — running the year backward from the early-June deadline through the two review rounds, the rebuttal, conditional-acceptance shepherding, the post-acceptance artifact evaluation, and the ACM Open Access camera-ready for the November Hong Kong conference.

Use when planning a CAV (Computer Aided Verification) project timeline from venue and category selection through submission, the two-stage review with early reject and rebuttal, artifact evaluation by the AEC, and the LNCS open-access camera-ready, with backward-planning offsets for a verification-tool paper and honest handling of the single-annual-deadline cycle.

Use when planning an ACM CHI submission cycle end to end — the single September deadline, two-round review with a five-week revise-and-resubmit window, December decisions, the TAPS and publication-ready chain, and the May conference — with owners and risk buffers for each stage.

Use to plan an ACM/IEEE HRI campaign backward from the full-paper deadline through the abstract-then-paper two-step, the rebuttal, the program-committee meeting, camera-ready, and the March conference, coordinating the parallel alt.HRI, Late-Breaking Reports, video, and Student Design deadlines.

Use when planning an ACM IMC campaign end to end, covering the choice between the two annual deadlines, backward planning from the target cutoff, the registration step, the One-Shot-Revision path across deadlines, availability shepherding, the camera-ready and dataset release, and the Replicability Track calendar.

Use when planning a KDD project calendar across the venue's two submission cycles per year, including cycle choice, abstract-then-paper deadline pairs a week apart, rebuttal capacity planning, the Resubmit-to-next-cycle loop, ADS evidence lead times, and ACM e-rights/TAPS camera-ready scheduling for SIGKDD.