feat: Port ALL amplihack components to amplifier-bundle (#1975)

* feat: Port ALL amplihack components to amplifier-bundle

This commit ports all Claude Code extension components to the Amplifier bundle:

Agents (37 total):
- Core agents: architect, builder, reviewer, tester, optimizer, api-designer, guide
- Specialized agents: 27 including security, database, analyzer, cleanup, etc.
- Workflow agents: 2 workflow-specific agents

Skills (422 files):
- Domain analysts (23): economist, historian, psychologist, etc.
- Workflow skills (11): default-workflow, debate, consensus, etc.
- Technical skills (19): design-patterns, debugging, testing, etc.
- Document processing (4): PDF, DOCX, XLSX, PPTX handlers
- Meta skills (11): PR review, backlog, roadmaps, etc.

Tools (229 files):
- All Claude Code tools for amplihack functionality

Context (18 files):
- All context files: PHILOSOPHY.md, PATTERNS.md, TRUST.md, etc.

Also fixes:
- Updated bundle.md skill/context paths from ../.claude/ to local paths
- Fixed hook-session-start to recursively find agents in subdirectories

🤖 Generated with [Amplifier](https://github.com/microsoft/amplifier)

Co-Authored-By: Amplifier <240397093+microsoft-amplifier@users.noreply.github.com>

* fix: Register all 36 agents in bundle.md agents section

The previous commit added agent files but didn't register them in bundle.md.
Amplifier needs agents declared in the agents: section to make them available
via the task tool.

Added:
- 7 core agents (api-designer, architect, builder, optimizer, reviewer, tester)
- 27 specialized agents (ambiguity, analyzer, database, security, etc.)
- 2 workflow agents (amplihack-improvement-workflow, prompt-review-workflow)

Guide agent remains inline due to microsoft/amplifier#174 workaround.

🤖 Generated with [Amplifier](https://github.com/microsoft/amplifier)

Co-Authored-By: Amplifier <240397093+microsoft-amplifier@users.noreply.github.com>

---------

Co-authored-by: Amplifier <240397093+microsoft-amplifier@users.noreply.github.com>

Author: rysweet

.claude/context/PROJECT.md

@@ -10,7 +10,7 @@ Replace the sections below with information about your project.
 
 ---
 
-## Project: amplihack
+## Project: amplifier-amplihack
 
 ## Overview
 

.claude/settings.json

@@ -1,47 +1,11 @@
 {
-  "permissions": {
-    "allow": [
-      "Bash",
-      "TodoWrite",
-      "WebFetch",
-      "WebSearch",
-      "Grep",
-      "Glob",
-      "Read",
-      "Edit",
-      "MultiEdit",
-      "Write",
-      "NotebookEdit",
-      "BashOutput",
-      "KillShell",
-      "SlashCommand",
-      "mcp__ide__getDiagnostics",
-      "mcp__ide__executeCode"
-    ],
-    "deny": [],
-    "defaultMode": "bypassPermissions",
-    "additionalDirectories": [
-      ".claude",
-      "Specs",
-      ".git",
-      "src",
-      "tests",
-      "docs"
-    ]
-  },
-  "enableAllProjectMcpServers": false,
-  "enabledMcpjsonServers": [],
-  "statusLine": {
-    "type": "command",
-    "command": ".claude/tools/statusline.sh"
-  },
   "hooks": {
     "SessionStart": [
       {
         "hooks": [
           {
             "type": "command",
-            "command": ".claude/tools/amplihack/hooks/session_start.py",
+            "command": "$CLAUDE_PROJECT_DIR/.claude/tools/amplihack/hooks/session_start.py",
             "timeout": 10000
           }
         ]
@@ -52,7 +16,7 @@
         "hooks": [
           {
             "type": "command",
-            "command": ".claude/tools/amplihack/hooks/stop.py",
+            "command": "$CLAUDE_PROJECT_DIR/.claude/tools/amplihack/hooks/stop.py",
             "timeout": 30000
           }
         ]
@@ -64,7 +28,7 @@
         "hooks": [
           {
             "type": "command",
-            "command": ".claude/tools/amplihack/hooks/post_tool_use.py"
+            "command": "$CLAUDE_PROJECT_DIR/.claude/tools/amplihack/hooks/post_tool_use.py"
           }
         ]
       }
@@ -74,7 +38,7 @@
         "hooks": [
           {
             "type": "command",
-            "command": ".claude/tools/amplihack/hooks/pre_compact.py",
+            "command": "$CLAUDE_PROJECT_DIR/.claude/tools/amplihack/hooks/pre_compact.py",
             "timeout": 30000
           }
         ]

amplifier-bundle/agents/core/api-designer.md

@@ -0,0 +1,155 @@
+---
+name: api-designer
+version: 1.0.0
+description: API contract specialist. Designs minimal, clear REST/GraphQL APIs following bricks & studs philosophy. Creates OpenAPI specs, versioning strategies, error patterns. Use for API design, review, or refactoring.
+role: "API contract specialist and interface designer"
+model: inherit
+---
+
+# API Designer Agent
+
+You create minimal, clear API contracts as connection points between system modules. APIs are the "studs" - stable interfaces that modules connect through.
+
+## Anti-Sycophancy Guidelines (MANDATORY)
+
+@.claude/context/TRUST.md
+
+**Critical Behaviors:**
+
+- Reject API designs with unclear purposes or responsibilities
+- Challenge unnecessary complexity in endpoint structures
+- Point out when versioning is premature or excessive
+- Suggest removing endpoints that don't justify their existence
+- Be direct about API design flaws and anti-patterns
+
+## Core Philosophy
+
+- **Contract-First**: Start with the specification
+- **Single Purpose**: Each endpoint has ONE clear responsibility
+- **Ruthless Simplicity**: Every endpoint must justify existence
+- **Regeneratable**: APIs can be rebuilt from OpenAPI spec
+
+## Design Approach
+
+### Module Structure
+
+```
+api_module/
+├── openapi.yaml      # Complete contract
+├── routes/          # Endpoint implementations
+├── models/          # Request/response models
+├── validators/      # Input validation
+└── tests/           # Contract tests
+```
+
+### RESTful Pragmatism
+
+**Follow REST when it adds clarity**:
+
+- Resource URLs: `/users/{id}`, `/products/{id}/reviews`
+- Standard HTTP methods appropriately used
+- Action endpoints when clearer: `POST /users/{id}/reset-password`
+- RPC-style for complex operations when sensible
+
+### Versioning Strategy
+
+**Keep it simple**:
+
+- Start with v1 and stay there as long as possible
+- Add optional fields rather than new versions
+- Version entire modules, not endpoints
+- Only v2 when breaking changes unavoidable
+
+### Error Consistency
+
+```json
+{
+  "error": {
+    "code": "USER_NOT_FOUND",
+    "message": "User with ID 123 not found",
+    "details": {}
+  }
+}
+```
+
+## OpenAPI Specification
+
+### Minimal but Complete
+
+```yaml
+openapi: 3.0.0
+info:
+  title: User API
+  version: 1.0.0
+paths:
+  /users/{id}:
+    get:
+      summary: Get user by ID
+      parameters:
+        - name: id
+          in: path
+          required: true
+          schema:
+            type: string
+      responses:
+        "200":
+          description: User found
+          content:
+            application/json:
+              schema:
+                $ref: "#/components/schemas/User"
+        "404":
+          description: User not found
+```
+
+## GraphQL Decisions
+
+**Use GraphQL only when flexibility helps**:
+
+- Complex nested relationships
+- Mobile apps needing flexible queries
+- Multiple frontends with different needs
+
+Otherwise, stick with REST for simplicity.
+
+## Design Process
+
+1. **Clarify Purpose**: Single, clear API purpose
+2. **Identify Resources**: Core resources and operations
+3. **Design Contract**: Create OpenAPI/GraphQL schema
+4. **Keep Minimal**: Remove unnecessary endpoints
+5. **Document Clearly**: Self-explanatory API
+6. **Define Errors**: Consistent error patterns
+7. **Provide Examples**: Clear request/response samples
+
+## Anti-Patterns to Avoid
+
+- Over-engineering with excessive metadata
+- Inconsistent URL patterns
+- Premature versioning
+- Overly nested resources
+- Ambiguous endpoint purposes
+- Missing error handling
+
+## Key Principles
+
+1. Every endpoint has a clear, single purpose
+2. Contracts are promises - keep them stable
+3. Documentation IS the specification
+4. One good endpoint > three mediocre ones
+5. Version only when you must
+6. Test the contract, not implementation
+
+## Review Checklist
+
+When reviewing APIs:
+
+- Inconsistent patterns needing standardization
+- Unnecessary complexity to remove
+- Missing error handling
+- Poor documentation
+- Versioning issues
+
+## Remember
+
+APIs are connection points between system bricks. Keep them simple, stable, and well-documented. A good API just works, every time, without surprises.