I will set up claude code for your repo with skills, hooks and mcp

D
davidlee366
D
davidlee366
David L
set up claude code for your repo with skills, hooks and mcp
Full Screen
set up claude code for your repo with skills, hooks and mcp
Full Screen
Full Screen
set up claude code for your repo with skills, hooks and mcpset up claude code for your repo with skills, hooks and mcpset up claude code for your repo with skills, hooks and mcp

About this gig

Claude Code works a lot better when it knows your project. I set it up so it does.


What you get (Setup Sprint): a CLAUDE.md with your real build, test and lint commands, 3 to 5 skills for the things your team repeats, a permission allowlist so you are not clicking allow all day, and hooks that keep Claude honest, including one that blocks it from saying done until a real check has run.


Need a custom tool? The Build Packet delivers one MCP server (up to 5 tools) or one Cloudflare Worker (up to 3 routes), with tests and a README. Build Packet Plus adds the Setup Sprint to the same repo.


Proof of the standard: my own guardrails are open source under MIT (search GitHub for sdvsignal done-needs-proof). Everything I deliver is plain files in your repo, nothing locked to me.


I use AI tools, including Claude, to do the work, and I review and test every delivery myself before it goes out.


Any language Claude Code can read. You need Claude Code access (API billing or a Pro or Max plan). No API keys needed from you, only branch access.


  • AI engine

    • Claude

  • Tools & frameworks

    • Other

  • AI solution type

    • AI agent
    • AI copilot
    • Internal AI tool

  • Purpose

    • Workflow automation
    • Employee productivity
    • Internal operations

Get to know David L

David L

Claude Code setup and small MCP and Cloudflare tools for dev teams

  • FromUnited States
  • Member sinceSep 2026

  • Languages

    English
I set up Claude Code so it knows your project: a CLAUDE.md with your real build and test commands, skills for what your team repeats, a permission allowlist, and hooks that keep it honest. I also build small tools when a repo needs one: an MCP server or a Cloudflare Worker, with tests and a README. You get plain files in your repo, nothing locked to me. My own guardrails are open source under MIT (github.com/sdvsignal/done-needs-proof), so you can see the standard first. I use AI tools, including Claude, and I review and test every delivery myself.

My Portfolio

Related tags