Total 34,351 skills
Showing 12 of 34351 skills
Structured logging strategy including log levels, correlation IDs, context propagation, and PII avoidance. Use when designing logging, reviewing log statements, or setting up log aggregation.
Guides structured code review with a checklist approach. Use when reviewing PRs, diffs, or code changes before merging.
Analysis of Lanhu design drafts and Axure prototypes. Directly read prototype pages, design drafts, and slice resources of Lanhu projects via lanhu MCP Server. Trigger scenarios: - Need to obtain Axure prototype pages from Lanhu for requirement analysis - Need to view Lanhu UI design drafts and design parameters - Need to extract slice resources from Lanhu design drafts - Need to collaborate via Lanhu team message board - Need to parse Lanhu invitation links Trigger words: Lanhu, lanhu, design draft, prototype, Lanhu link, design image, slice
Applies DRY, YAGNI, PORO, Convention over Configuration, and KISS to Rails code; defers style to the project's linter(s). Covers structured logging, comment discipline, and path-specific rules (models, workers, services, controllers, repositories, serializers, RSpec, raw SQL). Use when designing or reviewing Rails structure, avoiding over-engineering, or aligning code with team boundaries by directory.
Real-time systems expert for WebSockets, SSE, presence, and live synchronizationUse when "websocket, real-time updates, live collaboration, presence indicator, online status, live cursors, multiplayer, server-sent events, push notifications, collaborative editing, websocket, sse, realtime, presence, collaboration, live-updates, socket.io, pusher, ably, supabase-realtime" mentioned.
Use when reviewing a Ruby on Rails app for Domain-Driven Design boundaries, bounded contexts, language leakage, cross-context orchestration, or unclear ownership. Covers context mapping, leakage detection, and smallest credible boundary improvements.
Challenges stakeholder requests to identify real needs and propose optimal solutions. Use when receiving vague feature requests, reframing a problem before implementation, or when user mentions problem framing, XY problem, stakeholder request, or solution discovery. WHEN NOT: Well-defined technical tasks with clear requirements, bug fixes with known root causes, or routine CRUD operations.
Must be followed when writing error handling code that includes try-catch. Ensure that the catch block has substantial processing logic, is not empty, does not only log information, and must handle or re-throw exceptions. Trigger keywords: try-catch specification, error handling best practices, exception handling review.
Analyzes Rails code quality, architecture, and patterns without modifying code. Use when the user wants a code review, quality analysis, architecture audit, or when user mentions review, audit, code quality, anti-patterns, or SOLID principles. WHEN NOT: Actually implementing fixes (use specialist agents), writing new tests (use rspec-agent), or generating new features.
Create and manage a Notion-based tweet performance tracking system for "poor man's reinforcement learning"
BISON v1.1 — Conviction holder for top 10 Hyperliquid assets by volume. Enters on 4h trend structure + 1h momentum + SM alignment convergence. Holds through pullbacks with DSL High Water Mode (mandatory). Re-evaluates thesis every 5 min — exits when conviction breaks, not when price retraces. Wide Phase 1 floors, no time-based exits, infinite trailing at 85% of peak. v1.1: daily entry cap only enforced when day PnL is negative. When profitable, reloads in batches of 3 — BISON keeps trading as long as it's making money.
Configures Lean environments, installs external proof skills, runs preflight checks, and guides the workflow for proving downloaded OpenMath Lean theorems locally.