claude-proj-blueprint is a project template for people who want a clear way to plan and build software with Claude Code, Obsidian, and Figma.
It gives you a level-based setup so you can pick the right starting point for your work:
- L1 for a simple start
- L2 for a more organized setup
- L3 for deeper planning and team work
- L4 for a full project structure
Use it to keep specs, notes, and design work in one place.
This template is set up to help you:
- organize project notes
- keep requirements easy to find
- connect planning work with design work
- track progress in a simple folder layout
- work with Claude Code in a structured way
- store project knowledge in Obsidian
- keep design references close to the work
- use vector search tools like Chroma or pgvector for project memory
Make sure you have:
- a Windows PC
- internet access
- enough free disk space for the release files
- a browser such as Edge, Chrome, or Firefox
- a zip tool if the release comes as a .zip file
If you plan to connect this template to other tools, it also helps to have:
- Obsidian
- Figma
- Claude Code
Visit the release page here and download the file for Windows:
After the page opens:
- find the latest release
- look under the Assets section
- download the Windows file
- if the file is a
.zip, extract it first - if the file is an
.exe, double-click it to run it
If you downloaded a .zip file:
- right-click the file
- choose Extract All
- pick a folder like
DownloadsorDesktop - open the extracted folder
- double-click the main file inside
If you downloaded an .exe file:
- go to the folder where the file saved
- double-click the file
- if Windows asks for permission, choose Yes
- follow the steps on screen
If Windows blocks the file, open the release page again and make sure you downloaded the latest Windows asset.
Choose the level that fits your project:
Best for small ideas and early drafts.
Use this level when you want:
- a basic folder layout
- a simple spec file
- a place for notes and rough plans
Best for solo work that needs more structure.
Use this level when you want:
- clearer task lists
- better project notes
- a cleaner handoff between planning and building
Best for work that uses notes, code, and design together.
Use this level when you want:
- Obsidian notes linked to project work
- Figma references in the flow
- more detail around scope and steps
Best for larger projects with more moving parts.
Use this level when you want:
- a deeper spec tree
- better project tracking
- stronger structure for long work cycles
- room for vector search and project memory
A common setup may include:
specs/for project specsnotes/for planning and researchdesign/for Figma links and image refstasks/for work itemsdocs/for project documentsmemory/for reusable project context
This layout keeps your work in clear places so you can find it fast.
- download the release from the link above
- open the template folder
- choose your level
- add your project name
- fill in your specs
- add notes in Obsidian if you use it
- add design links from Figma if you use it
- keep Claude Code pointed at the project files
- update the plan as the work changes
Claude Code works best when your project has clear files and a clean structure.
Use this template to give Claude Code:
- a project brief
- a short spec
- task files
- design notes
- clear goals for each level
This helps keep the work focused and makes it easier to move from planning to building.
Obsidian can hold your project notes, research, and decisions.
Good things to store in Obsidian:
- feature ideas
- meeting notes
- user needs
- question lists
- decisions
- links to specs and tasks
If you use Obsidian well, you can turn it into a simple project memory hub.
Figma helps you keep design work next to the project plan.
You can use it for:
- wireframes
- layout ideas
- UI notes
- screen states
- handoff links
Keep the Figma links in the same project folder so everyone can find them.
This project template can work with tools like Chroma or pgvector for project memory and search.
Use this when you want to:
- search past notes
- find old decisions
- reuse project context
- keep large sets of notes easy to query
A simple setup can index your specs, notes, and task files so they stay easy to retrieve.
- pick L1, L2, L3, or L4
- copy the template into a new project folder
- write the project goal
- add feature notes
- link design files
- keep work items in order
- update the spec as you build
- save key decisions in Obsidian
- use Claude Code to work from the same source files
No. You can use this as a structured folder and note system first. If you work with Claude Code or a developer later, the structure still helps.
Yes. Start with L1 and keep the setup light.
Yes. L2 through L4 give you more room for shared planning and better project tracking.
Yes. It is made to fit design links and notes from Figma.
Yes. The structure works well with Chroma, pgvector, and similar tools.
If this is your first time using the template:
- download the latest release
- open the release files
- start with L1
- add one small project
- keep your notes short
- grow the setup only when you need it
Visit the release page here to download the Windows file: