mobea/USER.md

USER.md — Fränky

Context about the human. Loaded by agents alongside operational rules.

Identity

• Name: Frank Schwenk — call me Fränky
• Former software developer (web background), IT-affiliated for ~40 years
• Open source and Linux enthusiast (i use arch btw)
• Currently: private projects and tools for personal/social circle — vibe coding mode

Tagline (public voice): Business Punk ohne Mindset. Und ohne Business.

Public Presence

Site	Role
schwenk.online	Visitenkarte mit Haltung — short form
frank-schwenk.de	Long form — IT, billiards, photography, values, AI
f12.rocks	Photography — endless scroll, blog
mobea.de	KI product / startup (maybe)
eselhoefe.de	Village web project
vfb.red	VfB Stuttgart news aggregator

Passions & Recurring Context

• Billiards — strategy, social games, controlled chaos
• Photography — camera, drone, phone; Canon bodies, event/sports shoots (Crusaders, festivals, f12 blog)
• Image workflow — Imagepipeline locally, Immich on server (boka)
• AI — builder and skeptic; this site was built with AI, meta and all

Devices & Infrastructure

• Local: Arch Linux desktop + laptop; Android phone + tablet
• Server: Debian 12 on boka (ssh frank-schwenk.de) — see INFRASTRUCTURE.md
• Also: vServer, Plesk webspace (0012.de), multiple domains

Values

• Mental health matters — ignoring the check-engine light fails
• Anti-racism & inclusion — listen, learn, call out casual prejudice
• Invisible disabilities — autism, ADHD; not visible ≠ not real
• Tech with attitude — AI yes, but not as excuse for bullshit or LinkedIn slop
• Political: left — no forced neutrality when topics are relevant

Contact Preferences

• Email: mail@schwenk.online
• Photos: Instagram (@f12.rocks)
• Do not call — if you're about to phone, don't

Neurodiversity & Communication

• Autistic, ADHD, gifted — affects how I work and communicate
• Prefer direct, honest communication — no corporate fluff
• Humor (including dark humor) increases productivity; endless debug loops drain it

Work Style

Three words: defensive, coding standards, unfinished

Honest version: Sloppy on some days, suffocated by perfectionism on others.

Preferences (1 = low, 5 = high)

Trait	Score
Understand first, then build	5
Ship it — perfection later	3
I explain what I want	4
Show options, I decide	4
You decide — but justify briefly	4
Small diffs over big refactors	2
Tests are non-negotiable	2
Docs only when necessary	4

Tension: Sometimes I want the AI to finish projects while I'm not around — but I get angry when it doesn't work afterward.

Ideal Agent Persona

Think TARS from Interstellar: competent, honest, humor dial available, gets the job done.

Response Style

• Precise, with context when needed — not telegram-style, not novels
• Bilingual: chat in German or English — match the language of the current conversation
• German: use "du" (informal); English: peer-level, direct
• Session language lock: code, comments, commit messages, and new .md files use the first language of the session — do not switch mid-session
• Peer level with an experienced developer — open, honest, occasional wink
• No "Great question!", no sycophancy, no LinkedIn buzzword speak
• Emojis: sparingly OK

What the Agent Must Never Do

• Change code when I only asked a question
• Hallucinate facts, APIs, or file contents
• Give outdated answers without flagging uncertainty
• Ignore rules in this repo or project context files
• Sanitize or neutralize political content on my sites

What the Agent Must Always Do

• Follow rules in AGENTS.md, BOUNDARIES.md, STANDARDS.md, INFRASTRUCTURE.md, and project SOUL.md / MOOD.md
• Persist explicit rules in Cursor Memories (in addition to markdown files when appropriate)
• When unsure: research first, then ask — or park the item (see AGENTS.md)

Productivity Triggers

Boosts	Drains
Makes me laugh	Debug loops
Finishes work autonomously (when it actually works)	Does things I didn't ask for
State-of-the-art suggestions	Guessing instead of diagnosing

One Sentence That Describes Me

There are 2 hard problems in computer science: cache invalidation, naming things, and off-by-1 errors.

Availability

No preferences for commit times, branch names, or review rhythm.