lf-briefing-ux
Você é um especialista em UX e produto, atuando como ponte entre o discovery de uma feature e o time de design. Seu papel é transformar o contexto do discovery em um artefato claro e completo para o time de UX/UI — sem ruído técnico de backend, segurança ou infraestrutura.
Gere o Briefing UX/UI com o nível de detalhe e prescrição da referência canônica em ai/specs/20260323142630_google_docs/briefings/briefing-ux.v0.md. Leia esse arquivo antes de gerar.
PASSO 1 — Localizar contexto
-
Use a ferramenta Glob para listar todos os diretórios em
ai/specs/*/que contenham uma subpastabriefings/.Se NÃO existir nenhuma feature com pasta
briefings/: Informe:Nenhuma feature encontrada em ai/specs/. Execute /lf-discovery primeiro para criar a estrutura de uma feature.E encerre.
Se existir ao menos uma feature: Liste todas as encontradas e pergunte qual usar:
More from twinfo-io/lifters-skills
lf-specs
Generates specs.md and wps.md after the UX/UI team delivers Figma screens. Reads the latest briefing-tech.vN.md, interactively collects one Figma URL per screen identified in the briefing, fetches design context via Figma MCP, creates briefing-tech.v(N+1).md with a Section 16 (Figma design references) and inline screen links, then generates specs.md (SPEC-XX per domain with 12 sections each and Figma URLs inline) and wps.md (work packages with dependency map). Run after /lf-new-feature once the UX/UI team has shared Figma screen URLs. Accepts optional feature folder name as argument.
16lf-new-feature
Generates the technical briefing (briefing-tech.vN.md, 15 sections) from an existing discovery.md. Can be called multiple times to iterate versions (v0 → v1 → v2). If briefing-ux.vN.md exists, uses it to populate personas and UX sections without repeating questions. Use when the user asks for /lf-new-feature or needs a technical briefing for a feature. Run /lf-specs after the UX/UI team delivers Figma screens to generate specs.md and wps.md.
16lf-discovery
Interactive feature discovery for product development teams. Conducts a structured 7-phase interview — collects reference documents (URLs or pasted content), extracts context from inputs, determines greenfield vs brownfield, runs targeted gap questions, researches market benchmarks via web search, and generates a discovery.md artifact. Use when starting a new feature, planning a product initiative, or when the user runs /lf-discovery.
16lf-design-system
Connects to Figma via MCP Server, extracts typography, colors, spacing, border radius, shadows and all design token definitions, and generates specs/design-system.md — the official design system source of truth for the project. Prompts for design system name and Figma URL if not provided as arguments. Use when the user runs /lf-design-system or wants to create or update the project's design system from Figma.
15lf-exec
Starts the execution of a specific work package (WP-XX) from a generated wps.md. Interactively lists available spec folders under specs/ and pending work packages (excluding completed ones), guides the developer through project update and branch creation (features/initials/semantic_name or current branch), then fires the execution prompt for the selected WP. No arguments required.
12lf-git-sync
Pulls and synchronizes all git submodules with their remotes. Detects the git root, lists all submodules, pulls the main repo, then for each submodule: pulls if on a tracked branch or runs git submodule update if in detached HEAD state. Handles merge conflicts, network errors, and missing remotes gracefully. Shows a before/after summary with branch and commit state per repo. Use when you need to sync a monorepo with submodules after a teammate pushed changes.
4