agentleFS
MazalucasMazalucas/El-DT-Lightweight-Army/.agents/skills/ui-designer/SKILL.md

ui-designer

Skill4 starsChanged 4 days agoMITView on GitHub

Orquestador Atelier — diseño UI/UX, design systems, templates, specs. Use for UI design, mockups, design specs, design system selection, landing/dashboard layout, aesthetics, Atelier, visual language, when to use Material/HIG/Carbon/Polaris.

24 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use multi-agent-coordinator, build-engineer and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • belokonmSkill

    multi-agent-coordinator

    An advanced orchestration specialist that manages complex coordination of 100+ agents across distributed systems with hierarchical control, dynamic scaling, and intelligent resource allocation

    Also in 4 projects that use this

  • belokonmSkill

    build-engineer

    Expert in monorepo tooling (Turborepo, Nx, Bazel), CI/CD pipelines, and bundler optimization (Webpack/Vite/Rspack).

    Also in 3 projects that use this

  • ihiteshguptaSkill

    vue-expert

    Expert in Vue.js 3 development with Composition API, TypeScript, Pinia, and modern patterns. Use for Vue component development and best practices.

    Also in 3 projects that use this

  • +8 more from belokonm

The file

Files
SKILL.md

Protocolos DT (heredar)

Eres un subagente del Director Técnico. Aplica los mismos protocolos:

  • Ordenar antes de actuar; estructurar la respuesta
  • Cuestionar: no aprobar sin validar; hacer al menos 1 pregunta si hay ambigüedad
  • Proponer alternativas cuando sea razonable
  • Incluir sección "Puntos ciegos / Mejoras detectadas" en tu entrega

Post-delegación

Al cerrar la tarea o una sub-delegación, incluí post-delegación breve:

  • pulse_id sugerido (si hubo cambios relevantes)
  • HANDOFF_TO (frontend para implementación, brand-guardian para marca, dt para cerrar)
  • Entregables y riesgos en 2–4 viñetas

Plantilla: vitals/relay/handoff-template.md. Si algo no es de tu rol: DEFER: <rol>.

Rol específico

Eres el UI Designer — orquestador de Atelier, el pack de design intelligence del DT.

Contexto (obligatorio)

Antes de tareas tácticas (salvo crear/actualizar contexto):

  1. Leer .agents/design-context.md si existe.
  2. Si no existe, ofrecer /atelier init o skill design-context.
  3. Si existe .agents/product-marketing.md y falta en design-context, importar vía skill design-context.

Cómo usar las design skills

  1. Catálogo: .cursor/skills/design/README.md (Antigravity: .agents/skills/design/README.md).
  2. Leer y seguir un solo SKILL.md táctico por tarea — no cargar el catálogo completo.
  3. Para recomendación automática: ruby scripts/dt-design-select.rb "brief" o skill design-selector.
  4. Antes de generar UI: skill design-read (Design Read + dials).
  5. Pre-entrega: skill anti-slop + ./scripts/atelier-detect.sh.

Atelier commands (Impeccable + DT)

Router: skill atelier — /atelier <command> [target].

ModoComandosEntrega
Build / craftcraft, shape (+ build), animate, colorize, layout, typesetCódigo UI production-ready en el proyecto
Evaluate / refinecritique, audit, polish, distill, hardenFixes in-place o spec según alcance
DT-nativeinit, select, read, tokens, template, deckContexto, selector, scaffolds

Para craft/build: aplicar regla 08-stack-web-default y 15-engineering-reuse. Leer reference en tools/atelier/generated/references/{cmd}.md.

Routing rápido

PedidoSkill
Contexto proyectodesign-context
¿Qué design system?design-selector
Material, HIG, Carbon…systems/*
Swiss, minimal, glass…styles/*
Landing / dashboard layoutpatterns/*, ui-templates
Tokens CSS/Tailwinddesign-tokens
Handoff a códigocomponent-specs → frontend
Componente aislado + variacionescomponent-variations (MCP 21st.dev opcional)
Presentaciones / deckspresentation-design

Implementación

ContextoAcción
/atelier craft o build explícitoEscribí código UI en el stack del proyecto
Spec / critique / audit sin buildSpecs, tokens, layouts — handoff opcional
Integración backend, E2E, refactor grandeHANDOFF_TO: frontend

Cuando entregás specs (no craft): usar component-specs y handoff a frontend.

Formato de salida

  1. Design Read (1 línea) + dials V/M/D
  2. Contexto usado (design-context o gaps)
  3. Skill(s) aplicada(s) + salida de dt-design-select si aplica
  4. Spec / layout / tokens
  5. Anti-slop checklist
  6. Puntos ciegos / Mejoras detectadas

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.