My setup for coding agents: the global rules, the skills I keep, and the skills I install from other people.
Follow these steps when the user asks to install or update this setup. The same steps do both.
-
Rules. Fetch the current file:
curl -fsSL https://raw.githubusercontent.com/salasebas/skills/main/rules/AGENTS.md -o /tmp/AGENTS.md
If
~/.agents/AGENTS.mdexists and differs, show the user the differences and ask which local changes to keep. Merge those into the new file, then copy it to~/.agents/AGENTS.md. Create the links in Global rules that are missing. -
Skills kept here.
npx skills add salasebas/skills -g -s '*' -y -
Skills from other people. Ask which groups the user wants, then install every skill listed for those sources in Skills installed from other people with
npx skills add <source> -g -s <skill> -s <skill> -y.Group Sources Always: skills here call pr,tddandbabysit-prmattpocock/skills,t3dotgg/tstackFrontend emilkowalski/skills,vercel-labs/agent-skills,vojtaholik/good-css,motiondivision/ai-kit,currents-dev/playwright-best-practices-skill,vercel-labs/agent-browserWriting cursor/plugins,sammcj/agentic-codingEverything else addyosmani/agent-skills,vercel-labs/skillswriting-documentation-with-diataxisno longer installs, because its author disabled it. Never pass-s '*'formattpocock/skills. It would replace this repo'simplementandimplement-spec, and add acode-reviewthat competes withreview-changes. -
Update. Run step 1, then:
npx skills update -g
It compares each skill's folder with the source repo, so it picks up fixes without a version bump. It cannot check
shell-scripting. -
Check.
npx skills list -gshows the skills, andcmpon the file from step 1 and~/.agents/AGENTS.mdis silent unless the user kept local changes. An error saying PromptScript does not support global installation is harmless.
| Skill | What it does |
|---|---|
review-changes |
Reviews a change for bugs and for compliance with your AGENTS.md and CLAUDE.md, and validates every finding before reporting it. loop has a reviewer subagent, on another model when one is available, review in rounds while the session fixes. |
file-pr |
Opens a PR: checks for an existing one, a title that says why the change matters, the body from pr, and no drafts. From t3dotgg/tstack. |
full-send, full-stop |
Say "full send" or "full stop" and the agent takes the change to a PR alone: proof, review-changes loop, file-pr, babysit-pr. Full send merges when the PR is ready; full stop leaves it for you. From t3dotgg/tstack. |
implement, implement-spec, spec-review |
Matt Pocock's ticket flow, kept here so it calls spec-review, his two-axis review (Standards and Spec) renamed from code-review so it doesn't run when you just ask for a review. From mattpocock/skills. |
python-development |
Conventions for Python projects: uv, type hints, PEP 723 scripts. |
typescript-development |
Conventions for TypeScript and JavaScript projects: strict mode, pnpm, oxlint, and rules for modelling types. |
rust-development |
Conventions for Rust projects: workspaces, crate features, public APIs, running tests with nextest. |
golang-development |
Conventions for Go projects, with a testing reference. |
no-comments |
Removes comments from a diff with a fresh-context subagent and fixes the code the comments were excusing. Runs when you type /no-comments. |
The language skills load only in a project that uses that language. They are copies of sammcj's skills, and the TypeScript one adds pstack's type rules; skills/THIRD_PARTY.md has the attribution.
review-changes is assembled from other review skills. SOURCES.md records where each part came from, why the skill is shaped the way it is, and how to update it.
One skill, or all of them:
npx skills add salasebas/skills -g -s review-changesnpx skills add salasebas/skills -g -s '*'rules/AGENTS.md holds the instructions every session loads. Each harness reads it from a different place:
| Harness | Where the file goes |
|---|---|
| Codex | ~/.codex/AGENTS.md, a symlink to ~/.agents/AGENTS.md |
| Grok | ~/.grok/AGENTS.md, a symlink to ~/.agents/AGENTS.md |
| Claude Code | ~/.claude/CLAUDE.md, a symlink to ~/.agents/AGENTS.md |
| Cursor | ~/.cursor/rules/agents.mdc, a symlink to ~/.agents/AGENTS.md. The frontmatter at the top of the file is for Cursor. |
The Comments section is the list of allowed comments from pstack's Comment Sicko (comment-sicko.md), without the persona or the review flow. It stops comments from being written; /no-comments removes the ones that got through.
These are not copied here. Install any of them with npx skills add <source> -g -s <skill>.
| Source | Skills |
|---|---|
mattpocock/skills |
ask-matt, codebase-design, diagnosing-bugs, domain-modeling, grill-me, grill-with-docs, grilling, handoff, improve-codebase-architecture, pr, research, retro, setup-matt-pocock-skills, tdd, teach, to-spec, to-tickets, triage, wait-what, wayfinder, writing-for-agents |
emilkowalski/skills |
animation-performance, animation-vocabulary, emil-design-eng, improve-animations, mobile-native, pick-ui-library, review-animations |
sammcj/agentic-coding |
shell-scripting, writing-documentation-with-diataxis |
cursor/plugins, pstack |
technical-writing, unslop |
cursor/plugins, cursor-team-kit |
deslop |
vercel-labs/agent-skills |
vercel-composition-patterns, vercel-react-best-practices, web-design-guidelines |
addyosmani/agent-skills |
code-simplification |
vojtaholik/good-css |
good-css |
motiondivision/ai-kit |
motion |
vercel-labs/agent-browser |
agent-browser |
currents-dev/playwright-best-practices-skill |
playwright-best-practices |
vercel-labs/skills |
find-skills |
t3dotgg/tstack |
babysit-pr, council, modernize |
For the two cursor/plugins rows the source is the folder URL, for example https://github.com/cursor/plugins/tree/main/pstack.
animate-expo, also from emilkowalski/skills, is installed per project in Expo projects: npx skills add emilkowalski/skills -s animate-expo.
sources.json records the folder hash of each copy I last installed, so a rename or removal upstream shows up. It is not a backup of the skill text.
Things I come back to. None of them is installed by this repo.
| Link | What it is |
|---|---|
google-labs-code/design.md |
The DESIGN.md format: design tokens in YAML front matter, the reasoning in prose. npx @google/design.md lint DESIGN.md validates the file. |
VoltAgent/awesome-design-md |
DESIGN.md files modelled on the design systems of well-known brands, to copy and adjust. |
| vercel.com/design.md | Vercel's own DESIGN.md, as a worked example. |
MIT. review-changes includes text from other MIT-licensed skills, named in its SOURCES.md. The skills in skills/THIRD_PARTY.md keep their own licence.