jaredpalmer

Fine-tune a Kev decision model (open Jev-style System One model) on a user's own workload and serve it with calibrated probabilities. Interviews the user, finds existing Jev/TypeSafe questions or labelled data in their codebase, generates enough synthetic…

Deploy a Kev decision model (the open Jev-style System One model) as the user's own TypeSafe-compatible HTTPS endpoint on Modal with one command, wire it into their code, and take it down. Use when someone wants to host Kev, get a Kev API URL, replace Jev /…

Extremely strict structural review of a Kev branch or PR (code-judo simplifications, spaghetti growth, files past 1k lines, boundaries, duplication of canonical helpers). Use when asked to review a PR, audit a diff, or run a "thermonuclear" or deep code…

Search the Kev knowledge graph (private repo jaredpalmer/kev-knowledge) before re-deriving history. Use when asked what was tried, decided, measured or learned in earlier Kev sessions, why a rule or number exists, what a round or PR did, or when starting a…

Launch, monitor and pull Kev training studies, untrained-base probes, remote benchmarks and new-base smoke checks on Modal (modal_app.py). Use when running trials, delta fine-tunes, base probes, external evals or fit checks for the Kev repo.

Verify a Kev change has no regression and ship it as a reviewed PR. Use when refactoring, editing kev/*.py, scripts, the Space or the playground, and when opening or merging Kev pull requests (stacked branches, squash merges).

Write a Kev pull request title and body that teaches the reader why the change exists and how it works. Use when opening, editing or reviewing a PR on this repo, or when the PR title will become the squash-merge commit message.

Cut AI tells from any writing. Must always apply.

Capture solved problems as categorized documentation with YAML frontmatter for fast lookup

Answer questions about the AI SDK and help build AI-powered features. Use when developers: (1) Ask about AI SDK functions like generateText, streamText, ToolLoopAgent, embed, or tools, (2) Want to build AI agents, chatbots, RAG systems, or text generation…

Review code for adherence to project guidelines, style guides, and best practices. Use after writing or modifying code, especially before committing changes or creating pull requests.

Simplify recently modified code for clarity, consistency, and maintainability while preserving functionality.

Analyze code comments for accuracy, completeness, and long-term maintainability.

Review pull requests for test coverage quality and completeness.

Identify silent failures, inadequate error handling, and inappropriate fallback behavior in code changes or PRs.

Analyze type design for encapsulation, invariant expression, usefulness, and enforcement.

Write essays and reflective prose in the voice and style of Paul Graham. Use whenever the user asks for "Paul Graham", "PG style", "paulgraham.com style", or wants a topic, braindump, notes, or rough draft turned into an essay that should sound like PG.…

Write product changelogs and release notes in the house style of Vercel and Cursor — punchy, technical, marketing-inflected — and iteratively refine drafts until their measured writing statistics (sentence length, punctuation density, em-dash usage, etc.)…

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or…

Write a pull request title and body that teaches the reader why the change exists and how it works, in the essay style of Andrew Clark (acdlite) and Sebastian Markbåge (sebmarkbage) on facebook/react. Use when opening, editing or reviewing a PR in any repo,…

Write in the voice and style of Mark Zuckerberg. Use this skill whenever the user asks to "write like Zuckerberg", "draft something in Zuck's style", "write a memo like Mark Zuckerberg would", "channel Zuckerberg's voice", or wants any written content —…

Search GitHub code across millions of repositories using grep.app. Use when you need to find code patterns, implementations, examples, or understand how features are built in public codebases. (project)

Review Next.js App Router code for optimal Partial Prerendering (PPR), caching strategy, Suspense boundaries, and React Query integration. Ensure adherence to Next.js 16+ Cache Components best practices.