bakirgdev

applyTo	**

Copilot global instructions

Environment

• macOS + zsh. Stacks: Next.js + React + TypeScript + Tailwind + shadcn/ui, Postgres + Redis + Supabase, Python, Terraform/HCL, SQL, Docker, C++, Swift.
• Default tooling when project does not enforce its own: pnpm + biome (JS/TS), uv + ruff (Python).

bakirgdev

Claude Code global instructions

Environment

• macOS + zsh exclusively. All shell commands target this. Use brew & pbcopy/pbpaste. No assumptions about Linux-only tooling.
• Tooling defaults when a project does not enforce its own:
  • JS/TS: pnpm (not npm/yarn), biome (not Prettier/ESlint)
  • Python: uv (not pip/poetry/venv), ruff (not black/flake8/isort)
• Stacks I work in: Next.js + React + TypeScript + Tailwind + shadcn/ui, Postgres + Redis + Supabase, Python, Terraform/HCL, SQL, Docker + Docker Compose, C++, Swift. When a stack is ambiguous from context, ask before assuming.

Communication

bakirgdev

Tone and format

• Direct answers. No preamble, no question restatement, no closing pleasantries, no filler, no emojis, no reflexive apologies.
• Peer tone. Assume domain literacy. Skip 101-level scaffolding.
• No sugar coating. State conclusions plainly, including unwelcome ones.
• IMPORTANT: never use em dashes. Use commas, colons, parentheses, or split sentences.
• Scannable: bullets, bold for key terms, tables for comparisons, code blocks for code, commands, paths, exact strings.
• Density first. Cut anything that does not add signal.

Reasoning

• Reason before answering: decompose, surface assumptions, check edge cases.

bakirgdev

{
  "name": "__________",
  "version": "1.0.0",
  "private": true,
  "scripts": {
    "modules:update": "pnpx npm-check-updates -u --format group",
    "install:clean": "pnpx rimraf node_modules/ pnpm-lock.yaml && pnpm install",
    "supabase:typegen": "pnpx supabase gen types typescript --project-id \"______________\" --schema public > src/types/supabase.ts",
 "tsc": "pnpx rimraf .next/ && tsc --noEmit && pnpx rimraf tsconfig.tsbuildinfo",

bakirgdev

How to un-occupy port 53 used by systemd-resolved on Linux systems

On Linux systems systemd-resolved handles DNS resolution on port 53, thus occupying it on system level.

If you wish to, for example, run a custom DNS server; you'll need to unassign the port 53 by disabling systemd-resolved's usage of it. That can be achieved by (run these as root or sudo):

1. sudo nano /etc/systemd/resolved.conf (to open the configuration file)
2. locate line #DNSStubListener=yes
3. uncomment the line & change value to no --> DNSStubListener=no
4. exit saving the changes on the file

bakirgdev

Routing emails via CloudFlare is a free, simple and secure way to connect your domain with a professional email using Gmail inbox/client. Follow my comprehensive steps below to achieve that functionality and level-up your impact.

1. Enable 2FA on Google Account

Two-factor authentication is required for your Google account

Enable 2FA in your Google account here

2. Create App Password on Google Account

bakirgdev

Steam Launch Options

-novid -fullscreen +fps_max 0 +cl_forcepreload 1 -nojoy -high +violence_hblood 0 -console -refresh 144

Keybinds

bind mwheelup ";+jump;-jump;";