Agent skill

Glide Component Segregator

Component segregation guide for Glide (@srivarsank/glide). An agent skill from SrivarsanK/Glide.

Apache-2.0Auto-check passedFrontend & Design

Install Glide Component Segregator

skills CLI

$ npx skills add SrivarsanK/Glide --skill glide-component-segregator -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install SrivarsanK/Glide glide-component-segregator --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/SrivarsanK/Glide.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/glide-component-segregator .claude/skills/glide-component-segregator && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "glide-component-segregator" agent skill from https://github.com/SrivarsanK/Glide/tree/main/skills/glide-component-segregator into .claude/skills/glide-component-segregator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "glide-component-segregator", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/SrivarsanK/Glide/tree/main/skills/glide-component-segregator

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add SrivarsanK/Glide --skill glide-component-segregator -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install SrivarsanK/Glide glide-component-segregator --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/SrivarsanK/Glide.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/glide-component-segregator .agents/skills/glide-component-segregator && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "glide-component-segregator" agent skill from https://github.com/SrivarsanK/Glide/tree/main/skills/glide-component-segregator into .agents/skills/glide-component-segregator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "glide-component-segregator", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add SrivarsanK/Glide --skill glide-component-segregator -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install SrivarsanK/Glide glide-component-segregator --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/SrivarsanK/Glide.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/glide-component-segregator .cursor/skills/glide-component-segregator && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "glide-component-segregator" agent skill from https://github.com/SrivarsanK/Glide/tree/main/skills/glide-component-segregator into .cursor/skills/glide-component-segregator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "glide-component-segregator", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/SrivarsanK/Glide.git --path skills/glide-component-segregator

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add SrivarsanK/Glide --skill glide-component-segregator -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install SrivarsanK/Glide glide-component-segregator --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/SrivarsanK/Glide.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/glide-component-segregator .gemini/skills/glide-component-segregator && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "glide-component-segregator" agent skill from https://github.com/SrivarsanK/Glide/tree/main/skills/glide-component-segregator into .gemini/skills/glide-component-segregator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "glide-component-segregator", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install SrivarsanK/Glide glide-component-segregator

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add SrivarsanK/Glide --skill glide-component-segregator -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/SrivarsanK/Glide.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/glide-component-segregator .github/skills/glide-component-segregator && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "glide-component-segregator" agent skill from https://github.com/SrivarsanK/Glide/tree/main/skills/glide-component-segregator into .github/skills/glide-component-segregator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "glide-component-segregator", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add SrivarsanK/Glide --skill glide-component-segregator -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install SrivarsanK/Glide glide-component-segregator --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/SrivarsanK/Glide.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/glide-component-segregator .opencode/skills/glide-component-segregator && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "glide-component-segregator" agent skill from https://github.com/SrivarsanK/Glide/tree/main/skills/glide-component-segregator into .opencode/skills/glide-component-segregator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "glide-component-segregator", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: glide-component-segregator
GitHub stars: 125
Token cost: ~1.2k tokens
SKILL.md length: 304 words
Files: 1
Skills in repo: 3
Repo updated: Sep 30, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Component segregation guide for Glide (@srivarsank/glide). An agent skill from SrivarsanK/Glide.

Works in 5 steps: Locate a component before editing it → Find the root / background element → Target a specific nested element → …
Tasks that involve Static sites and blogs
SKILL.md covers What Is This?, Registry Shape, How to Use This as an AI Agent and Edge Cases, plus 1 more section
Calls npx

What it does

Glide Component Segregator is an agent skill from SrivarsanK/Glide. Component segregation guide for Glide (@srivarsank/glide). Teaches AI agents how to read glide-components.json to discover, locate, and edit components by name instead of raw file:line:col coordinates. Covers 300ms auto-watch behavior, adding new components, co-located CSS detection, root element targeting, multi-framework support (React, Vue, Svelte, Astro, HTML), and coordination with Glide's In-Memory SceneGraph and LWW delta queue.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Frontend & Design, covering Static sites and blogs and CSS and styling. It works with Astro, Svelte, Vue.js and React. The repository describes itself as: Local visual design tool for React, Vue and Svelte. Click any element on a live canvas, edit styles and layout visually, and Glide writes the changes directly back to your source… The licence is Apache-2.0.

When your agent uses it

Tasks that involve Static sites and blogs
Tasks that involve CSS and styling

Example prompts

“/glide-component-segregator”

Requirements

Node.js

Workflow steps

5 steps, taken from the step headings in SKILL.md.

Locate a component before editing it
Find the root / background element
Target a specific nested element
Jump to imported sub-component definitions
Edit co-located CSS

What it can do on your machine

Read from SKILL.md and the folder at commit 8fe0f4e. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- npx
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Glide Component Segregator loads about 1.2k tokens when it runs. Until then it costs about 117 tokens; SKILL.md has 304 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~117
When it runs · the whole SKILL.md, loaded when a task matches: ~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from SrivarsanK/Glide at commit 8fe0f4e, republished under its Apache-2.0 licence (© SrivarsanK). 304 words, ~1,248 tokens.

Download SKILL.mdSave it as .claude/skills/glide-component-segregator/SKILL.md (or your agent's skills folder).

name: glide-component-segregator
description: Component segregation guide for Glide (@srivarsank/glide). Teaches AI agents how to read `glide-components.json` to discover, locate, and edit components by name instead of raw file:line:col coordinates. Covers 300ms auto-watch behavior, adding new components, co-located CSS detection, root element targeting, multi-framework support (React, Vue, Svelte, Astro, HTML), and coordination with Glide's In-Memory SceneGraph and LWW delta queue.

Glide Component Segregator

What Is This?

When glide starts (via npx @srivarsank/glide or glide), it scans the target project's source tree and writes glide-components.json to the project root. It watches for source file changes and rebuilds incrementally with a 300 ms debounce.

Every component in the app — including layout wrappers, backgrounds, and sub-elements — is indexed in a ComponentBucket within that file.

Registry Shape

// glide-components.json
{
  "projectRoot": "/absolute/path/to/project",
  "generatedAt": "2026-09-24T12:00:00.000Z",
  "framework": "react" | "vue" | "svelte" | "astro" | "html" | "unknown",
  "buckets": ComponentBucket[]
}

interface ComponentBucket {
  name: string;           // "Card", "Header", "Hero", "Default", "Anonymous"
  file: string;           // absolute path to source file
  exportType: "default" | "named" | "anonymous" | "sfc" | "html";
  line: number;           // line of the function/export declaration
  column: number;
  elements: RegistryElement[];
  cssFiles: string[];     // co-located CSS files (same dir, same stem)
}

interface RegistryElement {
  id: string;             // data-gl-source value or "file:line:col" fallback
  tagName: string;        // "div", "button", "Card.Header", etc.
  line: number;
  column: number;
  isRoot: boolean;        // true = outermost element returned by the component
  classNames: string[];   // static className tokens
  text?: string;          // trimmed direct text content (≤25 chars)
}

How to Use This as an AI Agent

1. Locate a component before editing it

Do not guess file paths or scan the entire filesystem manually. Read the registry first:

bash

# In the target project root:
cat glide-components.json

Then find the bucket:

const bucket = registry.buckets.find(b => b.name === 'Card');
// bucket.file = "/Users/dev/myapp/src/components/Card.tsx"
// bucket.line = 12

Use bucket.file + bucket.line as the starting point for any edit.

2. Find the root / background element

The outermost wrapper element is tagged isRoot: true:

const root = bucket.elements.find(e => e.isRoot);
// root.tagName = "div", root.classNames = ["card-container"], root.id = "src/Card.tsx:13:8"

Use root.id as the data-gl-source target when sending style or layout edits via the Glide WebSocket protocol.

3. Target a specific nested element

Find by tagName, className, or text:

const btn = bucket.elements.find(e => e.tagName === 'button' && e.classNames.includes('submit'));
// btn.id → use this as the edit target

4. Jump to imported sub-component definitions

If an element has a capitalized tagName (e.g. <Button />, <Avatar />), it is a custom component instantiation. In Glide v1.1.0+:

The server provides resolveComponentDefinition to locate the origin file of that component.
The Properties panel header and Layers tree include a Jump to Component button.
Query registry.buckets.find(b => b.name === tagName) to jump directly to its definition.

5. Edit co-located CSS

Check bucket.cssFiles for associated stylesheets:

if (bucket.cssFiles.length > 0) {
  // Edit bucket.cssFiles[0] for CSS module changes
}

Edge Cases

Scenario	Behavior
Anonymous export (`export default function() { ... }`)	`bucket.name = "Anonymous"`, `exportType = "anonymous"`
Vue SFC (`.vue`)	Scans `<template>` block only; `exportType = "sfc"`
Svelte (`.svelte`)	Strips `<script>` and `<style>` blocks; scans template; `exportType = "sfc"`
Astro (`.astro`)	Preserves `---` frontmatter; scans template; `exportType = "sfc"`
Static HTML (`.html`)	Excludes `<head>`, `<script>`, `<style>`; `exportType = "html"`
Co-located CSS	Scans directory for `.css`, `.module.css`, `.scss`, `.sass` matching component stem
File added / deleted	Registry auto-rebuilds in 300 ms via `watchRegistry`
Simultaneous edits	Server `PropertyDeltaQueue` enforces LWW conflict resolution per `(nodeId, propKey)`

Recommended Workflow

1. Read glide-components.json
2. Find bucket by component name (e.g. "Card", "Header")
3. Inspect elements — target by isRoot / tagName / classNames
4. Use element.id as the target data-gl-source
5. For CSS edits — open file listed in bucket.cssFiles
6. If adding a new component — wait 300 ms, then re-read registry

Files

Just SKILL.md in skills/glide-component-segregator of SrivarsanK/Glide.

Open the folder on GitHubat commit 8fe0f4e

Compare with similar skills

Glide Component Segregator next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Glide Component Segregator compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Glide Component Segregator this skillSrivarsanK/Glide	125	—	~1.2k	Automated safety check: Pass	Apache-2.0	9 days ago
Kill AI Slopyetone/kill-ai-slop	1.3k	—	~1.4k	Automated safety check: Pass	Apache-2.0	24 days ago
Portable Text Serializationsanity-io/agent-toolkit	188	1 repos	~1.1k	Automated safety check: Pass	MIT	4 days ago
Design StyleCastor6/tactus	376	1 repos	~2.1k	Automated safety check: Pass	Apache-2.0	5 mo ago
Motion Dev Animations199-biotechnologies/motion-dev-animations-skill	114	1 repos	~2.8k	Automated safety check: Notes	MIT	6 mo ago
UI UX Pro Maxsundial-org/awesome-openclaw-skills	663	2 repos	~657	Automated safety check: Pass	None	7 mo ago

Similar skills

Kill AI Slop
yetone/kill-ai-slop
Find and remove AI slop — the generic, machine-default visual and copy tics of vibe-coded products — from a web project.
1.3k GitHub stars~1.4k tokensUpdated 24 days ago
Frontend & DesignAuto-check passed
Portable Text Serialization
sanity-io/agent-toolkit
Official
Render and serialize Portable Text to React, Svelte, Vue, Astro, HTML, Markdown, and plain text.
188 GitHub starsUsed in 1 repo~1.1k tokens
Frontend & DesignAuto-check passed
Design Style
Castor6/tactus
A skill your agent uses whenever the user asks to build, create, design, develop, improve, or style any frontend interface or visual element.
376 GitHub starsUsed in 1 repo~2.1k tokens
Frontend & DesignAuto-check passed
Motion Dev Animations
199-biotechnologies/motion-dev-animations-skill
Creates 120fps GPU-accelerated animations with Motion.dev (Framer Motion successor) for React, Next.js, Svelte, and Astro projects.
114 GitHub starsUsed in 1 repo~2.8k tokens
Frontend & DesignAuto-check: notes
UI UX Pro Max
sundial-org/awesome-openclaw-skills
UI/UX design intelligence and implementation guidance for building polished interfaces.
663 GitHub starsUsed in 2 repos~657 tokens
Frontend & DesignAuto-check passed
Tailwind CSS Patterns
ever-works/ever-works
Provides comprehensive Tailwind CSS utility-first styling patterns including responsive design, layout utilities, flexbox, grid, spacing, typography, colors, and modern CSS best practices.
162 GitHub starsUsed in 3 repos~1.6k tokens
Frontend & DesignAuto-check: notes

Questions about Glide Component Segregator

What does Glide Component Segregator do?

Component segregation guide for Glide (@srivarsank/glide). An agent skill from SrivarsanK/Glide. Glide Component Segregator is an agent skill from SrivarsanK/Glide. Component segregation guide for Glide (@srivarsank/glide).

When should I use Glide Component Segregator?

Glide Component Segregator fits situations like: tasks that involve Static sites and blogs; tasks that involve CSS and styling.

How do I install Glide Component Segregator in Claude Code?

Run `npx skills add SrivarsanK/Glide --skill glide-component-segregator -a claude-code`. Or copy the skill folder (skills/glide-component-segregator in SrivarsanK/Glide) into .claude/skills/glide-component-segregator in your project. Claude Code loads it when a task matches its description.

How do I install Glide Component Segregator in Codex?

Run `npx skills add SrivarsanK/Glide --skill glide-component-segregator -a codex`. Or copy the skill folder (skills/glide-component-segregator in SrivarsanK/Glide) into .agents/skills/glide-component-segregator in your project. Codex loads it when a task matches its description.

Can I use Glide Component Segregator in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add SrivarsanK/Glide --skill glide-component-segregator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/glide-component-segregator, .gemini/skills/glide-component-segregator, .github/skills/glide-component-segregator and .opencode/skills/glide-component-segregator in your project.

What does Glide Component Segregator need to run?

Going by SKILL.md and its folder, Glide Component Segregator needs the command-line tools its instructions call (npx). Our summary lists: Node.js.

Does Glide Component Segregator access the network?

SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Glide Component Segregator safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Glide Component Segregator use?

Glide Component Segregator is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Glide Component Segregator use?

About 1.2k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Glide Component Segregator?

Skills that share tags, products or a category with Glide Component Segregator: Kill AI Slop (yetone/kill-ai-slop, 1.3k stars), Portable Text Serialization (sanity-io/agent-toolkit, 188 stars), Design Style (Castor6/tactus, 376 stars) and Motion Dev Animations (199-biotechnologies/motion-dev-animations-skill, 114 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Glide Component Segregator?

SrivarsanK (a GitHub user) maintains it in SrivarsanK/Glide, which has 125 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on September 30, 2026.

Source: SrivarsanK/Glide on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Glide Component Segregator

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Glide Component Segregator

What Is This?

Registry Shape

How to Use This as an AI Agent

1. Locate a component before editing it

2. Find the root / background element

3. Target a specific nested element

4. Jump to imported sub-component definitions

5. Edit co-located CSS

Edge Cases

Recommended Workflow

Files

Compare with similar skills

Similar skills

More from SrivarsanK/Glide

Related

Questions about Glide Component Segregator