williamzujkowski

Analyzes and optimizes frontend performance using Core Web Vitals, bundle analysis, lazy loading, image optimization, and caching strategies

Design RESTful APIs with OpenAPI 3.1/3.2, resource modeling, HTTP semantics, versioning, pagination, HATEOAS, and OWASP API Security.

Design data pipelines with quality checks, orchestration, and governance using modern data stack patterns for robust ELT/ETL workflows.

Validate WCAG 2.2 compliance (A/AA/AAA) with ARIA, color contrast, keyboard navigation, screen readers, and automated testing via axe-core/Pa11y.

Design Kafka architectures with exactly-once semantics, Kafka Streams, ksqlDB, Schema Registry (Avro/Protobuf), performance tuning, and KRaft.

Design RabbitMQ architectures with exchanges, quorum queues, routing patterns, clustering, dead letter exchanges, and AMQP best practices.

Configure Prometheus with alerting, recording rules, service discovery (K8s, Consul, EC2), federation, PromQL optimization, and Alertmanager.

Design unified dashboards with golden signals, OpenTelemetry correlation, SLO tracking, and Grafana 11 auto-correlations for metrics/logs/traces.

Orchestration & Events:

Kubernetes standards for container orchestration, deployments, services, ingress, ConfigMaps, Secrets, and security policies. Covers production-ready configurations, monitoring, and best practices for cloud-native applications.

Master Kotlin coding standards with null safety, coroutines, and idiomatic patterns. Use when developing JVM/Android applications requiring type-safe async programming.

Comprehensive coding standards and best practices for maintainable, consistent software development across multiple languages and paradigms

React frontend standards covering hooks (useState, useEffect, useContext, custom hooks), state management (Context API, Redux, Zustand), performance optimization (memoization, lazy loading, code splitting), testing with React Testing Library, and accessibility (WCAG 2.1, ARIA) for modern SPAs

Security Operations Center (SOC) practices, incident response, SIEM management, and threat hunting following NIST 800-61

Implement robust E2E tests with Playwright or Cypress using Page Object Model, proper waits, and CI/CD integration. Covers selector strategies, flaky test prevention, and cross-browser testing patterns.

Comprehensive testing standards including unit, integration, security, and property-based testing with TDD methodology

Build a new page in a project that consumes `remarque-tokens` — pick the right archetype, fetch registry items instead of transcribing markup, wire the page per AGENT_RULES pitfalls, and gate on remarque-audit plus the registry's own markup-contract assertions. Use when the user says "new page", "add a page", "build an essay", "build an archive page", "build a landing page", "use an archetype", or asks for a page in a Remarque-consuming project. Companion to the `remarque` loader skill — load that one first for the tier rules and the two build-time pitfalls; this skill is the page-building procedure on top of it, not a restatement of it.

Run the remarque-tokens consumer-conformance playbook — the exact procedure for bumping a project's remarque-tokens pin and getting back to a passing audit. Use when the user says "bump remarque-tokens", "upgrade the design system", "adopt remarque in an existing site", "update to the latest remarque-tokens", or when `remarque-audit`/`npm run audit` starts failing after a version bump (missing-token failures). Distinct from the `remarque` skill, which is the build/review contract for pages already on the current version — load this one specifically for the migration itself, then defer to `remarque` for any actual page work the migration surfaces.

Load the Remarque design system's implementation contract before building, editing, or reviewing any page in a Remarque-based project — a typography-first system for editorial, technical, and personal sites (17px body floor, three-font system, four-then-seven page archetypes, strict token tiers). Use when the user says "remarque", "design system", "build a new page", "new archetype page", "style this like the site", or asks for a page/component in a project that imports `remarque-tokens`. Also use before reviewing a PR that touches design-system tokens or page layout in such a project.