Individual skill

sprucecss-library

Use the ready-made Spruce UI components, blocks and pages from the online library instead of writing them from scratch, when only the sprucecss npm package is installed. Look the item up in https://sprucecss.com/library.json (or llms.txt), fetch its Markdown endpoint (HTML, SCSS, JavaScript and ordered dependencies), copy it with its dependencies and adapt the content. Use whenever the user asks for a component, a page section (hero, pricing, FAQ, testimonials, footer…) or a whole page in a Spruce CSS project.

skills/sprucecss-library/SKILL.md

Read pinned source

Source commit 3ac9c503068495541510f71554d99983754d0de6

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
Yes
Skill scan complete
Yes
Observed behavior
Network or broad shell
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
265
Repository last updated
Oct 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Spruce UI library

The `sprucecss` npm package ships the framework only. The component library, **Spruce UI**, lives on the website: about 150 components, 50 blocks (full-width page sections) and 10 complete pages, all built with the Spruce conventions, tested in every design style, in dark mode and in RTL. Before you write a component, a block or a page, check whether the library already has it.

## 1. Find the item

Fetch the index once per task:

- **https://sprucecss.com/library.json**: every item with its `type` (`component`, `block`, `page`), `title`, `category`, `description`, the `markdown` URL and its dependencies.
- or **https://sprucecss.com/llms.txt**: the same list as Markdown, with the docs.

Pick by meaning, not by name: "a section with plans and prices" is the Pricing block or the Pricing Tiers block, "a slide-in cart" is the Cart Drawer. If two fit, read both descriptions and choose the closer one. For a whole page, start from the page template that's closest (a SaaS home, a portfolio, a course, a case study, a shop, a dashboard…) and swap or add blocks.

## 2. Fetch its endpoint