arkaos 2.4.3 → 2.5.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/VERSION CHANGED
@@ -1 +1 @@
1
- 2.4.3
1
+ 2.5.0
@@ -16,3 +16,11 @@ Full brand identity: strategy, verbal, visual in the correct order (never skip t
16
16
  ## Output
17
17
 
18
18
  Complete brand identity package saved to Obsidian
19
+
20
+ ## Browser Steps
21
+
22
+ Follow the [Browser Integration Pattern](/arka) for availability checking.
23
+
24
+ - [BROWSER] Open the website/app and verify brand elements match the identity system (colors, typography, spacing)
25
+ - [BROWSER] Compare generated assets side-by-side with the live site
26
+ - [BROWSER] Check favicon, og:image, and meta branding elements
@@ -16,3 +16,13 @@ UX heuristic audit: evaluate interface against Nielsen's 10 heuristics.
16
16
  ## Output
17
17
 
18
18
  Heuristic audit report with severity ratings and fix recommendations
19
+
20
+ ## Browser Steps
21
+
22
+ Follow the [Browser Integration Pattern](/arka) for availability checking.
23
+
24
+ - [BROWSER] Navigate the site following primary user flows (onboarding, core action, checkout)
25
+ - [BROWSER] Test accessibility: tab navigation, focus indicators, color contrast
26
+ - [BROWSER] Capture screenshots of key screens for the UX audit report
27
+ - [BROWSER] Check responsive design at mobile, tablet, and desktop breakpoints
28
+ - [BROWSER] Verify loading states, error states, and empty states render correctly
@@ -16,3 +16,11 @@ Code review against Clean Code and SOLID. Checks naming, SRP, DIP, test coverage
16
16
  ## Output
17
17
 
18
18
  Review report: BLOCKER/WARNING/NOTE with line references and fix suggestions
19
+
20
+ ## Browser Steps
21
+
22
+ Follow the [Browser Integration Pattern](/arka) for availability checking.
23
+
24
+ - [BROWSER] Open the application in the browser and verify UI changes visually
25
+ - [BROWSER] Check browser console for JavaScript errors or warnings
26
+ - [BROWSER] If CSS/layout changes: compare before/after visually
@@ -0,0 +1,49 @@
1
+ ---
2
+ name: dev/demo-gif
3
+ description: >
4
+ Record a GIF demo of a user flow in the browser. Navigates to a URL,
5
+ executes described interactions, and saves the recording as a GIF file.
6
+ Requires browser integration (claude --chrome or /chrome).
7
+ allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
8
+ ---
9
+
10
+ # Demo GIF Recording — `/dev demo-gif`
11
+
12
+ > **Agent:** Paulo (Tech Lead) | Requires: Browser integration (`/chrome`)
13
+
14
+ ## Command
15
+
16
+ ```
17
+ /dev demo-gif <url> <flow-description>
18
+ ```
19
+
20
+ ## What It Does
21
+
22
+ Records a GIF of a user flow in the browser for demos, documentation, or bug reports.
23
+
24
+ ## Workflow
25
+
26
+ 1. **Check browser availability** — follow [Browser Integration Pattern](/arka)
27
+ 2. **Navigate** to the provided URL
28
+ 3. **Execute the flow** step by step as described:
29
+ - Parse the flow description into discrete actions (click, type, navigate, scroll)
30
+ - Execute each action with a brief pause between steps for visual clarity
31
+ 4. **Record** the session as a GIF
32
+ 5. **Save** the GIF to the current directory with a descriptive filename
33
+ 6. **Report** file path, file size, and duration
34
+
35
+ ## Example
36
+
37
+ ```
38
+ /dev demo-gif http://localhost:3000 "login with test@example.com, navigate to dashboard, create a new project, fill in the name 'My Project', click save"
39
+ ```
40
+
41
+ ## Fallback (No Browser)
42
+
43
+ ```
44
+ ⚠ Browser required for demo recording. Enable with: claude --chrome or /chrome
45
+ ```
46
+
47
+ ## Output
48
+
49
+ GIF file saved to current working directory: `demo-<timestamp>.gif`
@@ -67,6 +67,15 @@ Permissions-Policy: camera=(), microphone=(), geolocation=()
67
67
  ### Recommendation: BLOCK release until C1 and H1 resolved
68
68
  ```
69
69
 
70
+ ## Browser Steps
71
+
72
+ Follow the [Browser Integration Pattern](/arka) for availability checking.
73
+
74
+ - [BROWSER] Navigate to the application and test input fields for XSS (script injection)
75
+ - [BROWSER] Verify HTTPS is enforced (check URL bar and certificate)
76
+ - [BROWSER] Open console and check for CSP (Content Security Policy) headers
77
+ - [BROWSER] Test authentication flows: login, logout, session expiry
78
+
70
79
  ## References
71
80
 
72
81
  - [owasp-2025-deep.md](references/owasp-2025-deep.md) — OWASP Top 10 (2025) with vulnerable and fixed code examples, testing methodology, and tools
@@ -54,3 +54,10 @@ REPEAT
54
54
  | React/Next | Jest | `npx jest` |
55
55
  | Python | pytest | `python -m pytest` |
56
56
  | E2E | Playwright | `npx playwright test` |
57
+
58
+ ## Browser Steps
59
+
60
+ Follow the [Browser Integration Pattern](/arka) for availability checking.
61
+
62
+ - [BROWSER] After tests pass, if web app: open localhost in browser and verify the feature works visually
63
+ - [BROWSER] Check console for runtime errors that tests might not catch
@@ -16,3 +16,12 @@ E-commerce analytics: AOV, conversion rate, CLV, ROAS, cart abandonment rate.
16
16
  ## Output
17
17
 
18
18
  Analytics dashboard with funnel visualization and benchmark comparison
19
+
20
+ ## Browser Steps
21
+
22
+ Follow the [Browser Integration Pattern](/arka) for availability checking.
23
+
24
+ - [BROWSER] Open the store and verify GA4 tracking fires on page load (check Network tab for collect requests)
25
+ - [BROWSER] Test conversion tracking: complete a purchase flow and verify events fire
26
+ - [BROWSER] Check Meta Pixel fires correctly (search for fbq in console)
27
+ - [BROWSER] Verify Google Tag Manager container loads
@@ -0,0 +1,55 @@
1
+ ---
2
+ name: ecom/browse-competitor
3
+ description: >
4
+ Navigate a competitor's e-commerce site and extract structured intelligence:
5
+ product categories, price ranges, promotions, layout patterns, and screenshots.
6
+ Requires browser integration (claude --chrome or /chrome).
7
+ allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
8
+ ---
9
+
10
+ # Browse Competitor — `/ecom browse-competitor`
11
+
12
+ > **Agent:** Ricardo (E-Commerce Director) | Requires: Browser integration (`/chrome`)
13
+
14
+ ## Command
15
+
16
+ ```
17
+ /ecom browse-competitor <url>
18
+ ```
19
+
20
+ ## What It Does
21
+
22
+ Navigates a competitor's e-commerce site and extracts structured competitive intelligence.
23
+
24
+ ## Workflow
25
+
26
+ 1. **Check browser availability** — follow [Browser Integration Pattern](/arka)
27
+ 2. **Navigate** to the competitor homepage
28
+ 3. **Extract** structured data:
29
+ - Product categories and subcategories
30
+ - Price ranges (min, max, average per category)
31
+ - Current promotions and discounts
32
+ - Layout patterns (grid, list, hero sections)
33
+ - Navigation structure
34
+ - Payment methods offered
35
+ - Shipping information
36
+ 4. **Capture screenshots** of:
37
+ - Homepage
38
+ - A product listing page
39
+ - A product detail page
40
+ - Cart page (if accessible)
41
+ - Footer (payment/shipping badges)
42
+ 5. **Generate report** in Obsidian with screenshots and structured findings
43
+
44
+ ## Fallback (No Browser)
45
+
46
+ ```
47
+ ⚠ Browser not available. Using WebFetch for partial extraction.
48
+ For full competitor analysis with screenshots, enable: /chrome
49
+ ```
50
+
51
+ Falls back to WebFetch/WebSearch for basic HTML extraction (no JS rendering, no screenshots, no interaction).
52
+
53
+ ## Output
54
+
55
+ Obsidian report: `Projects/<ecosystem>/Strategy/Competitors/<domain>.md`
@@ -16,3 +16,14 @@ Full store audit: UX, SEO, performance, content, conversion with 5 parallel agen
16
16
  ## Output
17
17
 
18
18
  Comprehensive audit report with scores per area and prioritized fixes
19
+
20
+ ## Browser Steps
21
+
22
+ Follow the [Browser Integration Pattern](/arka) for availability checking.
23
+
24
+ - [BROWSER] Open store URL and test the full checkout flow: browse → add to cart → checkout → payment → confirmation
25
+ - [BROWSER] Test mobile responsiveness at different viewport sizes (375px, 768px, 1024px)
26
+ - [BROWSER] Capture screenshots of homepage, product page, cart, and checkout for the audit report
27
+ - [BROWSER] Check page load performance via console timing (Performance API)
28
+ - [BROWSER] Verify search functionality works correctly
29
+ - [BROWSER] Test navigation menu and footer links
@@ -16,3 +16,12 @@ Operational dashboard design: select metrics, define targets, build layout.
16
16
  ## Output
17
17
 
18
18
  Dashboard spec with metrics, targets, data sources, and alert thresholds
19
+
20
+ ## Browser Steps
21
+
22
+ Follow the [Browser Integration Pattern](/arka) for availability checking.
23
+
24
+ - [BROWSER] Open the dashboard in browser and verify all widgets render correctly
25
+ - [BROWSER] Check that data loads and updates in real-time (if WebSocket)
26
+ - [BROWSER] Test responsive layout at different screen sizes
27
+ - [BROWSER] Verify charts, tables, and graphs display correct data
@@ -36,4 +36,12 @@ allowed-tools: [Read, Write, Edit, Agent, WebFetch]
36
36
  - Alert notification on failure (Slack/email)
37
37
  - Idempotency: safe to retry without duplicates
38
38
 
39
+ ## Browser Steps
40
+
41
+ Follow the [Browser Integration Pattern](/arka) for availability checking.
42
+
43
+ - [BROWSER] Open the relevant web tools (Gmail, Google Calendar, ClickUp, N8N) to verify automation results
44
+ - [BROWSER] Test the automated workflow end-to-end by triggering it and watching the result in the browser
45
+ - [BROWSER] Verify notifications and emails arrive correctly
46
+
39
47
  ## Output → Workflow diagram + platform config + error handling spec
@@ -0,0 +1,53 @@
1
+ ---
2
+ name: strat/extract-data
3
+ description: >
4
+ Navigate a web page and extract structured data: tables, lists, prices,
5
+ product listings. Supports CSV, markdown, and JSON output formats.
6
+ Requires browser integration (claude --chrome or /chrome).
7
+ allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
8
+ ---
9
+
10
+ # Extract Data — `/strat extract-data`
11
+
12
+ > **Agent:** Tomas (Chief Strategist) | Requires: Browser integration (`/chrome`)
13
+
14
+ ## Command
15
+
16
+ ```
17
+ /strat extract-data <url> [format]
18
+ ```
19
+
20
+ Formats: `csv` (default), `markdown`, `json`
21
+
22
+ ## What It Does
23
+
24
+ Navigates a web page and extracts structured data (tables, lists, prices, repeated patterns) into a clean format.
25
+
26
+ ## Workflow
27
+
28
+ 1. **Check browser availability** — follow [Browser Integration Pattern](/arka)
29
+ 2. **Navigate** to the URL (handles JS-rendered content, pagination, infinite scroll)
30
+ 3. **Identify structured data** on the page:
31
+ - HTML tables
32
+ - Repeated list patterns (product cards, directory entries)
33
+ - Price/value data
34
+ - Tabular data rendered via JavaScript
35
+ 4. **Extract** data into structured format
36
+ 5. **Handle pagination** if detected (ask user: "Found pagination — extract all pages?")
37
+ 6. **Output** in requested format:
38
+ - CSV: saved to `extracted-<domain>-<timestamp>.csv`
39
+ - Markdown: displayed inline as table
40
+ - JSON: saved to `extracted-<domain>-<timestamp>.json`
41
+
42
+ ## Fallback (No Browser)
43
+
44
+ ```
45
+ ⚠ Browser not available. Using WebFetch for basic extraction.
46
+ For interactive pages (JS-rendered, pagination), enable: /chrome
47
+ ```
48
+
49
+ Falls back to WebFetch for static HTML extraction only.
50
+
51
+ ## Output
52
+
53
+ File saved to current directory or displayed inline (markdown format).
@@ -71,4 +71,13 @@ allowed-tools: [Read, Write, Edit, Agent, WebFetch, WebSearch]
71
71
  3. ...
72
72
  ```
73
73
 
74
+ ## Browser Steps
75
+
76
+ Follow the [Browser Integration Pattern](/arka) for availability checking.
77
+
78
+ - [BROWSER] Navigate to competitor websites and extract real-time pricing data
79
+ - [BROWSER] Capture screenshots of competitor product pages, pricing pages, and feature comparisons
80
+ - [BROWSER] Check competitor positioning statements and messaging from their homepage
81
+ - [BROWSER] Extract supplier/partner information from competitor sites when available
82
+
74
83
  ## Output → Obsidian: `WizardingCode/Strategy/Analysis/FIVE-FORCES-<industry>-<date>.md`
@@ -16,3 +16,12 @@ Competitive positioning: alternatives, unique capabilities, value, target, categ
16
16
  ## Output
17
17
 
18
18
  Positioning statement + perceptual map + competitive differentiation
19
+
20
+ ## Browser Steps
21
+
22
+ Follow the [Browser Integration Pattern](/arka) for availability checking.
23
+
24
+ - [BROWSER] Visit competitor websites and extract their positioning: taglines, hero copy, value propositions
25
+ - [BROWSER] Capture visual identity elements: color schemes, typography, imagery style
26
+ - [BROWSER] Check social proof: testimonials, client logos, case studies
27
+ - [BROWSER] Compare pricing pages side-by-side
@@ -1,7 +1,20 @@
1
1
  {
2
2
  "_meta": {
3
3
  "description": "ARKA OS — Project Ecosystem Registry",
4
- "updated": "2026-03-15"
4
+ "updated": "2026-04-06"
5
5
  },
6
- "ecosystems": {}
6
+ "ecosystems": {
7
+ "wizardingcode": {
8
+ "projects": [
9
+ {
10
+ "name": "arka-os",
11
+ "role": "product",
12
+ "stack": "Python + Node.js + React",
13
+ "path": "/Users/andreagroferreira/AIProjects/arka-os",
14
+ "skill": "/platform-arka",
15
+ "description": "ArkaOS — The Operating System for AI Agent Teams"
16
+ }
17
+ ]
18
+ }
19
+ }
7
20
  }
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "arkaos",
3
- "version": "2.4.3",
3
+ "version": "2.5.0",
4
4
  "description": "The Operating System for AI Agent Teams",
5
5
  "type": "module",
6
6
  "bin": {
package/pyproject.toml CHANGED
@@ -1,6 +1,6 @@
1
1
  [project]
2
2
  name = "arkaos-core"
3
- version = "2.4.3"
3
+ version = "2.5.0"
4
4
  description = "Core engine for ArkaOS — The Operating System for AI Agent Teams"
5
5
  readme = "README.md"
6
6
  license = {text = "MIT"}
@@ -345,16 +345,7 @@ def job_cancel(job_id: str):
345
345
  return {"error": "Can only cancel queued jobs"}
346
346
 
347
347
 
348
- @app.post("/api/knowledge/upload")
349
- async def knowledge_upload(file: Any = None):
350
- """Upload a file for ingestion."""
351
- from fastapi import UploadFile, File as FastAPIFile
352
- # Re-import with proper type
353
- pass
354
-
355
-
356
- # Actual upload endpoint with proper signature
357
- from fastapi import UploadFile, File as FastAPIFile
348
+ from fastapi import UploadFile
358
349
 
359
350
  @app.post("/api/knowledge/upload-file")
360
351
  async def knowledge_upload_file(file: UploadFile):