Bootstrap
Agent skills library for AI coding assistants. Includes coding conventions, npm package preferences, and project bootstrapping tools.
npx -y skills add r-portas/skills --skill bootstrapAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Installs and fully integrates packages and libraries into a project — including config files, helper modules, and scaffolded templates. Use when the user asks to install, set up, configure, add, or bootstrap a specific package: drizzle, date-fns, oxlint, oxfmt or similar. Prefer this over a generic npm install whenever the package has an opinionated setup or requires boilerplate files.
SKILL.md
2.6 KB, 443 tokens by cl100k_base, as published. Nobody here has run it
Bootstrap
Fully integrate a package into the current project — not just npm install, but
config files, wrapper modules, and any scaffolded boilerplate.
Steps
- Identify which package is being bootstrapped from the user's request
- Read the reference file using the
Readtool before writing any code — do not rely on memory or training data - Follow the reference file's instructions exactly — do not delegate to other skills (e.g.
update-config) for steps covered by the reference; execute them directly yourself - If no reference file exists for the requested package, consult the
preferred-npm-packagesskill for stack defaults (runtime, package manager, etc.), then install and configure using the package's official docs. Prefer the simplest setup that fits the existing codebase — don't over-engineer.
Critical rules
- Never inline hook commands in settings JSON. When the reference defines a shell script (e.g.
.claude/hooks/format.sh), create that file and reference it from settings — do not collapse the logic into a one-linercommandstring. - Use
$CLAUDE_PROJECT_DIRfor project-relative paths in hook scripts, not hardcoded absolute paths. - Use
node_modules/.bin/<tool>for local binaries in hook scripts, notbunx/npx— it's faster and avoids network calls. - Pipe-test every hook script before writing it to settings:
echo '<json>' | .claude/hooks/script.shand verify exit 0 and the expected side effect.
Packages
| Package | Reference |
|---|---|
| drizzle | references/drizzle.md |
| date-fns | references/date-fns.md |
| oxlint + oxfmt | references/oxlint-oxfmt.md |
| react-testing-library | references/react-testing-library.md |