@flareum/mcp 0.2.8 → 0.2.9

package/dist/first-pull.js

@@ -39,8 +39,11 @@ export const firstPullReport = (outcome) => {
         return `[flareum] could NOT pull the stylesheets into ${outcome.dir} — ${outcome.error}. `
             + 'The token tools still work; run `npx -p @flareum/mcp flareum pull` to retry.';
     const { written, failed } = outcome.result;
+    // Naming the import is the difference between 24 files on disk and 24 files that apply: nothing
+    // loads them until the project's global stylesheet says so.
     const head = `[flareum] no local stylesheets — pulled ${written.length} into ${outcome.dir}. `
-        + 'Run `npx -p @flareum/mcp flareum watch` to keep them current, or set FLAREUM_AUTO_PULL=off.';
+        + `Import them once in your global stylesheet — \`@use '${outcome.dir.replace(/^src\//, './')}/main';\` `
+        + '— then `npx -p @flareum/mcp flareum watch` keeps them current (FLAREUM_AUTO_PULL=off to stop).';
     return failed.length ? `${head}\n[flareum] ${failed.length} could not be written: `
         + failed.map(({ path, reason }) => `${path} — ${reason}`).join('; ') : head;
 };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@flareum/mcp",
-  "version": "0.2.8",
+  "version": "0.2.9",
   "description": "Connect a coding agent to a Flareum project's design tokens.",
   "license": "MIT",
   "author": "Flareum",

package/skill/SKILL.md

@@ -31,6 +31,42 @@ page, and it is worth reading in full before the first line of code.
 | Any text — a heading, a label, body copy, a pseudo-element's `content` | [references/typography.md](references/typography.md) |
 | A token name, or judging one that already exists | [references/naming.md](references/naming.md) |
 
+## Before the first token: check the stylesheets are imported
+
+A token only resolves if the pulled stylesheets are actually loaded. `flareum pull` writes them into
+the project — it does not wire them in, because which file is the global entry point is the
+project's decision, not the tool's.
+
+So the first time you use a token in a project, check the import exists, and add it if it does not.
+Otherwise every `var([prefix]-…)` you write is correct and renders as nothing — the failure is
+silent, and it looks like the token is wrong rather than absent.
+
+**Find the pulled files** (`src/styles/flareum/`, or wherever `out` in `.flareum/config.json`
+points), then **find the global stylesheet** — the one the app already loads for everything:
+
+| Project | Usually |
+|---|---|
+| Angular | the `styles` entry in `angular.json` — commonly `src/styles.scss` |
+| Vite / React / Vue | the CSS imported by the entry module — `src/main.tsx`, `src/index.css` |
+| Next.js | `app/globals.css`, imported by the root layout |
+| Plain | whatever the HTML `<link>`s |
+
+Add the import at the **top**, before anything that uses a token:
+
+```scss
+@use './styles/flareum/main';   // SCSS
+```
+```css
+@import './styles/flareum/main.css';   /* plain CSS */
+```
+
+Then confirm it resolves — build, or grep the built CSS for a `--[prefix]-` declaration. A token
+that is imported but still not applying is usually the `font:` shorthand or a missing
+`--line-height`; [references/typography.md](references/typography.md) covers both.
+
+If the pulled folder does not exist at all, the project has never pulled: say so and give the
+command — `npx -p @flareum/mcp flareum pull` — rather than writing tokens that cannot resolve.
+
 ## Reading a search result
 
 The header tells you which kind of answer you got, and they mean different things: