006 apk acquisition

.claude-skills/after-task_skill/SKILL.md

@@ -291,3 +291,5 @@ From `founder_rules.mdc`:
 **Purpose**: Capture institutional knowledge so future work benefits from past work. The self-improvement loop closes here.
 
 
+
+

.claude-skills/code-review_skill/README.md

@@ -168,3 +168,5 @@ Update this skill when:
 **Maintainer:** Founder
 
 
+
+

.claude-skills/code-review_skill/assets/review-template.md

@@ -74,3 +74,5 @@
 **Recommended Action:** [Approve / Request Changes / Needs Discussion]
 
 
+
+

.claude-skills/code-review_skill/references/review-guidelines.md

@@ -316,3 +316,5 @@ This skill should evolve based on:
 Update this reference document when new patterns emerge or guidelines change.
 
 
+
+

.claude-skills/dev-log-monitoring_skill/SKILL.md

@@ -77,12 +77,26 @@ curl -s http://localhost:5173 | head -n 1
 
 ## Step 2: Navigate and Execute Flow with Playwright MCP
 
+### 2.0 Close Existing Browser Session (MANDATORY)
+
+**ALWAYS close any existing browser tabs first to avoid "about:blank" issues:**
+
+```
+# List existing tabs
+mcp_cursor-browser-extension_browser_tabs(action: "list")
+
+# Close all tabs
+mcp_cursor-browser-extension_browser_tabs(action: "close", index: 0)
+```
+
+Repeat until no tabs remain. This prevents stale browser state and ensures clean test execution.
+
 ### 2.1 Navigate to Application
 
 Use Playwright MCP to open the app:
 
 ```
-mcp_playwright_browser_navigate(url: "http://localhost:5173")
+mcp_cursor-browser-extension_browser_navigate(url: "http://localhost:5173")
 ```
 
 ### 2.2 Trigger Drift Detection
@@ -405,6 +419,50 @@ curl -s http://localhost:4000/graph/diagnostics
 grep "agent.event.screen_perceived" /tmp/backend-logs.txt
 ```
 
+### BrowserStack Session Issues
+
+**Symptom:** Agent times out during ProvisionApp or EnsureDevice with BrowserStack
+
+**Check:**
+```bash
+# Look for BrowserStack session creation
+grep "Creating Appium session" /tmp/backend-logs.txt | grep browserStack
+
+# Check for timeout errors
+grep -i "timeout\|timed out" /tmp/backend-logs.txt | grep -i browserstack
+
+# Verify device name
+grep "deviceName" /tmp/backend-logs.txt | tail -5
+```
+
+**Debug with BrowserStack MCP:**
+```bash
+# Check recent sessions
+curl -s -u "USERNAME:KEY" "https://api-cloud.browserstack.com/app-automate/builds.json?limit=3"
+
+# Get session details (replace SESSION_ID)
+curl -s -u "USERNAME:KEY" "https://api-cloud.browserstack.com/app-automate/builds/BUILD_ID/sessions/SESSION_ID.json"
+
+# Check available devices
+curl -s -u "USERNAME:KEY" "https://api-cloud.browserstack.com/app-automate/devices.json" | grep "Samsung\|Pixel"
+```
+
+**Common Fixes:**
+1. **Invalid device name**: Query available devices via API - names are account-specific and case-sensitive
+2. **Missing APK upload**: Pre-upload APK in buildAgentContext, pass `bs://` URL to session (CRITICAL)
+3. **Session not closed**: Add `driver.deleteSession()` in Stop node handler
+4. **Timeout issues**: 60s default is sufficient (BrowserStack completes in ~40s)
+
+**Artifact Locations:**
+```bash
+# Screenshots and UI XML stored by Encore
+ls -la ~/Library/Caches/encore/objects/*/artifacts/obj:/artifacts/[RUN_ID]/screenshot/
+ls -la ~/Library/Caches/encore/objects/*/artifacts/obj:/artifacts/[RUN_ID]/ui_xml/
+
+# Open most recent screenshot
+open "$(find ~/Library/Caches/encore/objects/*/artifacts/ -name "*.png" | tail -1)"
+```
+
 ## Resources
 
 ### references/log_patterns.md

.claude-skills/encore-svelte/SKILL.md

@@ -0,0 +1,85 @@
+---
+name: encore-svelte
+description: [TODO: Complete and informative explanation of what the skill does and when to use it. Include WHEN to use this skill - specific scenarios, file types, or tasks that trigger it.]
+---
+
+# Encore Svelte
+
+## Overview
+
+[TODO: 1-2 sentences explaining what this skill enables]
+
+## Structuring This Skill
+
+[TODO: Choose the structure that best fits this skill's purpose. Common patterns:
+
+**1. Workflow-Based** (best for sequential processes)
+- Works well when there are clear step-by-step procedures
+- Example: DOCX skill with "Workflow Decision Tree" → "Reading" → "Creating" → "Editing"
+- Structure: ## Overview → ## Workflow Decision Tree → ## Step 1 → ## Step 2...
+
+**2. Task-Based** (best for tool collections)
+- Works well when the skill offers different operations/capabilities
+- Example: PDF skill with "Quick Start" → "Merge PDFs" → "Split PDFs" → "Extract Text"
+- Structure: ## Overview → ## Quick Start → ## Task Category 1 → ## Task Category 2...
+
+**3. Reference/Guidelines** (best for standards or specifications)
+- Works well for brand guidelines, coding standards, or requirements
+- Example: Brand styling with "Brand Guidelines" → "Colors" → "Typography" → "Features"
+- Structure: ## Overview → ## Guidelines → ## Specifications → ## Usage...
+
+**4. Capabilities-Based** (best for integrated systems)
+- Works well when the skill provides multiple interrelated features
+- Example: Product Management with "Core Capabilities" → numbered capability list
+- Structure: ## Overview → ## Core Capabilities → ### 1. Feature → ### 2. Feature...
+
+Patterns can be mixed and matched as needed. Most skills combine patterns (e.g., start with task-based, add workflow for complex operations).
+
+Delete this entire "Structuring This Skill" section when done - it's just guidance.]
+
+## [TODO: Replace with the first main section based on chosen structure]
+
+[TODO: Add content here. See examples in existing skills:
+- Code samples for technical skills
+- Decision trees for complex workflows
+- Concrete examples with realistic user requests
+- References to scripts/templates/references as needed]
+
+## Resources
+
+This skill includes example resource directories that demonstrate how to organize different types of bundled resources:
+
+### scripts/
+Executable code (Python/Bash/etc.) that can be run directly to perform specific operations.
+
+**Examples from other skills:**
+- PDF skill: `fill_fillable_fields.py`, `extract_form_field_info.py` - utilities for PDF manipulation
+- DOCX skill: `document.py`, `utilities.py` - Python modules for document processing
+
+**Appropriate for:** Python scripts, shell scripts, or any executable code that performs automation, data processing, or specific operations.
+
+**Note:** Scripts may be executed without loading into context, but can still be read by Claude for patching or environment adjustments.
+
+### references/
+Documentation and reference material intended to be loaded into context to inform Claude's process and thinking.
+
+**Examples from other skills:**
+- Product management: `communication.md`, `context_building.md` - detailed workflow guides
+- BigQuery: API reference documentation and query examples
+- Finance: Schema documentation, company policies
+
+**Appropriate for:** In-depth documentation, API references, database schemas, comprehensive guides, or any detailed information that Claude should reference while working.
+
+### assets/
+Files not intended to be loaded into context, but rather used within the output Claude produces.
+
+**Examples from other skills:**
+- Brand styling: PowerPoint template files (.pptx), logo files
+- Frontend builder: HTML/React boilerplate project directories
+- Typography: Font files (.ttf, .woff2)
+
+**Appropriate for:** Templates, boilerplate code, document templates, images, icons, fonts, or any files meant to be copied or used in the final output.
+
+---
+
+**Any unneeded directories can be deleted.** Not every skill requires all three types of resources.

.claude-skills/encore-svelte/assets/example_asset.txt

@@ -0,0 +1,24 @@
+# Example Asset File
+
+This placeholder represents where asset files would be stored.
+Replace with actual asset files (templates, images, fonts, etc.) or delete if not needed.
+
+Asset files are NOT intended to be loaded into context, but rather used within
+the output Claude produces.
+
+Example asset files from other skills:
+- Brand guidelines: logo.png, slides_template.pptx
+- Frontend builder: hello-world/ directory with HTML/React boilerplate
+- Typography: custom-font.ttf, font-family.woff2
+- Data: sample_data.csv, test_dataset.json
+
+## Common Asset Types
+
+- Templates: .pptx, .docx, boilerplate directories
+- Images: .png, .jpg, .svg, .gif
+- Fonts: .ttf, .otf, .woff, .woff2
+- Boilerplate code: Project directories, starter files
+- Icons: .ico, .svg
+- Data files: .csv, .json, .xml, .yaml
+
+Note: This is a text placeholder. Actual assets can be any file type.