agentleFS
sodam-aisodam-ai/SoDam-Design-Kit/skills/design-pipeline/SKILL.md

design-pipeline

Skill7 starsChanged 4 months agoApache-2.0View on GitHub

Figma 디자인을 shadcn/ui 코드로 만들고 실제 브라우저 검증(Playwright+axe-core+3뷰포트)을 통과해야만 완료로 표시하는 파이프라인. "Figma", "디자인 코드로", "컴포넌트 만들어", "shadcn" 등 UI 생성 요청 시 사용.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. BENZEMA216/ai-ecommerce-agent-skills★ 71same name
    2. 2233admin/design-pipeline★ 15same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repositoryOne other file it gives its agents.

The file

Files
SKILL.md

design-pipeline

.PRD/04_PROJECT_SPEC.md의 절대 규칙(DO NOT/ALWAYS DO)을 그대로 따릅니다.

핵심 규칙 (요약 — 전문은 04_PROJECT_SPEC.md)

  • 컴포넌트 1개 단위로 작게 시작
  • component-map.json 재사용 우선, Figma 구조 데이터 사용(스크린샷 추측 금지)
  • 검증 순서 고정: 생성 → dev server 자동 기동 → Playwright 렌더 → axe-core → 3뷰포트 → Lighthouse(참고)
  • PASS 조건 4가지(02_DATA_MODEL.md 단일 출처): 렌더 성공·콘솔 에러 0·axe critical/serious 0·3뷰포트 스크린샷 존재
  • FAIL 시 실패 사유를 다음 시도에 주입, 최대 3회, 2연속 FAIL만 확정
  • 표시(presentation) 코드만 수정 — 로직·인증·저장·API 파일 금지

관련 명령

  • /sodam-design-kit:setup
  • /sodam-design-kit:pipeline

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.