adding-a-project
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
-
Add to
lib/projects.tsin 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
- Add a new entry to the
-
Add to
resume/projects.texin 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)
- Add a
-
Compile the resume PDF:
cd ~/repos/arjit-resume make buildThe symlink at
~/Documents/arjit_jaiswal_resume.pdfauto-updates. -
Push the site live:
cd ~/repos/arjit-me git add lib/projects.ts git commit -m "Add <project-name> to projects" git push origin main
Rules
- Resume uses human-readable names; site can use either.
- Always compile the PDF after resume changes.
- Always push arjit-me to main to deploy.
More from arjitj2/arjit-skills
creating-skills
Use when creating a new skill, adding a skill to the user's setup, or the user says "make this a skill". All personal skills live in the arjit-skills monorepo and are symlinked into place.
2frontend-slides
Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to build a presentation, convert a PPT/PPTX to web, or create slides for a talk/pitch. Helps non-designers discover their aesthetic through visual exploration rather than abstract choices.
2address-copilot-review
Handle GitHub Copilot PR review comments end-to-end. Use when the user asks to read Copilot's review on a pull request, decide which comments to act on, implement appropriate fixes, push follow-up commits, reply on each review thread with either the fix or the rationale for not changing code, and resolve threads that are fully addressed.
2ios-simulator-testing
End-to-end iOS simulator testing using blitz-iphone MCP and XcodeBuildMCP. Use this skill when testing an iOS app on the simulator — building, launching, interacting with the UI, and verifying state. Covers which MCP to use and when, gesture mechanics, and interaction patterns learned from real test runs.
2swiftui-design-principles
Design principles for building polished, native-feeling SwiftUI apps and widgets. Use this skill when creating or modifying SwiftUI views, iOS widgets (WidgetKit), or any native Apple UI. Ensures proper spacing, typography, colors, and widget implementations that look and feel like quality apps rather than AI-generated slop.
2resolve-merge-conflicts
Resolve PR merge conflicts end-to-end by identifying the base branch, merging it locally, fixing conflicted files carefully, validating the result, and pushing the updated branch. Use when the user asks to look at merge conflicts on a PR, resolve them, and push the branch.
1