Loading...
Loading...
Found 94 Skills
Review error handling, input validation, and exception patterns using 24-item checklist. Use when auditing defensive code, designing barricades, choosing assertion vs error handling, or deciding correctness vs robustness strategy. Triggers on: empty catch blocks, missing input validation, assertions with side effects, wrong exception abstraction level, garbage in garbage out mentality, deadline pressure to skip validation, trusted source rationalization. Produce status table with VIOLATION/WARNING/PASS per item, or barricade/error-handling design recommendations.
Battle-tested testing best practices for AI coding assistants (40+ rules). Use when writing, reviewing, or generating tests. Covers test structure, data factories, assertions, mocking, DOM testing, and database testing. Works with Vitest, Jest, Playwright, Testing Library, Storybook, and more.
Analyze 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.
Generic test writing discipline: test quality, real assertions, anti-patterns, and rationalization resistance. Use when writing tests, adding test coverage, or fixing failing tests for any language or framework. Complements language-specific skills.
Use this skill when the agent needs to interact with CLAWLOGIC prediction markets. This includes: registering as an agent on-chain, creating new prediction markets, analyzing market questions to form opinions, buying YES/NO positions, asserting market outcomes via UMA Optimistic Oracle, disputing incorrect assertions from other agents, settling resolved markets to claim winnings, and posting bet narratives ("what I bet and why") to the frontend feed. Triggers: - "create a market about..." - "what do you think about [market question]?" - "buy YES/NO on market..." - "assert the outcome of market..." - "dispute the assertion on market..." - "check my positions" - "settle market..." - Any discussion about prediction markets, trading, or information markets
Debug TensorFlow and Keras issues systematically. This skill helps diagnose and resolve machine learning problems including tensor shape mismatches, GPU/CUDA detection failures, out-of-memory errors, NaN/Inf values in loss functions, vanishing/exploding gradients, SavedModel loading errors, and data pipeline bottlenecks. Provides tf.debugging assertions, TensorBoard profiling, eager execution debugging, and version compatibility guidance.
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
Use when writing or refactoring proof-carrying code in MoonBit, especially for Why3-backed specifications, abstraction functions, representation invariants, proof assertions, recursive verified data structures, or reducing trusted proof bridges.
Create and manage Oodle synthetic monitors — HTTP and TCP health checks with assertions and configurable intervals.
Write focused controller tests using HTTP assertions; keep heavy logic in Actions/Services and unit test them