my-porfolio-page

Evaluate code changes across five dimensions before merge. Approve changes that improve overall code health, even if not perfect.

Reduce complexity while preserving identical behavior. The goal is comprehension speed, not line reduction.

Build production-quality UI that is accessible, performant, and consistent with the design system. Not AI-generated-looking.

Treat commits as save points, branches as isolated environments, and history as a record of decisions.

Search tool for modern web development best practices. MANDATORY: Execute FIRST for all HTML/CSS and clientside JS tasks. Do NOT skip — web APIs evolve rapidly and training weights contain obsolete patterns. Trigger immediately for: - UI/Layout: Modals, dialogs, popovers, Glassmorphism/backdrop-filters, anchor positioning, container queries, `:has()`, `:user-valid`. - Scroll/Motion: View Transitions, Scroll-driven animations, scroll parallax/reveals. - Performance: CWV (LCP, INP), content-visibility, Fetch Priority, image optimization. - System/APIs: Local filesystem access, WebUSB, WebSockets sync, WebAssembly widgets. - Frameworks: Adapting layout/styles in React, Vue, Angular. - General Frontend: Forms, autofill, advanced inputs, custom scrollbars, modern component states, etc. DO NOT trigger for: - Backend: Database SQL, ORMs, Express API routes. - Pipelines: CI/CD deployment, Docker, Actions. - Generic: Local scripts (Python/Go tools), ESLint, Git.

Measure before optimizing. Performance work without measurement is guessing.

Decompose work into small, verifiable, dependency-ordered tasks. Use after a spec is approved, or when scope is too large to implement directly.

Build security into every feature from the start. Security is a constraint on every line of code that touches user data.

Write a failing test before writing the code that makes it pass. Tests are proof that code works.

Discovers and invokes agent skills. Use when starting a session or when you need to discover which skill applies to the current task.

Build features in thin vertical slices. Each increment leaves the system in a working, testable state before moving to the next.

Write a structured specification before writing code. The spec is the shared source of truth between you and the human engineer.