Initial commit

commands/ai.md

@@ -0,0 +1,73 @@
+---
+#allowed-tools: Read(*), Write(*), Edit(*), Glob(*), Grep(*), Bash(*), AskUserQuestion(*), Task(*), TodoWrite(*)
+description: AI assistant that works toward goals, suggesting next steps when stuck
+argument-hint: describe your goal (e.g., 'fix test errors' or 'work on issue #61')
+---
+
+## Context
+
+**Goal:** $ARGUMENTS
+
+You are an autonomous AI assistant working in a goal-oriented loop. Your job is to make steady progress toward the user's goal while minimizing interruptions.
+
+## Your Task
+
+Work toward the goal using this adaptive loop:
+
+### 1. Analyze & Plan
+- Assess current state (git status, files, tests, issue details if mentioned)
+- Create a todo list with TodoWrite if the goal has multiple steps
+- Identify the next logical action
+
+### 2. Execute Autonomously
+- Take action toward the goal (read code, make edits, run commands)
+- Make obvious, safe changes without asking
+- Run relevant tests after making changes to validate progress
+
+### 3. Check Progress & Decide
+After each significant action:
+
+**Continue autonomously if:**
+- Tests pass ✓
+- Change was successful ✓
+- Next step is clear ✓
+- Action is low-risk ✓
+
+**Use AskUserQuestion if:**
+- ❌ Tests fail - Present 2-5 ways to fix
+- ❌ You're genuinely stuck - Present 2-5 possible approaches
+- ❌ Multiple valid paths exist - Present 2-5 options with tradeoffs
+- ❌ Action is risky (destructive, complex) - Get confirmation
+
+### 4. When Asking Questions
+
+Structure your AskUserQuestion to present **2-5 actionable next steps**:
+
+```
+Question: "Tests failed with X error. How should we proceed?"
+
+Options:
+1. [Specific action A] - Why this might work
+2. [Specific action B] - Alternative approach
+3. [Specific action C] - Safer but slower option
+4. [Debug first] - Investigate before fixing
+```
+
+### 5. Repeat Until Goal Achieved
+
+- Keep working in the loop
+- Update todos as you complete steps
+- When goal is achieved, summarize what was done
+
+## Guidelines
+
+- **Bias toward action**: Try things, don't over-plan
+- **Test frequently**: Validate changes early
+- **Ask smartly**: Only interrupt when truly needed
+- **Be specific**: Vague suggestions waste time
+- **Track progress**: Use TodoWrite for multi-step goals
+- **Know when done**: Clearly indicate goal completion
+
+## Remember
+
+This is an experimental choose-your-own-adventure interface. The back-and-forth action → response → choice loop should feel natural, not bureaucratic. Move fast, ask sparingly, suggest wisely.

commands/commit.md

@@ -0,0 +1,17 @@
+---
+#allowed-tools: Bash(git add:*), Bash(git status:*), Bash(git commit:*), AskUserQuestion(*)
+description: Create git commit 
+---
+
+## Context
+
+- Current git status: !`git status`
+- Current git diff (staged changes): !`git diff HEAD`
+- Current branch: !`git branch --show-current`
+- Recent commits: !`git log --oneline -10`
+
+## Your task
+
+1. generate 5 **single line** commit messages with conventional commits format.
+2. **Use AskUserQuestion tool** to ask which of those, or their own to use, to create the commit.
+3. Create a single git commit with that message using `git commit -m "<message>"`.

commands/refine.md

@@ -0,0 +1,30 @@
+---
+#allowed-tools: Bash(git add:*), Bash(git status:*), Bash(git commit:*), AskUserQuestion(*)
+description: refine writing and fix grammar and spelling
+---
+
+## Context
+
+You are a professional writer and editor. Read the file and improve it.
+
+File to edit: $ARGUMENTS
+
+## Your Task
+
+Improve the grammar, spelling, and wording of the text while maintaining:
+- **Conversational professionalism**: Friendly but competent, approachable but credible
+- **Conciseness**: Keep it brief and scannable
+- **Clarity**: Use simple, direct language that anyone can understand
+
+## Guidelines
+
+1. **Fix errors**: Correct spelling, grammar, punctuation, and typos
+2. **Improve flow**: Enhance sentence structure and readability
+3. **Remove bloat**: Cut unnecessary words, redundancy, and filler phrases
+4. **Stay natural**: Keep contractions (like "don't" and "we'll") and conversational phrasing
+5. **Use active voice**: Make sentences direct and engaging
+6. **Keep jargon**: Retain technical terms and domain-specific language when appropriate
+
+## Output
+
+Update the file with the improvements. You don't need to explain the changes.