register-project
starsforks
How to install register-project?
faizkhairi/claude-code-blueprint/register-project
$npx -y skills add faizkhairi/claude-code-blueprint --skill register-projectRegister an existing project in memory. Use when starting work on a new repo or when a project needs its own context file. Triggers on: 'register project', 'add project to memory', 'track this project', 'create project file'.
SKILL.md
| 1 | # Register Project in memory |
| 2 | |
| 3 | ## Step 1: Detect Project Info |
| 4 | |
| 5 | Gather from the current working directory or user input: |
| 6 | - Project name and path |
| 7 | - Framework/language (check package.json, pyproject.toml, composer.json, etc.) |
| 8 | - Test command (check scripts in package manager config) |
| 9 | - Git remote URL |
| 10 | - Current test count (run tests and count) |
| 11 | |
| 12 | ## Step 2: Read Template |
| 13 | |
| 14 | Read `./memory/templates/coding-template.md` for the standard format. |
| 15 | |
| 16 | ## Step 3: Check Capacity |
| 17 | |
| 18 | Scan `./memory/projects/active/`. If 10+ projects exist, identify the oldest by Last Accessed date and suggest archiving it. |
| 19 | |
| 20 | ## Step 4: Create Project File |
| 21 | |
| 22 | Write to `./memory/projects/active/{project-name}.md` using the template, filled with detected info. |
| 23 | |
| 24 | ## Step 5: Confirm |
| 25 | |
| 26 | Show the created file path and key fields to the user. |
| 27 | |
| 28 | ## Rules |
| 29 | - Never overwrite an existing project file; read it first and update if it exists |
| 30 | - Use the template format exactly |
| 31 | - Set Last Accessed to today's date |
| 32 | - Leave Session Context section with placeholder (populated during actual work) |
People who liked this also viewed
6 picksType
- requesting-code-reviewUse when completing tasks, implementing major features, or before merging to verify work meets requirementsSkillsJul 2026
- code-reviewSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- receiving-code-reviewUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performativeSkillsJul 2026
- baoyu-format-markdownFormats plain text or markdown files with frontmatter, titles, summaries, headings, bold, lists, and code blocks. Use when user asks to "format markdown", "beautify article", "add formatting", or imprSkillsJul 2026
- code-review-excellenceMaster effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing reSkillsJul 2026
- code-review-and-qualityConducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensiSkillsJul 2026
