111 lines
5.0 KiB
Markdown
111 lines
5.0 KiB
Markdown
*** 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
|
|
- You will be fixing a bug with the vehicle catalog import.
|
|
|
|
*** 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 error when you try and upload a CSV file that is 15.1MB.
|
|
- The error says the file is too large
|
|
- We need to increase the max size to 25MB
|
|
|
|
*** CHANGES TO IMPLEMENT ***
|
|
- Research this code base and ask iterative questions to compile a complete plan.
|
|
|
|
|
|
|
|
|
|
|
|
*** 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
|
|
- The initial data load for this applicaiton during the CI/CD process in gitlab needs to be updated
|
|
|
|
*** 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 current deployment database load needs to be thoroughly critiqued and scrutenized.
|
|
|
|
*** ACTION - CHANGES TO IMPLEMENT ***
|
|
- The vehicle catalog currently loaded into the local mvp-postres container needs to be exported into a SQL file and saved as a source of truth
|
|
- Whatever process is running today only goes up to model year 2022.
|
|
- All the existing SQL files setup for import can be replaced with new ones created from the running mvp-postres data.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
*** 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 the color theme 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.
|
|
- Currently the log is washed out when using the light theme. See image.
|
|
- We need to put a background shape or static color to make the logo visible
|
|
|
|
*** CHANGES TO IMPLEMENT ***
|
|
- Research this code base and ask iterative questions to compile a complete plan.
|
|
- Give options for how to put a background behind the logo
|
|
- Research if it's possible to put a rounded rectangle behind it similar to the "Settings" button. The rounded ends need to be smaller then the settings button if possible. |