EGO is a Go microservices framework designed around component-based lifecycle management. It provides servers (HTTP via Gin, gRPC), clients (HTTP, gRPC), scheduled tasks (cron, one-off jobs), and built-in observability (structured logging, Prometheus metrics, OpenTelemetry tracing). The framework uses a configuration-driven pattern (Load → Build) and includes protoc plugins for generating error types, HTTP handlers, and test scaffolding. Production usage typically involves defining components in TOML/YAML config files and wiring them via the ego.New().Serve(...) entry point. The architecture is modular with clear abstractions for configuration, logging, metrics, registry, and resilient interceptors.
This is a curated collection repository of Cursor AI editor rules (.mdc files), not a traditional software application. It functions as an awesome-list style repository that aggregates project-specific configuration files for the Cursor AI code editor. The repository contains over 200 rule files covering various programming languages, frameworks, testing methodologies, and development workflows. The architecture is straightforward: a flat collection of .mdc files in the rules/ directory, with a README.md serving as the index and discovery mechanism. The repository includes Node tooling for maintaining quality and consistency: scripts for checking repository hygiene, validating awesome-list format, converting README links between relative and absolute forms, checking PR author age policies, and cleaning up legacy artifacts. The CI/CD pipeline uses GitHub Actions with a main workflow file. The key value proposition is providing reusable Cursor AI configuration files that developers can drop into their .cursor/rules/ directories. Each rule file contains frontmatter metadata (description, globs pattern, alwaysApply flag) followed by instructions that guide Cursor AI's behavior for specific technology stacks or development patterns. The rules range from framework-specific guidance (React, Vue, Next.js, Svelte) to language best practices (TypeScript, Python, Go, Rust) to specialized domains (embedded systems, blockchain, machine learning workflows). The repository demonstrates moderate engineering quality in its maintenance tooling, with centralized configuration, test coverage for scripts, and automated quality checks. However, the rule files themselves vary significantly in quality and depth - some are comprehensive and well-structured while others are minimal or boilerplate.
This repository contains a Gradle plugin that enhances Gradle's built-in property loading mechanism. The plugin adds support for environment-specific property files (gradle-${environmentName}.properties) and user-specific property files (gradle-${gradleUserName}.properties), modifies the property processing order, creates filter tokens for file filtering, and provides task-level methods for validating required and recommended properties. It is implemented in Groovy and follows standard Gradle plugin patterns, with comprehensive test coverage verifying its behavior in various scenarios including multi-project builds.
This is a Home Assistant add-on repository for the Cloudflared add-on, which enables remote access to Home Assistant via a Cloudflare Tunnel without opening ports. The repository itself does not contain the add-on's runtime code (which resides in a separate repository); instead, it serves as a meta-repository that defines the add-on's configuration schema, provides multi-language translations, and hosts documentation and CI/CD infrastructure. The primary functional artifact is the `cloudflared/config.yaml` file, which defines input validation rules (including regex-based parameter validation), port mappings, and optional configuration fields. The repository is not a library or framework but a configuration and distribution hub for the add-on. It is well-maintained with automated dependency updates, linting, and release management.