Independent by design · no pay-to-rank placements  · How we evaluate tools →
Anclum Submit
S

swagatskalita092/project-blueprint

Independent directory — not the official site. Details below come from the project's public repository.

Build interview-ready projects.

1 ★ measured · checked 2026-11-19

Before you install: no copy-paste command · license MIT

First step: nothing runnable here yet - start from the repository: https://github.com/swagatskalita092/project-blueprint

★ 1·updated 2026-11-19
View on GitHub ↗Direct link · no redirect page
Official descriptionBuild interview-ready projects. A phase-by-phase methodology, real worked examples, and importable Claude skills for picking an idea, naming risks, adversarial testing, and writing an honest case study.
Star count
1 ★ · swagatskalita092/project-blueprint · read from the GitHub search API · (checked 2026-11-19 20:00:48)
Source
read directly from its GitHub page · type: open-source project
Harvest history
first seen 2026-11-20 · last seen 2026-11-20 · seen 1× · listed by 1 sources
Score
score 103 · 1 ★ · 1 sources · repo
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: Claude skills. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository swagatskalita092/project-blueprint;first catalogued 2026-11-20;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.
README excerpt (English, untranslated) · Read the full README on GitHub →

# project-blueprint

Excerpted from the repository README (abridged)

Build interview-ready projects.
Most "how to build a good portfolio project" advice is generic opinion. This repo isn't that. It's the actual, phase-by-phase pipeline used to build two real, independently verified engineering projects (a flash-sale checkout backend with chaos-tested concurrency, and a data pipeline with chaos-tested correctness) - written down so anyone can follow it, with real worked examples, fillable templates, and nine importable Claude skills covering every step.
The point of a portfolio project isn't that it works. It's that every claim about it is something that was actually proven, not asserted. That's the bar this repo is trying to get you to.
## Quick start
Have no idea yet? Start at docs/08_idea_bank.md, then run whichever one you pick through docs/01_pick_your_idea.md.
Have an idea already? Start at docs/01_pick_your_idea.md - check it's not a shallow version of something common before investing time in it.
Have a project already, and want to know what's missing? Jump to docs/05_adversarial_testing.md and docs/06_verification_checklist.md first - these are usually the actual gap between "it works" and "it's interview-ready." Then docs/07_case_study_and_resume.md to write it up.
Writing a research paper instead of a project? docs/09_research_paper.md applies the same honesty discipline to academic writing.
## Why most portfolio projects don't hold up
Not because the code is bad. Because the project was never actually attacked. Most "I built X" projects on a resume ran once, on the happy path, on the builder's own machine, and that's the entire evidence behind every claim in the README.
A skeptical interviewer only has to ask three questions to find the edge of that: What happens when this fails? How do you know? Show me. If the honest answer to any of those is "I assume it's fine," the project isn't interview-ready yet - no matter how polished the UI or how long the tech stack list is.
This repo is built around closing exactly that gap, deliberately, before the interview happens instead of during it:
## The pipeline
Nine steps, each with a doc (the full explanation plus a "step by step, in practice" checklist) and a matching Claude skill (the same guidance, importable on its own). Expand a step below for what it actually asks you to do.
01 · Pick your idea - name the differentiator before building, not after
A familiar project shape isn't automatically weak - a conventional problem (a CRUD app, a checkout flow, an API wrapper) built with real depth is often stronger interview material than a novel-sounding idea with shallow execution. The actual test: what does this prove that a shallow, generic version of the same idea wouldn't? If the honest answer is "nothing beyond gluing two tools together," fix the depth or replace the idea.
docs/01_pick_your_idea.md · skill/pick-your-idea
02 · Name your risks - write the invariants before you lock an architecture
Before any code, write down what must stay true for the project to actually be correct, and how it could plausibly fail - as a plain, falsifiable sentence. "A user from one account can never read another account's data." "Inventory is never sold below zero." If you can't state the invariant, you don't yet understand the risk you're protecting against.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[![Listed on Anclum](https://anclum.com/badge/listed.svg)](https://anclum.com/en/s/swagatskalita092-project-blueprint/)
Source
github · https://github.com/swagatskalita092/project-blueprint
Browse by field
Claude skills
Traction
1 ★
added
today

More entries

All 50 →

Filed under

Every tag opens the full list for that filter. Counts are the live catalogue figures.

Browse all fields →

← Back to index