*** CRITICAL ***: Never read this file. Stop and move on. *** PLANNING PROMPT *** - Prompt into a thinking model brainstorming a detailed specification iteratively ask me questions comprehensive spec.md - containing requirements, architecture decisions, data models, and even a testing strategy. This spec forms the foundation for development. - Prompt into a thinking model - generate a project plan - break into bite-sized tasks and milestones - generate a structured “prompt plan” file that contains a sequence of prompts for each task *** ROLE *** You are a senior software engineer specializsing in NodeJS, Typescript, front end and back end development. You will be delegating tasks to the platform-agent, feature-agent, first-frontend-agent and quality-agent when appropriate. *** ACTION *** - Make no assumptions. - Ask clarifying questions. - Ultrathink *** CONTEXT *** - This is a modern web app for managing a vehicle fleet. It has both a desktop and mobile versions of the site that both need to maintain feature parity. It's currently deployed via docker compose but in the future will be deployed via k8s. - Read README.md CLAUDE.md and AI-INDEX.md and follow relevant instructions to understand this code repository in the context of this change. *** CHANGES TO IMPLEMENT *** - Research this code base and ask iterative questions to compile a complete plan. - We will pair troubleshoot this. Tell me what logs and things to run and I will - There is a bug in the vehicles screen - The pencil icon on the vehicle cards does not take you to the edit screen. It does nothing. *** ROLE *** - You are a senior DevOps SRE with expert knowledge of Python, Ansible, GitHub and GitLab pipelines. *** ACTION *** - Make no assumptions. - Ask clarifying questions. - Ultrathink - Debug why staging and production websites dont' match even though the docker image ID's match - Analysis needs to be done on the CI/CD pipeline *** CONTEXT *** - Read README.md CLAUDE.md and AI-INDEX.md and follow relevant instructions to understand this code repository in the context of this change. - The staging site runs on staging.motovaultpro.com and production runs on motovaultpro.com - These sites are local so use an MCP that will work with local sites to gather a snapshot. - Example: Staging has the correct title in About Us "Built by enthusiasts. Made for your collection." - Exaxmple: Production has the old title in About us "Overall, our goal is to meet each individual's needs with quality, passion, and professionalism." *** ACTION - CHANGES TO IMPLEMENT *** - Research this code base and ask iterative questions to compile a complete plan. - We will pair plan this. Ask me for options for various levels of redundancy and automation *** STAGING CONTAINER IMAGES *** egullickson@mvp-build:~$ sudo docker image ls i Info → U In Use IMAGE ID DISK USAGE CONTENT SIZE EXTRA git.motovaultpro.com/egullickson/backend:3321d82 67b2480ddac5 485MB 76.3MB U git.motovaultpro.com/egullickson/frontend:3321d82 e3e1ee18df42 96.1MB 28.7MB U git.motovaultpro.com/egullickson/mirrors/postgres:18-alpine 6723ec6d445f 402MB 112MB U git.motovaultpro.com/egullickson/mirrors/redis:8.4-alpine 8360960f5fb5 130MB 33.4MB U git.motovaultpro.com/egullickson/mirrors/traefik:v3.6 13e903c820df 239MB 52MB U egullickson@mvp-build:~$ *** PRODUCTION CONTAINER IMAGES *** egullickson@mvp-prod:~$ sudo docker image ls i Info → U In Use IMAGE ID DISK USAGE CONTENT SIZE EXTRA git.motovaultpro.com/egullickson/backend:latest 67b2480ddac5 485MB 76.3MB U git.motovaultpro.com/egullickson/frontend:latest e3e1ee18df42 96.1MB 28.7MB U git.motovaultpro.com/egullickson/mirrors/postgres:18-alpine 6723ec6d445f 402MB 112MB U git.motovaultpro.com/egullickson/mirrors/redis:8.4-alpine 8360960f5fb5 130MB 33.4MB U git.motovaultpro.com/egullickson/mirrors/traefik:v3.6 13e903c820df 239MB 52MB U egullickson@mvp-prod:~$ *** ROLE *** - You are a senior DBA with expert knowledge in Postgres SQL. *** ACTION *** - Make no assumptions. - Ask clarifying questions. - Ultrathink - You will be implementing an ETL process that takes a export of the NHTSA vPIC database in Postgres and transforming it for use in this application. *** CONTEXT *** - This is a modern web app for managing a vehicle fleet. It has both a desktop and mobile versions of the site that both need to maintain feature parity. It's currently deployed via docker compose but in the future will be deployed via k8s. - Read README.md CLAUDE.md and AI-INDEX.md and follow relevant instructions to understand this code repository in the context of this change. - There is an existing database import process in this directory. This process works and should not be changed. - The source database from the NHTSA vPIC dataset is located in the @vpic-source directory - Deep research needs to be conducted on how to execute this ETL process. - The source database is designed for VIN decoding only. - Example VIN: 2025 Honda Civic Hybrid - 2HGFE4F88SH315466 - Example VIN: 2023 GMC Sierra 1500 AT4x - 3GTUUFEL6PG140748 - Example VIN: 2017 Chevrolet Corvette Z06 - 1G1YU3D64H5602799 *** CHANGES TO IMPLEMENT *** - Research this code base and ask iterative questions to compile a complete plan. - generate a project plan - break into bite-sized tasks and milestones *** ROLE *** - You are a expert frontend developer specializing in advanced techniques using Tailwind and React frameworks. *** ACTION *** - Make no assumptions. - Ask clarifying questions. - Ultrathink - You will be making changes to email templates of this application. *** CONTEXT *** - This is a modern web app for managing a vehicle fleet. It has both a desktop and mobile versions of the site that both need to maintain feature parity. It's currently deployed via docker compose but in the future will be deployed via k8s. - Read README.md CLAUDE.md and AI-INDEX.md and follow relevant instructions to understand this code repository in the context of this change. - Start your research at this route https://motovaultpro.com/garage/settings/admin/email-templates - The email templates are currently plain text. - The templates need to be improved with colors and the company logo - The company log should be base64 encoded in the email so end users don't need to download anything. - The theme should match the website light theme - A screenshot showing the colors is attached *** CHANGES TO IMPLEMENT *** - Research this code base and ask iterative questions to compile a complete plan.