Skip to content

Instantly share code, notes, and snippets.

View usirin's full-sized avatar

Umut Sirin usirin

View GitHub Profile
@usirin
usirin / research.md
Last active April 11, 2026 19:12
Interaction Models and Design Systems in Agentic Programming
title Interaction Models and Design Systems in Agentic Programming
date 2026-04-08
type research
status complete

Executive Summary

Agentic programming tools encode fundamentally different assumptions about who the human is and what they need. A terminal chat treats the developer as a collaborator reviewing diffs. A background agent treats the developer as a manager reviewing pull requests. A Figma MCP integration treats the designer as a spatial thinker who should never leave the canvas. The most important finding across this research is that agentic tooling works best when it meets each role in its native medium rather than collapsing everyone into a single interface. This is not a convenience preference. Cognitive science research demonstrates that spatial reasoning, direct manipulation, and visual judgment are load-bearing cognitive processes for designers [^43][^44], just as sequential textual reasoning is for developers. Forcing role collapse disables the cognitive machinery that makes

@usirin
usirin / knowledge.json
Created March 30, 2026 02:53
a11y fix-agent: manifest + knowledge (2026-03-29)
{
"fix_patterns": [
{
"id": "contrast_fix_text_token_category_mismatch",
"description": "Replace a background/surface semantic color token with a text color token where the property controls text rendering, causing near-zero contrast in light mode",
"wcag_rules": [
"1.4.3"
],
"platforms": [
"android"

Harness Audit — 2026-03-25

Skills before: 38 | Skills after: 27 active + 13 archived Shared rules created: 7 | Scripts created: 3 Model Assumptions added: 27/27 active skills New skills created: 2 (vault-quarterly, vault-half-review) — pending /skill-creator refinement

What Changed

Archived 13 skills (1,651 lines removed from active set)

@usirin
usirin / SKILL.md
Created March 25, 2026 23:53
harness-audit: on-demand skill suite auditor for Claude Code
name harness-audit
description Audit the skill suite to find complexity that's no longer justified by current model capabilities. Run on-demand after model releases, when skills feel like they're getting in the way, or for periodic maintenance. Use when user says "harness audit", "audit skills", "audit my harness", "simplify skills", "prune skills", "are my skills still needed", "what can I simplify", "skill review", "clean up skills", or mentions that a new model just dropped and they want to check if their setup needs updating.

Harness Audit

Evaluate whether each skill's complexity is still justified. Every skill encodes assumptions about what the model can't do on its own. Those assumptions go stale as models improve. This skill finds the stale ones.

Three phases: audit (read-only report) → propose (show changes one at a time) → execute (apply approved changes only).

@usirin
usirin / 2026-03-24-harness-design-research.md
Last active March 25, 2026 05:29
Harness Design for Long-Running Apps: Research & Vault Workflow Analysis

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

@usirin
usirin / SKILL.md
Created March 18, 2026 17:44
grill-me: Claude Code skill that interviews you relentlessly about your plan or design
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

@usirin
usirin / 2026-03-14-a11y-poc-spec.md
Created March 15, 2026 03:51
[Spec] A11y CLI Proof of Concept — Effect-TS v4, iOS, radio button roles

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

  • spec
  • a11y
  • poc notion: TBD
@usirin
usirin / 2026-03-14-rspack-module-graph.md
Created March 15, 2026 03:40
[RFC] rspack Module Graph Dump
title [RFC] rspack Module Graph Dump
date 2026-03-14
status draft
author Umut Sirin
tags
rfc
a11y
web-platform
@usirin
usirin / 2026-03-14-property-based-a11y-testing.md
Created March 15, 2026 03:00
[RFC] Property-Based Accessibility Testing
@usirin
usirin / 2026-03-14-a11y-automation-design.md
Created March 14, 2026 06:46
Cross-Platform Accessibility Automation — Design Doc

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: