skills/fragments-sdk/skills/fragments-cloud-setup

fragments-cloud-setup

SKILL.md

Fragments Cloud Setup

Set up design governance with Fragments Cloud -- from zero to running checks with optional CI.

1. Detect project environment

  • Confirm the project has a package.json. If not, ask if the user wants to initialize one.
  • Detect the package manager from lock files:
    • bun.lockb or bun.lock -> bun
    • pnpm-lock.yaml -> pnpm
    • yarn.lock -> yarn
    • Otherwise -> npm
  • Detect the framework (React, Next.js, Vue, Nuxt, Svelte, SvelteKit, Astro) from dependencies.
  • Check if @fragments-sdk/ui is already installed -- if so, note it and configure governance to work alongside it.

2. Install the governance SDK

<package-manager> add @fragments-sdk/govern

3. Configure the API key

  • Use the argument if provided: $ARGUMENTS
  • Otherwise ask: "Paste your Fragments Cloud API key (from the onboarding dashboard or Settings > API Keys):"
  • Write to .env (create if missing):
    FRAGMENTS_API_KEY=<key>
    
  • Also write to .env.local if that file already exists.
  • Ensure .env and .env.local are in .gitignore. Create .gitignore if needed.

4. Create governance config

Create fragments.config.ts in the project root. Adapt the input glob to the detected framework:

import { defineConfig } from '@fragments-sdk/govern';

export default defineConfig({
  cloud: true,
  checks: ['accessibility', 'consistency', 'responsive'],
  input: './src/**/*.{tsx,jsx}',
});

Framework-specific input patterns:

  • Next.js App Router: ['./app/**/*.{tsx,jsx}', './components/**/*.{tsx,jsx}']
  • Next.js Pages: ['./pages/**/*.{tsx,jsx}', './components/**/*.{tsx,jsx}']
  • Vue / Nuxt: ['./**/*.vue']
  • Svelte / SvelteKit: ['./src/**/*.svelte']
  • Astro: ['./src/**/*.{astro,tsx,jsx}']

5. Run the first check

npx fragments govern check --cloud

Show the output. If there are violations, briefly explain what they mean and how to fix them.

6. Offer CI/CD setup

Ask: "Want to add Fragments checks to your CI pipeline? (GitHub Actions / GitLab CI / skip)"

GitHub Actions

Create .github/workflows/fragments-check.yml:

name: Fragments Design Check
on:
  pull_request:
    branches: [main, master]
permissions:
  contents: read
  pull-requests: write
jobs:
  design-check:
    name: Design Governance
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: 20
      - run: npm ci
      - name: Run Fragments checks
        run: npx fragments govern check --cloud --format github
        env:
          FRAGMENTS_API_KEY: ${{ secrets.FRAGMENTS_API_KEY }}

GitLab CI

Add a fragments-check job to .gitlab-ci.yml:

fragments-check:
  stage: test
  image: node:20
  script:
    - npm ci
    - npx fragments govern check --cloud
  variables:
    FRAGMENTS_API_KEY: $FRAGMENTS_API_KEY
  rules:
    - if: $CI_PIPELINE_SOURCE == "merge_request_event"

After creating the CI config, remind the user to add FRAGMENTS_API_KEY as a secret in their CI provider settings.

7. Confirm completion

Summarize what was done:

  • @fragments-sdk/govern installed
  • API key configured (remind them not to commit .env)
  • Governance config created at fragments.config.ts
  • First check ran -- results visible in Fragments Cloud dashboard
  • CI workflow created (if chosen)

Mention related skills:

  • /fragments-govern to run checks, review staged changes, and fix violations
  • /fragments-policy to create custom design rules
  • If @fragments-sdk/ui is not installed, mention /fragments-ui-setup to add the component library
Weekly Installs
4
First Seen
9 days ago
Installed on
opencode4
gemini-cli4
claude-code4
github-copilot4
codex4
kimi-cli4