Ark DevSpace
Run Ark from cloned source using devspace
Best use case
Ark DevSpace is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Run Ark from cloned source using devspace
Teams using Ark DevSpace should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/ark-devspace/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How Ark DevSpace Compares
| Feature / Agent | Ark DevSpace | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Run Ark from cloned source using devspace
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Ark DevSpace Run Ark from a cloned repository using devspace for development/PR testing. ## CRITICAL: Failure Behavior **If devspace fails, you MUST STOP and report the error. Do NOT try alternative approaches like ark-cli or npm install. DevSpace failures must be diagnosed and fixed.** ## When to use - Testing Ark pull requests - Running Ark from source code ## Prerequisites - Ark repo cloned (e.g., `/workspace/ark` or `/workspace/agents-at-scale-ark`) - Kind cluster running (use kind-setup skill if needed) - Verify cluster: `kubectl cluster-info` ## Steps 1. **Navigate to ark repo** ```bash cd /workspace/ark # or /workspace/agents-at-scale-ark ``` 2. **Deploy with devspace (non-interactive)** ```bash devspace deploy ``` This deploys all components and exits. Check the exit code - if non-zero, STOP and troubleshoot. 3. **Verify deployment succeeded** ```bash kubectl get pods -n ark-system kubectl get pods -n cert-manager ``` 4. **Wait for pods to be ready** ```bash kubectl wait --for=condition=Ready pods --all -n ark-system --timeout=300s ``` 5. **Check services** ```bash kubectl get svc -n ark-system ``` ## Troubleshooting ### Check devspace logs ```bash ls -la .devspace/logs/ cat .devspace/logs/default.log ``` ### Common failures 1. **"namespace not found"** - Set namespace first ```bash devspace use namespace ark-system ``` 2. **"image pull error"** - Build images locally ```bash devspace build ``` 3. **Cert-manager not ready** - Wait for it ```bash kubectl wait --for=condition=Available deployment --all -n cert-manager --timeout=120s ``` 4. **Cluster connectivity** - Re-export kubeconfig ```bash kind export kubeconfig --name ark-cluster --internal ``` ### If devspace exits with error 1. Check the exit code and error message 2. Check `.devspace/logs/` for detailed logs 3. Check pod status: `kubectl get pods -A` 4. Check events: `kubectl get events -A --sort-by='.lastTimestamp'` 5. **STOP and report the specific error - do not try workarounds** ## Cleanup ```bash devspace purge kubectl delete ns ark-system --ignore-not-found ```
Related Skills
bgo
Automates the complete Blender build-go workflow, from building and packaging your extension/add-on to removing old versions, installing, enabling, and launching Blender for quick testing and iteration.
accessibility-ux-audit
Audit and enhance accessibility and UX across all pages and components.
accessibility-testing
WCAG 2.2 compliance testing, screen reader validation, and inclusive design verification. Use when ensuring legal compliance (ADA, Section 508), testing for disabilities, or building accessible applications for 1 billion disabled users globally.
accessibility-rules
Concise accessibility checklist and practices for components in the repository. Use when implementing UI to ensure keyboard, screen reader, and focus semantics.
accessibility-planning
Plan accessibility compliance - WCAG 2.2, Section 508, EN 301 549, inclusive design principles, audit planning, and remediation strategies.
accessibility-design
WCAG 2.1 AA compliance patterns, screen reader compatibility, keyboard navigation, and ARIA best practices. Use when implementing accessible interfaces, reviewing UI components, or auditing accessibility compliance. Covers semantic HTML, focus management, color contrast, and assistive technology testing.
accessibility-design-checklist
Эксперт по accessibility дизайну. Используй для WCAG, a11y чеклистов и inclusive design.
accessibility-design-checker
Ensures designs meet accessibility requirements including WCAG compliance, color contrast, keyboard navigation, screen reader support, and focus management. Reviews designs for accessibility issues and provides recommendations.
accessibility-contrast-audit
[Design System] Quantitative accessibility audit for UI - contrast ratios, font sizes, tap targets, heading hierarchy. Use when (1) checking WCAG color contrast compliance, (2) auditing text sizes for readability, (3) validating touch/click target sizes, (4) reviewing heading structure and landmarks, (5) user asks to 'check accessibility', 'audit contrast', 'WCAG compliance', or 'a11y check'.
accessibility-compliance
Implement WCAG 2.2 compliant interfaces with mobile accessibility, inclusive design patterns, and assistive technology support. Use when auditing accessibility, implementing ARIA patterns, building for screen readers, or ensuring inclusive user experiences.
accessibility-by-default
Treats accessibility as a baseline requirement, not a feature. WCAG 2.1/2.2 AA principles embedded into every decision.
accessibility-basic-check
Run a basic accessibility checklist for UI changes. Use when a junior developer needs quick a11y guidance.