gulmezeren2-byte
- 66 skills
- 0 followers
- 14 hours ago last updated
- ▌ Refactoring · gulmezeren2-byteChange structure without changing behaviour: identifying the seam, characterising with tests first, and stopping before the refactor becomes a rewrite.
- ▌ Airflow Dags · gulmezeren2-byteIdempotent tasks, backfills that do not double-count, and sensors that do not hold a worker slot for a day.
- ▌ CI Pipelines · gulmezeren2-bytePipeline structure that fails fast and honestly: what to run per-commit versus nightly, caching that does not go stale, and flaky-test quarantine that does not hide regressions.
- ▌ Git Workflow · gulmezeren2-byteBranching, rebase-versus-merge, and writing a commit message that explains the why. Includes recovering from the mistakes that feel unrecoverable.
- ▌ Regex Review · gulmezeren2-byteRead and repair a regular expression: anchoring, catastrophic backtracking, and the character class that quietly matches a newline.
- ▌ Supabase Rls · gulmezeren2-byteRow Level Security policies that hold under an anon key: policy per operation, testing as an unauthenticated caller, and the join that leaks a row the policy meant to hide.
- ▌ Accessibility · gulmezeren2-byteKeyboard paths, focus order, contrast and labelling — checked with a screen reader rather than assumed from the markup.
- ▌ Adr Authoring · gulmezeren2-byteRecord an architecture decision with the alternatives and the forces, so the next person can tell whether it still holds.
- ▌ Dbt Modelling · gulmezeren2-byteStaging, marts and tests in dbt: incremental models that survive a late-arriving row, and a test suite that fails for the right reason.
- ▌ Docker Images · gulmezeren2-byteBuild small, reproducible images: layer ordering for cache hits, multi-stage builds, pinning by digest, and why running as root is still the most common finding.
- ▌ Figma Handoff · gulmezeren2-byteTurn a design file into implementable specs: tokens, spacing scales, and the states designers forget to draw.
- ▌ Firebase Auth · gulmezeren2-byteSign-in flows, custom claims and token refresh: what belongs in a claim versus a database read, and the race between a claim change and the token that still carries the old one.
- ▌ K8S Debugging · gulmezeren2-byteDiagnose a failing workload on Kubernetes: reading events before logs, distinguishing CrashLoopBackOff causes, probe misconfiguration, and the resource-limit symptoms that look like application bugs.
- ▌ Kafka Streams · gulmezeren2-bytePartitioning, ordering guarantees and consumer-group rebalances: what a key buys you, and the reprocessing a retry actually causes.
- ▌ Observability · gulmezeren2-byteTraces, metrics and logs that answer a question: cardinality budgets, span naming, and the dashboard nobody looks at.
- ▌ Openapi Specs · gulmezeren2-byteAuthor and validate an OpenAPI document that generators accept: schema reuse, discriminated payloads, and examples that stay in step with the schema.
- ▌ Pandas Idioms · gulmezeren2-byteVectorised transformations, groupby patterns, and the chained assignment that appears to work until it does not.
- ▌ Prompt Design · gulmezeren2-byteStructure a prompt so the failure mode is visible: task framing, worked examples, and asking for the reasoning you intend to check.
- ▌ SQL Analytics · gulmezeren2-byteWindow functions, grain discipline and the join that silently fans out rows — with the row count checked before the number is believed.
- ▌ Test Strategy · gulmezeren2-byteChoose the cheapest test that would actually have caught the bug: what belongs in a unit test versus an integration test, and when a test asserts the implementation instead of the behaviour.
- ▌ AWS Iam Review · gulmezeren2-byteLeast-privilege review of IAM policies: spotting wildcard actions, confused-deputy exposure in cross-account roles, and the difference between a resource policy and an identity policy in an access decision.
- ▌ Data Modelling · gulmezeren2-byteDimensional versus normalised design, slowly changing dimensions, and choosing a grain you can still defend in six months.
- ▌ Go Concurrency · gulmezeren2-byteChannels, contexts and cancellation in Go: goroutine leaks, when a mutex beats a channel, and propagating deadlines through a call tree.
- ▌ GRAPHQL Schema · gulmezeren2-byteSchema design that ages: nullability meaning something, pagination via connections, and the resolver that quietly becomes an N+1.
- ▌ Ml Experiments · gulmezeren2-byteTrack an experiment so a result can be reproduced: seeds, data versions, and the holdout that never gets peeked at.
- ▌ Perf Profiling · gulmezeren2-byteFind where the time actually goes before optimising: sampling versus instrumentation, reading a flame graph, and separating a slow algorithm from a slow I/O wait.
- ▌ Playwright E2e · gulmezeren2-byteEnd-to-end tests that are not flaky: auto-waiting over sleeps, locators that survive a redesign, and isolating state so a failure points at one cause.
- ▌ React Patterns · gulmezeren2-byteComponent composition, hooks discipline and render-cost review for React 19: when to reach for a server component, why a context provider re-renders more than you expect, and how to read a Profiler flame chart before reaching for memo.
- ▌ Redis Patterns · gulmezeren2-byteCaching, locks and queues on Redis: TTL discipline, the lock that expires mid-work, and why a cache stampede shows up only under load.
- ▌ Rust Ownership · gulmezeren2-byteBorrow checker fluency: lifetimes that actually need naming, when to reach for Rc/RefCell, and the clone that is fine versus the clone that hides a design problem.
- ▌ Stripe Billing · gulmezeren2-byteSubscriptions, proration and webhook idempotency — including the reconciliation nobody writes until the first mismatch.
- ▌ MCP Integration · gulmezeren2-byteWire an MCP server into a client: transports, tool schemas that an agent can route on, and the read-only guarantees worth enforcing in code.
- ▌ Onboarding Docs · gulmezeren2-byteDocumentation that gets someone to their first successful change, measured by whether they got there.
- ▌ Postgres Tuning · gulmezeren2-byteIndex selection, EXPLAIN reading and lock diagnosis for PostgreSQL: which scan the planner chose and why, when an index is not used, and how to find the query holding the lock everyone else is waiting on.
- ▌ Security Review · gulmezeren2-byteReview a change for injection, authz gaps, secret handling and unsafe deserialisation, with the threat model stated rather than assumed.
- ▌ Shell Scripting · gulmezeren2-byteScripts that fail loudly: set -euo pipefail, quoting that survives spaces, and the trap that cleans up on the path nobody tested.
- ▌ Tailwind Design · gulmezeren2-byteUtility composition without a class-name soup: extracting a component when a pattern repeats, using the scale instead of arbitrary values, and keeping dark mode a variant rather than a fork.
- ▌ Excel Automation · gulmezeren2-byteRead and write workbooks programmatically: preserving formatting, handling merged cells, and the date serial that silently shifts by a day.
- ▌ Makefile Hygiene · gulmezeren2-byteTargets that are honest about their inputs: phony targets, real dependencies, and the rebuild that should not have happened.
- ▌ Migration Review · gulmezeren2-byteReview a database migration before it runs in production. Covers lock acquisition and how long each statement holds one, the difference between a metadata lock and a row lock, adding a column with a default on a large table, backfilling in batches with a bounded window, creating an index concurrently and what happens when that fails halfway, dropping a column that application code still references, renaming in two deploys instead of one, foreign keys added as NOT VALID and validated separately, the difference between a transactional and a non-transactional migration and which engines allow which, statement timeouts as a safety net, estimating table size and row count before choosing a strategy, checking replica lag before and during, the rollback that is not actually possible once data is written, and how to stage a destructive change so that each step is independently reversible. Also covers reading the query plan after the change to confirm the index is used, verifying constraint validity, and writing the r
- ▌ Typescript Types · gulmezeren2-byteModel the domain in the type system: discriminated unions over optional soup, when a generic earns its complexity, and reading a long inference error.
- ▌ Changelog Writing · gulmezeren2-byteWrite a changelog a user can act on: what changed, whether it breaks them, and what to do about it.
- ▌ Cost Optimisation · gulmezeren2-byteFind cloud spend that buys nothing: idle capacity, egress surprises, and the storage class nobody revisited.
- ▌ Incident Response · gulmezeren2-byteRun an incident without making it worse: stabilise before diagnosing, a written timeline, and a postmortem that names causes not people.
- ▌ Nextjs App Router · gulmezeren2-byteRouting, layouts, streaming and cache semantics in the Next.js App Router: which boundary makes a component a server component, why a fetch is deduplicated, when revalidation actually happens, and reading the build output to see what became static.
- ▌ Terraform Modules · gulmezeren2-byteModule boundaries, state layout and drift review for Terraform: what belongs in a module versus a root, how to split state so a blast radius stays small, and reading a plan for the change you did not intend.
- ▌ License Compliance · gulmezeren2-byteReconcile a dependency tree against what you are allowed to ship, including the transitive copyleft nobody declared.
- ▌ Email Deliverability · gulmezeren2-byteSPF, DKIM and DMARC alignment, warm-up, and the content patterns that route a legitimate message to spam.
- ▌ Skilldoctor · gulmezeren2-byteDiagnose the Claude Code skills installed on this machine — why one never triggers, and whether Claude can see it at all. Use when the user says a skill isn't firing, isn't triggering, or is being ignored; asks to check, audit, or debug their skills; mentions the skill description budget, truncated skills, or duplicate skills; or asks whether a skill they installed is safe to trust. Runs a deterministic CLI over every installed skill at once, so it catches whole-system problems no single-file check can see.
- ▌ I18N · gulmezeren2-byteExternalise strings without breaking layout: plural rules, RTL, date and number formats, and the concatenation that cannot be translated.
- ▌ LLM Cost · gulmezeren2-byteToken accounting across a pipeline: where the spend actually accrues, caching that works, and the retry loop nobody budgeted for.
- ▌ Review Pr · gulmezeren2-byteReview a pull request for correctness, design and readability, naming the severity of each comment so the author knows what blocks the merge.
- ▌ API Design · gulmezeren2-byteREST and RPC surface design: resource modelling, idempotency, pagination that survives inserts, error shapes a client can act on, and versioning that does not strand callers.
- ▌ Django Orm · gulmezeren2-byteQuery construction, N+1 detection and migration safety for Django: select_related vs prefetch_related, when a migration needs a separate data step, and how to read the SQL a queryset actually emits.
- ▌ Notion API · gulmezeren2-byteRead and write Notion databases: property types, pagination, and rate limits that appear only at scale.
- ▌ Slack Bots · gulmezeren2-byteSlash commands, interactivity payloads, and the three-second acknowledgement deadline that shapes the whole design.
- ▌ Agent Evals · gulmezeren2-byteMeasure an agent instead of vibing it: fixed task sets, seeded runs, and a rubric written before the results are seen.
- ▌ Code Review · gulmezeren2-byteReview for correctness first, then design, then style — with the severity said out loud so the author knows what blocks the merge.
- ▌ Powerbi Dax · gulmezeren2-byteMeasures over calculated columns, filter context, and the time-intelligence pattern that breaks on a non-standard calendar.
- ▌ Otif Analysis · gulmezeren2-byteAudit delivery performance from order-level data - compute the OTIF metric ladder (tolerant to strict), find where lateness concentrates, and quantify the gap between the reported KPI and what customers experience. Use when the user mentions OTIF, on-time delivery, delivery performance, late orders, teslimat performansı, zamanında teslimat, or asks why customers complain despite a high on-time score. Differentiator - exposes measurement choices before optimizing operations.
- ▌ Using Ops Method · gulmezeren2-byteEntry point for any operations or supply-chain data analysis - routes the work through a fixed method (brief, data contract, honest metrics, driver decomposition, stress test, decision memo) and calls the specialized skills at the right step. Use when starting any ops analysis, KPI study, delivery/forecast/inventory question, operasyon analizi, veri analizi, or when unsure which ops skill applies. Differentiator - enforces sequence and validation, not just tool choice.
- ▌ Root Cause Pareto · gulmezeren2-byteBuild a decision-grade Pareto for downtime, defects, complaints or delays - with unit-of-measure discipline, category hygiene, exposure normalization and a follow-up metric. Use when the user mentions pareto analysis, kök neden, duruş analizi, downtime, arıza analizi, defect ranking, şikayet analizi, 80/20 analysis. Differentiator - treats the Pareto as the start of a causal investigation, not a bar chart deliverable.
- ▌ Weekly Ops Report · gulmezeren2-byteTurn raw operational data into a weekly management report that answers exactly three questions - what changed, where is it concentrated, what needs a decision. Use when the user mentions weekly report, haftalık rapor, yönetim raporu, ops review, KPI summary, or asks to summarize operational data for managers. Differentiator - contract-first reporting with plain-language findings and driver decomposition, never a chart dump.
- ▌ Safety Stock Review · gulmezeren2-byteSize or audit safety stock with assumption checks - the z*sigma*sqrt(LT) formula plus an empirical stress test of what it actually delivers (cycle service vs fill rate) per variability class. Use when the user mentions safety stock, emniyet stoku, emniyet stoğu, reorder point, service level, stok seviyesi belirleme. Differentiator - refuses to hand back a number without validating the demand-distribution assumptions behind it.
- ▌ Abc Xyz Segmentation · gulmezeren2-byteSegment a SKU portfolio on value (ABC) and demand variability (XYZ), produce the 9-box with a planning policy per cell, and reallocate planner attention accordingly. Use when the user mentions ABC analysis, inventory segmentation, SKU rationalization, stok segmentasyonu, envanter sınıflandırma, or asks which items deserve forecasting effort. Differentiator - ABC alone is treated as half an answer; policy lives in the value x variability combination.
- ▌ Forecast Accuracy Review · gulmezeren2-byteEvaluate demand-forecast quality honestly - WMAPE, bias and Forecast Value Added against a naive benchmark over a rolling-origin backtest. Use when the user mentions forecast accuracy, MAPE, demand planning performance, tahmin doğruluğu, talep tahmini, or asks whether a forecasting process or tool is worth it. Differentiator - judges the process (value added vs doing nothing), not just the model.