Menu
Cog architecture and cross-cutting review guidelines
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Guide and automate the Cog release process
Use this skill when updating, reviewing, or creating architecture documentation in the architecture/ directory. This includes after refactors, feature additions, component changes, or when auditing docs for accuracy. Use it any time code changes affect how Cog's internals work -- new packages, changed IPC protocols, modified build pipeline, runtime behavior changes. Also use it proactively when reviewing PRs that touch core systems to check whether the architecture docs need updating.
Go code review guidelines for the Cog codebase
Python code review guidelines for the Cog SDK
Rust code review guidelines for Coglet
| name | cog-review |
| description | Cog architecture and cross-cutting review guidelines |
Cog packages ML models into production-ready containers. Use this skill for changes that cross language boundaries or touch core architecture.
cmd/cog/ and pkg/ -- builds, runs, and deploys modelspython/cog/ -- predictor interface, types, HTTP/queue servercrates/ -- prediction server inside containers (HTTP, worker management, IPC)Wheel resolution: The CLI discovers SDK and coglet wheels from dist/ at
Docker build time. Wheels are NOT embedded in the binary. Changes to build
artifacts need to account for this.
Dockerfile generation: pkg/dockerfile/ generates Dockerfiles from cog.yaml
config. Template injection and escaping matter here.
Config parsing: pkg/config/config.go parses cog.yaml. Schema is at
pkg/config/data/config_schema_v1.0.json. Changes must keep schema and Go
code in sync.
Two-process coglet: Parent process (HTTP server + orchestrator) and child worker process (Python predictor execution) communicate via IPC. Changes to the IPC protocol affect both Rust and Python code.
Compatibility matrix: CUDA/PyTorch/TensorFlow compatibility is managed in
tools/compatgen/. Framework version changes have wide blast radius.
Cargo.toml must match.python/cog/base_predictor.py affect all downstream model authors.docs/ require running mise run docs:llm to regenerate docs/llms.txt.cmd/ or pkg/cli/ require mise run docs:cli.integration-tests/ use Go's testscript and need a built cog binary.