skills.rest
briannadoubt
briannadoubtCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

raven-dev

Automate the Raven build-serve-test-debug workflow for Swift WASM apps.

Updated Feb 4, 2026
Search Tags:#development#build#debug#swift#wasm#serve#raven
One-click install
npx skills add https://github.com/briannadoubt/Raven --skill raven-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: raven-dev
Source: https://github.com/briannadoubt/Raven/tree/main/.codex/skills/raven-dev
Command: npx skills add https://github.com/briannadoubt/Raven --skill raven-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Raven development workflow streamlines building, serving, testing, and debugging Swift WASM apps and Raven runtime changes, reducing iteration time and increasing feedback velocity.

Core Features & Use Cases

  • Provides a repeatable build-serve-test loop for Raven example apps
  • Enables browser-based validation of rendering, DOM events, and runtime changes
  • Supports end-to-end debugging with quick iteration cycles in a local development environment

Quick Start

Run raven dev from the Example/TodoApp directory to start the local WASM UI server.

Frequently Asked Questions about raven-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build and serve Swift WASM apps locally?▼

To build and serve Swift WASM apps locally, you can run `raven dev` from an example project directory to start the local UI server and automate the build-serve-test loop.

What is the best way to debug Raven runtime changes in a local environment?▼

The best way to debug Raven runtime changes is using an automated workflow that coordinates the Swift build process with the Raven CLI dev server, enabling quick iteration cycles and browser-based validation in your local environment.

Can I validate DOM events and rendering for Swift WASM apps in the browser?▼

Yes, you can validate DOM events and rendering for Swift WASM apps by running the local development server, which enforces repeatable build steps and supports browser-based validation for example projects.

Do I need the Raven CLI to test Swift WASM applications?▼

You need the Raven CLI dev server to automate the end-to-end testing workflow for Swift WASM applications, as it coordinates the build process and serves the UI for browser validation.

Why does my Swift WASM development loop lack repeatable build steps?▼

Your Swift WASM development loop may lack repeatable build steps if the workflow is not enforcing safe boundaries between the build process, dev server, and browser validation, which an automated development workflow provides.

What limitations exist when using raven-dev for local development?▼

The raven-dev workflow enforces safe boundaries and repeatable steps for local development environments, meaning it is specifically scoped to local build-serve-test loops rather than production deployment or continuous integration pipelines.

Related Skills

Explore More Software Engineering Skills→
briannadoubtbriannadoubt

swift-wasm

Install and validate the Swift 6.2 WASM toolchain for WebAssembly targets.

Community
Advanced
mambisimambisi

pocopine-cli

Orchestrate build, development, and deployment for Rust/WASM Pocopine projects.

Community
Advanced
AskTinNguyenAskTinNguyen

browser-testing-with-devtools

Inspect live pages, DOM, console logs, and network activity via Chrome DevTools MCP.

Community
Advanced
radius-projectradius-project
1.7k

radius-build-cli

Builds the Radius CLI binary from source using Makefile targets with optional debug and version injection.

Official
Intermediate