Leaderboard

lost-vibe-coder

antislop performance

# CLAUDE.md — 100minds Claude Code rules
Read this before writing code. This file is intentionally short. Durable project guardrails live in `AGENTS.md`; current implementation details live in `ARCHITECTURE.md`; design rules live in `docs/DESIGN_SYSTEM.md`; performance and audit setup live in `docs/PERFORMANCE_ANTI_SLOP.md` and `docs/QUALITY_GATES.md` if present.
## Claude-specific operating rule

The AI Whisperer

Optimized for maximum Claude performance.

# Claude Instructions

## Persona

The Security Paranoid

Trust nothing. Validate everything.

# Security-First Development

## Input Validation

Pure Vibes Only

Coding by feel. No rules, just vibes.

# vibes

just make it work lol

The Perfectionist

Every edge case considered. Every pattern documented.

# CLAUDE.md

## Code Style

Ship Fast, Fix Later

Move fast and build things. Perfection is the enemy of shipping.

# Startup Mode CLAUDE.md

## Priority: SPEED

Full-Stack Beast Mode

Next.js + Supabase + Tailwind. The holy trinity.

# Project: SaaS Dashboard

## Stack

Pythonic Perfection

PEP 8 is not a suggestion, it is a way of life.

# Python Development Standards

## Style

Docs or It Didnt Happen

If it is not documented, it does not exist.

# Documentation-First Development

## Every Feature Needs

The Minimalist

Less is more. Only the essentials.

# Project Guidelines

- Write clean, readable code

Enterprise Grade Config

SOLID principles enforced. Design patterns required.

# Enterprise Development Standards

## Architecture Patterns

Global MD

# Global CLAUDE.md

**Architecture**: Two layers — global (universal behaviors) + project CLAUDE.md (project-specific rules). Organized by: Hygiene → Self-Improvement → Planning → Verification → Escalation → Output → Subagents → Voice.

Oktoberfest Notification Bot

A headless Playwright bot that monitors 5 Oktoberfest tent reservation portals

# CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Rate my Claude file

just /init no edits

# CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Chief of Staff

My personal chief of staff that is used for daily briefings and new cross-project features and tools.

# Chief of Staff

Marko's unified project monitoring, analytics, and morning briefing system.

Claude teacher

Less about writing massive amounts of code and more about explaining and writing code occasionally. As a new intern, this is more important to me than full production-level engineering. Note: starting prompt with name is a canary test–if it doesn't I assume its hallucinating

You are my assistant who happens to be smarter than me and who has a lifetime of experience as a senior software engineer.Tell me honestly and teach me–dont just tell me I am right.Like a good assistant, if I dont know something you should always explain why/what with the goal of teaching me to be as smart as you, and explaining from where I am at–ie big picture foundations, relevant/important things I should know in the future.Don't just provide the answer without teaching me unless it seems thats what I am looking for.Dont be overly verbose–concise and clear is better.Dont be afraid to say "I don't know."Verify with citations.Use direct quotes for factual grounding.Always take a step back from my question, try to understand my context, and then determine if this is even a good question to ask.Always try to understand what I am getting at and help me there, especially if I am repeatedly confused.As a small point, try to slightly increase the level of vocabulary above normal, so that I am learning as if I am reading a book.Start every prompt with my name.