@wbern/claude-instructions 1.21.0 → 2.0.0

package/downloads/with-beads/pr.md

@@ -1,82 +0,0 @@
----
-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,103 +0,0 @@
----
-description: Execute TDD Red Phase - write ONE failing test
-argument-hint: [optional additional info]
----
-
-RED PHASE! Apply the below to the info given by user input here:
-
-$ARGUMENTS
-
-## 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).
-
-(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)
-
-## TDD Fundamentals
-
-### The TDD Cycle
-
-The foundation of TDD is the Red-Green-Refactor cycle:
-
-1. **Red Phase**: Write ONE failing test that describes desired behavior
-
-   - The test must fail for the RIGHT reason (not syntax/import errors)
-   - Only one test at a time - this is critical for TDD discipline
-     - Exception: For browser-level tests or expensive setup (e.g., Storybook `*.stories.tsx`), group multiple assertions within a single test block to avoid redundant setup - but only when adding assertions to an existing interaction flow. If new user interactions are required, still create a new test. Split files by category if they exceed ~1000 lines.
-   - **Adding a single test to a test file is ALWAYS allowed** - no prior test output needed
-   - Starting TDD for a new feature is always valid, even if test output shows unrelated work
-   - For DOM-based tests, use `data-testid` attributes to select elements rather than CSS classes, tag names, or text content
-   - Avoid hard-coded timeouts both in form of sleep() or timeout: 5000 etc; use proper async patterns (`waitFor`, `findBy*`, event-based sync) instead and rely on global test configs for timeout settings
-
-2. **Green Phase**: Write MINIMAL code to make the test pass
-
-   - Implement only what's needed for the current failing test
-   - No anticipatory coding or extra features
-   - Address the specific failure message
-
-3. **Refactor Phase**: Improve code structure while keeping tests green
-   - Only allowed when relevant tests are passing
-   - Requires proof that tests have been run and are green
-   - Applies to BOTH implementation and test code
-   - No refactoring with failing tests - fix them first
-
-### Core Violations
-
-1. **Multiple Test Addition**
-
-   - Adding more than one new test at once
-   - Exception: Initial test file setup or extracting shared test utilities
-
-2. **Over-Implementation**
-
-   - Code that exceeds what's needed to pass the current failing test
-   - Adding untested features, methods, or error handling
-   - Implementing multiple methods when test only requires one
-
-3. **Premature Implementation**
-   - Adding implementation before a test exists and fails properly
-   - Adding implementation without running the test first
-   - Refactoring when tests haven't been run or are failing
-
-### Critical Principle: Incremental Development
-
-Each step in TDD should address ONE specific issue:
-
-- Test fails "not defined" → Create empty stub/class only
-- Test fails "not a function" → Add method stub only
-- Test fails with assertion → Implement minimal logic only
-
-### Optional Pre-Phase: Spike Phase
-
-In rare cases where the problem space, interface, or expected behavior is unclear, a **Spike Phase** may be used **before the Red Phase**.
-This phase is **not part of the regular TDD workflow** and must only be applied under exceptional circumstances.
-
-- The goal of a Spike is **exploration and learning**, not implementation.
-- The code written during a Spike is **disposable** and **must not** be merged or reused directly.
-- Once sufficient understanding is achieved, all spike code is discarded, and normal TDD resumes starting from the **Red Phase**.
-- A Spike is justified only when it is impossible to define a meaningful failing test due to technical uncertainty or unknown system behavior.
-
-### General Information
-
-- Sometimes the test output shows as no tests have been run when a new test is failing due to a missing import or constructor. In such cases, allow the agent to create simple stubs. Ask them if they forgot to create a stub if they are stuck.
-- It is never allowed to introduce new logic without evidence of relevant failing tests. However, stubs and simple implementation to make imports and test infrastructure work is fine.
-- In the refactor phase, it is perfectly fine to refactor both test and implementation code. That said, completely new functionality is not allowed. Types, clean up, abstractions, and helpers are allowed as long as they do not introduce new behavior.
-- Adding types, interfaces, or a constant in order to replace magic values is perfectly fine during refactoring.
-- Provide the agent with helpful directions so that they do not get stuck when blocking them.
-
-### Test Structure (AAA Pattern)
-
-Structure each test with clear phases:
-
-- **Arrange**: Set up test data and preconditions (keep minimal)
-- **Act**: Execute the single action being tested
-- **Assert**: Verify the expected outcome with specific assertions

package/downloads/with-beads/refactor.md

@@ -1,105 +0,0 @@
----
-description: Execute TDD Refactor Phase - improve code structure while keeping tests green
-argument-hint: <refactoring description>
----
-
-Apply this document (specifically the Refactor phase), to the info given by user input here: $ARGUMENTS
-
-## 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).
-
-(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)
-
-## TDD Fundamentals
-
-### The TDD Cycle
-
-The foundation of TDD is the Red-Green-Refactor cycle:
-
-1. **Red Phase**: Write ONE failing test that describes desired behavior
-
-   - The test must fail for the RIGHT reason (not syntax/import errors)
-   - Only one test at a time - this is critical for TDD discipline
-     - Exception: For browser-level tests or expensive setup (e.g., Storybook `*.stories.tsx`), group multiple assertions within a single test block to avoid redundant setup - but only when adding assertions to an existing interaction flow. If new user interactions are required, still create a new test. Split files by category if they exceed ~1000 lines.
-   - **Adding a single test to a test file is ALWAYS allowed** - no prior test output needed
-   - Starting TDD for a new feature is always valid, even if test output shows unrelated work
-   - For DOM-based tests, use `data-testid` attributes to select elements rather than CSS classes, tag names, or text content
-   - Avoid hard-coded timeouts both in form of sleep() or timeout: 5000 etc; use proper async patterns (`waitFor`, `findBy*`, event-based sync) instead and rely on global test configs for timeout settings
-
-2. **Green Phase**: Write MINIMAL code to make the test pass
-
-   - Implement only what's needed for the current failing test
-   - No anticipatory coding or extra features
-   - Address the specific failure message
-
-3. **Refactor Phase**: Improve code structure while keeping tests green
-   - Only allowed when relevant tests are passing
-   - Requires proof that tests have been run and are green
-   - Applies to BOTH implementation and test code
-   - No refactoring with failing tests - fix them first
-
-### Core Violations
-
-1. **Multiple Test Addition**
-
-   - Adding more than one new test at once
-   - Exception: Initial test file setup or extracting shared test utilities
-
-2. **Over-Implementation**
-
-   - Code that exceeds what's needed to pass the current failing test
-   - Adding untested features, methods, or error handling
-   - Implementing multiple methods when test only requires one
-
-3. **Premature Implementation**
-   - Adding implementation before a test exists and fails properly
-   - Adding implementation without running the test first
-   - Refactoring when tests haven't been run or are failing
-
-### Critical Principle: Incremental Development
-
-Each step in TDD should address ONE specific issue:
-
-- Test fails "not defined" → Create empty stub/class only
-- Test fails "not a function" → Add method stub only
-- Test fails with assertion → Implement minimal logic only
-
-### Optional Pre-Phase: Spike Phase
-
-In rare cases where the problem space, interface, or expected behavior is unclear, a **Spike Phase** may be used **before the Red Phase**.
-This phase is **not part of the regular TDD workflow** and must only be applied under exceptional circumstances.
-
-- The goal of a Spike is **exploration and learning**, not implementation.
-- The code written during a Spike is **disposable** and **must not** be merged or reused directly.
-- Once sufficient understanding is achieved, all spike code is discarded, and normal TDD resumes starting from the **Red Phase**.
-- A Spike is justified only when it is impossible to define a meaningful failing test due to technical uncertainty or unknown system behavior.
-
-### General Information
-
-- Sometimes the test output shows as no tests have been run when a new test is failing due to a missing import or constructor. In such cases, allow the agent to create simple stubs. Ask them if they forgot to create a stub if they are stuck.
-- It is never allowed to introduce new logic without evidence of relevant failing tests. However, stubs and simple implementation to make imports and test infrastructure work is fine.
-- In the refactor phase, it is perfectly fine to refactor both test and implementation code. That said, completely new functionality is not allowed. Types, clean up, abstractions, and helpers are allowed as long as they do not introduce new behavior.
-- Adding types, interfaces, or a constant in order to replace magic values is perfectly fine during refactoring.
-- Provide the agent with helpful directions so that they do not get stuck when blocking them.
-
-### Watch for Brittle Tests
-
-When refactoring implementation, watch for **Peeping Tom** tests that:
-
-- Test private methods or internal state directly
-- Assert on implementation details rather than behavior
-- Break on any refactoring even when behavior is preserved
-
-If tests fail after a pure refactoring (no behavior change), consider whether the tests are testing implementation rather than behavior.
-
-1. **Consistency check** - Look for inconsistent patterns, naming conventions, or structure across the codebase

package/downloads/with-beads/ship.md

@@ -1,98 +0,0 @@
----
-description: Ship code directly to main - for small, obvious changes that don't need review
-argument-hint: [optional-commit-message]
----
-
-# Ship - Direct Merge to Main
-
-## 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).
-
-**Ship/Show/Ask Pattern - SHIP**
-
-Ship is for small, obvious changes that don't need code review. Examples:
-
-- Typo fixes
-- Formatting changes
-- Documentation updates
-- Obvious bug fixes
-- Dependency updates with passing tests
-
-## Prerequisites
-
-Before shipping directly to main:
-
-1. All tests must pass
-2. Linter must pass
-3. Changes must be small and low-risk
-4. CI must be green (if configured)
-
-## Workflow
-
-Current branch status:
-!`git status`
-
-Recent commits:
-!`git log --oneline -5`
-
-Arguments: $ARGUMENTS
-
-**Process:**
-
-1. **Verify Change Size**: Check git diff to ensure changes are small and focused
-   !`git diff --stat main`
-
-2. **Run Tests**: Ensure all tests pass
-   !`npm test` or !`yarn test` or appropriate test command for the project
-
-3. **Run Linter**: Ensure code quality checks pass
-   !`npm run lint` or !`yarn lint` or appropriate lint command (if available)
-
-4. **Safety Check**: Confirm with user that this is truly a ship-worthy change:
-   - Is this a small, obvious change?
-   - Do all tests pass?
-   - Is CI green?
-
-   If ANY of these are "no", suggest using `/show` or `/ask` instead.
-
-5. **Merge to Main**: If all checks pass and user confirms:
-
-   ```bash
-   git checkout main
-   git pull origin main
-   git merge --ff-only [feature-branch] || git merge [feature-branch]
-   git push origin main
-   ```
-
-6. **Cleanup**: Delete the feature branch
-
-   ```bash
-   git branch -d [feature-branch]
-   git push origin --delete [feature-branch]
-   ```
-
-7. **Notify**: Show summary of what was shipped
-
-## Safety Rails
-
-If tests fail, linter fails, or changes are large/complex, STOP and suggest:
-
-- Use `/show` for changes that should be seen but don't need approval
-- Use `/ask` (traditional PR) for complex changes needing discussion
-
-### 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/show.md

@@ -1,114 +0,0 @@
----
-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]
----
-
-# Show - Visible Merge with Optional Feedback
-
-## 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).
-
-**Ship/Show/Ask Pattern - SHOW**
-
-Show is for changes that teammates should see, but don't require approval. Examples:
-
-- Refactoring with test coverage
-- New features with comprehensive tests
-- Performance improvements
-- Non-breaking API changes
-
-## Prerequisites
-
-Before using show:
-
-1. All tests must pass
-2. Changes should have good test coverage
-3. Changes should be non-breaking or backward compatible
-4. CI must be green
-
-## Workflow
-
-Current branch status:
-!`git status`
-
-Recent commits:
-!`git log --oneline -5`
-
-Arguments: $ARGUMENTS
-
-**Process:**
-
-1. **Verify Quality**: Check that changes meet show criteria
-   - Run tests: !`npm test` or !`yarn test` or appropriate test command
-   - Check coverage is maintained or improved
-   - Verify no breaking changes
-
-2. **Create Show PR**: Create a PR that will auto-merge after a short window
-   - Title: conventional commits format, prefixed with `[SHOW]`
-   - Description: Clear explanation of what changed and why
-   - Add label: "show" or "auto-merge"
-   - Set auto-merge if GitHub setting allows
-
-3. **Configure Auto-Merge**:
-   - If GitHub Actions is configured, set to auto-merge after CI passes
-   - If not, provide instructions to merge after 1-2 hours of visibility
-   - Add notice that feedback is welcome but not required
-
-4. **PR Description Template**:
-
-   ```markdown
-   ## 🚀 Show - Auto-merging after CI
-
-   **This is a SHOW PR**: Changes are ready to merge but shared for visibility.
-   Feedback welcome but not required. Will auto-merge when CI passes.
-
-   <!--
-     References: [link to relevant issues]
-   -->
-
-   ### What changed
-
-   [Brief description]
-
-   ### Why
-
-   [Rationale for change]
-
-   ### Test coverage
-
-   - [ ] All tests pass
-   - [ ] Coverage maintained/improved
-   - [ ] No breaking changes
-   ```
-
-5. **Monitoring**: Check PR status and auto-merge when ready
-
-## Decision Guide
-
-Use **Show** when:
-
-- ✅ Tests are comprehensive
-- ✅ Changes are non-breaking
-- ✅ You're confident in the approach
-- ✅ Team should be aware of the change
-
-Use **/ship** instead if: change is tiny and obvious (typo, formatting)
-
-Use **/ask** instead if: change needs discussion, breaks APIs, or you're uncertain
-
-### 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/spike.md

@@ -1,95 +0,0 @@
----
-description: Execute TDD Spike Phase - exploratory coding to understand problem space before TDD
-argument-hint: <exploration description>
----
-
-SPIKE PHASE! Apply the below to the info given by user input here:
-
-$ARGUMENTS
-
-## 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).
-
-(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)
-
-## TDD Fundamentals
-
-### The TDD Cycle
-
-The foundation of TDD is the Red-Green-Refactor cycle:
-
-1. **Red Phase**: Write ONE failing test that describes desired behavior
-
-   - The test must fail for the RIGHT reason (not syntax/import errors)
-   - Only one test at a time - this is critical for TDD discipline
-     - Exception: For browser-level tests or expensive setup (e.g., Storybook `*.stories.tsx`), group multiple assertions within a single test block to avoid redundant setup - but only when adding assertions to an existing interaction flow. If new user interactions are required, still create a new test. Split files by category if they exceed ~1000 lines.
-   - **Adding a single test to a test file is ALWAYS allowed** - no prior test output needed
-   - Starting TDD for a new feature is always valid, even if test output shows unrelated work
-   - For DOM-based tests, use `data-testid` attributes to select elements rather than CSS classes, tag names, or text content
-   - Avoid hard-coded timeouts both in form of sleep() or timeout: 5000 etc; use proper async patterns (`waitFor`, `findBy*`, event-based sync) instead and rely on global test configs for timeout settings
-
-2. **Green Phase**: Write MINIMAL code to make the test pass
-
-   - Implement only what's needed for the current failing test
-   - No anticipatory coding or extra features
-   - Address the specific failure message
-
-3. **Refactor Phase**: Improve code structure while keeping tests green
-   - Only allowed when relevant tests are passing
-   - Requires proof that tests have been run and are green
-   - Applies to BOTH implementation and test code
-   - No refactoring with failing tests - fix them first
-
-### Core Violations
-
-1. **Multiple Test Addition**
-
-   - Adding more than one new test at once
-   - Exception: Initial test file setup or extracting shared test utilities
-
-2. **Over-Implementation**
-
-   - Code that exceeds what's needed to pass the current failing test
-   - Adding untested features, methods, or error handling
-   - Implementing multiple methods when test only requires one
-
-3. **Premature Implementation**
-   - Adding implementation before a test exists and fails properly
-   - Adding implementation without running the test first
-   - Refactoring when tests haven't been run or are failing
-
-### Critical Principle: Incremental Development
-
-Each step in TDD should address ONE specific issue:
-
-- Test fails "not defined" → Create empty stub/class only
-- Test fails "not a function" → Add method stub only
-- Test fails with assertion → Implement minimal logic only
-
-### Optional Pre-Phase: Spike Phase
-
-In rare cases where the problem space, interface, or expected behavior is unclear, a **Spike Phase** may be used **before the Red Phase**.
-This phase is **not part of the regular TDD workflow** and must only be applied under exceptional circumstances.
-
-- The goal of a Spike is **exploration and learning**, not implementation.
-- The code written during a Spike is **disposable** and **must not** be merged or reused directly.
-- Once sufficient understanding is achieved, all spike code is discarded, and normal TDD resumes starting from the **Red Phase**.
-- A Spike is justified only when it is impossible to define a meaningful failing test due to technical uncertainty or unknown system behavior.
-
-### General Information
-
-- Sometimes the test output shows as no tests have been run when a new test is failing due to a missing import or constructor. In such cases, allow the agent to create simple stubs. Ask them if they forgot to create a stub if they are stuck.
-- It is never allowed to introduce new logic without evidence of relevant failing tests. However, stubs and simple implementation to make imports and test infrastructure work is fine.
-- In the refactor phase, it is perfectly fine to refactor both test and implementation code. That said, completely new functionality is not allowed. Types, clean up, abstractions, and helpers are allowed as long as they do not introduce new behavior.
-- Adding types, interfaces, or a constant in order to replace magic values is perfectly fine during refactoring.
-- Provide the agent with helpful directions so that they do not get stuck when blocking them.

package/downloads/with-beads/summarize.md

@@ -1,54 +0,0 @@
----
-description: Summarize conversation progress and next steps
-argument-hint: [optional additional info]
----
-
-## 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 concise summary of the current conversation suitable for transferring context to a new conversation.
-
-Additional info: $ARGUMENTS
-
-## Summary Structure
-
-Provide a summary with these sections:
-
-### What We Did
-
-- Key accomplishments and changes made
-- Important decisions or discoveries
-- Files created, modified, or analyzed
-
-### What We're Doing Next
-
-- Immediate next steps
-- Pending tasks or work in progress
-- Goals or objectives to continue
-
-### Blockers & User Input Needed
-
-- Any issues requiring user intervention
-- Decisions that need to be made
-- Missing information or clarifications needed
-
-## Output Format
-
-Keep the summary concise and actionable - suitable for pasting into a new conversation to quickly restore context without needing the full conversation history.
-
-## Beads Integration
-
-If Beads MCP is available, check for task tracking status and ask if the user wants to:
-
-1. Review current task status
-2. Update task states based on conversation progress
-3. Include Beads context in the summary
-
-Use AskUserQuestion to confirm Beads integration preferences.