Skip to content
Back to skills

Zt Vibefarsi Components

ASecurity

VibeFarsi component integration: production-level official CLI, compound states, RTL. Use when implementing, reviewing or testing vibefarsi component integration for React, Vite, Next.js or Perfect_AI projects.

  • 14 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 7, 2026
developmentreactnextjstestingapibackendperformance

Works with

  • cli
  • api
  • mcp

Security analysis

A100/100

Scanned November 7, 2026

npx -y skills add Realjustawall/Perfect-AI --skill zt-vibefarsi-components --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Zt Vibefarsi Components?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Zt Vibefarsi Components
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/realjustawall-zt-vibefarsi-components/badge)](https://www.skillsdirectory.com/skills/realjustawall-zt-vibefarsi-components)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: zt-vibefarsi-components
description: VibeFarsi component integration: production-level official CLI, compound states, RTL. Use when implementing, reviewing or testing vibefarsi component integration for React, Vite, Next.js or Perfect_AI projects.
---

# VibeFarsi component integration

## When to activate
Use on tasks involving **official CLI, compound states, RTL**. For unrelated backend tasks do not load this skill.

## Implementation sequence
1. Look up exact slug in registry-index.json and per-item implementation specs.
2. Dry-run `npx vibefarsi add <slug> --dry-run` in a compatible React + Tailwind v4 project.
3. Install chosen official component through CLI after verifying file diffs and dependencies; no MCP.
4. Adapt semantic tokens, Persian text, RTL logical properties and animations without double ownership.
5. Test mobile/keyboard/validation/reduced-motion; keep upstream license notes.

## Task-specific requirements
- Scope: **official CLI, compound states, RTL**. Design the full execution path, not a screenshot placeholder.
- Identify dependency version and actual supported API signature; avoid inventing APIs.
- Use original code, or install licensed upstream through its maintained tool if the user wants upstream code.
- Choose measurable states, error handling, accessibility and performance budgets.

## Implementation starter
**Implementation notes:** Model official CLI, compound states, RTL as explicit states, define input/output props and independent cleanup. Read master reference(s) below before writing code.


## Evidence / acceptance
- Official slug resolves; files installed without overwrite; observed keyboard and RTL behavior correct.
- Test common, edge, interrupted, accessibility and responsive states; provide concrete artifacts/evidence.

## Deep references
- `../perfect-ai-master/references/07-vibefarsi-full-catalog.md`
- `../perfect-ai-master/references/21-vibefarsi-implementation.md`

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.