Skill UI

Guide to adding Firebase to Flutter projects: setup, flutterfire configure, initialization in main.dart, and multi-flavor Firebase configuration with best practices.

Enforces full, unabridged code and document generation by overriding LLM truncation safeguards, forbidding placeholder patterns, and managing token-limit splits so every requested deliverable is returned complete.

A comprehensive guide to idiomatic Go programming style and code clarity. This skill addresses best practices for line breaking, variable declaration intent, control flow structure (e.g., early returns, switch usage), and function design principles. Use it when writing, reviewing, or establishing project-wide coding standards to ensure maximum readability and maintainability.

A comprehensive guide to best practices for managing dependencies in Go projects. It covers the use of go.mod, go.sum, and essential commands like go mod tidy and govulncheck to ensure secure, stable, and reproducible builds. Use this skill when adding, upgrading, removing, or auditing external Go modules to maintain project integrity.

This skill provides comprehensive guidance on idiomatic Go patterns for building production-ready, robust applications. It covers best practices like functional options, proper constructor design, resource management (timeouts, graceful shutdown), error handling, concurrency patterns, and architectural styles (DDD, Hexagonal). Use it when structuring complex Go APIs, defining service boundaries, or auditing existing code for common anti-patterns and performance pitfalls.

A comprehensive guide and skill set for optimizing Go (Golang) application performance. It establishes a core philosophy of profiling before optimizing, focusing on reducing allocations, improving CPU efficiency, and addressing structural anti-patterns. Provides systematic modes for deep review (hot path, architecture review) and follows an iterative methodology (Benchmark -> Diagnose -> Improve -> Compare) to ensure measurable and stable performance gains.

A comprehensive guide for structuring robust Go applications, covering best practices for new projects, from CLI tools to complex microservices and monorepos. It details directory conventions (cmd, internal, pkg), naming rules, adopting 12-Factor App principles, and choosing appropriate architectures (Clean, DDD, Hexagonal).

This skill guides developers in writing robust and defensive Go code. It addresses common pitfalls that lead to runtime panics and silent data corruption, such as nil map writes, slice backing array aliasing, silent numeric truncation (int64 to int32), and inaccurate float comparisons. Use this when designing highly reliable Go systems that must withstand typical programmer errors and maintain data integrity.

A comprehensive, generics-first utility library designed for Go developers who prefer declarative, functional programming patterns over manual loops. It provides 500+ type-safe functions for common data transformations (Map, Filter, Reduce, GroupBy, etc.) on slices, maps, and strings. By defaulting to immutable operations, it ensures thread safety and predictable state changes. The library also offers specialized packages (lop, lom, loi) to address performance bottlenecks, such as CPU-bound parallel processing or lazy evaluation, allowing engineers to choose the optimal approach for their c...

samber/oops is a robust library that transforms standard Go error handling by adding crucial structured context. Instead of generic error messages, it allows developers to attach key-value attributes, stack traces, error codes, and user-facing messages directly to the error object. This is essential for modern microservices, allowing APM tools (Datadog, Sentry) and on-call engineers to diagnose failures accurately by understanding the full context of the failure, such as the domain, user ID, and specific query that failed.

A comprehensive guide to advanced design patterns in Go, focusing on writing highly testable and clear code. It covers principles like keeping interfaces small and composable, defining contracts where they are consumed, preferring concrete return types, utilizing generics over 'any', and mastering the use of struct embedding and field tags for serialization.

Reply to every recipient in a Gmail thread from the CLI with gws gmail +reply-all, handling threading automatically while allowing HTML bodies, attachments, drafts, and recipient adjustments such as adds, CC/BCC, or removals.