Skip to content

jirawatp/resume-career-toolkit / skills/resume-section-guide

Resume Section Guide

Verified

Build individual resume sections optimized for specific career stages and role types. Use this skill when someone needs help with a specific resume section such as the summary, skills, experience, education, projects, or certifications. Trigger for "resume summary", "skills section", "experience section", "what to include", "resume sections", "professional summary", or any question about how to structure a particular part of a resume.

Resume Section Guide

Build each resume section to serve its purpose for the target role and career stage.

Professional Summary

When to include: Career changers (to explain the pivot), senior professionals (to distill a long career), people with non-obvious fit (to frame relevance). Skip if you are early career with a straightforward background.

Formula: "[Role] with [X years] in [domain]. [Top achievement with a number]. Skilled in [3-5 relevant keywords]."

Length: 2-4 sentences. No more.

Never write: "Results-oriented professional seeking challenging opportunities" (says nothing specific).

Skills Section

Placement: After summary, before experience, so ATS scans it early.

Organization: Group by category for technical roles (Languages, Frameworks, Tools, Cloud). Use a flat comma-separated list for non-technical roles.

Include: Skills you can discuss in an interview. Use exact phrasing from target job postings.

Exclude: Microsoft Office (assumed), "soft skills" as a list (demonstrate these in bullets instead), anything you cannot actually do.

Experience Section

Bullet count by recency: 4-6 for current/recent role, 3-4 for previous role, 2-3 for older roles. Cut ruthlessly for relevance.

Each bullet: Start with a strong verb, include at least one number, show result or scale.

Date format: Be consistent. "Jan 2020 - Present" or "01/2020 - Present". Never mix formats.

Multiple roles at one company: List each role separately under the company name to show progression.

Education Section

Early career: Include GPA (if above 3.5), relevant coursework, academic projects, honors. Mid-career: Degree, school, year. Drop GPA and coursework. Senior: Degree and school only. May drop graduation year to avoid age bias.

Additional Sections

Projects: Include if you are junior, changing careers, or the role values hands-on work. Format: name, tech stack, link, one-line description, key metric.

Certifications: Include if the job posting mentions them. List certification name, issuing body, and year.

Languages: Include only if relevant to the role or above conversational level. State proficiency clearly: Native, Professional, Conversational.

Volunteer: Include if it fills a gap, demonstrates leadership, or is directly relevant to the target role.

Section Order by Situation

Standard: Contact, Summary, Skills, Experience, Education Technical: Contact, Skills, Experience, Projects, Education New graduate: Contact, Education, Skills, Internships/Projects Executive: Contact, Executive Profile, Career Highlights, Experience, Board Roles, Education Career changer: Contact, Summary (pivot narrative), Skills (transferable), Experience (reframed), Bridge Experience, Education

reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall