🔧 feat(portfolio): complete portfolio redesign spec

📝 Descripción / Description:
- EN: Implement full portfolio redesign with shared design system, semantic HTML5, accessibility, SEO, and comprehensive test suite
- ES: Implementar rediseño completo del portafolio con sistema de diseño compartido, HTML5 semántico, accesibilidad, SEO y suite de pruebas completa

📁 Files changed:
- styles.css (shared design system with light/dark themes, components, responsive breakpoints)
- main.js (ThemeEngine, LocaleEngine, Navigation, AnimationController, AccessRequestForm modules)
- index.html (restructured with semantic HTML5, shared assets, SEO metadata)
- learning-resources.html (restructured with shared assets, navbar, SEO)
- access-request.html (restructured with shared assets, form accessibility)
- 404.html (new error page with theme/locale support)
- sitemap.xml (new SEO sitemap listing all pages)
- robots.txt (new crawler directives)
- tests/ (13 test files: 5 unit test suites, 6 property-based test suites, HTML structure tests, SEO tests)
- package.json (test infrastructure with fast-check, jsdom)
- .kiro/specs/portfolio-redesign/ (requirements, design, tasks)
- .gitignore (updated for node_modules)

🏷️ Type: feat

Author: gamaware

.gitignore

@@ -1,10 +1,20 @@
-# General
+# macOS
 .DS_Store
 .AppleDouble
 .LSOverride
+._*
+
+# Windows
 Thumbs.db
 ehthumbs.db
 Desktop.ini
+$RECYCLE.BIN/
+
+# Kiro AI
+.kiro/cache/
+.kiro/logs/
+.kiro/temp/
+.kiro/.session
 
 # IDE - VSCode
 .vscode/*
@@ -19,87 +29,66 @@ Desktop.ini
 *.iml
 *.iws
 *.ipr
-.idea_modules/
+
+# Node
+node_modules/
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+package-lock.json
+yarn.lock
+.pnpm-debug.log*
+
+# Environment variables
+.env
+.env.*
+!.env.example
+
+# Build outputs
+dist/
+build/
+out/
+.cache/
+.parcel-cache/
+.next/
+.nuxt/
+.output/
+
+# Static site generators
+.jekyll-cache/
+.jekyll-metadata
+.sass-cache/
+_site/
 
 # Python
 __pycache__/
 *.py[cod]
 *$py.class
 *.so
-.Python
-env/
-build/
-develop-eggs/
-dist/
-downloads/
-eggs/
-.eggs/
-lib/
-lib64/
-parts/
-sdist/
-var/
-*.egg-info/
-.installed.cfg
-*.egg
 venv/
+env/
 ENV/
-
-# Node
-node_modules/
-npm-debug.log
-yarn-debug.log
-yarn-error.log
-.env
-.env.test
-.env.local
-.env.development.local
-.env.test.local
-.env.production.local
+*.egg-info/
 
 # AWS
 .aws-sam/
 samconfig.toml
-.chalice/deployments/
-.chalice/venv/
 cdk.out/
-.cdk.staging/
 .terraform/
 *.tfstate
 *.tfstate.*
 .terraform.lock.hcl
-terraform.tfvars
-*.tfvars.json
-crash.log
-
-# Docker
-.docker/
-
-# Kubernetes
-kubeconfig
-*.kubeconfig
 
 # Logs
-logs
+logs/
 *.log
-npm-debug.log*
-yarn-debug.log*
-yarn-error.log*
 
 # Sensitive data
 *.pem
 *.key
 *.p12
 *.pfx
-*.cer
-*.crt
-*.env
-*.env.*
 credentials
 credentials.json
-.secrets
+.secrets/
 .secret
-.password
-.passwords
-.token
-.tokens

.kiro/hooks/code-quality-review.kiro.hook

@@ -0,0 +1,21 @@
+{
+  "enabled": true,
+  "name": "Code Quality Review",
+  "description": "Analyzes modified source code files for potential improvements including code smells, design patterns, and best practices. Generates suggestions for improving readability, maintainability, and performance while preserving existing functionality.",
+  "version": "1",
+  "when": {
+    "type": "fileEdited",
+    "patterns": [
+      "*.html",
+      "*.css",
+      "*.js",
+      "*.py",
+      "*.yml",
+      "*.yaml"
+    ]
+  },
+  "then": {
+    "type": "askAgent",
+    "prompt": "Review the edited file for potential code quality improvements. Analyze for:\n\n1. Code smells (duplicated logic, overly complex functions, magic numbers, dead code)\n2. Design pattern opportunities (better organization, separation of concerns)\n3. Best practices (semantic HTML, accessible markup, modern CSS/JS patterns)\n4. Readability (naming, comments, structure)\n5. Maintainability (DRY violations, tight coupling)\n6. Performance (unnecessary DOM queries, inefficient selectors, render-blocking patterns)\n\nProvide concise, actionable suggestions. Do not rewrite the entire file — just highlight specific areas and recommend targeted improvements. Preserve existing functionality."
+  }
+}

.kiro/hooks/git-auto-commit.kiro.hook

@@ -0,0 +1,13 @@
+{
+  "enabled": true,
+  "name": "Auto Git Commit & Push",
+  "description": "When the agent finishes a task, automatically runs git status, stages changes, creates a structured bilingual commit message (English/Spanish), and pushes to main.",
+  "version": "1",
+  "when": {
+    "type": "agentStop"
+  },
+  "then": {
+    "type": "askAgent",
+    "prompt": "Run the following git workflow in order. Do NOT skip any step:\n\n1. Run `git status` to see what changed.\n2. Run `git diff --stat` to get a summary of modifications.\n3. Run `git add -A` to stage all changes.\n4. Create a commit with a structured message following this EXACT template every time:\n\n```\n🔧 <type>(<scope>): <short summary in English>\n\n📝 Descripción / Description:\n- EN: <bullet points describing what changed in English>\n- ES: <bullet points describing what changed in Spanish>\n\n📁 Files changed:\n- <list each file changed>\n\n🏷️ Type: <feat|fix|refactor|style|docs|chore|test>\n```\n\nWhere:\n- `type` is one of: feat, fix, refactor, style, docs, chore, test\n- `scope` is the area affected (e.g., index, access-request, styles, docs, config)\n- The short summary is max 50 chars, imperative mood\n- Description bullets should be concise and match between EN and ES\n\n5. Run `git push origin main` to push the commit.\n\nAlways follow this exact structure. Never deviate from the template."
+  }
+}

.kiro/hooks/sync-translations.kiro.hook

@@ -0,0 +1,16 @@
+{
+  "enabled": true,
+  "name": "Sync Translations",
+  "description": "Monitors HTML files containing inline translation objects (index.html, access-request.html, learning-resources.html) for changes to user-facing text. When changes are detected, identifies new or modified English (en) translation keys and generates corresponding Spanish (es) and Portuguese (pt) translations, maintaining proper context, meaning, and locale-specific conventions.",
+  "version": "1",
+  "when": {
+    "type": "fileEdited",
+    "patterns": [
+      "*.html"
+    ]
+  },
+  "then": {
+    "type": "askAgent",
+    "prompt": "A user-facing HTML file was just edited. This project uses inline JavaScript translation objects (`const translations = { en: {...}, es: {...}, pt: {...} }`) inside each HTML file for i18n support across English, Spanish, and Portuguese.\n\nPlease do the following:\n1. Locate the `translations` object in the edited file.\n2. Compare the `en` (English) keys and values against the `es` (Spanish) and `pt` (Portuguese) sections.\n3. If any keys exist in `en` but are missing from `es` or `pt`, or if an English value has been modified (suggesting the translation is now stale), generate accurate translations for the missing or outdated entries.\n4. Ensure translations:\n   - Maintain the original meaning and context\n   - Follow locale-specific conventions (e.g., formal/informal tone consistency, date formats, punctuation)\n   - Match the existing translation style and tone already used in that file\n5. Insert the new or updated translations into the `es` and `pt` sections of the same file.\n6. If all translations are already in sync, do nothing and confirm they are up to date."
+  }
+}

.kiro/hooks/update-docs-on-change.kiro.hook

@@ -0,0 +1,19 @@
+{
+  "enabled": true,
+  "name": "Update Docs on Source Change",
+  "description": "When source files (HTML, CSS, YAML workflows, or issue templates) are edited, automatically update the relevant documentation in docs/ and README.md to reflect the changes.",
+  "version": "1",
+  "when": {
+    "type": "fileEdited",
+    "patterns": [
+      "*.html",
+      "*.css",
+      ".github/workflows/*.yml",
+      ".github/ISSUE_TEMPLATE/*.yml"
+    ]
+  },
+  "then": {
+    "type": "askAgent",
+    "prompt": "A source file was just edited. Review the change and determine if the documentation in docs/ (especially docs/README.md and docs/website-architecture.md) or the root README.md needs to be updated to stay in sync. If so, make the minimal necessary documentation updates. Focus on accuracy — only update docs that are actually affected by the change."
+  }
+}

.kiro/specs/portfolio-redesign/.config.kiro

@@ -0,0 +1 @@
+{"generationMode": "requirements-first"}