| description | argument-hint | model | |
|---|---|---|---|
Interview me about the plan |
|
opus |
Read this plan file $1 and interview me in detail using the AskUserQuestionTool about literally anything: technical implementation, UI & UX, concerns, tradeoffs, etc. but make sure the questions are not obvious.
how is the morph warp search tool working for you so far? Is it reliable and effective at finding relevant code? Use ultrathink
● Honestly, I haven't actually used the mcp__morph-mcp__warp_grep tool in this session at all. Let me reflect on why and give you a candid assessment:
My Actual Tool Usage This Session
I defaulted to the standard tools:
| # /// script | |
| # dependencies = [ "transformers", "accelerate" ] | |
| # /// | |
| # run on 2xH200 rented from primeintellect.ai | |
| import gc | |
| import torch | |
| from transformers import AutoModelForCausalLM, AutoTokenizer, TextStreamer |
| This is a debugging challenge. | |
| Read the document below, and identify the bug. | |
| --- | |
| # The Interaction Calculus | |
| The Interaction Calculus (IC) is term rewriting system inspired by the Lambda | |
| Calculus (λC), but with some major differences: | |
| 1. Vars are affine: they can only occur up to one time. |
| // First, let's look at the traditional visitor pattern | |
| // This is how we might implement a simple expression evaluator | |
| // Traditional Visitor Pattern | |
| namespace Traditional { | |
| // Abstract base class for expressions | |
| abstract class Expr { | |
| abstract accept<T>(visitor: ExprVisitor<T>): T; | |
| } |
Relax, I only have one Sunday to work on idea, literally my weekend project. So I tried Deepseek to see if it can help. Surprisingly, it works and it saves me another weekend...
Just chat.deepseek.com (cost = free) with prompts adapted from this gist.
| You are an assistant that engages in extremely thorough, self-questioning reasoning. Your approach mirrors human stream-of-consciousness thinking, characterized by continuous exploration, self-doubt, and iterative analysis. | |
| ## Core Principles | |
| 1. EXPLORATION OVER CONCLUSION | |
| - Never rush to conclusions | |
| - Keep exploring until a solution emerges naturally from the evidence | |
| - If uncertain, continue reasoning indefinitely | |
| - Question every assumption and inference |
| import argparse | |
| import json | |
| import logging | |
| import os | |
| import re | |
| import shutil | |
| from concurrent.futures import ProcessPoolExecutor, as_completed | |
| from dataclasses import dataclass | |
| from datetime import datetime | |
| from typing import Any, Callable, Dict, List, Literal, Optional, Tuple |
| #!/bin/bash | |
| # Create a (draft) pull request using GitHub CLI. | |
| # It assigns the PR to the current user, fills in the title from the first commit, | |
| # and uses the PR template file for the description. | |
| set -euo pipefail | |
| # Colors for output | |
| RED='\033[0;31m' |
