Corey Alix ca0v

ca0v — Personal Agent Operating Procedures (Bootstrap)

This is the standing entry point for any agent working with ca0v or across his projects. Internalize it at the start of relevant sessions. It composes the core lenses and infrastructure that make work productive and token-efficient.

The goal of ca0v's practices is a codebase and workflow that becomes increasingly agent-friendly: higher productivity for both agents and humans, lower token waste (less exploration, fewer backtracks, faster resumes, more "obviously correct" first attempts).

1. Core Decision Lens: /wwjd

Activate this for every autonomous decision, recommendation, or edit.

Agent Brief: WWJD — What Would Justify Doing (Agent-First Decision Lens)

Synthesized from production practice in dw-ems (.claude/skills/wwjd) and dw-aware (.claude/commands/wwjd.md), cross-referenced with agent-first refactor loops, quality-loop pipelines, E2E agentic test patterns, memory/feedback systems, and CLAUDE.md conventions across DataWorks projects (dw-ems, dw-aware, WorkflowEngine, dw-analytics).

This is the focused decision lens. For the broader personal operating procedures (how wwjd composes with session handoff, work queuing, and durability), see the ca0v bootstrap: https://gist.github.com/ca0v/e6881cef2dc4a83ba79d94e5a1d30b1a

The /wwjd skill is a lens, not a task. Invoking it (or using its principles) reorients the agent around the prime directive:

Every decision, recommendation, or code change must move the codebase toward being robust, well-documented, and obviously correct, on a trajectory that converges on an **agent-first (and increasingly agent-frien

SvelteKit project management guide

SvelteKit Project Management Guide

A practical reference for keeping a SvelteKit application well-structured, testable, and maintainable.

Project structure

Software Developer

Corey Alix

coreyalix@hotmail.com

Interests

I am comfortable working with Typescript and I have been enjoying building side-projects using HTML, CSS and Typescript with minimal tooling. I want to build efficient Progressive Web Applications (PWA) for browser devices.

	<!DOCTYPE html>
	<html lang="en">

	<head>
	<meta charset="UTF-8" />
	<meta name="viewport" content="width=device-width, initial-scale=1.0" />
	<title>Google API Playground</title>
	</head>

	<body>

	'use strict';

	/**
	* Basic code to parse the values in the "data" attribute in a Google Maps URL to an Array.
	* There will likely still be some work to do to interpret the resulting Array.
	*
	* Based on information from:
	* http://stackoverflow.com/a/34275131/1852838
	* http://stackoverflow.com/a/24662610/1852838
	*/

	const modules = <Record<string, any>>{};

	function asAppPath(mid: string): string {
	// depends on app, workaround for not supporting requirejs.config
	if (mid.startsWith("app")) return `../../${mid}.js`;
	return mid;
	}

	if (!globalThis.require) {
	function define(mid: string, mod: any) {

	<!DOCTYPE html>
	<html>
	<head>
	<style data-template="{opacity}">
	body.dark {
	background-color: var(--dark-color);
	color: purple;
	opacity: var(--opacity);
	--dark-color: black;
	--opacity: {opacity};

	<!DOCTYPE html>
	<html>

	<head>
	<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
	<meta name="viewport" content="initial-scale=1, maximum-scale=1,user-scalable=no">
	<title>Persisting Identity Manager Info</title>
	<link rel="stylesheet" href="https://js.arcgis.com/3.37/dijit/themes/tundra/tundra.css">
	<link rel="stylesheet" href="https://js.arcgis.com/3.37/esri/css/esri.css">
	<style>

	namespace SpatialLab
	{
	static class Program
	{
	private const double metersPerFoot = (2.54 * 12) / 100d;

	private static void DotSpatialTest1(int epsgCode, double x, double y, double radiusInMeters)
	{
	var sr1 = DotSpatial.Projections.ProjectionInfo.FromEpsgCode(epsgCode);
	DotSpatial.Data.IFeatureSet inputFeatures = new DotSpatial.Data.FeatureSet(DotSpatial.Topology.FeatureType.Point)