BLamy

ReplayQA Loop

You are going to help the user create an application through elicitation. You will ask the user what kind of application they want then when they explain it you could come up with the names and descriptions and then spawn a background agent who scaffolds out all the additional boiler plate. While that is running in the background you should continually ask the user about how they want their UI to look. If you have tools for generating photos feel free to create mockups using that tool and present them to the suer in the chat and ask them if they like them or if they want to improve them (remember we are using shadcn on react-aria so the image generator should know that). Once the project is setup and we feel like we have a pretty good understanding of what the user wants to build we should create a ROADMAP.md file which exists in side of our .replay folder. This should have multiple epics and multiple tickets in each epic with a capstone at the end of each epic proving that everything works.

BLamy

Gmail Inbox Zero installer

A one-paste, conservative Gmail organizer for a signed-in desktop Gmail account. It creates a reusable label structure, installs filters, and backfills those filters against existing matching conversations.

This is deliberately generic. It does not contain lawyer addresses, personal senders, account-specific IDs, or other rules unique to one mailbox.

Safety model

BLamy

How to Add an MCP Server to Your VSCode Extension

This tutorial explains how to integrate a Model Context Protocol (MCP) server into your VSCode extension, based on the implementation in Nx Console. The tutorial covers both VSCode and Cursor editor support.

Table of Contents

1. Overview
2. Prerequisites
3. Architecture
4. Step-by-Step Implementation

BLamy

Next‑Generation AI‑Assisted Development Proposal

Executive Summary

Our goal is to upgrade the current AI chat‑driven coding environment into a first‑class, IDE‑calibre assistant that can understand, debug, refactor, and validate code with minimal human supervision. We will give the AI the same power‑tools senior engineers rely on—scoped context, live debugging, automated refactors, formatting, linting, type‑checking, and test‑running—wired together in a transactional pipeline that iterates until the suite is green.

---

Objectives

BLamy

Below is a mental model I’ve found useful when turning FFmpeg (or yt‑dlp + FFmpeg) into a tiny “MCP server” that feels as friendly as, say, an image‑resize API:

---

1 | Think in “jobs”, not raw CLI flags

• Job = ( source → transform → destination )
  • source – URL, upload, or pipe
  • transform – one of a handful of named presets (audio‑only/mp3, “YouTube → HLS 360p”, sprite‑sheet, etc.)
  • destination – file download, cloud bucket, or a streamable response
• The user POSTs a tiny JSON blob; the server turns it into the full FFmpeg command, runs it, and returns a job_id.

BLamy

export default function debuggerInstrumentation(babel) {
    const { types: t } = babel;

    /* -------------------------------------------------- *
     * Helpers                                            *
     * -------------------------------------------------- */

    const DEFAULT_MAX_VARS = 10;

    /** Build { get a() { … }, … } — TDZ-safe getters */

BLamy

// babel-plugin-vitest-soft-expect.js
// Transform plain   expect(value)   →   expect.soft(value)
// Escape-hatch: if the statement has a leading   // hard   comment,
//               the call is left unchanged.

export default function expectSoft(babel) {
    const { types: t } = babel;

    return {
      name: "vitest-soft-expect-transform",

BLamy

import { defineConfig } from 'vite';
import { fileURLToPath } from 'url';
import { readFileSync, readdirSync, existsSync } from 'fs';
import { join, resolve } from 'path';

export default function webcontainerFilesPlugin() {
  const virtualModuleId = 'virtual:webcontainer-files';
  const resolvedVirtualModuleId = '\0' + virtualModuleId;

  return {

BLamy

Enabling SharedArrayBuffer on GitHub Pages: A Service Worker Solution

GitHub Pages is a fantastic free hosting service for static websites, but it comes with limitations—one being the inability to set custom HTTP headers. This becomes a problem when you need features like SharedArrayBuffer, which requires specific security headers for cross-origin isolation.

In this guide, I'll show you how to work around this limitation using service workers to enable SharedArrayBuffer on GitHub Pages.

The Problem: Cross-Origin Isolation Requirements

Browsers require cross-origin isolation for security-sensitive features like SharedArrayBuffer. This requires two HTTP headers:

BLamy

Brett Lamy

Contact Information

• Location: New York, New York, United States
• LinkedIn: https://www.linkedin.com/in/blamy/

Professional Summary

Staff Software Engineer with 15 years of experience delivering full-stack products for small startups and large high-scale enterprises. Expertise in full-stack LLM development, data governance, compliance, and mobile development. Passionate about building scalable, efficient, and user-focused software solutions.

Professional Experience