dockerize-and-deploy
Dockerize and Deploy
Containerize a repo and produce a production-ready deployment setup. Work in phases — never write everything at once.
Quick Start
- Audit the repo (language, services, DB, existing Docker files).
- Confirm phases with the user.
- Execute one phase at a time, verifying after each.
Workflow
1. Audit the repo
Read the codebase to identify:
- Runtime: Node.js, Python, Go, Java, etc. and version
- Services: web server, background workers, scheduled jobs
- Datastores: PostgreSQL, MySQL, Redis, MongoDB, S3-compatible storage
More from rockclaver/systemcraft
refactor-codebase
Incrementally refactor and rearchitect a codebase toward a scalable structure using a phased plan. Use when the user wants to restructure code, improve architecture, reduce coupling, reorganize modules, or migrate toward a cleaner design without breaking the working system.
16code-graph
Builds and maintains a `.claude/codegraph.md` index of a codebase — a structured map of every module with purpose, key exports, and dependencies — so the agent can navigate any repo by reading one file instead of scanning dozens. Use when starting work on an unfamiliar codebase, when asked to index a repo, when context costs are high from repeated scans, or at the start of any task that will touch multiple files.
15find-code
Locate files and code using grep and shell scripts — never by AI scanning. Returns exact file paths and line numbers so the agent can jump directly to the location. Use whenever the agent needs to find a function, class, variable, import, file, or any pattern in the codebase. Code and file discovery must always be a tool call, never an AI guess.
15grill-me
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
14prd-to-plan
Turn a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in ./plans/. Use when user wants to break down a PRD, create an implementation plan, plan phases from a PRD, or mentions "tracer bullets".
14write-a-prd
Create a PRD through user interview, codebase exploration, and module design, then submit as a GitHub issue. Use when user wants to write a PRD, create a product requirements document, or plan a new feature.
14