Skip to content

CopyKit

Recursive grep with context

grep -rn --include="*.{{extension}}" "{{pattern}}" .

Kill process on port

lsof -ti:{{port}} | xargs kill -9

Add more agents

ntm add myproject --cc=2

Create empty tmux session without agents

ntm create myproject --panes=2

Create a new session for your project

ntm new myproject

Spawn agents to a project

ntm spawn myproject --cc=2 --cod=1 --gmi=1

View existing sessions

br sync --import-only

View existing sessions

ntm list

Add remote to local repo

git remote add origin {{url}}

Create and immediately switch to a new branch from a specific commit

git switch -c {{new_branch_name}} {{commit_hash}}

Create and immediately switch to a new branch

git switch -c {{branch_name}}

Delete a local branch

git branch -d {{branch_name}}

Delete a remote branch

git push origin --delete {{branch_name}}

Push a newly created branch to the remote for the first time

git push -u origin {{branch_name}}

Delete merged local branches

git branch --merged main | grep -v "main" | xargs -r git branch -d

Amend your last commit with new changes, but keep the old message

git commit --amend --no-edit

Fetch latest changes and branch references from the remote

git fetch origin

Pull remote updates directly into your current branch

git pull origin {{branch_name}}

Interactive rebase last N commits

git rebase -i HEAD~{{n}}

Rebase current branch onto main

git fetch origin && git rebase origin/main

List all stashes

git stash list

Pop the most recent stash

git stash pop

Stash including untracked files

git stash push -u -m "{{message}}"

Scaffold Next.js project

pnpm dlx shadcn@latest init --template next --name {{project-name}} --no-monorepo && cd {{project-name}} && pnpm add lucide-react && pnpm add -D vitest @vitejs/plugin-react jsdom @testing-library/react @testing-library/jest-dom @testing-library/user-event && pnpm dlx shadcn@latest add --all && pnpm create playwright

Scaffold Vite project

pnpm dlx shadcn@latest init --template vite --name {{project-name}}-vite --no-monorepo \ && cd {{project-name}}-vite \ && pnpm add react-router lucide-react \ && pnpm add -D vitest jsdom @testing-library/react @testing-library/jest-dom @testing-library/user-event \ && pnpm dlx shadcn@latest add --all \ && pnpm create playwright

Commit changes

Review all of the code changes and commit the changes in a logical manner. If it does not make sense for all changes to be in a single commit, then make multiple commits.

Implement UI

Make sure you review AGENTS.md. Then review the PLAN.md thoroughly and fully. Then read and understand the skill: frontend-design skill. Stop and report to me if you have any issues reviewing any of the above. Do not move forward if you cannot read any of them. Once you've successfully read everything thoroughly, begin implementing with the MVP milestones in mind (from PLAN.md) The milestones are guidance and may not capture everything that needs to be done. Keep in mind that I've scaffolded the majority of the project already, so review what's been done. Create detailed tasks for yourself to methodically keep track of everything that needs to be done in order to satisfy the requirements of the PLAN.md As you're completing your work commit all changed files in a series of logically connected groupings with super detailed commit messages for each and then push. Take your time to do it right. Don't commit obviously ephemeral files.

Create design document

Create a design document for this project. Below are details to include in the design doc. Think about what goes into a good design document that will give agents good context to understand the product features and the technical requirements to begin implementing. The document should be thorough and leave little room for interpretation on how to implement the requirements. If there is an area that needs specifying, let me know.

Review design document

With fresh eyes, I want you to thoroughly review the design document for the project. Then I want you to analyze the document and tell me how to improve on it to make the requirements and context more clear. If there are any areas needing clarification, then list them out in a numbered list so that I can respond by addressing it.

Task breakdown

I want you to review @PLAN.md thoroughly and then create a comprehensive and granular set of beads for all this with tasks, subtasks, and dependency structure overlaid, with detailed comments so that the whole thing is totally self-contained and self-documenting (including relevant background, reasoning/justification, considerations, etc.-- anything we'd want our "future self" to know about the goals and intentions and thought process and how it serves the over-arching goals of the project.) Use the `br` tool repeatedly to create the actual beads. Create the bead graph one by one. Wait 1 second between each `br create` command to prevent SQLite fragmentation. Use /effort max.

Review multiple design documents

I've attached {{number}} design documents from different LLMs. I want you to review them with fresh eyes so that you can pinpoint areas that are done well and areas that need to be clarified and improved on. I want you to intelligently and precisely consider how to consolidate the plans into a hybrid plan that addresses the requirements and goals of the application. If there are any areas of discrepancy, then provide the each area in a diff style for me to review between the {{number}} plans.