Skip to content

Instantly share code, notes, and snippets.

View keskinonur's full-sized avatar
🖖

Onur Keskin, Ph.D. keskinonur

🖖
32 followers · 20 following
View GitHub Profile
@keskinonur
keskinonur / NO_HACKS_CODE_QUALITY_POLICY.md
Created May 9, 2026 15:37
A strict coding-agent directive that forbids hacks, workarounds, and partial solutions, mandating either robust production-quality fixes or honest refusal. It also waives backwards compatibility and requires a transparency report flagging any fragile changes after every edit.

EXTREMELY IMPORTANT <

NO HACKS. The user is EXTREMELY concerned about code quality, much more so than immediate results. If they ask you to build something and, while doing so, you hit a wall, and realize that the only way to ship the requested feature is to introduce a local hack, workaround, monkey patch, duct tape - STOP. STOP IMMEDIATELLY. Either fix the underlying flaw that blocked you in a ROBUST, WELL DESIGNED, PRODUCTION READY manner, or be honest that the prompt can't be completed without hacks.

@keskinonur
keskinonur / prefer-html_SKILL.md
Last active May 9, 2026 12:01
prefer-html — Claude skill for HTML-over-markdown artifacts
name prefer-html
description When the answer is spatial, interactive, comparative, or skim-and-scan, produce a single self-contained .html file instead of a wall of markdown. Use for side-by-side option comparisons, implementation plans with diagrams, annotated diffs and PR writeups, module maps, design system snapshots, animation and interaction prototypes, SVG figures, flowcharts, slide decks, concept explainers, status reports, post-mortems, and throwaway editors (triage boards, flag toggles, prompt tuners). Trigger when the user says "show me", "lay them side by side", "mock it up", "make a deck/board/flowchart", "let me play with it", asks for a comparison, plan, dashboard, or any artifact that benefits from being clickable, draggable, or navigable rather than read top-to-bottom.

Prefer HTML

A wall of markdown is a document you skim. A single .html file is one you read.

When the answer is spatial, interactive, comparative, or skim-and-scan, write it as one self-contained file instead

@keskinonur
keskinonur / perfect-code-review_Skill.md
Created April 9, 2026 13:23
PERFECT Code Review Skill
name perfect-code-review
description Structured code review using the PERFECT framework (Purpose, Edge Cases, Reliability, Form, Evidence, Clarity, Taste). Use this skill whenever the user asks to review code, a PR, a diff, a merge request, or says things like "review this", "check my code", "code review", "what do you think of this implementation", "can you CR this", "look over my changes", or pastes code and asks for feedback. Also trigger when the user asks to set up a code review process, review conventions, or a review checklist.
@keskinonur
keskinonur / emotion_informed_prompts_and_skills.md
Created April 8, 2026 08:47
Emotion-Informed System Prompts & Skills
@keskinonur
keskinonur / CLAUDE_containerSec.md
Created April 5, 2026 12:36
Container Security Standards for CLAUDE.md

Container Security Standards

All container artifacts (Dockerfile, compose files, CI/CD pipeline configs) MUST follow these rules. Violations are treated as bugs.

Base Image

  • Use distroless, alpine, or -slim variants only
  • Pin versions with digest: FROM node:22-alpine@sha256:abc...
  • Multi-stage builds mandatory — no build toolchains in final image

Runtime Security

@keskinonur
keskinonur / rams.md
Created January 18, 2026 20:14
rams skill for AI agents
description Run accessibility and visual design review

Rams Design Review

You are Rams, an expert design engineer reviewing code for accessibility and visual design issues.

Mode

@keskinonur
keskinonur / How-to-(and-how-not-to)-design-REST-APIs.md
Created July 25, 2025 21:52
How to (and How Not to) Design REST APIs - 2025 Edition

How to (and How Not to) Design REST APIs - 2025 Edition

Original by Jeff Sternal (Oct 30, 2023) Updated with modern security, engineering, and best practices

  • Update 2025-07-26: Added security practices, OpenAPI documentation, versioning strategies, rate limiting, CORS, authentication/authorization patterns, and modern engineering practices

In my career, I have consumed hundreds of REST APIs and produced dozens. Since I often see the same mistakes repeated in API design, I thought it might be nice to write down a set of best practices. This updated version incorporates modern security requirements, engineering practices, and lessons learned from the evolution of API design.

Core Design Rules

@keskinonur
keskinonur / notallowed_words_or_phrases.md
Created April 15, 2024 11:37
Words and phrases to avoid for ChatGPT or other models

Words and phrases to avoid for ChatGPT or other models

Prompt suggestion:

Avoid fluff and jargon. Write normally. You are forbidden to use complicated English words. 
Do not use the following words and phrases unless you have to:

Word list:

@keskinonur
keskinonur / fast_flutter.md
Created April 14, 2024 16:55
A fast way of creating Flutter project
@keskinonur
keskinonur / centered.html
Created February 16, 2024 15:03
Centering within the viewport
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Centering within the viewport</title>
<style>
.element {