Menu
Use when planning, scaffolding, restructuring, or documenting the web app: application mode, stack, routes, data flow, frontend/backend boundary, and the design-quality gate.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Creates and audits GitHub portfolio material — profile READMEs, per-project READMEs, and repo pinning/organization strategy — optimized for how recruiters and technical reviewers actually evaluate GitHub profiles. Use this skill whenever the user asks to write, improve, or review a README; asks how to make a repo or profile "look good," "portfolio-ready," or "hireable"; asks what to pin; asks for help before a job/internship/PhD-internship application; or mentions showcasing projects to recruiters, hiring managers, or research reviewers. Trigger even if the user just says "clean up this repo" or "write docs for this project" — README quality is almost always part of what they need. Has two modes: standard (SWE/new-grad hiring) and research (PhD/research-lab internships, e.g. applying to industry research labs) — ask or infer which applies before writing.
Read this skill first before doing any work in the Magnification repository. It defines the source-of-truth docs, environment manager, documentation-maintenance rules, testing/verification expectations, and the git workflow every agent must follow.
Creates and audits GitHub portfolio material — profile READMEs, per-project READMEs, and repo pinning/organization strategy — optimized for how recruiters and technical reviewers actually evaluate GitHub profiles. Use this skill whenever the user asks to write, improve, or review a README; asks how to make a repo or profile "look good," "portfolio-ready," or "hireable"; asks what to pin; asks for help before a job/internship/PhD-internship application; or mentions showcasing projects to recruiters, hiring managers, or research reviewers. Trigger even if the user just says "clean up this repo" or "write docs for this project" — README quality is almost always part of what they need. Has two modes: standard (SWE/new-grad hiring) and research (PhD/research-lab internships, e.g. applying to industry research labs) — ask or infer which applies before writing.
Use when implementing, auditing, or documenting mobile-responsive, touch-friendly, and accessible web UI (viewport, tap targets, forms, media, Core Web Vitals).
Read this FIRST before any work in this repo. It defines the source-of-truth docs, the uv environment, documentation-maintenance rules, testing expectations, and the git workflow.
Use when asked to create, refine, or evaluate an implementation plan, roadmap, migration plan, or staged sequence of work before coding.
| name | website-architecture |
| description | Use when planning, scaffolding, restructuring, or documenting the web app: application mode, stack, routes, data flow, frontend/backend boundary, and the design-quality gate. |
Read these files before acting:
docs/skills/global-project-rules/SKILL.mddocs/skills/website-architecture/SKILL.mddocs/architecture.mddocs/routes.mddocs/api-contract.mddocs/data-flow.mddocs/design-system.md