egullickson/motovaultpro
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: Scheduled Maintenance feature complete

Browse Source
This commit is contained in:
Eric Gullickson
2025-12-22 14:12:33 -06:00
parent c017b8816f
commit 91b4534e76
44 changed files with 2740 additions and 117 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
docs/PROMPTS.md
View File

@@ -1,11 +1,25 @@
*** 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 implementing the "User Management" feature of this web application.
- You will be enhancing the maintenance record feature.
- Make no assumptions.
- Ask clarifying questions.
- Ultrathink
@@ -13,13 +27,11 @@ You are a senior software engineer specializsing in NodeJS, Typescript, front en
*** 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 currently is no user management system in this application.
- We need to do basic CRUD operations on user accounts
- We need to set the groundwork for a tiered paid system in the future. Start with four types of users.
- 1. Free 2. Pro 3. Enterprise 4. Administrator
- 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 look for any gaps in user account management.
- Research this code base and ask iterative questions to compile a complete plan.