Menu
Create a new domain model from TMDb
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | create-domain-model |
| description | Create a new domain model from TMDb |
Guide for creating a new domain model from TMDb SDK types. See references/domain-model-patterns.md for code patterns, file locations, and common pitfalls.
Ask the user for:
DocC documentation: https://adamayoung.github.io/TMDb/documentation/tmdb/
Source code (in Xcode DerivedData after build):
.../SourcePackages/checkouts/TMDb/Sources/TMDb/Domain/Models/
Contexts/Popcorn<X>/Sources/<X>Domain/Entities/<Name>.swiftIdentifiable, Equatable, SendableAdapters/.../Tests/.../Mappers/<Name>MapperTests.swiftAdapters/.../Sources/.../Mappers/<Name>Mapper.swiftContexts/Popcorn<X>/Sources/<X>Infrastructure/DataSources/Local/Models/<Context><Name>Entity.swiftEquatable, ModelExpirableContexts/.../Tests/<X>InfrastructureTests/Mappers/<Name>MapperTests.swiftContexts/.../Sources/<X>Infrastructure/DataSources/Local/Mappers/<Name>Mapper.swiftContexts/Popcorn<X>/Sources/<X>Application/Models/<Name>Details.swiftURL? paths with ImageURLSet?Contexts/.../Tests/<X>ApplicationTests/Mappers/<Name>DetailsMapperTests.swiftContexts/.../Sources/<X>Application/Mappers/<Name>DetailsMapper.swift<Name>+Mocks.swift in each test target that needs itFollow the /add-use-case skill for wiring into the architecture.
Run the full pre-PR checklist: make lint, /build, /test (formatting is applied automatically by the PostToolUse hook)
$ARGUMENTS
Build the project for testing
Build the project
Take the current plan all the way to a ready-to-merge pull request — review the plan (scaled to risk), implement it test-first, code-review and fix, security-review, verify the acceptance criteria, open the PR, and watch it green. Use after you have an approved plan (e.g. from plan mode) and want the rest of the feature pipeline run end-to-end. Invoking it is itself plan approval — it then runs autonomously to a single hard stop: ready-to-merge.
Run a specific test target or test class
Run all unit tests
Run snapshot tests