All directories
SkillDesignProduct

AnyDesign

Analyzes any image, URL, or Figma file into a structured design.md—design system, component inventory, reconstruction notes portable to v0/Lovable/Cursor.

Open on GitHubBrowse more skills
01

Overview

AnyDesign is a Claude skill added to LimeDock Directories from recent community and vendor roundups. Analyzes any image, URL, or Figma file into a structured design.md—design system, component inventory, reconstruction notes portable to v0/Lovable/Cursor. This page covers install, how to invoke it, example prompts, prerequisites, and concrete use cases.

SaaSAgencyOther

Work with LimeDock

Using this skill? LimeDock can wire it into a durable automation you own.

Skills show what's possible. LimeDock builds and runs the owned marketing, sales, and ops automations around them.

We sell owned automations for SaaS teams — live workflows that plug into Slack, CRM, and your internal platform — not just a skill list.

Book a workflow call
02

Link

https://github.com/uxKero/anydesign
03

Installation guide

git clone https://github.com/uxKero/anydesign.git ~/.claude/skills/anydesign
04

How to use it

Point at a URL, screenshot, or Figma file and ask for design.md with system + inventory.

05

Example prompts

  • “Use the AnyDesign skill for: Reverse-engineer a competitor’s visual system”
  • “Walk me through AnyDesign step by step, then execute on my project.”
  • “Review my current approach and improve it using AnyDesign.”
  • “Produce a reusable checklist for running AnyDesign on similar work.”
06

Use cases and examples

  • Reverse-engineer a competitor’s visual system
  • Figma → design.md handoff
  • Feed design.md into Cursor/v0
  • Audit component inventories
  • Team playbook trial of AnyDesign on a real workflow
07

Prerequisites

  • Claude Code, Claude.ai (Skills enabled), or an Agent Skills–compatible host
  • Permission to install third-party skills — audit SKILL.md and scripts first
  • Project context (CLAUDE.md / product notes) for better outputs
08

Tips

  • Keep triggers specific so AnyDesign only fires when relevant.
  • Audit SKILL.md and any bundled scripts before production use.
  • Pair with verification (tests, review, screenshots) before shipping.
  • Re-audit installed skills monthly to avoid context tax from unused packs.
09

Sources