arkaos 2.5.1 → 2.5.2
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 +1 -1
- package/departments/brand/skills/ux-audit/SKILL.md +7 -0
- package/departments/dev/skills/code-review/SKILL.md +7 -0
- package/departments/dev/skills/security-audit/SKILL.md +7 -0
- package/departments/dev/skills/tdd-cycle/SKILL.md +7 -0
- package/departments/ecom/skills/analytics/SKILL.md +7 -0
- package/departments/ecom/skills/store-audit/SKILL.md +7 -0
- package/departments/ops/skills/dashboard-build/SKILL.md +7 -0
- package/departments/ops/skills/workflow-automate/SKILL.md +7 -0
- package/departments/strategy/skills/five-forces/SKILL.md +7 -0
- package/departments/strategy/skills/position/SKILL.md +7 -0
- package/package.json +1 -1
- package/pyproject.toml +1 -1
package/VERSION
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
2.5.
|
|
1
|
+
2.5.2
|
|
@@ -32,3 +32,10 @@ Follow the [Browser Integration Pattern](/arka) for availability checking.
|
|
|
32
32
|
Follow the [Computer Use Availability Check](/arka) for availability checking.
|
|
33
33
|
|
|
34
34
|
- [COMPUTER] Launch the native app, test user flows, screenshot each screen for the audit report
|
|
35
|
+
|
|
36
|
+
## Scheduling ⏰
|
|
37
|
+
|
|
38
|
+
```
|
|
39
|
+
/schedule weekly — run Lighthouse audit on main pages, flag performance regressions
|
|
40
|
+
/schedule monthly — full UX heuristic review of core user flows
|
|
41
|
+
```
|
|
@@ -30,3 +30,10 @@ Follow the [Browser Integration Pattern](/arka) for availability checking.
|
|
|
30
30
|
Follow the [Computer Use Availability Check](/arka) for availability checking.
|
|
31
31
|
|
|
32
32
|
- [COMPUTER] If native app: launch and click through UI to verify changes visually
|
|
33
|
+
|
|
34
|
+
## Scheduling ⏰
|
|
35
|
+
|
|
36
|
+
```
|
|
37
|
+
/loop 30m check open PRs on this repo and summarize any that need review
|
|
38
|
+
/schedule weekdays at 9am — review all open PRs and post summary
|
|
39
|
+
```
|
|
@@ -82,6 +82,13 @@ Follow the [Computer Use Availability Check](/arka) for availability checking.
|
|
|
82
82
|
|
|
83
83
|
- [COMPUTER] Launch app and test input fields, permissions dialogs, and authentication flows via GUI
|
|
84
84
|
|
|
85
|
+
## Scheduling ⏰
|
|
86
|
+
|
|
87
|
+
```
|
|
88
|
+
/schedule weekly — run npm audit and pip audit, flag any critical vulnerabilities
|
|
89
|
+
/schedule daily at 8am — check for new CVEs affecting project dependencies
|
|
90
|
+
```
|
|
91
|
+
|
|
85
92
|
## References
|
|
86
93
|
|
|
87
94
|
- [owasp-2025-deep.md](references/owasp-2025-deep.md) — OWASP Top 10 (2025) with vulnerable and fixed code examples, testing methodology, and tools
|
|
@@ -67,3 +67,10 @@ Follow the [Browser Integration Pattern](/arka) for availability checking.
|
|
|
67
67
|
Follow the [Computer Use Availability Check](/arka) for availability checking.
|
|
68
68
|
|
|
69
69
|
- [COMPUTER] If native/mobile app: build, launch, and verify feature in the running app or iOS Simulator
|
|
70
|
+
|
|
71
|
+
## Scheduling ⏰
|
|
72
|
+
|
|
73
|
+
```
|
|
74
|
+
/loop 5m run pytest and notify if any test fails
|
|
75
|
+
/loop 10m run full test suite, report only failures
|
|
76
|
+
```
|
|
@@ -31,3 +31,10 @@ Follow the [Browser Integration Pattern](/arka) for availability checking.
|
|
|
31
31
|
Follow the [Computer Use Availability Check](/arka) for availability checking.
|
|
32
32
|
|
|
33
33
|
- [COMPUTER] Open analytics dashboards in native apps (Mixpanel, Amplitude) and verify event tracking
|
|
34
|
+
|
|
35
|
+
## Scheduling ⏰
|
|
36
|
+
|
|
37
|
+
```
|
|
38
|
+
/loop 1h check store conversion rate and flag if below 2% threshold
|
|
39
|
+
/schedule daily at 9am — morning e-commerce metrics summary: revenue, orders, conversion, AOV
|
|
40
|
+
```
|
|
@@ -33,3 +33,10 @@ Follow the [Browser Integration Pattern](/arka) for availability checking.
|
|
|
33
33
|
Follow the [Computer Use Availability Check](/arka) for availability checking.
|
|
34
34
|
|
|
35
35
|
- [COMPUTER] If mobile app: open in iOS Simulator, test purchase flow, verify responsiveness
|
|
36
|
+
|
|
37
|
+
## Scheduling ⏰
|
|
38
|
+
|
|
39
|
+
```
|
|
40
|
+
/schedule daily at 8am — quick store health check: uptime, broken links, price errors
|
|
41
|
+
/loop 1h check store homepage and top 5 product pages for errors or downtime
|
|
42
|
+
```
|
|
@@ -31,3 +31,10 @@ Follow the [Browser Integration Pattern](/arka) for availability checking.
|
|
|
31
31
|
Follow the [Computer Use Availability Check](/arka) for availability checking.
|
|
32
32
|
|
|
33
33
|
- [COMPUTER] Launch dashboard app and verify widgets, charts, and real-time data render correctly
|
|
34
|
+
|
|
35
|
+
## Scheduling ⏰
|
|
36
|
+
|
|
37
|
+
```
|
|
38
|
+
/loop 10m check dashboard API health and flag if any endpoint returns errors
|
|
39
|
+
/schedule hourly — verify dashboard data freshness and alert if stale
|
|
40
|
+
```
|
|
@@ -50,4 +50,11 @@ Follow the [Computer Use Availability Check](/arka) for availability checking.
|
|
|
50
50
|
|
|
51
51
|
- [COMPUTER] Open desktop apps (Slack, Notion, calendar apps) to verify automation results
|
|
52
52
|
|
|
53
|
+
## Scheduling ⏰
|
|
54
|
+
|
|
55
|
+
```
|
|
56
|
+
/loop 15m check N8N workflow executions, flag any failures in the last hour
|
|
57
|
+
/schedule hourly — monitor all active automations and report error rate
|
|
58
|
+
```
|
|
59
|
+
|
|
53
60
|
## Output → Workflow diagram + platform config + error handling spec
|
|
@@ -86,4 +86,11 @@ Follow the [Computer Use Availability Check](/arka) for availability checking.
|
|
|
86
86
|
|
|
87
87
|
- [COMPUTER] Open competitor native apps, screenshot UX patterns, extract feature comparisons
|
|
88
88
|
|
|
89
|
+
## Scheduling ⏰
|
|
90
|
+
|
|
91
|
+
```
|
|
92
|
+
/schedule weekly — check competitor pricing pages for changes and summarize differences
|
|
93
|
+
/schedule monthly — full five forces reassessment for the industry
|
|
94
|
+
```
|
|
95
|
+
|
|
89
96
|
## Output → Obsidian: `WizardingCode/Strategy/Analysis/FIVE-FORCES-<industry>-<date>.md`
|
|
@@ -31,3 +31,10 @@ Follow the [Browser Integration Pattern](/arka) for availability checking.
|
|
|
31
31
|
Follow the [Computer Use Availability Check](/arka) for availability checking.
|
|
32
32
|
|
|
33
33
|
- [COMPUTER] Launch competitor apps side-by-side, compare UI/UX, capture positioning differences
|
|
34
|
+
|
|
35
|
+
## Scheduling ⏰
|
|
36
|
+
|
|
37
|
+
```
|
|
38
|
+
/schedule monthly — review competitor positioning changes: taglines, messaging, pricing
|
|
39
|
+
/schedule quarterly — full competitive positioning reassessment
|
|
40
|
+
```
|
package/package.json
CHANGED