From egg
This skill should be used when the user has already run resume-analyzer and wants to generate the tailored resume.tex. Trigger phrases include "generate resume", "write the resume", "create resume.tex", "tailor the resume now", "build the resume from notes", or when the user asks to proceed after a resume analysis session. It reads the notes.md produced by resume-analyzer and generates a tailored LaTeX resume.
npx claudepluginhub luqmannurhakimbazman/ashfordThis skill uses the workspace's default tool permissions.
Generate a tailored `resume.tex` from analysis notes. Reads `hojicha/<company>-<role>-resume/notes.md` (produced by `resume-analyzer`) and the master resume (`hojicha/resume.tex`).
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.
Generate a tailored resume.tex from analysis notes. Reads hojicha/<company>-<role>-resume/notes.md (produced by resume-analyzer) and the master resume (hojicha/resume.tex).
Prerequisite: notes.md must exist in the output directory. If missing, tell the user to run resume-analyzer first.
candidate-context.md, and discoveries persisted during analysis.fed-res.cls document class. Do not modify \documentclass[letterpaper,12pt]{fed-res} or add packages. Copy hojicha/fed-res.cls into the output directory.Required:
- notes.md from the output directory (keyword analysis, gap analysis, recommendations)
- Master resume: hojicha/resume.tex
- Candidate context: hojicha/candidate-context.md
Generate a role-specific summary if space permits. Omit if the resume already speaks for itself.
| Experience Level | Order |
|---|---|
| <3 years / recent grad | Summary, Education, Experience, Projects, Skills |
| 3+ years | Summary, Experience, Education, Projects, Skills |
Use the recommendation from notes.md if present.
Rewrite experience bullets using the XYZ formula:
Accomplished [X] as measured by [Y], by doing [Z]
Keyword placement priority:
Review commented-out sections in the master resume. Uncomment entries that strengthen the application per notes.md recommendations. Comment out entries that weaken the narrative. Link project names to GitHub repos where possible.
Reorder skills categories and items to front-load the most relevant ones. First items in each line are what ATS and recruiters see first.
Create hojicha/<company>-<role>-resume/resume.tex:
\documentclass[letterpaper,12pt]{fed-res}hojicha/fed-res.cls into output directoryVerify: All meaningful content is text (not layout-dependent), special characters render when LaTeX is stripped, acronyms expanded at least once.
Append a "Changes Made" section to notes.md listing all modifications.
| Command | Usage |
|---|---|
\resumeSubheading{Org}{Loc}{Title}{Date} | Experience/education entry |
\resumeSubheadingShort{Title}{Date} | Entry without location |
\resumeSubSubheading{Title}{Date} | Sub-position at same org |
\resumeProjectHeading{Title | Tech}{Date} | Project entry |
\resumeItem{text} | Bulleted item |
\resumeSubItem{text} | Compact bullet variant |
\resumeSubHeadingListStart/End | Wrap subheading groups |
\resumeItemListStart/End | Wrap bullet lists |
Skills section pattern:
\section{Skills and Interests}
\begin{itemize}[leftmargin=0.15in, label={}]
{\item{
\textbf{Category}{: item1, item2, item3} \\
\textbf{Category}{: item1, item2, item3}
}}
\end{itemize}
Header pattern:
\begin{center}
\textbf{\Huge \scshape Name} \\ \vspace{1pt}
\underline{email} \ $|$ \ \underline{linkedin} \ $|$ \
\underline{github} \\ \vspace{1pt}
\end{center}
Commenting: Prefix every line with % to hide a section. Remove % to restore.
Do NOT add packages to resume.tex -- all formatting is handled by fed-res.cls.