VibeFarsi offline/vendor workflow

When to activate

Use on tasks involving CLI install in local project; no MCP. 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: CLI install in local project; no MCP. 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

npx vibefarsi@latest init --dry-run
npx vibefarsi@latest init
npx vibefarsi add button calendar price --dry-run
npx vibefarsi add button calendar price

Do this in a React + Tailwind v4 project after review. Downloaded code becomes local; runtime does not need a service connection. There is no MCP.

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