3.2K skills · sorted by relevance
Test local web applications with Python scripts using Playwright, a browser automation tool. Verify interface behavior, investigate problems, capture screenshots, and inspect browser logs, with a helper that manages one or more application servers.
Design modules that expose simple interfaces while hiding substantial behavior. Use shared terms and principles to assess interface complexity, decide where behavior can be swapped, and organize code so callers and tests use the same interface.
Turn a reported defect into a concise bug report or issue draft that someone else can reproduce or investigate. Organize symptoms, reproduction steps, expected and actual behavior, environment, and impact while separating evidence from unknowns.
Review concrete code changes for defects, compatibility problems, repository-rule violations, and unnecessary code. Produce evidence-based findings and, when explicitly requested, make minimal cleanup changes while checking that existing behavior is preserved.
Investigate local Rust services by starting the crate’s executable with debug logging and following its log output. Use the recorded messages to examine startup problems, runtime behavior, and errors while discussing findings with the agent.
Test local web applications with Playwright, a browser automation tool. Write Python scripts to check interface behavior, inspect rendered pages, capture screenshots, and collect browser logs, with a helper that manages one or more application servers.
Build features or fix bugs through test-driven development: write one failing test, add enough code to pass, then refactor. Focuses on observable behavior through public interfaces, helping tests remain useful when internal code changes.
Build features and fix bugs through test-driven development: write a test for the desired behavior, confirm it fails for the expected reason, then add minimal code and clean it up while keeping all tests passing.
Simplify code, tests, documentation, and configuration while preserving required behavior. Use it during implementation or before handoff to remove duplication, reuse existing mechanisms, and validate that each remaining part serves a clear purpose.
Review a git diff or selected files with parallel agents to find behavior regressions, security risks, reliability problems, and compatibility or test gaps. Receive filtered, evidence-backed findings and prioritized recommendations without changing files.
Keep documentation aligned with changes to behavior, configuration, and operational procedures. It updates existing pages, corrects stale instructions, and preserves reusable workflow or research guidance so future readers can find authoritative information.
Measure JS SDK test coverage and identify untested behavior using coverage reports. It supports gap assessments and scoped test improvements, prioritizing public behavior, error handling, cancellation, and lifecycle paths, then reporting verification results and remaining gaps.
Investigate slow interactions and rendering using performance traces, which record execution events, alongside source code. Identify the responsible code, distinguish measurements from hypotheses, and guide fixes that preserve behavior, with tests and comparable recordings for verification.
Explain an existing machine learning model by summarizing influential input features and examining individual predictions. It helps investigate unexpected feature interactions and communicate model behavior to nontechnical stakeholders, while noting limitations and potentially misleading explanations.
Turn feature ideas and behavior changes into agreed designs before implementation. Clarify goals through one question at a time, compare alternative approaches, review the design in sections, and save a design document before moving to implementation planning.
Tune adaptive behavior in an instrumented NeMo Relay application using runtime data. Configure tool parallelism, prompt caching, and state storage, then compare changes against a baseline to check latency, correctness, and failure rates.
Troubleshoot applications where NeMo Relay is installed but runtime behavior is missing or incorrect. It helps isolate loading failures, inactive execution contexts, missing events, and plugin or export configuration issues before changing application settings.
Build NPC AI in Unreal Engine 5 with Behavior Trees and Blackboards: composites (Selector/Sequence), tasks, decorators, services, and running the tree from an AIController. Use when creating enemy/NPC AI, BT_/BB_ assets, custom BTTask or BTService nodes, or when the user mentions Behavior Tree, Blackboard, AIController, BTTask, decorator, or service.
The English summary is being prepared. Showing the original description.
LoongCollector E2E Testing Framework Development Guide. Use this rule when you need to understand E2E testing framework architecture, develop new test behavior functions, or extend testing capabilities. Contains detailed BDD testing framework usage, test behavior function development and registration workflows, and comprehensive reference of existing testing capabilities. Example: When adding custom test behaviors for new plugins, use this rule to understand how to write and register new test functions. Example: When developing E2E tests, use this rule to understand the e2e framework.
The English summary is being prepared. Showing the original description.
Maintain and extend the open-websearch MCP server. Trigger when changing search engines, proxy or TLS behavior, tool registration, live parsing behavior, or compatibility and regression behavior inside this repository.
The English summary is being prepared. Showing the original description.
Self-coaching analysis of your own behavior across meetings — talk-time ratio, filler words, hedging language, monologue length, energy patterns, and (when meetings are tagged via /minutes-tag) what your behavior in winning meetings looks like vs losing ones. Use this whenever the user says "how did I do", "review my last meeting", "mirror", "self-review", "show my patterns", "coach me", "where am I weak", "talk time", "am I improving", "what do I do in meetings I win", "feedback on me", or asks for any kind of personal feedback on their own meeting behavior. This is the rare skill that gives the user a mirror to their own habits — surface it whenever they show curiosity about their own performance, even if they don't use the word "mirror".
The English summary is being prepared. Showing the original description.
Write tests that pin real behavior instead of implementation details, config values, or lucky samples. Use when adding tests for new behavior, writing a regression test, fixing a brittle or flaky test, reviewing a test diff, or when a test breaks after a refactor or config change that didn't change behavior.
The English summary is being prepared. Showing the original description.
Apply behavioral psychology, cognitive biases, and 70+ mental models to marketing for conversion optimization, pricing, copy, and campaigns. Use for persuasion, behavioral science, why people buy, consumer behavior, or neuromarketing.
The English summary is being prepared. Showing the original description.
When the user wants to apply psychological principles, mental models, or behavioral science to marketing. Also use when the user mentions 'psychology,' 'mental models,' 'cognitive bias,' 'persuasion,' 'behavioral science,' 'why people buy,' 'decision-making,' 'consumer behavior,' 'anchoring,' 'social proof,' 'scarcity,' 'loss aversion,' 'framing,' or 'nudge.' Use this whenever someone wants to understand or leverage how people think and make decisions in a marketing context. For applying psychology to specific pages, see cro; for pricing tactics, see pricing; for copy framing, see copywriting.
The English summary is being prepared. Showing the original description.