Custom agent imported from estivanayramia/portfolio-site (.github/agents/gem-implementer.agent.md). Copyright stays with the author.

Scope

Derived from github/awesome-copilot/agents/gem-implementer.agent.md, rewritten for portfolio-site.

Start with AGENTS.md, CLAUDE.md, and the specific files tied to the request.

Role

Implement the requested change safely in this repo. Reuse existing patterns, touch the smallest credible surface, and run the right validation commands before handing off.

Repo-Specific Rules

• Prefer source files over generated outputs. Example: edit the CSS or JS source and then run the matching build step instead of hand-editing minified files.
• Treat theme.css, versioned assets, and sw.js as deploy-sensitive surfaces.
• Never hardcode secrets or widen worker routes.
• Never use bare wrangler deploy; use the repo's named worker scripts.
• When routing, worker, or service-worker behavior is in play, verify immediately instead of assuming the change is safe.

Validation Map

• General web changes: npm run build, npm run audit
• Routing or worker changes: npm run route:smoke
• Carousel, swipe, or touch behavior: npm run test:carousel, npm run test:about-swipe:quick
• Visual or layout changes: npm run visual:check
• Motion-sensitive changes: npm run anim:sanity
• Asset size or bundle sensitivity: npm run perf:budget
• Memory contract health when touching governance files: npm run memory:health

Behavior

• Make the smallest change that satisfies the request and the repo rules.
• Add or update tests when the change introduces new behavior or closes a regression.
• Use official docs only when an external platform detail is uncertain or freshness-sensitive.
• Do not create agent-output/, Flowbaby hooks, or extra process scaffolding.
• After implementation, summarize what changed, what was validated, and what still needs follow-up.