@wbern/claude-instructions 1.8.0 → 1.9.0

package/downloads/with-beads/ask.md

@@ -1,6 +1,5 @@
 ---
-allowed-tools: mcp__github__create_pull_request, mcp__github__update_pull_request, Bash(git status:*), Bash(git log:*), Bash(git push:*), Bash(git branch:*)
-description: Request team review and approval - for complex changes needing discussion (OK fine, traditional PRs still have their place - Cursor)
+description: Request team review and approval - for complex changes needing discussion
 argument-hint: [optional-pr-title-and-description]
 ---
 
@@ -18,8 +17,6 @@ Beads is available for task tracking. Use `mcp__beads__*` tools to manage issues
 
 **Ship/Show/Ask Pattern - ASK**
 
-> 💭 **Cursor says**: Fine, SOME things still need traditional PRs. But be intentional about it.
-
 Ask is for complex changes that need team discussion and approval. Examples:
 
 - Breaking API changes

package/downloads/with-beads/beepboop.md

@@ -1,5 +1,4 @@
 ---
-allowed-tools: Read, Grep, Glob
 description: Communicate AI-generated content with transparent attribution
 argument-hint: <task-description>
 ---

package/downloads/with-beads/busycommit.md

@@ -1,5 +1,4 @@
 ---
-allowed-tools: Bash(pnpm test:*), Bash(pnpm lint:*)
 description: Create multiple atomic git commits, one logical change at a time
 argument-hint: [optional-commit-description]
 ---

package/downloads/with-beads/commands-metadata.json

@@ -1,96 +1,124 @@
 {
   "add-command.md": {
     "description": "Guide for creating new slash commands",
+    "hint": "Create command",
     "category": "Utilities",
     "order": 3
   },
   "ask.md": {
-    "description": "Request team review and approval - for complex changes needing discussion (OK fine, traditional PRs still have their place - Cursor)",
-    "category": "Workflow",
-    "order": 4
+    "description": "Request team review and approval - for complex changes needing discussion",
+    "hint": "Request review",
+    "category": "Ship / Show / Ask",
+    "order": 3,
+    "selectedByDefault": false
   },
   "beepboop.md": {
     "description": "Communicate AI-generated content with transparent attribution",
+    "hint": "AI attribution",
     "category": "Utilities",
     "order": 2
   },
   "busycommit.md": {
     "description": "Create multiple atomic git commits, one logical change at a time",
+    "hint": "Atomic commits",
     "category": "Workflow",
     "order": 2
   },
   "commit.md": {
     "description": "Create a git commit following project standards",
+    "hint": "Git commit",
     "category": "Workflow",
     "order": 1
   },
   "cycle.md": {
     "description": "Execute complete TDD cycle - Red, Green, and Refactor phases in sequence",
-    "category": "TDD Cycle",
+    "hint": "Full TDD cycle",
+    "category": "Test-Driven Development",
     "order": 5
   },
   "gap.md": {
     "description": "Analyze conversation context for unaddressed items and gaps",
+    "hint": "Find gaps",
     "category": "Workflow",
     "order": 11
   },
   "green.md": {
     "description": "Execute TDD Green Phase - write minimal implementation to pass the failing test",
-    "category": "TDD Cycle",
+    "hint": "Make it pass",
+    "category": "Test-Driven Development",
     "order": 3
   },
   "issue.md": {
     "description": "Analyze GitHub issue and create TDD implementation plan",
+    "hint": "Analyze issue",
     "category": "Planning",
     "order": 1
   },
   "plan.md": {
     "description": "Create implementation plan from feature/requirement with PRD-style discovery and TDD acceptance criteria",
+    "hint": "Plan feature",
     "category": "Planning",
     "order": 2
   },
+  "pr.md": {
+    "description": "Creates a pull request using GitHub MCP",
+    "hint": "Create PR",
+    "category": "Workflow",
+    "order": 5
+  },
   "red.md": {
     "description": "Execute TDD Red Phase - write ONE failing test",
-    "category": "TDD Cycle",
+    "hint": "Failing test",
+    "category": "Test-Driven Development",
     "order": 2
   },
   "refactor.md": {
     "description": "Execute TDD Refactor Phase - improve code structure while keeping tests green",
-    "category": "TDD Cycle",
+    "hint": "Clean up code",
+    "category": "Test-Driven Development",
     "order": 4
   },
   "ship.md": {
-    "description": "Ship code directly to main - for small, obvious changes that don't need review (Cursor's modern alternative to PRs)",
-    "category": "Workflow",
-    "order": 2
+    "description": "Ship code directly to main - for small, obvious changes that don't need review",
+    "hint": "Direct to main",
+    "category": "Ship / Show / Ask",
+    "order": 1,
+    "selectedByDefault": false
   },
   "show.md": {
-    "description": "Show code to team with auto-merge - for changes that should be visible but don't need approval (Cursor's modern workflow)",
-    "category": "Workflow",
-    "order": 3
+    "description": "Show code to team with auto-merge - for changes that should be visible but don't need approval",
+    "hint": "Auto-merge PR",
+    "category": "Ship / Show / Ask",
+    "order": 2,
+    "selectedByDefault": false
   },
   "spike.md": {
     "description": "Execute TDD Spike Phase - exploratory coding to understand problem space before TDD",
-    "category": "TDD Cycle",
+    "hint": "Explore first",
+    "category": "Test-Driven Development",
     "order": 1
   },
   "summarize.md": {
     "description": "Summarize conversation progress and next steps",
+    "hint": "Summarize chat",
     "category": "Workflow",
     "order": 10
   },
   "tdd.md": {
     "description": "Remind agent about TDD approach and continue conversation",
-    "category": "Utilities",
+    "hint": "TDD reminder",
+    "category": "Test-Driven Development",
     "order": 1
   },
   "worktree-add.md": {
     "description": "Add a new git worktree from branch name or GitHub issue URL, copy settings, install deps, and open in current IDE",
+    "hint": "Add worktree",
     "category": "Worktree Management",
     "order": 1
   },
   "worktree-cleanup.md": {
     "description": "Clean up merged worktrees by verifying PR/issue status, consolidating settings, and removing stale worktrees",
+    "hint": "Cleanup worktree",
     "category": "Worktree Management",
     "order": 2
   }

package/downloads/with-beads/commit.md

@@ -1,5 +1,4 @@
 ---
-allowed-tools: Bash(pnpm test:*), Bash(pnpm lint:*)
 description: Create a git commit following project standards
 argument-hint: [optional-commit-description]
 ---

package/downloads/with-beads/cycle.md

@@ -1,5 +1,4 @@
 ---
-allowed-tools: Read, Glob, Grep, Bash(pnpm test:*)
 description: Execute complete TDD cycle - Red, Green, and Refactor phases in sequence
 argument-hint: <feature or requirement description>
 ---

package/downloads/with-beads/green.md

@@ -1,5 +1,4 @@
 ---
-allowed-tools: Read, Glob, Grep, Bash(pnpm test:*)
 description: Execute TDD Green Phase - write minimal implementation to pass the failing test
 argument-hint: <implementation description>
 ---

package/downloads/with-beads/issue.md

@@ -1,5 +1,4 @@
 ---
-allowed-tools: mcp__github__issue_read, mcp__github__get_issue, Task
 description: Analyze GitHub issue and create TDD implementation plan
 argument-hint: [optional-issue-number]
 ---

package/downloads/with-beads/plan.md

@@ -1,5 +1,4 @@
 ---
-allowed-tools: Read, Glob, Grep, Task, AskUserQuestion, mcp__github__issue_read, mcp__github__search_issues
 description: Create implementation plan from feature/requirement with PRD-style discovery and TDD acceptance criteria
 argument-hint: <feature/requirement description or GitHub issue URL/number>
 ---

package/downloads/with-beads/pr.md

@@ -0,0 +1,82 @@
+---
+description: Creates a pull request using GitHub MCP
+argument-hint: [optional-pr-title-and-description]
+---
+
+# Create Pull Request
+
+## General Guidelines
+
+### Output Style
+
+- **Never explicitly mention TDD** in code, comments, commits, PRs, or issues
+- Write natural, descriptive code without meta-commentary about the development process
+- The code should speak for itself - TDD is the process, not the product
+
+Beads is available for task tracking. Use `mcp__beads__*` tools to manage issues (the user interacts via `bd` commands).
+
+Create a pull request for the current branch using GitHub MCP tools.
+
+## Workflow
+
+Current branch status:
+!`git status`
+
+Recent commits:
+!`git log --oneline -5`
+
+Arguments: $ARGUMENTS
+
+**Process:**
+
+1. **Ensure Branch is Ready**:
+   !`git status`
+   - Commit all changes
+   - Push to remote: `git push origin [branch-name]`
+
+2. **Create PR**: Create a well-formatted pull request
+
+   Title: conventional commits format, like `feat(#123): add user authentication`
+
+   Description template:
+
+   ```markdown
+   <!--
+     Are there any relevant issues / PRs / mailing lists discussions?
+     Please reference them here.
+   -->
+
+   ## References
+
+   - [links to github issues referenced in commit messages]
+
+   ## Summary
+
+   [Brief description of changes]
+
+   ## Test Plan
+
+   - [ ] Tests pass
+   - [ ] Manual testing completed
+   ```
+
+3. **Set Base Branch**: Default to main unless specified otherwise
+
+4. **Link Issues**: Reference related issues found in commit messages
+
+## Use GitHub MCP Tools
+
+1. Check current branch and ensure it's pushed
+2. Create a well-formatted pull request with proper title and description
+3. Set the base branch (default: main)
+4. Include relevant issue references if found in commit messages
+
+### Beads Integration
+
+Use Beads MCP to:
+
+- Track work with `bd ready` to find next task
+- Create issues with `bd create "description"`
+- Track dependencies with `bd dep add`
+
+See <https://github.com/steveyegge/beads> for more information.

package/downloads/with-beads/red.md

@@ -1,5 +1,4 @@
 ---
-allowed-tools: Read, Glob, Grep, Bash(pnpm test:*)
 description: Execute TDD Red Phase - write ONE failing test
 argument-hint: [optional additional info]
 ---

package/downloads/with-beads/refactor.md

@@ -1,5 +1,4 @@
 ---
-allowed-tools: Read, Glob, Grep, Bash(pnpm test:*)
 description: Execute TDD Refactor Phase - improve code structure while keeping tests green
 argument-hint: <refactoring description>
 ---

package/downloads/with-beads/ship.md

@@ -1,6 +1,5 @@
 ---
-allowed-tools: Bash(git status:*), Bash(git log:*), Bash(git diff:*), Bash(git checkout:*), Bash(git pull:*), Bash(git merge:*), Bash(git push:*), Bash(git branch:*)
-description: Ship code directly to main - for small, obvious changes that don't need review (Cursor's modern alternative to PRs)
+description: Ship code directly to main - for small, obvious changes that don't need review
 argument-hint: [optional-commit-message]
 ---
 
@@ -18,8 +17,6 @@ Beads is available for task tracking. Use `mcp__beads__*` tools to manage issues
 
 **Ship/Show/Ask Pattern - SHIP**
 
-> 🎯 **Cursor says**: It's 2025! Not everything needs a PR. Ship small, obvious changes directly.
-
 Ship is for small, obvious changes that don't need code review. Examples:
 
 - Typo fixes

package/downloads/with-beads/show.md

@@ -1,6 +1,5 @@
 ---
-allowed-tools: mcp__github__create_pull_request, mcp__github__update_pull_request, Bash(git status:*), Bash(git log:*), Bash(git push:*), Bash(git branch:*)
-description: Show code to team with auto-merge - for changes that should be visible but don't need approval (Cursor's modern workflow)
+description: Show code to team with auto-merge - for changes that should be visible but don't need approval
 argument-hint: [optional-pr-title-and-description]
 ---
 
@@ -18,8 +17,6 @@ Beads is available for task tracking. Use `mcp__beads__*` tools to manage issues
 
 **Ship/Show/Ask Pattern - SHOW**
 
-> 🚀 **Cursor says**: Not every change needs a traditional review. Show your work, then merge.
-
 Show is for changes that teammates should see, but don't require approval. Examples:
 
 - Refactoring with test coverage

package/downloads/with-beads/spike.md

@@ -1,5 +1,4 @@
 ---
-allowed-tools: Read, Glob, Grep, Task
 description: Execute TDD Spike Phase - exploratory coding to understand problem space before TDD
 argument-hint: <exploration description>
 ---

package/downloads/with-beads/summarize.md

@@ -1,5 +1,4 @@
 ---
-allowed-tools: AskUserQuestion
 description: Summarize conversation progress and next steps
 argument-hint: [optional additional info]
 ---

package/downloads/with-beads/tdd.md

@@ -1,5 +1,4 @@
 ---
-allowed-tools: Read, Glob, Grep, Task
 description: Remind agent about TDD approach and continue conversation
 argument-hint: [optional-response-to-last-message]
 ---

package/downloads/with-beads/worktree-add.md

@@ -1,5 +1,4 @@
 ---
-allowed-tools: Bash(code-insiders:*), Bash(code:*), Bash(zed:*), Bash(cursor:*), Bash(which:*), Read, mcp__github__issue_read, mcp__ide__getDiagnostics, ListMcpResourcesTool
 description: Add a new git worktree from branch name or GitHub issue URL, copy settings, install deps, and open in current IDE
 argument-hint: <branch-name-or-github-issue-url> [optional-base-branch]
 ---

package/downloads/with-beads/worktree-cleanup.md

@@ -1,5 +1,4 @@
 ---
-allowed-tools: Read, mcp__mcp-jq__jq_query, mcp__mcp-jq__jq_query_file, mcp__github__search_pull_requests, mcp__github__pull_request_read, mcp__github__issue_read, mcp__github__issue_write, mcp__github__add_issue_comment, ListMcpResourcesTool
 description: Clean up merged worktrees by verifying PR/issue status, consolidating settings, and removing stale worktrees
 argument-hint: (no arguments)
 ---

package/downloads/without-beads/ask.md

@@ -1,6 +1,5 @@
 ---
-allowed-tools: mcp__github__create_pull_request, mcp__github__update_pull_request, Bash(git status:*), Bash(git log:*), Bash(git push:*), Bash(git branch:*)
-description: Request team review and approval - for complex changes needing discussion (OK fine, traditional PRs still have their place - Cursor)
+description: Request team review and approval - for complex changes needing discussion
 argument-hint: [optional-pr-title-and-description]
 ---
 
@@ -16,8 +15,6 @@ argument-hint: [optional-pr-title-and-description]
 
 **Ship/Show/Ask Pattern - ASK**
 
-> 💭 **Cursor says**: Fine, SOME things still need traditional PRs. But be intentional about it.
-
 Ask is for complex changes that need team discussion and approval. Examples:
 
 - Breaking API changes

package/downloads/without-beads/beepboop.md

@@ -1,5 +1,4 @@
 ---
-allowed-tools: Read, Grep, Glob
 description: Communicate AI-generated content with transparent attribution
 argument-hint: <task-description>
 ---

package/downloads/without-beads/busycommit.md

@@ -1,5 +1,4 @@
 ---
-allowed-tools: Bash(pnpm test:*), Bash(pnpm lint:*)
 description: Create multiple atomic git commits, one logical change at a time
 argument-hint: [optional-commit-description]
 ---

package/downloads/without-beads/commands-metadata.json

@@ -1,96 +1,124 @@
 {
   "add-command.md": {
     "description": "Guide for creating new slash commands",
+    "hint": "Create command",
     "category": "Utilities",
     "order": 3
   },
   "ask.md": {
-    "description": "Request team review and approval - for complex changes needing discussion (OK fine, traditional PRs still have their place - Cursor)",
-    "category": "Workflow",
-    "order": 4
+    "description": "Request team review and approval - for complex changes needing discussion",
+    "hint": "Request review",
+    "category": "Ship / Show / Ask",
+    "order": 3,
+    "selectedByDefault": false
   },
   "beepboop.md": {
     "description": "Communicate AI-generated content with transparent attribution",
+    "hint": "AI attribution",
     "category": "Utilities",
     "order": 2
   },
   "busycommit.md": {
     "description": "Create multiple atomic git commits, one logical change at a time",
+    "hint": "Atomic commits",
     "category": "Workflow",
     "order": 2
   },
   "commit.md": {
     "description": "Create a git commit following project standards",
+    "hint": "Git commit",
     "category": "Workflow",
     "order": 1
   },
   "cycle.md": {
     "description": "Execute complete TDD cycle - Red, Green, and Refactor phases in sequence",
-    "category": "TDD Cycle",
+    "hint": "Full TDD cycle",
+    "category": "Test-Driven Development",
     "order": 5
   },
   "gap.md": {
     "description": "Analyze conversation context for unaddressed items and gaps",
+    "hint": "Find gaps",
     "category": "Workflow",
     "order": 11
   },
   "green.md": {
     "description": "Execute TDD Green Phase - write minimal implementation to pass the failing test",
-    "category": "TDD Cycle",
+    "hint": "Make it pass",
+    "category": "Test-Driven Development",
     "order": 3
   },
   "issue.md": {
     "description": "Analyze GitHub issue and create TDD implementation plan",
+    "hint": "Analyze issue",
     "category": "Planning",
     "order": 1
   },
   "plan.md": {
     "description": "Create implementation plan from feature/requirement with PRD-style discovery and TDD acceptance criteria",
+    "hint": "Plan feature",
     "category": "Planning",
     "order": 2
   },
+  "pr.md": {
+    "description": "Creates a pull request using GitHub MCP",
+    "hint": "Create PR",
+    "category": "Workflow",
+    "order": 5
+  },
   "red.md": {
     "description": "Execute TDD Red Phase - write ONE failing test",
-    "category": "TDD Cycle",
+    "hint": "Failing test",
+    "category": "Test-Driven Development",
     "order": 2
   },
   "refactor.md": {
     "description": "Execute TDD Refactor Phase - improve code structure while keeping tests green",
-    "category": "TDD Cycle",
+    "hint": "Clean up code",
+    "category": "Test-Driven Development",
     "order": 4
   },
   "ship.md": {
-    "description": "Ship code directly to main - for small, obvious changes that don't need review (Cursor's modern alternative to PRs)",
-    "category": "Workflow",
-    "order": 2
+    "description": "Ship code directly to main - for small, obvious changes that don't need review",
+    "hint": "Direct to main",
+    "category": "Ship / Show / Ask",
+    "order": 1,
+    "selectedByDefault": false
   },
   "show.md": {
-    "description": "Show code to team with auto-merge - for changes that should be visible but don't need approval (Cursor's modern workflow)",
-    "category": "Workflow",
-    "order": 3
+    "description": "Show code to team with auto-merge - for changes that should be visible but don't need approval",
+    "hint": "Auto-merge PR",
+    "category": "Ship / Show / Ask",
+    "order": 2,
+    "selectedByDefault": false
   },
   "spike.md": {
     "description": "Execute TDD Spike Phase - exploratory coding to understand problem space before TDD",
-    "category": "TDD Cycle",
+    "hint": "Explore first",
+    "category": "Test-Driven Development",
     "order": 1
   },
   "summarize.md": {
     "description": "Summarize conversation progress and next steps",
+    "hint": "Summarize chat",
     "category": "Workflow",
     "order": 10
   },
   "tdd.md": {
     "description": "Remind agent about TDD approach and continue conversation",
-    "category": "Utilities",
+    "hint": "TDD reminder",
+    "category": "Test-Driven Development",
     "order": 1
   },
   "worktree-add.md": {
     "description": "Add a new git worktree from branch name or GitHub issue URL, copy settings, install deps, and open in current IDE",
+    "hint": "Add worktree",
     "category": "Worktree Management",
     "order": 1
   },
   "worktree-cleanup.md": {
     "description": "Clean up merged worktrees by verifying PR/issue status, consolidating settings, and removing stale worktrees",
+    "hint": "Cleanup worktree",
     "category": "Worktree Management",
     "order": 2
   }

package/downloads/without-beads/commit.md

@@ -1,5 +1,4 @@
 ---
-allowed-tools: Bash(pnpm test:*), Bash(pnpm lint:*)
 description: Create a git commit following project standards
 argument-hint: [optional-commit-description]
 ---

package/downloads/without-beads/cycle.md

@@ -1,5 +1,4 @@
 ---
-allowed-tools: Read, Glob, Grep, Bash(pnpm test:*)
 description: Execute complete TDD cycle - Red, Green, and Refactor phases in sequence
 argument-hint: <feature or requirement description>
 ---
@@ -16,10 +15,7 @@ $ARGUMENTS
 - Write natural, descriptive code without meta-commentary about the development process
 - The code should speak for itself - TDD is the process, not the product
 
-(If there was no info above, fallback to:
-
-1. Context of the conversation, if there's an immediate thing
-2. `bd ready` to see what to work on next and start from there)
+(If there was no info above, fallback to the context of the conversation)
 
 ## TDD Fundamentals
 

package/downloads/without-beads/green.md

@@ -1,5 +1,4 @@
 ---
-allowed-tools: Read, Glob, Grep, Bash(pnpm test:*)
 description: Execute TDD Green Phase - write minimal implementation to pass the failing test
 argument-hint: <implementation description>
 ---
@@ -16,10 +15,7 @@ $ARGUMENTS
 - Write natural, descriptive code without meta-commentary about the development process
 - The code should speak for itself - TDD is the process, not the product
 
-(If there was no info above, fallback to:
-
-1. Context of the conversation, if there's an immediate thing
-2. `bd ready` to see what to work on next and start from there)
+(If there was no info above, fallback to the context of the conversation)
 
 ## TDD Fundamentals
 

package/downloads/without-beads/issue.md

@@ -1,5 +1,4 @@
 ---
-allowed-tools: mcp__github__issue_read, mcp__github__get_issue, Task
 description: Analyze GitHub issue and create TDD implementation plan
 argument-hint: [optional-issue-number]
 ---

package/downloads/without-beads/plan.md

@@ -1,5 +1,4 @@
 ---
-allowed-tools: Read, Glob, Grep, Task, AskUserQuestion, mcp__github__issue_read, mcp__github__search_issues
 description: Create implementation plan from feature/requirement with PRD-style discovery and TDD acceptance criteria
 argument-hint: <feature/requirement description or GitHub issue URL/number>
 ---