probitas-info
Information about Probitas framework. Use when asked "what is Probitas", explaining its purpose, features, or comparing with other test frameworks.
Discover research debugging skills, compare source repositories and read the instructions for each workflow.
Information about Probitas framework. Use when asked "what is Probitas", explaining its purpose, features, or comparing with other test frameworks.
Analyze logs, reproduce issues, and create a fix plan.
Reverse-engineer specifications from source code
Four-phase debugging methodology with root cause analysis. Use when investigating bugs, fixing test failures, or troubleshooting unexpected behavior. Emphasizes NO FIXES WITHOUT ROOT CAUSE FIRST.
Analyze web interfaces for UX issues, accessibility compliance (WCAG 2.1), color contrast, typography hierarchy, responsive design, and Core Web Vitals. Returns actionable improvements with code examples.
Systematic identification of race conditions, concurrency bugs, and thread-safety issues across codebases. Use when asked to find race conditions, audit concurrent code, debug non-deterministic behavior, review...
Perform comprehensive code audits on repositories or directories. Use when asked to audit code, review a codebase, analyze code quality, find bugs, check for security issues, review architecture, check SOLID/DR...
Provide architecture guidance, module boundaries, data flow, API design, and trade-off analysis. Use when asked for system design, refactor plans, or architecture docs.
Review BitZero game server code for bugs, security issues, and testability. Use when reviewing handlers, extensions, sessions, or game logic.
Identify and fix common Next.js App Router anti-patterns and mistakes. Use when reviewing code for Next.js best practices, debugging performance issues, migrating from Pages Router patterns, or preventing commo...
Analyzes TypeScript/Node.js projects for code quality, type safety, and technical debt
Expert code review for TypeScript/Node.js applications focusing on quality and best practices
Knowledge about Flutter/Dart code formatting, analysis tools (flutter analyze, dart fix, dart format), and when to apply them. Use when formatting code, fixing lint issues, running code cleanup, or when user me...
Expert knowledge for reviewing Flutter/Dart code including critical bugs, memory leaks, null safety violations, lifecycle issues, Bloc/Provider anti-patterns, collection equality, and code quality patterns. Use...
Auto-detects technology stack from existing project files (package.json, tsconfig, etc.). Use ONLY for existing projects with established code to discover what's already installed. For NEW projects where tech s...
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs. Use w...
This skill should be used when the user asks to "write playwright test", "e2e test", "playwright locator", "test isolation", "page object", or needs guidance on Playwright E2E testing patterns, locator strategi...
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
Native crash reporting, hang diagnostics, and performance metrics using Apple's MetricKit framework without third-party dependencies. Use this skill when implementing MXMetricManagerSubscriber, creating custom...
Intelligent agent that monitors, analyzes, and improves test suite health. Detects flaky tests, identifies coverage gaps, tracks test performance trends, and recommends improvements. Ensures test suites remain...
Comprehensive performance testing framework for load testing, stress testing, and benchmarking. Measures throughput, latency percentiles (p50, p95, p99), and resource utilization. Identifies bottlenecks and det...
Comprehensive codebase analysis system that evaluates security vulnerabilities, code quality, architecture patterns, and operational readiness across any technology stack.
This skill should be used when the user asks to "review code", "check quality", "assess implementation", "validate standards", "identify issues", or requests code review and quality assessment. Use for systemat...
This skill should be used when the user reports "error", "bug", "not working", "failing tests", "unexpected behavior", "investigate issue", or describes something broken or malfunctioning. Use for systematic de...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.