Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

The component & design-token baseline for human and agentic developers (spacing, typography, theme, etc)

Abierto
  • ¿Algo no está bien?
#300 0 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@IanoNjuguna ya está trabajando en esto.

Desde el 15/9/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

Discussed in https://github.com/IntersectMBO/developer-experience/discussions/299

Originally posted by IanoNjuguna September 14, 2026
A design-token baseline translates human visual decisions into machine-readable data structures (such as JSON or W3C format). Human developers visually interpret design specs, whereas agentic AI developers require programmatic constraints to prevent hardcoding arbitrary values and pixel padding, or fragmented font hierarchies.

Implementation Guideline

This entails shipping design skills for AI agents, and a brand assets page for human developers. Context:

  • CSS Variable Export: Transform tokens into CSS Custom Properties (e.g., --space-md, --color-text-primary) using tools like Style Dictionary so both human and agentic developers consume a single source of truth.

  • Agent Context Injection: Provide the token taxonomy as a system prompt, MCP tool, or skill file. Instruct AI agents to fail generation if arbitrary values are output instead of semantic variables.

Why a Shared Baseline Matters

  • Eliminates AI Hallucinations: Agentic developers evaluate hard constraints better than open-ended style guidelines. Named tokens enforce guardrails (e.g., forcing the agent to use space.md instead of guessing padding is 13px).

  • Enforces Deterministic UI Rules: Enables automated programmatic checks (e.g., CI/CD linters, AST checks, Model Context Protocol servers) to validate generated code against a token schema.

  • Simplifies Multi-Theme Architecture: Decouples raw values (primitives) from intent (semantics), allowing humans and agents to update light/dark/brand themes without modifying component code.

Three-Tier Token Architecture

  • Primitive Tokens (Option Layer): Raw visual values. Never referenced directly inside UI code.

  • Semantic Tokens (Intent Layer): Defines the meaning or purpose of a value. Used by human and agentic coders.

  • Component Tokens (Scope Layer): Specific overrides for single-purpose components (e.g., button.primary.bg).

Lenguaje dominante
TypeScript
Estrellas
13
Forks
22
Merge medio
19 h 1 min
PR fusionados (30 d)
10

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de IntersectMBO/developer-experience

Todos los issues de IntersectMBO/developer-experience

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.