메뉴
Automated dev environment setup for deadline-cloud-for-cinema-4d. Use when onboarding, setting up the Cinema 4D integration repo, building the package, or installing the submitter. The agent automates all steps and only prompts when user input is required.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
AI-guided design for Cinema 4D features and major changes in Deadline Cloud integration. Use when designing new features, planning major refactors, creating design docs, or making architectural decisions for deadline-cloud-for-cinema-4d. Triggers on requests like "design a feature", "write a design doc", "plan a major change", or "architect a solution".
Day-to-day development for deadline-cloud-for-cinema-4d. Use when building, testing, linting, debugging, or running integration tests with Cinema 4D, Redshift, Arnold, or V-Ray. Covers submitter iteration, adaptor debugging, and project structure.
SOC 직업 분류 기준
| name | c4d-dev-setup |
| description | Automated dev environment setup for deadline-cloud-for-cinema-4d. Use when onboarding, setting up the Cinema 4D integration repo, building the package, or installing the submitter. The agent automates all steps and only prompts when user input is required. |
| tags | ["skill","deadline-cloud","deadline-cloud-for-cinema-4d","deadline-cloud-for-c4d","dev-setup","onboarding","submitter-install"] |
AI-guided automated setup for the deadline-cloud-for-cinema-4d project. The agent executes all steps, validates results, and only prompts the user when manual intervention is truly required.
Use this skill when:
deadline-cloud-for-cinema-4d repoPlatforms:
Python: Cinema 4D 2026 uses Python 3.11; Cinema 4D 2024–2025 uses Python 3.10.
Build system: Hatch.
You MUST automate all possible steps by running commands directly. You MUST only prompt the user when their input is required (Cinema 4D version, custom paths). You MUST validate each step's output before proceeding to the next. You MUST inform the user clearly when manual intervention is needed. You SHOULD report progress at each step.
Follow the detailed step-by-step workflow in references/setup-guide.md.
Summary of steps:
README.md, DEVELOPMENT.md, docs/software_arch.md)hatch build)Refer to references/troubleshooting.md for common issues and solutions.
| Resource | Location |
|---|---|
| Setup workflow | references/setup-guide.md |
| Troubleshooting | references/troubleshooting.md |
| Architecture context | AGENTS.md (repo root) |
| Project docs | README.md, DEVELOPMENT.md, docs/software_arch.md |