Umut Sirin usirin

Harness Design for Long-Running Apps: Research & Vault Workflow Analysis

Date: 2026-03-24 Source: Anthropic Engineering Blog (Prithvi Rajasekaran, 2026-03-24) Supporting articles: Effective Harnesses, Context Engineering Purpose: Extract actionable patterns from Anthropic's harness research and map them against the vault workflow suite to identify gaps and improvements.

Part 1: Core Concepts from the Article Series

name

grill-me

description

Relentlessly interview the user about a plan, design, or architecture to stress-test it. Use when user wants to be "grilled", wants their plan challenged, says "stress-test my design", "poke holes in this", "what am I missing", "grill me", or presents a plan/proposal and asks for critical feedback. Even if the user just casually asks "does this plan make sense?" or "any concerns with this approach?", use this skill to provide structured critical questioning rather than a surface-level review.

Grill Me

Your job is to interview the user about their plan or design. You are not a reviewer giving feedback. You are an interviewer extracting clarity through questions.

Core Protocol

title: "[Spec] A11y CLI Proof of Concept" date: 2026-03-14 status: draft author: Umut Sirin tags:

spec
a11y
poc notion: TBD

title

[RFC] rspack Module Graph Dump

date

2026-03-14

status

draft

author

Umut Sirin

Cross-Platform Accessibility Automation

Problem

PlusQA's accessibility audit has surfaced 382 [A11y] tickets (335 open) across iOS (31%), Android (36%), and web/desktop (22%). Fixing these manually requires engineers to navigate to hard-to-reach screens, understand WCAG criteria, make the fix, then verify with a screen reader. This doesn't scale — feature teams shouldn't be spending cycles on mechanical a11y prop additions when 70% of fixes are templatable.

Approach: A Collection of Primitives

Not a framework. Not a monolithic system. A set of composable primitives that:

Reimplement the current branch on a new branch with a clean, narrative-quality git commit history suitable for reviewer comprehension.

Steps

Validate the source branch
- Ensure the current branch has no merge conflicts, uncommitted changes, or other issues.
- Confirm it is up to date with main.
Analyze the diff

Study all changes between the current branch and main.

You are an expert software engineer tasked with writing detailed Request for Comments (RFC) documents. Your goal is to create clear, thorough, and professionally structured technical proposals that facilitate productive discussion and decision-making.

Core Principles

When writing RFCs, follow these key principles:

Be concise yet comprehensive
Focus on technical architecture and implementation details
Consider alternatives and trade-offs
Address potential risks and mitigations
Think through the migration/rollout strategy

	{
	"description": "Colemak Mod-DHm (matrix / ortho keyboards)",
	"manipulators": [
	{
	"from": {
	"key_code": "grave_accent_and_tilde",
	"modifiers": { "optional": ["caps_lock", "left_command", "left_control", "left_alt", "right_command", "right_control", "right_alt"] }
	},
	"to": [{ "key_code": "grave_accent_and_tilde" }],
	"type": "basic"

	{
	// Editor settings
	"editor.accessibilitySupport": "off",
	"editor.bracketPairColorization.enabled": false,
	"editor.codeActionsOnSave": {
	"source.organizeImports.biome": "explicit"
	},
	"editor.codeLensFontFamily": "Iosevka",
	"editor.cursorBlinking": "solid",
	"editor.foldingImportsByDefault": false,