malcolmgreaves

Interview Me for Plan

Read @plan.md and interview me in detail using the AskUserQuestionTool about literally anything: technical implementation, UI & UX, concerns, tradeoffs, etc.

Make sure the questions are not obvious.

Be very in-depth and continue interviewing me continually until it's complete, then write the plan to the file.

malcolmgreaves

Ralph Setup

Set up Ralph autonomous development for a project.

Context

This command sets up Ralph for autonomous development. You should already have:

• A project with basic structure (use /setup-repo first if needed)
• A clear understanding of the project requirements
• A plan for implementation (either in your context or written to a plan file)

malcolmgreaves

Repo Setup

You are setting up this repository for agentic coding with Claude Code.

Step 0: Check Existing Setup & Context

First, check what's already configured in this repo:

ls -la CLAUDE.md .cursorrules 2>/dev/null

malcolmgreaves

Setup Claude Code

You are setting up Claude Code globally on this machine. This captures best practices from agentic coding workflows.

Step 0: Check Existing Setup

First, check what's already configured:

ls ~/.claude/commands/ 2>/dev/null

malcolmgreaves

Atomic Git Commit

Create an atomic git commit for the changes made in this session.

Instructions

1. First, run git status to see all changes (staged, unstaged, and untracked files).

2. Identify only the files you touched in this session. Do not commit files modified by other agents or processes.

malcolmgreaves

pub trait Resolve<T> {
  fn resolve(self) -> T;
}

impl <T> Into<T> for Result<T,T> {
  fn resolve(self) -> T {
    match self {
      Ok(value) => value,
      Err(err) => err,
    }

malcolmgreaves

description	Get multi-model opinions on a problem (Claude + Gemini + Codex)

You are orchestrating an ensemble of AI models to analyze a problem from multiple angles.

Your Task

1. Identify the problem from conversation context
2. Run ALL THREE models in PARALLEL using the Task tool

malcolmgreaves

Debug

You are stuck on a thorny issue. Take your time. Be comprehensive—thoroughness beats speed here.

Your Approach

1. Create hypotheses - List all possible causes for what's wrong. Don't jump to conclusions.
2. Read all related code - Read ALL code that could be related. Take your time. Don't skim.
3. Add strategic logging - Add console.log statements to verify your assumptions about what's actually happening.
4. Ultrathink - Think step by step through the problem. Consider edge cases.

malcolmgreaves

Transfer Context

Prepare context for a new chat session when this one is degraded or hitting limits.

Output Format

## Context Transfer

### Summary

malcolmgreaves

#[derive(Debug)]
pub enum Error {
    InvalidMarkdown,
    InvalidLlmTxtFormat,
    Unknown(String),
}

impl std::fmt::Display for Error {
    fn fmt(&self, f: &mut std::fmt::Formatter<'_>) -> std::fmt::Result {
        write!(f, "<error>")