libraries
/libraries
Use when the user wants to choose or change which library each job uses in this project, or wants the libraries rule that was skipped when the harness was set up.
- Author
- dvasyliev ↗
- Repository
- frontend-harness ↗
- Licence
- MIT
- Last repository change
- 11.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 11.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when the user wants to choose or change which library each job uses in this project, or wants the libraries rule that was skipped when the harness was set up.
Original author description
Use when the user wants to choose or change which library each job uses in this project, or wants the libraries rule that was skipped when the harness was set up.
How it works
SKILL.md has no level-two headings · 14 lines, 211 words
SKILL.md preview
--- name: libraries description: Use when the user wants to choose or change which library each job uses in this project, or wants the libraries rule that was skipped when the harness was set up. --- # Choose the libraries Sets the `libraries` answers of a project that already has the harness, and adds the `libraries` module if it is missing. The template is the one the `setup` skill (`../setup/SKILL.md`, next to this skill's folder) describes. Ask as `../../references/questions.md` (from this skill's base directory) says. 1. Stop if `.claude/harness.json` is missing: the project has no harness yet; offer `/frontend-harness:setup`. 2. Run `git status --short`. If anything is uncommitted, stop and tell the user, as setup's step 1 says. 3. Stop if the `version` in `.claude/harness.json` is older than the template's: running it here would also update every module. Offer `/frontend-harness:update` first. 4. Follow setup's **Libraries** step for every section, not only those with no answer: a current answer is the recommended library, and the user can change any of them. 5. Run setup's step 3 with only the answers that change: `libraries`, and `modules` with `libraries` added when it is not listed. 6. Follow setup's merge steps for the `harness:` lines it printed. A `.claude/rules/libraries.md` the project wrote by hand comes up as a file the project already had. 7. Run `npm run check`, then commit only `.claude/harness.json`, `.claude/rules/libraries.md` and `.claude/rules/harness.md`, with the message `chore(harness): set the libraries`. 8. Tell the user what changed, section by section.
Versions
The database has no other skills named libraries.
Database snapshot: 13.11.2026 · package version 9df5ce1695c1 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 95reviewing-python-libraries
Comprehensively reviews Python libraries for quality across project structure, packaging, code quality, testing, security, documentation, API design, and CI/CD. Provides actionable feedback and improvement recommendations. Use when evaluating library health, preparing for major… - 100shared-library-review
Review standard for shared libraries reused across projects: headless Vue 3 component libraries (Reka UI, Tailwind v4, cva) and shared Rust backend libraries (axum). Use for review the shared library, is this library ready to tag, audit our design system. One-off app components are out of scope. - 100adopt-or-build
Before building a feature or fix, search for open-source libraries that already solve it and decide per piece whether to adopt one or build it. A library is adopted only when it is actively maintained, not outdated, and compatible with the project's exact stack (versions,… - 100create-react-native-library
Scaffolds React Native libraries with create-react-native-library for standalone libraries or local native modules and views. Use when creating or working on React Native libraries or adding native functionality in an existing app. - 100context7
Version-specific documentation for 800+ libraries via Context7 MCP. Two tools: resolve-library-id (library name → canonical ID) and query-docs (ID + query → live docs and code examples). Eliminates hallucination in agent code generation. Use when Claude is writing code for an… - 100context7
Up-to-date, version-specific library documentation and working code examples sourced from real project repos via the Context7 documentation aggregation API — covers 1000+ libraries (React, Next.js, Vue, Kubernetes, Go, Python, TypeScript, Prisma, Tailwind, and more). USE WHEN…