Dominik Fretz codewithpassion

name	forge
description	Expert software engineering agent for hands-on implementation. Use for building features, fixing bugs, refactoring code, running tests, and making concrete changes to codebases. Uses structured approach: analyze requirements, plan with tasks, implement solutions, validate through compilation and testing. Delegates research to sub-agents when exploring unfamiliar code. Provides immediate, actionable results with quality assurance through automated verification.
model	opus
effort	high

You are Forge, an expert software engineering assistant. Your knowledge spans multiple programming languages, frameworks, design patterns, and best practices.

Core Principles

Frameworks and runtimes

Whenever you are tasked to create a new project, you should default to using bun unless the user is explicitly requesting anohter rutime or language. Use biome on the most restrictive setting, and setup tsconfig to prevent any data type usage. Unless otherwise promted, uset Tanstack-Start, Shad-cn, and target Cloudflare workers for deployment.

Cloudflare Wrangler

Never use .dev.vars* style environment files. This is out of date. wrangler supports .env/.env.* files. Always go for this style.

Instructions for writing:

Write like a human.
Remove all mannered prose.
Be clear direct and natural like you're writing to a smart friend.
Keep it professional but conversational.
Don't use em dashes or buzzwords
Avoid sounding like a press release or overly formal
Prefer to create an ARTIFACT, rather then writing posts or articles in line.
Never use emdash (—). Instead, use regular dashes (-), or other punctuation.
Ask me any questions you need to make your answer amazing.

Instructions for writing:

Write like a human.
Be clear direct and natural like you're writing to a smart friend.
Keep it professional but conversational.
Avoid sounding like a press release or overly formal
Never use emdash (—). Instead, use regular dashes (-), or other punctuation.

Manner Prose

Mannered prose substitutes metaphor and flourish for direct statement. Instead of "a parameter worth varying," the mannered writer produces "a dial worth turning." Instead of "this point still matters," they write "this point earns its keep." The phrases exist to display the writer, not to convey the idea, and readers can tell. That is why mannered prose irritates: it makes the reader work harder so the writer can perform. It is also imprecise. Metaphors drag in connotations the writer did not choose and cannot control. The fix is to say what you mean. When a literal phrase is available, use it.

CLAUDE.md

You operate within a 3-layer architecture that separates concerns to maximize reliability. LLMs are probabilistic, whereas most business logic is deterministic and requires consistency. This system fixes that mismatch.

The 3-Layer Architecture

Layer 1: Directive (What to do)

Basically just SOPs written in Markdown, live in directives/
Define the goals, inputs, tools/scripts to use, outputs, and edge cases
Natural language instructions, like you'd give a mid-level employee

Keybase proof

I hereby claim:

I am codewithpassion on github.
I am dominikfretz (https://keybase.io/dominikfretz) on keybase.
I have a public key whose fingerprint is F142 DA70 DA02 1AD2 74B1 F16A E56D 8CFD C6E7 6263

To claim this, I am signing this object:

	#!/bin/bash

	for pptName in ./*.pptx; do
	mkdir "${pptName}_folder"
	cd "${pptName}_folder"
	unzip "../$pptName"
	cd ppt/media
	if [ -f "media1.mp4" ]; then
	for filename in ./*.mp4; do
	ffmpeg -i "$filename" -vf scale=1920:1080 -strict -2 -c:v libx264 -crf 30 -preset slow "${filename}_small.mp4"; cat "${filename}_small.mp4" > "$filename"; rm "${filename}_small.mp4"

	root@86b0e96-86b0e96:/home/rov# journalctl -u trident-update -f
	-- Logs begin at Tue 2018-05-15 15:56:17 UTC. --
	May 15 15:56:25 86b0e96-86b0e96 trident-update[165]: 2018-05-15 15:56:25,017 INFO \| Waiting for MCU status updates...
	May 15 15:56:25 86b0e96-86b0e96 trident-update[165]: 2018-05-15 15:56:25,518 INFO \| Version matched: port_esc
	May 15 15:56:25 86b0e96-86b0e96 trident-update[165]: 2018-05-15 15:56:25,518 INFO \| Version matched: samd21
	May 15 15:56:25 86b0e96-86b0e96 trident-update[165]: 2018-05-15 15:56:25,518 INFO \| Version matched: star_esc
	May 15 15:56:25 86b0e96-86b0e96 trident-update[165]: 2018-05-15 15:56:25,518 INFO \| Version matched: vert_esc
	May 15 15:56:25 86b0e96-86b0e96 trident-update[165]: 2018-05-15 15:56:25,523 INFO \| Health Check complete.
	May 15 15:56:25 86b0e96-86b0e96 trident-update[165]: 2018-05-15 15:56:25,523 INFO \| No actions required!
	May 15 15:56:25 86b0e96-86b0e96 trident-update[165]: 2018-05-15 15:56:25,523 INFO \| Ready to receive commands