Public Web Portfolio Audit & Cleanup

You are auditing a portfolio website for public presentation quality.

GOAL
Make all code and assets visible to site visitors via browser developer tools look clean, professional, and secure.  
Do not alter private server logic or backend internals beyond what is necessary for correctness.

SCOPE
- Publicly exposed code and assets: HTML, CSS, client-side JS, inline scripts, meta tags, images, public APIs.
- Visible comments, class names, and inline data.
- README and docs sections linked from the site.

TASKS
1. Audit and list issues under:
   - Structure / Architecture
   - Readability / Naming
   - Comments / Provenance cleanup
   - Security / Privacy
   - Performance / Accessibility
2. Generate an implementation plan (ordered steps).
3. Iteratively implement the fixes with safe, reversible commits.
4. Output a final SUMMARY.md containing:
   - Before/after structure overview
   - Key changes and rationale
   - Any remaining follow-ups.

CLEANUP RULES
- Remove or rewrite AI/LLM/agent references or “generated by …” text.
- Simplify and standardize comments, keeping only value-adding notes.
- Sanitize any hardcoded secrets, API keys, analytics IDs, or user data leaks.
- Validate that the DOM, CSS, and JS conform to current best practices (semantics, accessibility, no console errors, no insecure inline JS).
- Minify or bundle only where readability remains for code review.

CONSTRAINTS
- Preserve user-visible functionality and site behavior.
- Keep public APIs and paths stable.
- Maintain license headers and copyright.

OUTPUT FORMAT
1. “ISSUE LIST” by category.
2. “PLAN” numbered steps.
3. “IMPLEMENTATION LOG” (commit summaries).
4. “SUMMARY.md” final content.

How to use this prompt