Sponsored by

Find leads on Reddit on auto pilot

Topic: golang

205 skills in this topic.

shadcn-code-review Reviews shadcn/ui components for CVA patterns, composition with asChild, accessibility states, and data-slot usage. Use when reviewing React components using shadcn/ui, Radix primitives, or Tailwind styling.
existential-birds/beagle 44
shadcn-ui shadcn/ui component patterns with Radix primitives and Tailwind styling. Use when building UI components, using CVA variants, implementing compound components, or styling with data-slot attributes. Triggers on shadcn, cva, cn(), data-slot, Radix, Button, Card, Dialog, VariantProps.
existential-birds/beagle 44
tailwind-v4 Tailwind CSS v4 with CSS-first configuration and design tokens. Use when setting up Tailwind v4, defining theme variables, using OKLCH colors, or configuring dark mode. Triggers on @theme, @tailwindcss/vite, oklch, CSS variables, --color-, tailwind v4.
existential-birds/beagle 44
vitest-testing Vitest testing framework patterns and best practices. Use when writing unit tests, integration tests, configuring vitest.config, mocking with vi.mock/vi.fn, using snapshots, or setting up test coverage. Triggers on describe, it, expect, vi.mock, vi.fn, beforeEach, afterEach, vitest.
existential-birds/beagle 44
zustand-state Zustand state management for React and vanilla JavaScript. Use when creating stores, using selectors, persisting state to localStorage, integrating devtools, or managing global state without Redux complexity. Triggers on zustand, create(), createStore, useStore, persist, devtools, immer middleware.
existential-birds/beagle 44
axum-code-review Reviews axum web framework code for routing patterns, extractor usage, middleware, state management, and error handling. Use when reviewing Rust code that uses axum, tower, or hyper for HTTP services. Covers axum 0.7+ patterns including State, Path, Query, Json extractors.
existential-birds/beagle 44
review-rust Comprehensive Rust code review with optional parallel agents
existential-birds/beagle 44
review-verification-protocol Mandatory verification steps for all code reviews to reduce false positives. Load this skill before reporting ANY code review findings.
existential-birds/beagle 44
rust-code-review Reviews Rust code for ownership, borrowing, lifetime, error handling, trait design, unsafe usage, and common mistakes. Use when reviewing .rs files, checking borrow checker issues, error handling patterns, or trait implementations. Covers Rust 2021 edition patterns and modern idioms.
existential-birds/beagle 44
rust-testing-code-review Reviews Rust test code for unit test patterns, integration test structure, async testing, mocking approaches, and property-based testing. Use when reviewing _test.rs files,
existential-birds/beagle 44
serde-code-review Reviews serde serialization code for derive patterns, enum representations, custom implementations, and common serialization bugs. Use when reviewing Rust code that uses serde, serde_json, toml, or any serde-based serialization format. Covers attribute macros, field renaming, and format-specific pitfalls.
existential-birds/beagle 44
sqlx-code-review Reviews sqlx database code for compile-time query checking, connection pool management, migration patterns, and PostgreSQL-specific usage. Use when reviewing Rust code that uses sqlx, database queries, connection pools, or migrations. Covers offline mode, type mapping, and transaction patterns.
existential-birds/beagle 44
tokio-async-code-review Reviews tokio async runtime usage for task management, sync primitives, channel patterns, and runtime configuration. Use when reviewing Rust code that uses tokio, async/await patterns, spawn, channels, or async synchronization. Also covers tokio-util, tower, and hyper integration patterns.
existential-birds/beagle 44
gen-test-plan Analyze repo, detect stack, trace changes to user-facing entry points, generate YAML test plan
existential-birds/beagle 44
run-test-plan Execute YAML test plan, stop on first failure, output rich debug prompt
existential-birds/beagle 44
lsp-enable Use when navigating code, understanding unfamiliar functions, finding definitions or references, tracing call hierarchies, preparing for refactoring, or analyzing code impact. Enforces LSP-first semantic code intelligence with mandatory pre-edit checks, impact analysis before refactoring, and post-edit diagnostics. Provides IDE-like precision for code operations in large codebases. Covers navigation (goToDefinition, findReferences), understanding (hover, documentSymbol), and call analysis (incomingCalls, outgoingCalls).
zircote/lsp-tools 2
autoresearch Autonomously optimize any Claude Code skill by running it repeatedly, scoring outputs against binary evals, mutating the prompt, and keeping improvements. Based on Karpathy's autoresearch methodology. Use when: optimize this skill, improve this skill, run autoresearch on, make this skill better, self-improve skill, benchmark skill, eval my skill, run evals on. Outputs: an improved SKILL.md, a results log, and a changelog of every mutation tried.
unix2dos/skills 2
book-recommender Only invoke when explicitly requested via "推荐一本书"、"书籍推荐"、"@book-rec" or "book recommendation". Do NOT auto-trigger.
unix2dos/skills 2
code-refactor Use when refactoring Go code for better structure, maintainability, extensibility, or testability - follows SOLID principles and idiomatic Go patterns
unix2dos/skills 2
geo-explorer Only invoke when explicitly requested via "地缘探索"、"@geo-explorer" or "geo explorer". Do NOT auto-trigger.
unix2dos/skills 2
go-code-review Use when reviewing Go code for performance, concurrency safety, security vulnerabilities, or readability issues
unix2dos/skills 2
history-autopsy Only invoke when explicitly requested via "历史速览"、"@history-autopsy" or "history autopsy". Do NOT auto-trigger.
unix2dos/skills 2
strategic-product-advisor Only invoke when explicitly requested via "产品方向"、"怎么赚钱"、"竞品分析"、"@strategic-product-advisor". Do NOT auto-trigger.
unix2dos/skills 2
technical-content-optimizer Only invoke when explicitly requested via "润色博客"、"技术博客优化"、"@technical-content-optimizer" or "polish blog". Do NOT auto-trigger.
unix2dos/skills 2