메뉴
Use when implementing, auditing, or documenting mobile-responsive, touch-friendly, and accessible web UI (viewport, tap targets, forms, media, Core Web Vitals).
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | accessibility-mobile |
| description | Use when implementing, auditing, or documenting mobile-responsive, touch-friendly, and accessible web UI (viewport, tap targets, forms, media, Core Web Vitals). |
Read these files before acting:
docs/skills/global-project-rules/SKILL.mddocs/skills/accessibility-mobile/SKILL.mddocs/design-system.mdCreates 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.
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.
Use when setting up, restructuring, documenting, or enforcing repository layout, structure docs, or project organization.