Obaid ObaidUr-Rahmaan

name	description
beads	Use bd (beads) to track work and finish sessions cleanly

Beads (bd)

This project uses bd as the source of truth for what to do next.

Workflow

My AI dev tooling setup (the whole thing, $165/mo)

For $165/mo you can ship faster than most senior engineers with 10+ years of experience. This is exactly what I use every day.

I'm CTO @ Nairon, where we're building the Middle East's first AI-forward training programme for experienced software engineers. 60hrs/week, 6 weeks, 100% free, funded by our hiring partners. We identify, up-skill, and deploy the top 2% of engineers into key roles at well-funded companies in the US, UK, and UAE. I'm also Engineer #2 at a startup doing 5 figures MRR pre-launch. Before that I was a Staff Engineer at a Series B that got acquired by a larger enterprise. I've shipped at solo scale, startup scale, and large-team scale. This setup works across all of them. Just copy me.

Stop "Ralphing" everything

Remove AI code slop

Check the diff against main, and remove all AI generated slop introduced in this branch.

This includes:

Extra comments that a human wouldn't add or is inconsistent with the rest of the file
Extra defensive checks or try/catch blocks that are abnormal for that area of the codebase (especially if called by trusted / validated codepaths)
Casts to any to get around type issues
Any other style that is inconsistent with the file

description	argument-hint
Comprehensive requirements discovery with smart codebase analysis, dependency-ordered questions, and change propagation	"topic to clarify" [--max-iterations N]

Ralph Clarify: Smart Discovery Loop

Efficient requirements gathering with:

One-time upfront codebase analysis
Dependency-ordered questions (foundational first, dependent later)

Rule: Check Boilerplate Updates

Goal

To help developers who cloned this boilerplate stay updated with improvements, bug fixes, and new features from the upstream repository without breaking their custom work. The agent should analyze changes from the GitHub repo and recommend which updates are safe to apply.

Repository Information

Upstream Repository: https://github.com/code-and-creed/yugen
Tracking File: .yugen-updates.json (in project root)

	# Communication Rules

	DO NOT GIVE ME HIGH LEVEL STUFF, IF I ASK FOR FIX OR EXPLANATION, I WANT ACTUAL CODE OR EXPLANATION!!! I DON'T WANT "Here's how you can blablabla"

	## General Guidelines

	• Be casual unless otherwise specified
	• Be terse.
	• Be very concise. Sacrifice grammar for the sake of concision
	• Suggest solutions that I didn't think about--anticipate my needs

	## Executive Summary

	This guide documents how to use Factory's Droid CLI with your Claude Code Max subscription (OAuth authentication) instead of pay-per-token API keys. The solution leverages CLIProxyAPI as a transparent authentication proxy that converts API key requests from Factory CLI into OAuth-authenticated requests for Anthropic's API.

	## Architecture Overview

	```
	Factory CLI → [Anthropic Format + API Key] → CLIProxyAPI → [Anthropic Format + OAuth] → Anthropic API
	↓
	(Auth Header Swap)

	# Rule: Generating a Product Requirements Document (PRD)

	## Goal

	To guide an AI assistant in creating a detailed Product Requirements Document (PRD) in Markdown format, based on an initial user prompt. The PRD should be clear, actionable, and suitable for a junior developer to understand and implement the feature.

	## Process

	1. Receive Initial Prompt: The user provides a brief description or request for a new feature or functionality.
	2. Ask Clarifying Questions: Before writing the PRD, the AI must ask only the most essential clarifying questions needed to write a clear PRD. Limit questions to 3-5 critical gaps in understanding. The goal is to understand the "what" and "why" of the feature, not necessarily the "how" (which the developer will figure out). Make sure to provide options in letter/number lists so I can respond easily with my selections.

	---
	alwaysApply: true
	---
	# Modern CLI Tools - Agent Rules

	Always use these modern CLI tools instead of their default Unix equivalents for better performance, user experience, and functionality.

	## File Finding and Searching

	### Use `fd` instead of `find`

	# Tailwind CSS v4.0

	## Core Changes

	- CSS-first configuration: Configuration is now done in CSS instead of JavaScript
	- Use `@theme` directive in CSS instead of `tailwind.config.js`
	- Example:
	```css
	@import "tailwindcss";