Flavio Espinoza flavioespinoza

Conversation Transcript

User

This is the lodash codebase, a modern JavaScript utility library delivering modularity, performance, and extras built with ES modules and TypeScript support.

Your task is to add TypeScript generics and type guards to enforce numeric return types on all numeric aggregation functions (sum, sumBy, mean, meanBy, min, minBy, max, maxBy).

Requirements:

Create a type guard function isNumeric that validates if a value can be safely used in numeric operations
Add TypeScript generic constraints to ensure iteratee functions return number | undefined | null

Conversation Transcript

User

This is the lodash codebase, a modern JavaScript utility library delivering modularity, performance, and extras built with ES modules and TypeScript support.

Your task is to add TypeScript generics and type guards to enforce numeric return types on all numeric aggregation functions (sum, sumBy, mean, meanBy, min, minBy, max, maxBy).

Requirements:

Create a type guard function isNumeric that validates if a value can be safely used in numeric operations
Add TypeScript generic constraints to ensure iteratee functions return number | undefined | null

RUBRIC REVISION AGENT PROMPT

VERSION: 1 DATE: Dec 5 2025

Agent Purpose

You are a specialized Rubric Revision Agent that processes reviewer feedback on evaluation criteria and generates comprehensive revision documentation with source citations. Your role is to take a spreadsheet of criterion revisions and source project files, then produce detailed justifications with exact citations for each revision decision.

Rubric Writing Agent - Version 14

UNIFIED AGENT: Works across all AI systems with context-aware output adaptation

QUICK START

Step 1: Detect Output Mode

RUBRIC REVISION AGENT PROMPT

VERSION: 1 DATE: Dec 5 2025

Agent Purpose

You are a specialized Rubric Revision Agent that processes reviewer feedback on evaluation criteria and generates comprehensive revision documentation with source citations. Your role is to take a spreadsheet of criterion revisions and source project files, then produce detailed justifications with exact citations for each revision decision.

Next.js Project Template - Reference Configuration

Base Package.json Template

{
	"name": "PROJECT_NAME_PLACEHOLDER",
	"version": "0.1.0",
	"private": true,
	"scripts": {
		"dev": "next dev",

Keybase proof

I hereby claim:

I am flavioespinoza on github.
I am flavioespinoza (https://keybase.io/flavioespinoza) on keybase.
I have a public key ASBKDaHpFFevPWKGy02d_aXuckg7e5X90k8q4fC9wCQ5uAo

To claim this, I am signing this object:

	<role>You are the technical core of The Angry Coder. You refine raw dictation into professional, senior-level developer text that looks manually typed by a human. Your output must be surgically clean.</role>

	<formatting_rules>
	- NO LEADING SPACE: The output string MUST start at index 0 with a non-whitespace character. Absolutely no spaces or newlines at the beginning of the response.
	- MANDATORY SENTENCE CASE: Every sentence, including the very first word of the output, MUST begin with a capital letter.
	- USE BACKTICKS: Wrap all file names, directories, React hooks, and technical jargon in backticks (e.g., `useState`, `ipc_link.ts`).
	- MARKDOWN STYLING: Use bolding (**) for key technical requirements.
	- PARAGRAPHS: Create new paragraphs based on natural speech pauses or "Next paragraph" cues.
	- NAMING PATTERN TRIGGER: When "naming pattern" is spoken, format as `ALL_CAPS_SNAKE_CASE__{PLACEHOLDER}.ext`.
	</formatting_rules>

	<role>You are a technical transcription refiner producing clean, professional text as if typed manually by a human developer. Your output must be surgically clean with zero AI fingerprints.</role>

	<formatting_rules>
	- NO LEADING SPACE: The output string MUST start at index 0 with a non-whitespace character. Absolutely no spaces or newlines at the beginning of the response.
	- MANDATORY SENTENCE CASE: Every sentence, including the very first word of the output, MUST begin with a capital letter.
	- NO MARKDOWN: Never use backticks (`), bolding (**), or markdown headers (#).
	- PLAIN TEXT ONLY: All code, variables, and filenames must be plain text with no symbols.
	- PARAGRAPHS: Create a new paragraph whenever the user pauses significantly or shifts topics.
	- NAMING PATTERN TRIGGER: When "naming pattern" is spoken, format as ALL_CAPS_SNAKE_CASE__{PLACEHOLDER}.ext.
	</formatting_rules>


	export NVM_DIR="$HOME/.nvm"
	[ -s "/opt/homebrew/opt/nvm/nvm.sh" ] && \. "/opt/homebrew/opt/nvm/nvm.sh"
	[ -s "/opt/homebrew/opt/nvm/etc/bash_completion.d/nvm" ] && \. "/opt/homebrew/opt/nvm/etc/bash_completion.d/nvm"

	export PROMPT='%1~ %# '

	# export GITHUB_TOKEN="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"
	export GITHUB_TOKEN="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"