
Adding A Project
- 4 installs
- Updated July 18, 2026
- arjitj2/arjit-skills
adding-a-project is a Claude skill that adds a new project to the owner's personal site and resume, compiles the resume PDF, and pushes it live.
About
This skill adds a new project to the owner's personal site and resume and makes it live. It updates the projects list in the arjit-me site and the projects.tex file in arjit-resume, compiles the resume PDF, and pushes the site to main to deploy. It is a personal, repo-specific publishing workflow tied to fixed local paths.
- Updates both arjit-me site and arjit-resume from one workflow
- Compiles the resume PDF (make build) after resume edits
- Pushes arjit-me to main to deploy
Adding A Project by the numbers
- 4 all-time installs (skills.sh)
- Ranked #1,780 of 2,715 Automation & Workflows skills by installs in the Skillselion catalog
- Data as of Jul 28, 2026 (Skillselion catalog sync)
adding-a-project capabilities & compatibility
- Capabilities
- resume · portfolio update
- Works with
- github
- Use cases
- resume
What adding-a-project says it does
Use when adding a new project to the user's personal site and resume, or when the user says to make something "live".
Resume uses human-readable names; site can use either.
npx skills add https://github.com/arjitj2/arjit-skills --skill adding-a-projectAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 4 |
|---|---|
| Last updated | July 18, 2026 |
| Repository | arjitj2/arjit-skills ↗ |
What it does
Add a new project to the owner's personal site and resume, compile the resume PDF, and push it live.
Who is it for?
Adding a project to the owner's arjit-me site and arjit-resume and deploying it
Skip if: General-purpose portfolio or resume generation outside these specific repos
When should I use this skill?
Adding a new project to the personal site and resume, or when the user says to make something live
What you get
The new project appears on the site and resume PDF and is pushed live
- updated projects.ts entry
- updated projects.tex entry
- recompiled resume PDF
By the numbers
- updates 2 repos (arjit-me, arjit-resume)
- 4-step process
Files
Adding a Project
Overview
When a new project is created, it needs to be added to both the personal site (arjit-me) and the resume (arjit-resume), then made live.
Locations
- Site projects:
~/repos/arjit-me/lib/projects.ts - Resume projects:
~/repos/arjit-resume/resume/projects.tex - Resume PDF:
~/repos/arjit-resume/arjit_jaiswal_resume.pdf(symlinked to~/Documents/arjit_jaiswal_resume.pdf)
Process
1. Add to `lib/projects.ts` in arjit-me:
- Add a new entry to the
projectsarray - Set
featured: falseunless told otherwise - Use the repo slug for
id, but a human-readable name fortitleon the site is fine either way
2. Add to `resume/projects.tex` in arjit-resume:
- Add a
\projectentry{Name}{url}{description}{tech}{date} - Always use human-readable names, not repo slugs (e.g. "Arjit Skills" not "arjit-skills")
- Keep descriptions concise (one line)
- Insert in chronological order (newest first)
3. Compile the resume PDF:
cd ~/repos/arjit-resume
make buildThe symlink at ~/Documents/arjit_jaiswal_resume.pdf auto-updates.
4. Push the site live:
cd ~/repos/arjit-me
git add lib/projects.ts
git commit -m "Add <project-name> to projects"
git push origin mainRules
- Resume uses human-readable names; site can use either.
- Always compile the PDF after resume changes.
- Always push arjit-me to main to deploy.
Related skills
FAQ
Which repos does this update?
It updates both arjit-me (the personal site, lib/projects.ts) and arjit-resume (resume/projects.tex), then compiles the PDF and pushes.
How is the resume named on the site versus the resume?
The resume always uses human-readable project names, while the site can use either the repo slug or a human-readable name.