Initial commit

commands/load-context.md

@@ -0,0 +1,9 @@
+# Load Context
+
+You will inspect the code under the directory $ARGUMENTS and load it into context. You MUST 
+focus on understand the the project structure, and key concepts. You will NOT write any code.
+Your goal is to build an understanding of the project so that you can effectively plan changes 
+and execute changes to it.
+
+### Important rules 
+Do not use subagents. You your self MUST inspect the code so that YOU understand it.

commands/read-session.md

@@ -0,0 +1,2 @@
+Read the /session.md file to get an understanding of the recent changes made to
+the project.

commands/review-implementation.md

@@ -0,0 +1,11 @@
+# Review Plan 
+
+You will use `git` to review the current uncommitted changes. You will assess how well these changes achieve the plan found in the $ARGUMENTS file. You want to look for the following:
+
+1. Does the code match the plan?
+2. Is the code clean and maintainable?
+3. Are there tests for the code? 
+4. Are there extra changes that are not part of the plan?
+
+After your review produce a report for the user to let them know about any issues 
+they should be aware of. Keep this report Short. Only provide a high level overview, and point out any issues. Don't bother listing all the things that have been done correctly. The user may prompt you to fix any issues you find.

commands/run.md

@@ -0,0 +1,12 @@
+# Run Plan
+
+You will execute the plan laid out in the file $ARGUMENTS. You will follow the plan
+step by step. Once you've implemented the plan think critically to see if you achieved the goals laid out in the plan. If the plan appears wrong or something is unclear ask the user for clarification.
+
+# Review your code 
+
+After you've run through the plan. Use a subagent to review the code you wrote. Give the subagent the following prompt file ./.claude/commands/review-plan-implementation.md targeting the same plan file you just executed, i.e. $ARGUMENTS.
+
+# Fix Review Feedback
+
+After the review is complete, address any issues you found. Then go BACK to the review phase again, until there are no more issues to address.

commands/write-session.md

@@ -0,0 +1,34 @@
+# Session Recording Procedure
+
+1. The session info is stored in the /session.md file.
+2. The session is recorded in chronological order, append entries to the end of
+   the file.
+3. You will add your session summary to the `session.md` file at the end of the
+   file.
+4. After adding your session summary. You will TRIM the summary file, if the
+   following conditions are met:
+   - The summary file is more than 1000 lines long. When trimming, you will
+     remove the oldest entries until the file is less than 1000 lines long.
+
+# How to Record a Session
+
+Record a summary of the tasks you just performed to the `session.md`. This
+should be a high level summary to inform the user of the changes made. Include
+any relevant context or details that would help the user understand the
+modifications.
+
+# Summary Template
+
+The summary must follow this very simple template
+
+## <title> - <date>
+
+<summary>
+
+### For example:
+
+## Add new endpoint /help - 2023-10-05-10:00
+
+Updated the backend to include a new `/help` endpoint that provides assistance
+with common issues. This endpoint is now accessible via the main application
+interface.

commands/write.md

@@ -0,0 +1,13 @@
+# Write Plan
+
+You will write a detailed plan on how to achieve the request found in the file $ARGUMENTS 
+Write this plan in to a `/plan/<request name>-plan.md` file.
+
+#### Planing Process 
+1. Read the request file in its entirety.
+2. Research the existing code, looking for related files. 
+3. Research the web for any relevant information and documentation on libraries and APIs that you will need to use.
+4. Devise a plan in great detail. 
+4.1 Create a detailed step by step task list that outlines the work to be done.
+4.2 List the files to modify, create, and delete giving an overview of the changes.
+4.3 Describe the main changes to make, and the task to be achieved.