<Devsly/>
NotebookLM Watermark Remover
Remove the NotebookLM watermark from PDF slide exports — free, unlimited, and 100% in your browser.
View
NotebookLM Video Watermark Remover
Remove the NotebookLM watermark from every frame of your MP4 and auto-trim the end card — free and unlimited.
View
Gemini Watermark Remover
Remove the Gemini (Veo) sparkle watermark from every frame of your AI-generated MP4 — free and unlimited.
View
MCP https://devsly.io/mcp MCP Tools Best Skills API Docs

Keyboard Shortcuts

Navigation

Quick Search
⌘ / Ctrl + K
Toggle Dark Mode
⌘ / Ctrl + D
Close Dialogs
Esc

Tool Actions

Execute / Process
⌘ / Ctrl + Enter
Clear Input
⌘ / Ctrl + Shift + C
Copy Output
⌘ / Ctrl + Shift + X

Editor

Select All
⌘ / Ctrl + A
Undo
⌘ / Ctrl + Z
Redo
⌘ / Ctrl + Shift + Z

Updated 3w ago

by faizkhairi

claude-code-blueprint

A battle-tested, framework-agnostic reference architecture for Claude Code. Beginner-friendly with graduated adoption (minimal / standard / core / full presets). 12 agents, 19 skills, 15 hooks, 6 rules, with reasoning behind every decision.

  • Multi-agent — Targets three or more agents
Works with
  • Claude
  • Codex
  • Cursor
  • Gemini

73 GitHub stars (73)

+2 in 16 days

Stars gained per day · daily snapshots since Sep 30
Stars gained per day, Sep 30 to Oct 16: +2 in total; the busiest day was Oct 9 with +1 stars.Oct 1: 0 starsOct 2: 0 starsOct 3: 0 starsOct 4: 0 starsOct 5: 0 starsOct 6: 0 starsOct 7: 0 starsOct 8: 0 starsOct 9: +1 starsOct 10: 0 starsOct 11: 0 starsOct 12: 0 starsOct 13: +1 starsOct 14: 0 starsOct 15: 0 starsOct 16: 0 stars
Stars gained between daily snapshots
PeriodNew stars
Oct 10
Oct 20
Oct 30
Oct 40
Oct 50
Oct 60
Oct 70
Oct 80
Oct 9+1
Oct 100
Oct 110
Oct 120
Oct 13+1
Oct 140
Oct 150
Oct 160
  • 19 skills (19 skills found in its SKILL.md files)
  • 22 forks (22 forks)
  • 3w ago last update (Last updated 3w ago)

Install

Skills CLI

npx skills add faizkhairi/claude-code-blueprint

Asks which skills and agents to install. Just one: npx skills add faizkhairi/claude-code-blueprint --skill changelog — add -g for every project.

Claude Code

git clone https://github.com/faizkhairi/claude-code-blueprintcp -r "claude-code-blueprint/skills/changelog" ~/.claude/skills/

Copies the changelog skill into ~/.claude/skills/ for every project (use .claude/skills/ for one project). Repeat for the other skills listed below.

Plugin

/plugin marketplace add faizkhairi/claude-code-blueprint

Run inside Claude Code if the repository ships a plugin marketplace, then pick plugins from /plugin.

Skills can run code on your machine — read the SKILL.md first.

What it does

In the author's own words, from each skill's SKILL.md.

  • changelog

    Generate a changelog from git history since a tag, date, or commit

    skills/changelog/SKILL.md on GitHub (opens in a new tab)
  • db-check

    Validate database schema integrity and check for common issues

    skills/db-check/SKILL.md on GitHub (opens in a new tab)
  • deploy-check

    MUST use before any git push to main/master/production, or when user mentions 'deploy', 'going live', 'push to prod', 'ready to ship', 'merge to main', 'release'. Also trigger before any npm publish for CLI tools, or on 'audit', 'check vulnerabilities', 'are our deps safe?', 'npm audit', 'yarn audit'. Performs: test suite validation, dev-artifact scan (`console.log`, `TODO`/`FIXME`, hardcoded sec…

    skills/deploy-check/SKILL.md on GitHub (opens in a new tab)
  • e2e-check

    Run E2E tests or interactive browser verification. Triggers on: 'run e2e', 'e2e test', 'browser test', 'check in browser', 'verify UI', 'interactive test'.

    skills/e2e-check/SKILL.md on GitHub (opens in a new tab)
  • elicit-requirements

    Structured pre-feature requirements gathering. Run before writing any new feature or API endpoint to clarify scope, acceptance criteria, and technical constraints. Produces: a Requirements Summary (Problem | Scope | Stories | Acceptance Criteria | Out of Scope | Open Questions), presented to the user for confirmation BEFORE saving to a file, so requirements can be edited before they become refere…

    skills/elicit-requirements/SKILL.md on GitHub (opens in a new tab)
  • load-session

    Restore session context at the start of every new conversation. Auto-triggers on session start, or when user says 'continue', 'what were we doing', 'where did we leave off'.

    skills/load-session/SKILL.md on GitHub (opens in a new tab)
  • pr-review

    Review and post feedback on a GitHub or Gitea pull request end-to-end: fetch the PR diff, run a multi-agent code review, and auto-post the verdict as a real PR review (approve/request-changes/comment) via the platform's API. Triggers on: 'review this PR', 'review PR #N', 'check this pull request', 'post a PR review', 'do a PR review on <url>'. For local uncommitted changes or a branch diff with n…

    skills/pr-review/SKILL.md on GitHub (opens in a new tab)
  • register-project

    Register 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'.

    skills/register-project/SKILL.md on GitHub (opens in a new tab)
  • review-diff

    Scan git diffs for project-specific anti-patterns. Triggers on: 'scan diff', 'check diff', 'anti-pattern check', 'pattern scan', 'review changes'.

    skills/review-diff/SKILL.md on GitHub (opens in a new tab)
  • review-full

    Run a comprehensive multi-perspective code review on recent changes. Also triggers on 'is this secure?', 'security review', 'check for vulnerabilities', 'could this be exploited?' for security-focused review. Produces: GO/NO-GO verdict + findings table (Severity | Category | File:Line | Issue | Recommendation) grouping CRITICAL/HIGH/MEDIUM/LOW across code quality (patterns, error handling, types)…

    skills/review-full/SKILL.md on GitHub (opens in a new tab)
  • save-diary

    MUST use when user says 'save diary', 'write diary', 'diary entry', 'update diary', or 'document session'. Also auto-trigger at the end of any significant session (feature shipped, major bug fixed, architecture decision, new project started).

    skills/save-diary/SKILL.md on GitHub (opens in a new tab)
  • save-session

    MUST use when user says 'save', 'save session', or explicitly wants to preserve session state. {USER_NAME} does NOT use slash commands; also trigger proactively when significant work has been completed and session context should be persisted. For session endings (bye/done/goodbye), use the session-end skill instead which combines save-session + save-diary.

    skills/save-session/SKILL.md on GitHub (opens in a new tab)
  • scaffold-project

    Scaffold a new project with standard structure, configs, and CLAUDE.md

    skills/scaffold-project/SKILL.md on GitHub (opens in a new tab)
  • self-audit

    Run the verify-plan checklist against YOUR OWN plan before finalizing it (before ExitPlanMode), with special emphasis on the consumer audit. Triggers on: 'audit yourself', 'self-audit', 'check your own plan', 'did you check everything', 'verify before exit plan', or automatically before any non-trivial ExitPlanMode. Catches the gap where a rule exists but was not applied at the decision point.

    skills/self-audit/SKILL.md on GitHub (opens in a new tab)
  • session-end

    MUST use when user says 'bye', 'goodbye', 'good night', 'gnight', 'done for today', 'that's all', 'that's it', 'see you', 'see ya', 'let's stop', 'stopping here', 'wrapping up', 'signing off', 'closing down', 'done', 'finished for now', 'talk later', 'cya'. The user does NOT use slash commands; detect these natural session-ending phrases and run the full wrap-up automatically.

    skills/session-end/SKILL.md on GitHub (opens in a new tab)
  • sprint-plan

    MUST use when user describes a multi-step feature to build, says 'let's build', 'new project', 'let's implement', or when a task clearly requires more than 3 steps and no plan exists yet. Do NOT trigger for simple additions like adding a comment, renaming a variable, or single-file changes. Produces: task breakdown with S/M/L/XL size estimates, dependency ordering, risk analysis, and a Definition…

    skills/sprint-plan/SKILL.md on GitHub (opens in a new tab)
  • status

    Show project status dashboard across registered repositories

    skills/status/SKILL.md on GitHub (opens in a new tab)
  • tech-radar

    MUST use when user asks 'what's new?', 'any updates?', 'latest versions?', 'breaking changes?', 'should we upgrade?', 'what changed in X?', or when starting a new project. Detects dependencies dynamically from `package.json` / `requirements.txt` / `go.mod` / `composer.json` first, then reports per-package: latest version (vs. installed), breaking changes since installed version, security advisori…

    skills/tech-radar/SKILL.md on GitHub (opens in a new tab)
  • test-check

    MUST use after implementing new features or bug fixes, when user asks 'run the tests', 'are tests passing?', 'test this', or before any deployment step. Also trigger when tests were previously failing and fixes were applied.

    skills/test-check/SKILL.md on GitHub (opens in a new tab)

Review before you install

A skill is a set of instructions and scripts your agent will follow, and it can run code on your machine. Read the SKILL.md and any scripts first — this listing is not a security review.