lucidreactor-ui
Skill0 starsChanged 5 days agoMITView on GitHub
Import components from the LucidReactor UI library into your project. To use this skill, reference it in your message: Or more naturally: When the user requests to add a component from lucidreactor-ui: Fetch from GitHub (when published) or local file: - GitHub: https://raw.githubusercontent.com/kashaziz/lucidreactor-ui/main/packages/ui/src/components/{category}/{ComponentName}.tsx - Local: ~/work/kashif/lucidreactor-ui/packages/ui/src/components/{category}/{ComponentName}.tsx Check if src/lib/utils.ts exists in the target project. If not, create it with the cn utility: After copying, inform the user: Show all available components organized by category: Props: title, subtitle, image, category, readTime,…
In this repository4 other files it gives its agents.
- content-writerSkill
- full-stack-mvp-builderSkill
- screenshotsSkill
- social-cardsSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 8 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 3
Import components from the LucidReactor UI library into your project.
- Distinctive: line 23
When the user requests to add a component from lucidreactor-ui:
- Distinctive: line 47
Create directory if it doesn't exist
- Distinctive: line 48
Write the component file with the same name
- Very specific: line 52
Check if src/lib/utils.ts exists in the target project.
- Very specific: line 54
If not, create it with the cn utility:
- Distinctive: line 67
After copying, inform the user:
- Distinctive: line 130
All components use Tailwind CSS for styling
- Distinctive: line 131
All components are TypeScript with full type definitions
- Distinctive: line 132
All components support dark mode via CSS variables
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
LucidReactor UI Component Importer
Import components from the LucidReactor UI library into your project.
Usage
To use this skill, reference it in your message:
Using ~/.claude/skills/lucidreactor-ui/SKILL.md, add the blog-hero component
Using ~/.claude/skills/lucidreactor-ui/SKILL.md, list all available componentsOr more naturally:
Add the BlogHero component from lucidreactor-ui
List components in lucidreactor-uiInstructions
When the user requests to add a component from lucidreactor-ui:
1. Fetch Component Source
Fetch from GitHub (when published) or local file:
- GitHub:
https://raw.githubusercontent.com/kashaziz/lucidreactor-ui/main/packages/ui/src/components/{category}/{ComponentName}.tsx - Local:
~/work/kashif/lucidreactor-ui/packages/ui/src/components/{category}/{ComponentName}.tsx
2. Available Components
Blog Components (blog/)
- BlogHero.tsx - Hero header with gradient overlay for blog posts
- BlogCallout.tsx - Status-colored callout boxes (info, success, warning, error)
- BlogPullQuote.tsx - Pull quotes with accent styling and author attribution
- BlogRelatedPosts.tsx - Related posts carousel with hover effects
Coming Soon
- marketing/ - Marketing/landing page components
- forms/ - Form components (SearchBar, FileUpload, etc.)
- layout/ - Layout components (Header, Footer, etc.)
3. Copy Component to Project
- Target directory:
src/components/{category}/ - Create directory if it doesn't exist
- Write the component file with the same name
4. Copy Utilities (if needed)
Check if src/lib/utils.ts exists in the target project.
If not, create it with the cn utility:
import { type ClassValue, clsx } from 'clsx';
import { twMerge } from 'tailwind-merge';
export function cn(...inputs: ClassValue[]) {
return twMerge(clsx(inputs));
}5. Show Success Message
After copying, inform the user:
- Component location: Where the file was created
- Import statement: How to import it
import { ComponentName } from '@/components/{category}/{ComponentName}'; - Required dependencies: List any packages that need to be installed
lucide-react- Icons (most components)clsx- Class name utilitytailwind-merge- Tailwind class merging@radix-ui/*- UI primitives (some components)
- Usage example: Basic usage of the component
When User Lists Components
Show all available components organized by category:
🎨 LucidReactor UI Components
Blog Components:
• BlogHero - Hero header with gradient overlay
• BlogCallout - Status-colored callout boxes
• BlogPullQuote - Pull quotes with accent styling
• BlogRelatedPosts - Related posts carousel
Usage: "Add the BlogHero component from lucidreactor-ui"Component Details
BlogHero
Hero header with gradient overlay, category badge, and scroll indicator.
Props: title, subtitle, image, category, readTime, date, author, gradient
Dependencies: lucide-react
BlogCallout
Status-colored callout boxes for highlighting important information.
Props: children, variant (info/success/warning/error), title
Dependencies: lucide-react
BlogPullQuote
Styled pull quotes with optional author attribution.
Props: children, author, role, variant (default/accent/bordered)
Dependencies: lucide-react
BlogRelatedPosts
Related posts carousel with hover effects and customizable grid.
Props: posts, title, columns (2/3/4)
Dependencies: lucide-react
Notes
- All components use Tailwind CSS for styling
- All components are TypeScript with full type definitions
- All components support dark mode via CSS variables
- Components follow shadcn/ui patterns and conventions
- Local file path should be used when GitHub repo is not yet public
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

