integration-implementation

To generate a Dockerfile for local development, use this skill to create a Dockerfile.local with hot reload support. It automates entrypoint wiring, launch scripts, and environment templates to ensure deterministic container startup and validated component integration.

Managing startup sequences across multiple Docker components is done by generating standardized entrypoints and launch scripts. This approach enforces a deterministic startup order and integrates health checks to validate component readiness across modules.

Adding health checks and readiness endpoints for container integration testing requires standardized scripts and test scaffolding. This skill generates those scripts to validate component integration scenarios and ensure reproducible deployments across local development workflows.

Yes, packaging components into runnable containers requires a defined SKILL.md frontmatter, a Dockerfile.local, and environment templates. These prerequisites ensure the generated launch scripts and entrypoints fulfill startup, health checks, and test scenarios deterministically.

Container integration fails during local component startup when entrypoint wiring and launch scripts are not standardized. Use this skill to generate deterministic startup sequences, apply environment templates, and scaffold integration tests to validate module readiness.