claude
cf78c31e05
Updated general-dev-workflow skill to stress that for Docker projects, BOTH build success AND successful container startup are required before considering a change complete. Key additions: - Docker container startup verification is mandatory, not optional - Containers must have status 'Up', not 'Restarting' or 'Exited' - Check container logs for errors during startup - Missing config files, invalid env vars, DB issues only show at runtime - Startup failures block production deployments - Updated Phase 4 checkpoint to include container startup validation Lesson from email-api issue: missing appsettings.json caused restart loop that had no visible logs during build. This must be caught in Phase 4 before code review and prevents production issues. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Introduction
TODO: Give a short introduction of your project. Let this section explain the objectives or the motivation behind this project.
Getting Started
TODO: Guide users through getting your code up and running on their own system. In this section you can talk about:
- Installation process
- Software dependencies
- Latest releases
- API references
Build and Test
TODO: Describe and show how to build your code and run the tests.
Contribute
TODO: Explain how other users and developers can contribute to make your code better.
If you want to learn more about creating good readme files then refer the following guidelines. You can also seek inspiration from the below readme files: