security
Security vulnerability detection methodology. Use when reviewing code to find security issues - focuses on HOW TO FIND vulnerabilities, not how to write secure code.
Découvrez les skills research debugging, comparez leurs dépôts et consultez leurs instructions.
Security vulnerability detection methodology. Use when reviewing code to find security issues - focuses on HOW TO FIND vulnerabilities, not how to write secure code.
Exploit development workflow. Use when: write exploit, PoC, payload, shellcode, bypass, buffer overflow, RCE, reverse shell.
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
prevents effect re-runs
TypeScript and JavaScript expert with deep knowledge of type-level programming, performance optimization, monorepo management, migration strategies, and modern tooling. Use PROACTIVELY for any TypeScript/JavaSc...
Safely detects and removes truly dead/unused code in Next.js + TypeScript projects. Invoked only via prompt-classifier SEQUENCE (e.g. after verification-guardian flags unused items or explicit "clean dead code"...
Audit de sécurité du code. Analyse OWASP Top 10, dépendances vulnérables, secrets exposés, et configurations. Utiliser après l'implémentation ou avant une release.
Systematically debug and diagnose code issues. Use this skill when investigating bugs, analyzing error messages, tracing code paths, or understanding unexpected behavior. Provides structured approaches to find...
This skill should be used when the user asks to "scan the codebase", "analyze multiple patterns", "parallel agent workflow", or "multi-agent research". Spawns multiple agents in parallel for comprehensive codeb...
Activates when user requests performance optimization, N+1 query analysis, caching strategy design, database tuning, or scalability assessment. Do NOT use for security audits. Examples: 'Optimize this slow quer...
Visual regression testing for Bubble Tea TUI applications. This skill should be used when testing terminal UI appearance, capturing TUI screenshots, comparing visual output against golden files, or detecting UI...
Debug Emacs Lisp code using edebug, trace, profiler, and error handling - use when encountering elisp errors or performance issues
Analyze and fix "ineffective" subproblems in SciCode benchmark. Classify issues as MAJOR or MINOR, apply minimal fixes to MAJOR issues. Use when "analyze subproblem", "classify issue", "fix benchmark problem",...
Reviews code changes in the Nick Stack codebase, checking for tech stack patterns, security, type safety, and best practices. Use when reviewing PRs, commits, or code changes.
Comprehensive code review with failure scenario analysis, security checks, and prioritized fix suggestions. Use after /execute to validate implementation quality.
React and Next.js performance optimization guidelines from the React community. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Trigg...
wasted computation on every render
Review code for implementation correctness, scalability, and production readiness. Use when reviewing PRs, auditing code quality, checking for performance issues, or evaluating production readiness. Triggers on...
Implement, refactor, or review worker-based multithreading in TypeScript/JavaScript apps (browser or Node). Use when offloading CPU-heavy loops to Web Workers, setting up a worker pool, moving data across threa...
Best practices and guidelines for TypeScript (2025-2026 Edition), focusing on TS 5.x+, modern type safety, and performance.
Optimize code for speed and efficiency. Use this skill when profiling, identifying bottlenecks, or improving performance. Covers profiling tools, common patterns, and optimization strategies.
Design load tests and bottleneck analysis.
Web performance analysis, Core Web Vitals, and optimization
Four-phase debugging methodology for finding and fixing bugs. Use when debugging issues, investigating errors, fixing crashes, or troubleshooting problems.
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.