| name | new-project |
| description | Add a new project to Colton's portfolio. Creates a detail page under src/html/portfolio/, adds a listing card to portfolio.njk, and places images under src/assets/images/portfolio/{slug}/. Use when the user wants to showcase a new project they've built. |
| argument-hint | <project name or absolute path to the project repo> |
| allowed-tools | Read, Glob, Grep, Write, Edit, Bash(ls *), Bash(mkdir *), Bash(cp *), Bash(file *), Task |
New Project
Adds a project to the portfolio site. The portfolio is a Gulp + Nunjucks static site (see CLAUDE.md). Adding a project requires touching three locations — do not skip any.
Process
- Get the source project location. If the user only gave a name, ask for the absolute path to the repo. Read its
README.md, package.json (or composer.json), and .git/config to gather:
- Project name, one-sentence description, longer description
- Tech stack (framework, key libraries, hosting)
- Live URL and repo URL
- Role (sole dev? team? rescue? greenfield?)
- 3–7 notable technical highlights for the Summary section
- Pick a slug. kebab-case, matches the live domain or project name. Examples:
roof-maxx, montana-tags, arkansas-honeyworks.
- Choose the section in
src/html/portfolio.njk:
#idustry — "Industry Projects" — salaried employer work or agency-for-client work#ios-android — mobile app binaries shipped to App Store / Play Store#personal — "Personal / Free Lance Projects" — side projects, family/friend builds, OSS, rescues- If ambiguous, ask the user before placing.
- Place an image under
src/assets/images/portfolio/{slug}/:
- Prefer a real brand logo (
logo.png / logo.svg)
- If no logo exists, use a responsive-mockup screenshot or a representative photo (see
montana-tags/responsive-showcase-mockup.png for the mockup pattern)
- Create the directory with
mkdir -p, then cp the file in
- If nothing suitable exists in the source repo, ask the user which image to use — do not invent one
- Create the detail page at
src/html/portfolio/{slug}.njk using the template below. Copy the wording style from src/html/portfolio/montana-tags.njk (small/medium project) or src/html/portfolio/roof-maxx.njk (large project with many achievements).
- Insert the listing card into
src/html/portfolio.njk at the top of the chosen section (so newest work appears first). Use the listing-card template below.
- Tell the user how to preview and deploy. Do NOT run
npm run deploy yourself.
cd /Users/cwilliams/Desktop/Code/My-Portfolio
nvm use
gulp # full build
npx serve dist # preview at http://localhost:3000/portfolio.html
npm run deploy # when you're happy — pushes to GitHub Pages
Detail-page template
Save to src/html/portfolio/{slug}.njk. Replace every {{PLACEHOLDER}}. Keep the partial includes exactly as written.
<!DOCTYPE HTML>
<html>
{% include "./partials/headPortfolioDetail.html" %}
<body class="is-preload">
<div id="wrapper">
<div id="main">
<div class="inner">
{% include "./partials/header-socialLinks.html" %}
<a href="../portfolio.html" class="button" style="margin-top: 35px;"><i class="fas fa-chevron-left"></i> Back to portfolio</a>
<section>
<header class="main">
<h1>{{TITLE}}</h1>
</>
About {{CLIENT_OR_PROJECT}}
{{ABOUT_PARAGRAPH}}
About The Project
Mission: {{MISSION_PARAGRAPH}}
Technologies Used: {{COMMA_SEPARATED_TECHS}}.
Links
{{LIVE_URL_LABEL}}
Live Site: {{LIVE_URL_DISPLAY}}
Summary
{{ROLE_PARAGRAPH}}
{{ACHIEVEMENT_1_TITLE}}: {{ACHIEVEMENT_1_BODY}}
{{ACHIEVEMENT_2_TITLE}}: {{ACHIEVEMENT_2_BODY}}
{% include "./partials/sidebar-footer.html" %}
{% include "./partials/scriptsPortfolioDetail.html" %}
Listing-card template
Insert into src/html/portfolio.njk at the top of the chosen <div class="posts"> block. The <img> path is relative to dist/ (no ../ prefix — the listing page sits one level above detail pages).
<article>
<a href="portfolio/{{SLUG}}.html" class="image"><img src="images/portfolio/{{SLUG}}/{{IMAGE_FILENAME}}" alt="" /></a>
<h3>{{TITLE}}</h3>
<p>{{2–3 SENTENCE SUMMARY — stack, role, and 1–2 standout features}}</p>
<ul class="actions block">
<li><a href="portfolio/{{SLUG}}.html" class="button">About the project</a></li><br>
<li><a href="{{LIVE_URL}}" target="_blank" class="btn-blue">Go To {{LIVE_DOMAIN}}</a></li>
</ul>
</article>
If the live site is a GitHub repo (OSS / no live URL), the second button should read Go To {{ProjectName}} and link to the repo — see the attendIT and OpenGL_3D_Game entries for examples.
Conventions & gotchas
- Relative paths only. In detail pages use
../images/portfolio/{slug}/.... In portfolio.njk use images/portfolio/{slug}/... (no leading /, no ../).
- Never edit
dist/. It's generated by gulp. All edits go under src/.
- Image file location:
src/assets/images/portfolio/{slug}/ — create the dir with mkdir -p. Gulp optimizes images with gulp-imagemin at build time, so drop raw files in — no pre-optimization needed.
- Match the listing section order. New work goes at the top of its section so recent projects are seen first.
- Copy the section wording style from an existing similar project — the portfolio has a consistent voice (achievement-focused, bolded subsection titles, concrete technical details).
- Don't invent tech. Only list technologies you can verify from the source repo's
package.json / composer.json / config files.
- Don't fabricate metrics or quotes. If the user doesn't mention a specific number or testimonial, leave it out.
Section heuristic
| Type of work | Section |
|---|
| Salaried W-2 employer project | #idustry |
| Agency client work (paid by firm) | #idustry |
| Contract / 1099 freelance for a business | #idustry |
| Family, friend, or personal side-build | #personal |
| Open-source or school/capstone project | #personal |
| Portfolio/self site or experiments | #personal |
| iOS or Android app shipped to a store | #ios-android |
When in doubt, ask.
Completion checklist
