53 lines
2.2 KiB
Markdown
53 lines
2.2 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 ***
|
|
- You will be enhancing the maintenance record feature.
|
|
- 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.
|
|
- There is a basic maintenance record system implemented.
|
|
- We need to implement schedule maintenance records with notifications tied into the existing notification system.
|
|
|
|
*** 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. |