arkaos 2.5.0 → 2.5.2

package/VERSION

@@ -1 +1 @@
-2.5.0
+2.5.2

package/departments/brand/skills/design-review/SKILL.md

@@ -0,0 +1,57 @@
+---
+name: brand/design-review
+description: >
+  Open a design tool (Figma, Sketch, Canva desktop) and compare live designs
+  against brand guidelines. Screenshot and annotate differences.
+  Requires Computer Use (/mcp → computer-use).
+allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent]
+---
+
+# Design Review — `/brand design-review`
+
+> **Agent:** Valentina (Creative Director) | Requires: Computer Use (`/mcp` → `computer-use`)
+
+## Command
+
+```
+/brand design-review <app-or-file>
+```
+
+App can be: Figma, Sketch, Canva, or a direct file path to a design file.
+
+## What It Does
+
+Opens a design tool and compares live designs against brand guidelines. Screenshots and annotates differences.
+
+## Workflow
+
+1. **Check computer-use availability** — follow [Computer Use Availability Check](/arka)
+2. **Open** the design tool or file
+3. **Navigate** to the relevant artboards/pages
+4. **Compare** against brand guidelines:
+   - Color palette accuracy (hex values, contrast)
+   - Typography (font family, sizes, weights)
+   - Spacing and layout consistency
+   - Logo usage and clear space
+   - Icon style consistency
+5. **Screenshot** each artboard with annotations of issues found
+6. **Generate report** with side-by-side comparisons
+
+## Example
+
+```
+/brand design-review Figma
+/brand design-review ~/Documents/Homepage-v3.sketch
+/brand design-review "Canva — Social Media Templates"
+```
+
+## Fallback (No Computer Use)
+
+```
+⚠ Computer Use required for design tool interaction.
+Enable via: /mcp → computer-use (macOS only, Pro/Max plan required)
+```
+
+## Output
+
+Design review report saved to Obsidian: `Projects/<ecosystem>/Brand/Reviews/<date>.md`

package/departments/brand/skills/identity-system/SKILL.md

@@ -24,3 +24,9 @@ Follow the [Browser Integration Pattern](/arka) for availability checking.
 - [BROWSER] Open the website/app and verify brand elements match the identity system (colors, typography, spacing)
 - [BROWSER] Compare generated assets side-by-side with the live site
 - [BROWSER] Check favicon, og:image, and meta branding elements
+
+## Computer Use Steps
+
+Follow the [Computer Use Availability Check](/arka) for availability checking.
+
+- [COMPUTER] Open design tools (Figma, Canva desktop, Sketch) to verify brand assets match guidelines

package/departments/brand/skills/ux-audit/SKILL.md

@@ -26,3 +26,16 @@ Follow the [Browser Integration Pattern](/arka) for availability checking.
 - [BROWSER] Capture screenshots of key screens for the UX audit report
 - [BROWSER] Check responsive design at mobile, tablet, and desktop breakpoints
 - [BROWSER] Verify loading states, error states, and empty states render correctly
+
+## Computer Use Steps
+
+Follow the [Computer Use Availability Check](/arka) for availability checking.
+
+- [COMPUTER] Launch the native app, test user flows, screenshot each screen for the audit report
+
+## Scheduling ⏰
+
+```
+/schedule weekly — run Lighthouse audit on main pages, flag performance regressions
+/schedule monthly — full UX heuristic review of core user flows
+```

package/departments/dev/skills/app-test/SKILL.md

@@ -0,0 +1,52 @@
+---
+name: dev/app-test
+description: >
+  Build, launch, and click through a native app (macOS or iOS Simulator).
+  Screenshot each screen, report crashes or visual issues.
+  Requires Computer Use (/mcp → computer-use).
+allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent]
+---
+
+# App Test — `/dev app-test`
+
+> **Agent:** Paulo (Tech Lead) | Requires: Computer Use (`/mcp` → `computer-use`)
+
+## Command
+
+```
+/dev app-test <target>
+```
+
+Target can be: Xcode build target, app bundle path, or iOS Simulator app name.
+
+## What It Does
+
+Builds, launches, and interactively tests a native application by clicking through every control and screen.
+
+## Workflow
+
+1. **Check computer-use availability** — follow [Computer Use Availability Check](/arka)
+2. **Build** the target (if source provided): `xcodebuild` or appropriate build command
+3. **Launch** the app (or open in iOS Simulator)
+4. **Click through** every tab, button, and control systematically
+5. **Screenshot** each distinct screen state
+6. **Report** findings: crashes, visual glitches, unresponsive controls, layout issues
+
+## Example
+
+```
+/dev app-test MenuBarStats
+/dev app-test /Applications/MyApp.app
+/dev app-test "My iOS App" --simulator
+```
+
+## Fallback (No Computer Use)
+
+```
+⚠ Computer Use required for native app testing.
+Enable via: /mcp → computer-use (macOS only, Pro/Max plan required)
+```
+
+## Output
+
+Test report with screenshots and issue list, saved to current directory.

package/departments/dev/skills/code-review/SKILL.md

@@ -24,3 +24,16 @@ Follow the [Browser Integration Pattern](/arka) for availability checking.
 - [BROWSER] Open the application in the browser and verify UI changes visually
 - [BROWSER] Check browser console for JavaScript errors or warnings
 - [BROWSER] If CSS/layout changes: compare before/after visually
+
+## Computer Use Steps
+
+Follow the [Computer Use Availability Check](/arka) for availability checking.
+
+- [COMPUTER] If native app: launch and click through UI to verify changes visually
+
+## Scheduling ⏰
+
+```
+/loop 30m check open PRs on this repo and summarize any that need review
+/schedule weekdays at 9am — review all open PRs and post summary
+```

package/departments/dev/skills/security-audit/SKILL.md

@@ -76,6 +76,19 @@ Follow the [Browser Integration Pattern](/arka) for availability checking.
 - [BROWSER] Open console and check for CSP (Content Security Policy) headers
 - [BROWSER] Test authentication flows: login, logout, session expiry
 
+## Computer Use Steps
+
+Follow the [Computer Use Availability Check](/arka) for availability checking.
+
+- [COMPUTER] Launch app and test input fields, permissions dialogs, and authentication flows via GUI
+
+## Scheduling ⏰
+
+```
+/schedule weekly — run npm audit and pip audit, flag any critical vulnerabilities
+/schedule daily at 8am — check for new CVEs affecting project dependencies
+```
+
 ## References
 
 - [owasp-2025-deep.md](references/owasp-2025-deep.md) — OWASP Top 10 (2025) with vulnerable and fixed code examples, testing methodology, and tools

package/departments/dev/skills/tdd-cycle/SKILL.md

@@ -61,3 +61,16 @@ Follow the [Browser Integration Pattern](/arka) for availability checking.
 
 - [BROWSER] After tests pass, if web app: open localhost in browser and verify the feature works visually
 - [BROWSER] Check console for runtime errors that tests might not catch
+
+## Computer Use Steps
+
+Follow the [Computer Use Availability Check](/arka) for availability checking.
+
+- [COMPUTER] If native/mobile app: build, launch, and verify feature in the running app or iOS Simulator
+
+## Scheduling ⏰
+
+```
+/loop 5m run pytest and notify if any test fails
+/loop 10m run full test suite, report only failures
+```

package/departments/ecom/skills/analytics/SKILL.md

@@ -25,3 +25,16 @@ Follow the [Browser Integration Pattern](/arka) for availability checking.
 - [BROWSER] Test conversion tracking: complete a purchase flow and verify events fire
 - [BROWSER] Check Meta Pixel fires correctly (search for fbq in console)
 - [BROWSER] Verify Google Tag Manager container loads
+
+## Computer Use Steps
+
+Follow the [Computer Use Availability Check](/arka) for availability checking.
+
+- [COMPUTER] Open analytics dashboards in native apps (Mixpanel, Amplitude) and verify event tracking
+
+## Scheduling ⏰
+
+```
+/loop 1h check store conversion rate and flag if below 2% threshold
+/schedule daily at 9am — morning e-commerce metrics summary: revenue, orders, conversion, AOV
+```

package/departments/ecom/skills/store-audit/SKILL.md

@@ -27,3 +27,16 @@ Follow the [Browser Integration Pattern](/arka) for availability checking.
 - [BROWSER] Check page load performance via console timing (Performance API)
 - [BROWSER] Verify search functionality works correctly
 - [BROWSER] Test navigation menu and footer links
+
+## Computer Use Steps
+
+Follow the [Computer Use Availability Check](/arka) for availability checking.
+
+- [COMPUTER] If mobile app: open in iOS Simulator, test purchase flow, verify responsiveness
+
+## Scheduling ⏰
+
+```
+/schedule daily at 8am — quick store health check: uptime, broken links, price errors
+/loop 1h check store homepage and top 5 product pages for errors or downtime
+```

package/departments/ops/skills/dashboard-build/SKILL.md

@@ -25,3 +25,16 @@ Follow the [Browser Integration Pattern](/arka) for availability checking.
 - [BROWSER] Check that data loads and updates in real-time (if WebSocket)
 - [BROWSER] Test responsive layout at different screen sizes
 - [BROWSER] Verify charts, tables, and graphs display correct data
+
+## Computer Use Steps
+
+Follow the [Computer Use Availability Check](/arka) for availability checking.
+
+- [COMPUTER] Launch dashboard app and verify widgets, charts, and real-time data render correctly
+
+## Scheduling ⏰
+
+```
+/loop 10m check dashboard API health and flag if any endpoint returns errors
+/schedule hourly — verify dashboard data freshness and alert if stale
+```

package/departments/ops/skills/workflow-automate/SKILL.md

@@ -44,4 +44,17 @@ Follow the [Browser Integration Pattern](/arka) for availability checking.
 - [BROWSER] Test the automated workflow end-to-end by triggering it and watching the result in the browser
 - [BROWSER] Verify notifications and emails arrive correctly
 
+## Computer Use Steps
+
+Follow the [Computer Use Availability Check](/arka) for availability checking.
+
+- [COMPUTER] Open desktop apps (Slack, Notion, calendar apps) to verify automation results
+
+## Scheduling ⏰
+
+```
+/loop 15m check N8N workflow executions, flag any failures in the last hour
+/schedule hourly — monitor all active automations and report error rate
+```
+
 ## Output → Workflow diagram + platform config + error handling spec

package/departments/strategy/skills/five-forces/SKILL.md

@@ -80,4 +80,17 @@ Follow the [Browser Integration Pattern](/arka) for availability checking.
 - [BROWSER] Check competitor positioning statements and messaging from their homepage
 - [BROWSER] Extract supplier/partner information from competitor sites when available
 
+## Computer Use Steps
+
+Follow the [Computer Use Availability Check](/arka) for availability checking.
+
+- [COMPUTER] Open competitor native apps, screenshot UX patterns, extract feature comparisons
+
+## Scheduling ⏰
+
+```
+/schedule weekly — check competitor pricing pages for changes and summarize differences
+/schedule monthly — full five forces reassessment for the industry
+```
+
 ## Output → Obsidian: `WizardingCode/Strategy/Analysis/FIVE-FORCES-<industry>-<date>.md`

package/departments/strategy/skills/position/SKILL.md

@@ -25,3 +25,16 @@ Follow the [Browser Integration Pattern](/arka) for availability checking.
 - [BROWSER] Capture visual identity elements: color schemes, typography, imagery style
 - [BROWSER] Check social proof: testimonials, client logos, case studies
 - [BROWSER] Compare pricing pages side-by-side
+
+## Computer Use Steps
+
+Follow the [Computer Use Availability Check](/arka) for availability checking.
+
+- [COMPUTER] Launch competitor apps side-by-side, compare UI/UX, capture positioning differences
+
+## Scheduling ⏰
+
+```
+/schedule monthly — review competitor positioning changes: taglines, messaging, pricing
+/schedule quarterly — full competitive positioning reassessment
+```

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "arkaos",
-  "version": "2.5.0",
+  "version": "2.5.2",
   "description": "The Operating System for AI Agent Teams",
   "type": "module",
   "bin": {

package/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "arkaos-core"
-version = "2.5.0"
+version = "2.5.2"
 description = "Core engine for ArkaOS — The Operating System for AI Agent Teams"
 readme = "README.md"
 license = {text = "MIT"}