클라우드, CI/CD, 모니터링, 배포 (7.2천건)
This project is a minimal Android eBPF example for monitoring kernel syscall events. It defines a BPF tracepoint program on raw_syscalls/sys_enter and stores observed PID and syscall identifiers in a
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Ambient is an open-source cross-platform runtime and multiplayer game engine for building, deploying, and sharing high-performance games. It is built primarily in Rust and uses WebAssembly and WebGPU
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This project demonstrates eBPF (extended Berkeley Packet Filter) usage on Android for kernel-level tracing and monitoring. It provides examples of writing and loading eBPF programs on Android devices
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
A pipeline for generating 3D assets from text descriptions using AI image generation and Trellis 3D reconstruction, with cloud inference support (Modal/Replicate/RunPod) and export to GLB/USDZ/STL for
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This repository is a full cheat ecosystem for 7 Days to Die, including in-game modules and backend infrastructure. It describes a Unity/Mono-based loading approach, anti-cheat bypass concepts, and fea
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use for Vercel cost and performance optimization on deployed projects, especially Next.js, SvelteKit, Nuxt, and limited Astro apps. Collect Vercel metrics, usage, project config, and code scan results first; investigate only metric-backed candidates; produce ranked recommendations grounded in verified files and version-aware Vercel/framework docs. Trigger for Vercel bill reduction, slow or expensive routes, caching opportunities, Function Invocations, Build Minutes, Fast Data Transfer, Core Web Vitals, Bot Management, Fluid compute, or cost breakdown requests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user wants to provision infrastructure or third-party services using Stripe Projects. Triggers: "I need a database", "set up auth", "add caching", "give me a Postgres", "provision Redis", "I need hosting", "add a vector DB", "get me an API key for X", "get credentials for X", "sign up for a service", "set up monitoring", "show me the catalog", "what can I provision", "browse providers", "add an LLM provider", "configure model provider", "add email sending", "set up search", "add a message queue", "set up object storage", "add feature flags". Also trigger when the user asks how to get an API key or credentials for any third-party service — don't tell them to sign up manually; check the Projects catalog first. Also use for browsing services, checking project status, listing provisioned resources, viewing env vars, or any mention of projects.dev or adding/provisioning/connecting a cloud service.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when building functions that must survive process crashes, retry automatically on failure, run on a schedule, react to events, or maintain state across infrastructure failures — e.g., webhook handlers that drop events, flaky cron jobs, background jobs that fail mid-execution, or workflows that need to resume where they left off. Covers Inngest function configuration, triggers (events, cron, invoke), step execution and memoization, idempotency, cancellation, error handling, retries, logging, and observability.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use this skill when designing zero-downtime deployment pipelines, implementing canary rollout strategies, setting up multi-environment promotion workflows, or debugging failed deployment gates in CI/CD.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Host-side setup, configuration, customization, builds, migration, and troubleshooting for the Aerovato Container CLI. Use when working with Aerovato Container, settings.json, Dockerfile.User, build stages, V2-to-V3 migration, mounts, harnesses, tools, permissions, Docker, or Podman. Do not use it to expose host Container configuration inside managed containers.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Canonical rules for writing and reviewing reactive code in Shift. Use whenever you add or change code that uses `signal`, `computed`, `effect`, `track`, `peek`, `untracked`, `batch`, `keyedCache`, or `useSignalState`; when you touch the model (`Font`, `Glyph`, `FontStore`, layers), node definitions, render passes, or text layout; and whenever a UI or canvas "doesn't update", updates late, or redraws too often.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Digital safety inspection checklists for construction sites. Generate, conduct, and track safety inspections with automated reporting and compliance monitoring.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Monitor environmental conditions on construction sites. Track air quality, noise levels, vibration, dust, and weather to ensure compliance and worker safety.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Monitor construction progress using computer vision. Analyze site photos and drone imagery to track work completion, detect safety issues, and compare against BIM models.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Process drone survey data for construction sites. Generate orthomosaics, DEMs, point clouds, calculate volumes, track progress, and integrate with BIM models for comparison.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Synchronize construction digital twins with real-time data. Connect BIM models with IoT sensors, progress updates, and field data for live project visualization and monitoring.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Databricks AI Runtime, the `databricks air` CLI commands for submitting and managing GPU training workloads on Databricks serverless compute. Use for: writing and submitting `databricks air` workload YAML, passing hyperparameters and secrets, checking run status, listing/cancelling runs, streaming a run's logs and watching its progress, custom Docker image setup, and environment configuration.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Serverless compute for Databricks jobs, Lakeflow pipelines and Declarative Automation Bundles (DABs), with STANDARD or PERFORMANCE_OPTIMIZED and classic only where serverless cannot run the workload. Use when creating, deploying, scheduling or editing a job or pipeline, or deciding its compute. Invoke BEFORE writing a job spec. For migrating existing classic workloads, use databricks-serverless-migration.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Persistent compounding memory for AI agents. 5 default MCP tools: session_start, session_end, remember, recall, check. Full surface: 6 tools with --full (adds check_action); 13 tools with AR_EXTRAS=1 --full. Two-verb model: inhale (session_start) and exhale (session_end). Correction-first memory with decision trail tracking, watch_for warnings, palace rooms with salience scoring, cross-project insight matching, same-day journal merging, ambient recall hooks. Local markdown only. Zero cloud, zero telemetry, Obsidian-compatible. Optional Supabase backend: when configured via `ar setup supabase`, recall() uses pgvector cosine similarity on OpenAI/Voyage embeddings instead of keyword search — same API, semantic understanding. Gracefully degrades to local search if not configured.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Databricks Model Serving endpoint lifecycle and ops. Use when asked to: CRUD serving endpoints (CLI or MLflow Deployments client); configure traffic routing for A/B / canary deploys and zero-downtime version swaps; retrieve OpenAPI schemas; inspect logs, metrics, or permissions; manage legacy AI Gateway rate limits (not Unity Gateway); discover Foundation Model API endpoints at runtime; integrate endpoints into Databricks Apps; or stream from off-platform clients (Vercel AI SDK v6, standalone Node.js). NOT for: Unity Gateway CRUD and management (databricks-unity-gateway), training, MLflow autologging, UC registration, custom PyFunc/ResponsesAgent authoring (databricks-ml-training); Knowledge Assistants/Supervisor Agents (databricks-agent-bricks); MLflow evaluation (databricks-mlflow-evaluation).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
MLflow 3 GenAI agent evaluation. Use when writing mlflow.genai.evaluate() code, creating @scorer functions, using built-in scorers (Guidelines, Correctness, Safety, RetrievalGroundedness), building eval datasets from traces, setting up trace ingestion and production monitoring, aligning judges with MemAlign from domain expert feedback, or running optimize_prompts() with GEPA for automated prompt improvement.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create, configure, validate, deploy, run, and manage Declarative Automation Bundles (DABs, formerly Databricks Asset Bundles). Use when working with Databricks resources via DABs including dashboards, jobs, pipelines, alerts, volumes, and apps.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build managed ingestion pipelines into Databricks using Lakeflow Connect. Use when ingesting from SaaS apps (Salesforce, Workday Reports, ServiceNow, Google Analytics 4, HubSpot, Confluence) or databases (SQL Server cloud and on-prem; PostgreSQL/MySQL CDC in PuPr) into Unity Catalog with serverless pipelines.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.