Results for “cac”

Provides production-grade Django architecture patterns including project structure, model design, REST API design with DRF, ORM best practices, caching, signals, and middleware.

Reads related records across multiple sObjects in one GraphQL request, paginates related lists with cursors, and replaces overlapping @wire(getRecord) calls with a single cache-shared query.

Execute AEM Edge Delivery Services admin operations: manage content, cache, code, indexes, sitemaps, snapshots, logs, users, jobs, sites, config, secrets, API keys, tokens, profiles, and versioning. Also supports Document Authoring operations.

Guides usage of the Gemini API on Agent Platform with the Google Gen AI SDK, covering SDK usage (Python, JS/TS, Go, Java, C#), capabilities like multimodal inputs, tools, media generation, caching, batch prediction, and Live API.

Laravel architecture patterns, routing/controllers, Eloquent ORM, service layers, queues, events, caching, and API resources for production apps.

Django architecture patterns, REST API design with DRF, ORM best practices, caching, signals, middleware, and production-grade Django apps.

Django architecture patterns, REST API design with DRF, ORM best practices, caching, signals, middleware, and production-grade Django apps.

Django architecture patterns, REST API design with DRF, ORM best practices, caching, signals, middleware, and production-grade Django apps.

Clean and package the project for distribution. Removes __pycache__, .venv, build artifacts, data caches, logs, IDE files, coverage reports, and sanitizes API keys in config. Produces a minimal, ready-to-share codebase. Use when user says 'package', 'clean project', 'clean up', '打包', '清理项目', '清理缓存', 'prepare for distribution', 'remove caches', or wants to deliver a clean copy of the code.

Clean and package the project for distribution. Removes __pycache__, .venv, build artifacts, data caches, logs, IDE files, coverage reports, and sanitizes API keys in config. Produces a minimal, ready-to-share codebase. Use when user says 'package', 'clean project', 'clean up', '打包', '清理项目', '清理缓存', 'prepare for distribution', 'remove caches', or wants to deliver a clean copy of the code.

CI with Apache Bench. CI integration.

Provides slash commands to start, stop, and message Claude Code relay sessions from chat channels like Telegram, with auto-forwarding and inline button menus.

Clean and package the project for distribution. Removes __pycache__, .venv, build artifacts, data caches, logs, IDE files, coverage reports, and sanitizes API keys in config. Produces a minimal, ready-to-share codebase. Use when user says 'package', 'clean project', 'clean up', '打包', '清理项目', '清理缓存', 'prepare for distribution', 'remove caches', or wants to deliver a clean copy of the code.

Fix continuous integration (CI) test or build failures for the current PR branch. Fetch CI failure logs, map them to local commands, reproduce the failures, fix the code, verify locally, and commit and push.

Designs scalable GraphQL APIs with schema design, DataLoader for N+1 prevention, and Apollo Client caching, while avoiding common anti-patterns.

Design and implement production-grade GraphQL APIs with schema design, DataLoader for N+1 prevention, Apollo Client caching, and federation patterns.

This skill should be used when importing, listing, or exporting Granola meeting recordings and transcripts. Queries Granola's local cache and API to list meetings, extract transcripts, and export to Obsidian notes in Fathom-compatible format.

Manage Hugging Face Hub resources: download/upload models, datasets, spaces; manage repos, buckets, collections, discussions, and cache; run SQL queries on datasets; authenticate and manage tokens.

Searches a local cache of Windows WinMD metadata to find the right Windows API for any capability and retrieve full type details including methods, properties, events, and enumeration values.

Streams change data capture events from a TigerBeetle financial transactions database into Redpanda or Kafka using the tigerbeetle_cdc input, with checkpointing, filtering, and routing guidance.

Points developers to the canonical WordPress Presence API sources and explains its ephemeral-table-plus-TTL architectural pattern, so they avoid inventing postmeta-based presence implementations.