rebar-mcp 2.0.0

package/.claude/skills/coercion-test/SKILL.md

@@ -0,0 +1,50 @@
+---
+name: coercion-test
+description: A test skill
+invocation: undefined
+context: undefined
+---
+
+# Test Writer
+
+You write tests that catch real bugs, not tests that just check if the code runs.
+
+## Before Writing
+
+1. **Read existing tests** — find 2-3 test files to understand:
+   - Which testing framework (Jest, Vitest, pytest, JUnit, etc.)
+   - Test file naming convention (`.test.ts`, `.spec.ts`, `_test.go`, etc.)
+   - Test location (colocated vs. `__tests__/` vs. `test/`)
+   - Mocking patterns used (jest.mock, vi.mock, unittest.mock, etc.)
+   - Setup/teardown patterns (beforeEach, fixtures, etc.)
+
+2. **Read the code under test** — understand:
+   - All public functions and their signatures
+   - Edge cases: What happens with null/undefined/empty/zero/negative inputs?
+   - Error paths: What exceptions can be thrown?
+   - Side effects: Database calls, API calls, file system operations
+
+## Test Writing Rules
+
+### Coverage Strategy
+- **Happy path**: Normal inputs produce expected outputs
+- **Edge cases**: Empty strings, empty arrays, zero, negative numbers, max values
+- **Error cases**: Invalid inputs, network failures, permission errors
+- **Boundary conditions**: First item, last item, exactly at limits
+
+### Quality Standards
+- Each test has a descriptive name: `"returns empty array when user has no orders"`
+- One assertion per concept (not one assertion per test)
+- Tests are independent — no test relies on another test's side effects
+- Mock external dependencies (APIs, databases) — never make real calls
+- Use factories/fixtures for complex test data
+
+### Anti-Patterns to Avoid
+- Testing implementation details (internal method calls, private state)
+- Snapshot tests for logic (only use for UI rendering)
+- Tests that pass when the code is broken
+- Copy-pasting the implementation as the expected value
+
+## Output
+Place test files where the project convention expects them.
+Run the tests after writing to verify they pass.

package/.claude/skills/large-skill/SKILL.md

@@ -0,0 +1,21 @@
+---
+name: large-skill
+description: A skill with large instructions
+invocation: undefined
+context: undefined
+---
+
+# large-skill
+
+A skill with large instructions
+
+## Instructions
+
+<!-- Replace this with your skill instructions.
+Good skill instructions:
+1. Define the agent's role clearly
+2. Specify the exact output format
+3. List what to check/do step by step
+4. Include examples of good output
+-->
+

package/.claude/skills/long-desc-skill/SKILL.md

@@ -0,0 +1,21 @@
+---
+name: long-desc-skill
+description: aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
+invocation: undefined
+context: undefined
+---
+
+# long-desc-skill
+
+aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
+
+## Instructions
+
+<!-- Replace this with your skill instructions.
+Good skill instructions:
+1. Define the agent's role clearly
+2. Specify the exact output format
+3. List what to check/do step by step
+4. Include examples of good output
+-->
+

package/.claude/skills/mcp-dev/SKILL.md

@@ -0,0 +1,61 @@
+---
+name: mcp-dev
+description: Guidelines for developing MCP server tools in the rebar-mcp-server project
+invocation: auto
+context: inline
+---
+
+# MCP Development Skill
+
+When working on rebar-mcp-server tool implementations, follow these patterns:
+
+## Tool Registration Pattern
+
+```typescript
+server.registerTool(
+  "rebar_tool_name",
+  {
+    title: "Human Readable Title",
+    description: "Multi-line description with:\n" +
+      "• What the tool does\n" +
+      "• Key parameters\n" +
+      "• 2-3 usage examples\n" +
+      "• Error handling notes",
+    inputSchema: ZodSchemaWithStrict,
+    annotations: {
+      readOnlyHint: false,
+      destructiveHint: false,
+      idempotentHint: true,
+      openWorldHint: false,
+    },
+  },
+  async (args) => {
+    // Implementation
+    return {
+      content: [{ type: "text", text: "result" }],
+    };
+  }
+);
+```
+
+## Zod Schema Pattern
+
+```typescript
+export const InputSchema = z.object({
+  project_path: z.string().min(1).describe("Absolute or relative path to project"),
+  option: z.enum(["a", "b"]).default("a").describe("What this option controls"),
+}).strict();
+```
+
+## Error Pattern
+
+```typescript
+return {
+  content: [{ type: "text", text: `Failed: ${message}\n\nSuggestions:\n• Fix A\n• Fix B` }],
+  isError: true,
+};
+```
+
+## File Write Pattern
+Always use `atomicWrite()` from services/file-ops.ts.
+Never overwrite without checking `merge_existing` or `force`.

package/.claude/skills/nl-mmibweus/SKILL.md

@@ -0,0 +1,25 @@
+---
+name: nl-mmibweus
+description: Line one
+Line two
+Line three
+invocation: undefined
+context: undefined
+---
+
+# nl-mmibweus
+
+Line one
+Line two
+Line three
+
+## Instructions
+
+<!-- Replace this with your skill instructions.
+Good skill instructions:
+1. Define the agent's role clearly
+2. Specify the exact output format
+3. List what to check/do step by step
+4. Include examples of good output
+-->
+

package/.claude/skills/nl-mmibwjhf/SKILL.md

@@ -0,0 +1,25 @@
+---
+name: nl-mmibwjhf
+description: Line one
+Line two
+Line three
+invocation: undefined
+context: undefined
+---
+
+# nl-mmibwjhf
+
+Line one
+Line two
+Line three
+
+## Instructions
+
+<!-- Replace this with your skill instructions.
+Good skill instructions:
+1. Define the agent's role clearly
+2. Specify the exact output format
+3. List what to check/do step by step
+4. Include examples of good output
+-->
+

package/.claude/skills/nl-mmibwsf7/SKILL.md

@@ -0,0 +1,25 @@
+---
+name: nl-mmibwsf7
+description: Line one
+Line two
+Line three
+invocation: undefined
+context: undefined
+---
+
+# nl-mmibwsf7
+
+Line one
+Line two
+Line three
+
+## Instructions
+
+<!-- Replace this with your skill instructions.
+Good skill instructions:
+1. Define the agent's role clearly
+2. Specify the exact output format
+3. List what to check/do step by step
+4. Include examples of good output
+-->
+

package/.claude/skills/nl-mmibwxvq/SKILL.md

@@ -0,0 +1,25 @@
+---
+name: nl-mmibwxvq
+description: Line one
+Line two
+Line three
+invocation: undefined
+context: undefined
+---
+
+# nl-mmibwxvq
+
+Line one
+Line two
+Line three
+
+## Instructions
+
+<!-- Replace this with your skill instructions.
+Good skill instructions:
+1. Define the agent's role clearly
+2. Specify the exact output format
+3. List what to check/do step by step
+4. Include examples of good output
+-->
+

package/.claude/skills/nl-mmibx3rt/SKILL.md

@@ -0,0 +1,25 @@
+---
+name: nl-mmibx3rt
+description: Line one
+Line two
+Line three
+invocation: undefined
+context: undefined
+---
+
+# nl-mmibx3rt
+
+Line one
+Line two
+Line three
+
+## Instructions
+
+<!-- Replace this with your skill instructions.
+Good skill instructions:
+1. Define the agent's role clearly
+2. Specify the exact output format
+3. List what to check/do step by step
+4. Include examples of good output
+-->
+

package/.claude/skills/nl-mmji0lrz/SKILL.md

@@ -0,0 +1,25 @@
+---
+name: nl-mmji0lrz
+description: Line one
+Line two
+Line three
+invocation: undefined
+context: undefined
+---
+
+# nl-mmji0lrz
+
+Line one
+Line two
+Line three
+
+## Instructions
+
+<!-- Replace this with your skill instructions.
+Good skill instructions:
+1. Define the agent's role clearly
+2. Specify the exact output format
+3. List what to check/do step by step
+4. Include examples of good output
+-->
+

package/.claude/skills/nl-mmjinipx/SKILL.md

@@ -0,0 +1,25 @@
+---
+name: nl-mmjinipx
+description: Line one
+Line two
+Line three
+invocation: undefined
+context: undefined
+---
+
+# nl-mmjinipx
+
+Line one
+Line two
+Line three
+
+## Instructions
+
+<!-- Replace this with your skill instructions.
+Good skill instructions:
+1. Define the agent's role clearly
+2. Specify the exact output format
+3. List what to check/do step by step
+4. Include examples of good output
+-->
+

package/.claude/skills/nl-mmjio87f/SKILL.md

@@ -0,0 +1,25 @@
+---
+name: nl-mmjio87f
+description: Line one
+Line two
+Line three
+invocation: undefined
+context: undefined
+---
+
+# nl-mmjio87f
+
+Line one
+Line two
+Line three
+
+## Instructions
+
+<!-- Replace this with your skill instructions.
+Good skill instructions:
+1. Define the agent's role clearly
+2. Specify the exact output format
+3. List what to check/do step by step
+4. Include examples of good output
+-->
+

package/.claude/skills/nl-mmjiolfs/SKILL.md

@@ -0,0 +1,25 @@
+---
+name: nl-mmjiolfs
+description: Line one
+Line two
+Line three
+invocation: undefined
+context: undefined
+---
+
+# nl-mmjiolfs
+
+Line one
+Line two
+Line three
+
+## Instructions
+
+<!-- Replace this with your skill instructions.
+Good skill instructions:
+1. Define the agent's role clearly
+2. Specify the exact output format
+3. List what to check/do step by step
+4. Include examples of good output
+-->
+

package/.claude/skills/nl-mmjit1mc/SKILL.md

@@ -0,0 +1,25 @@
+---
+name: nl-mmjit1mc
+description: Line one
+Line two
+Line three
+invocation: undefined
+context: undefined
+---
+
+# nl-mmjit1mc
+
+Line one
+Line two
+Line three
+
+## Instructions
+
+<!-- Replace this with your skill instructions.
+Good skill instructions:
+1. Define the agent's role clearly
+2. Specify the exact output format
+3. List what to check/do step by step
+4. Include examples of good output
+-->
+

package/.claude/skills/nl-mmjita26/SKILL.md

@@ -0,0 +1,25 @@
+---
+name: nl-mmjita26
+description: Line one
+Line two
+Line three
+invocation: undefined
+context: undefined
+---
+
+# nl-mmjita26
+
+Line one
+Line two
+Line three
+
+## Instructions
+
+<!-- Replace this with your skill instructions.
+Good skill instructions:
+1. Define the agent's role clearly
+2. Specify the exact output format
+3. List what to check/do step by step
+4. Include examples of good output
+-->
+

package/.claude/skills/rapid-1/SKILL.md

@@ -0,0 +1,21 @@
+---
+name: rapid-1
+description: Rapid test 1
+invocation: undefined
+context: undefined
+---
+
+# rapid-1
+
+Rapid test 1
+
+## Instructions
+
+<!-- Replace this with your skill instructions.
+Good skill instructions:
+1. Define the agent's role clearly
+2. Specify the exact output format
+3. List what to check/do step by step
+4. Include examples of good output
+-->
+

package/.claude/skills/rapid-2/SKILL.md

@@ -0,0 +1,21 @@
+---
+name: rapid-2
+description: Rapid test 2
+invocation: undefined
+context: undefined
+---
+
+# rapid-2
+
+Rapid test 2
+
+## Instructions
+
+<!-- Replace this with your skill instructions.
+Good skill instructions:
+1. Define the agent's role clearly
+2. Specify the exact output format
+3. List what to check/do step by step
+4. Include examples of good output
+-->
+

package/.claude/skills/rapid-3/SKILL.md

@@ -0,0 +1,21 @@
+---
+name: rapid-3
+description: Rapid test 3
+invocation: undefined
+context: undefined
+---
+
+# rapid-3
+
+Rapid test 3
+
+## Instructions
+
+<!-- Replace this with your skill instructions.
+Good skill instructions:
+1. Define the agent's role clearly
+2. Specify the exact output format
+3. List what to check/do step by step
+4. Include examples of good output
+-->
+

package/.claude/skills/rapid-4/SKILL.md

@@ -0,0 +1,21 @@
+---
+name: rapid-4
+description: Rapid test 4
+invocation: undefined
+context: undefined
+---
+
+# rapid-4
+
+Rapid test 4
+
+## Instructions
+
+<!-- Replace this with your skill instructions.
+Good skill instructions:
+1. Define the agent's role clearly
+2. Specify the exact output format
+3. List what to check/do step by step
+4. Include examples of good output
+-->
+

package/.claude/skills/rapid-5/SKILL.md

@@ -0,0 +1,21 @@
+---
+name: rapid-5
+description: Rapid test 5
+invocation: undefined
+context: undefined
+---
+
+# rapid-5
+
+Rapid test 5
+
+## Instructions
+
+<!-- Replace this with your skill instructions.
+Good skill instructions:
+1. Define the agent's role clearly
+2. Specify the exact output format
+3. List what to check/do step by step
+4. Include examples of good output
+-->
+

package/.claude/skills/test/", /"malicious/": /"true/SKILL.md"

@@ -0,0 +1,69 @@
+---
+name: test", "malicious": "true
+description: {"injected": true}
+invocation: undefined
+context: undefined
+---
+
+## Test Writing Process
+
+### Step 1: Analyze What Needs Testing
+- Read the function/module signature, parameters, and return type
+- Identify the happy path (normal successful execution)
+- Identify error paths (what can go wrong?)
+- Identify edge cases (empty input, null, boundary values, max values)
+- Identify integration points (database calls, API calls, file system)
+
+### Step 2: Write Tests in This Order
+
+1. **Happy path test** — The most basic successful case
+2. **Input validation tests** — Invalid inputs, missing required fields, wrong types
+3. **Edge case tests** — Empty arrays, zero values, very long strings, special characters
+4. **Error handling tests** — Network failures, database errors, file not found
+5. **Integration tests** — Full request/response cycle (if applicable)
+
+### Step 3: Test Structure
+
+Every test MUST follow this structure:
+
+```
+// Descriptive name that explains what is being tested and expected outcome
+test("createUser returns the created user with a generated ID when given valid input", async () => {
+  // ARRANGE: Set up test data and dependencies
+  const input = { name: "Test User", email: "test@example.com" };
+
+  // ACT: Execute the function under test
+  const result = await createUser(input);
+
+  // ASSERT: Verify the outcome
+  expect(result.id).toBeDefined();
+  expect(result.name).toBe("Test User");
+  expect(result.email).toBe("test@example.com");
+});
+```
+
+### Mandatory Test Categories
+
+For EVERY function, write tests covering:
+
+| Category | Example | Required? |
+|---|---|---|
+| Valid input, expected output | Normal successful operation | ALWAYS |
+| Missing required field | Omit a required parameter | ALWAYS |
+| Invalid type | Pass string where number expected | ALWAYS |
+| Empty input | Empty string, empty array, null | ALWAYS |
+| Boundary values | 0, -1, MAX_INT, very long string | WHEN APPLICABLE |
+| Duplicate/conflict | Creating something that already exists | WHEN APPLICABLE |
+| Not found | Requesting something that does not exist | WHEN APPLICABLE |
+| Unauthorized | Accessing without proper permissions | WHEN AUTH EXISTS |
+| Concurrent access | Two operations on same resource | WHEN APPLICABLE |
+| Error recovery | Service dependency fails | WHEN EXTERNAL DEPS EXIST |
+
+### Rules
+- Test file names MUST match source file: `user.service.ts` → `user.service.test.ts`
+- NEVER test implementation details — test behavior and outcomes
+- NEVER use `test("should work")` — test names must describe the specific scenario and expected outcome
+- EVERY test must be independent — no test should depend on another test running first
+- ALWAYS clean up test data (use beforeEach/afterEach or setup/teardown)
+- Mock external dependencies (databases, APIs, file system) — do not make real network calls in unit tests
+- NEVER write a test that always passes — verify your test fails before the implementation exists

package/.claude/skills/test-emoji-/360/237/230/200-skill/SKILL.md

@@ -0,0 +1,69 @@
+---
+name: test-emoji-😀-skill
+description: A skill with emoji
+invocation: undefined
+context: undefined
+---
+
+## Test Writing Process
+
+### Step 1: Analyze What Needs Testing
+- Read the function/module signature, parameters, and return type
+- Identify the happy path (normal successful execution)
+- Identify error paths (what can go wrong?)
+- Identify edge cases (empty input, null, boundary values, max values)
+- Identify integration points (database calls, API calls, file system)
+
+### Step 2: Write Tests in This Order
+
+1. **Happy path test** — The most basic successful case
+2. **Input validation tests** — Invalid inputs, missing required fields, wrong types
+3. **Edge case tests** — Empty arrays, zero values, very long strings, special characters
+4. **Error handling tests** — Network failures, database errors, file not found
+5. **Integration tests** — Full request/response cycle (if applicable)
+
+### Step 3: Test Structure
+
+Every test MUST follow this structure:
+
+```
+// Descriptive name that explains what is being tested and expected outcome
+test("createUser returns the created user with a generated ID when given valid input", async () => {
+  // ARRANGE: Set up test data and dependencies
+  const input = { name: "Test User", email: "test@example.com" };
+
+  // ACT: Execute the function under test
+  const result = await createUser(input);
+
+  // ASSERT: Verify the outcome
+  expect(result.id).toBeDefined();
+  expect(result.name).toBe("Test User");
+  expect(result.email).toBe("test@example.com");
+});
+```
+
+### Mandatory Test Categories
+
+For EVERY function, write tests covering:
+
+| Category | Example | Required? |
+|---|---|---|
+| Valid input, expected output | Normal successful operation | ALWAYS |
+| Missing required field | Omit a required parameter | ALWAYS |
+| Invalid type | Pass string where number expected | ALWAYS |
+| Empty input | Empty string, empty array, null | ALWAYS |
+| Boundary values | 0, -1, MAX_INT, very long string | WHEN APPLICABLE |
+| Duplicate/conflict | Creating something that already exists | WHEN APPLICABLE |
+| Not found | Requesting something that does not exist | WHEN APPLICABLE |
+| Unauthorized | Accessing without proper permissions | WHEN AUTH EXISTS |
+| Concurrent access | Two operations on same resource | WHEN APPLICABLE |
+| Error recovery | Service dependency fails | WHEN EXTERNAL DEPS EXIST |
+
+### Rules
+- Test file names MUST match source file: `user.service.ts` → `user.service.test.ts`
+- NEVER test implementation details — test behavior and outcomes
+- NEVER use `test("should work")` — test names must describe the specific scenario and expected outcome
+- EVERY test must be independent — no test should depend on another test running first
+- ALWAYS clean up test data (use beforeEach/afterEach or setup/teardown)
+- Mock external dependencies (databases, APIs, file system) — do not make real network calls in unit tests
+- NEVER write a test that always passes — verify your test fails before the implementation exists