85 lines
4.0 KiB
Markdown
85 lines
4.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 extending the "Documents" feature to include manuals.
|
|
|
|
*** 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.
|
|
- You need to extend the Documents feature to include a third "Document Type"
|
|
- Right now the document has two types. Insurance and Registration
|
|
- The third type will be called "Manual"
|
|
- This document will just have the uploaded file and a notes field and Title field
|
|
- When implementing this we need to play for the future feature of scanning the document for maintenance schedules
|
|
- Add a toggle for this scanning. Label it "Scan for Maintenance Schedule"
|
|
- Do not implement this feature at this time but put the toggle in the interface and the backend changes to facility this workflow.
|
|
|
|
*** 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 ***
|
|
- You need to update the secrets scripts to include the newly added Resend email notification API key.
|
|
- Make no assumptions.
|
|
- Ask clarifying questions.
|
|
- Ultrathink
|
|
|
|
*** CONTEXT ***
|
|
- The secrets architecture is based of a future state of being deployed into k8s. Right now it's in docker compose with files that are copied in via the pipeline.
|
|
|
|
*** ACTION - CHANGES TO IMPLEMENT ***
|
|
- Replicate the same secrets process that's implemented with the Google API and Auth0 API keys.
|
|
|
|
|
|
|
|
*** 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 |