docs(claude): add new command markdown files and reorder settings.json keys

claude/commands/grill.md

@@ -0,0 +1,3 @@
+Interview me relentlessly about every aspect of this plan util we reach a shared understanding.
+
+Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each decision, ask me to explain the rationale behind it, and challenge me to justify it with evidence or reasoning.

claude/commands/study-expand.md

@@ -0,0 +1 @@
+Read the file called plan.md. This is a study plan for a topic. For every point of this plan, create a new file in the same directory that goes into more detail about the specific point. It should also contain a list of resources to understand the point.

claude/commands/study.md

@@ -0,0 +1,7 @@
+Create a study plan in a file called plan.md. The plan should contain structured information about the topic. Separate the plan from introduction to expert level. The plan should be divided into concrete iterative items that can be completed in a reasonable amount of time. Each item should have a clear goal and a list of resources to understand the subject.
+
+Search online through resources to make sure you have a good understanding of the topic and can create a comprehensive plan.
+
+The plan is for the following topic:
+
+$1

claude/commands/terminology.md

@@ -0,0 +1,25 @@
+Extract the terminology of the codebase and create a file named `terminology.md` that defines the key terms and concepts used in the codebase. This file should include clear definitions and explanations for each term, as well as any relevant examples or context to help users understand how the terms are used within the codebase.
+
+Example:
+
+```markdown
+# Terminology
+
+## Key Terms and Concepts
+
+### 1. **Command**
+
+A command is an instruction that can be executed by the system. It typically consists of a name and a set of parameters or arguments that specify the details of the action to be performed. Commands are used to trigger specific functions or operations within the codebase.
+
+### 2. **Customer**
+
+A customer is an individual or entity that interacts with the system to receive services or products. In the context of the codebase, a customer may have specific attributes such as name, contact information, and purchase history.
+
+### 3. **Contact**
+
+A contact refers to the information related to an individual or entity that can be used for communication purposes. This may include email addresses, phone numbers, and physical addresses. A customer may have multiple contacts associated with them.
+
+### 4. **Interaction**
+
+An interaction is any form of communication or engagement between the customer and the system. This can include actions such as making a purchase, sending a message, or receiving a notification. Interactions are often logged for tracking and analysis purposes.
+```

claude/commands/vibes.md

@@ -0,0 +1 @@
+Read the .vibes folder to get context of the current project.

claude/settings.json

@@ -13,6 +13,6 @@
       }
     }
   },
-  "voiceEnabled": true,
-  "skipDangerousModePermissionPrompt": true
+  "skipDangerousModePermissionPrompt": true,
+  "voiceEnabled": true
 }