ixlab-engineer

Original：🇺🇸 English

Translated

Use when the user wants to implement UI from IxLab artifacts and needs design-system-aware frontend execution rather than generic code generation.

1installs

Sourcejesusexpositol/ixlab

Added on2026-03-08

NPX Install

npx skill4agent add jesusexpositol/ixlab ixlab-engineer

SKILL.md Content

View Translation Comparison →

IxLab Engineer

Use this skill when implementation should follow IxLab artifacts instead of improvising directly from the prompt.

Read These Files

```
design/system.md
```
when present
```
design/entities/{entity}/ux.md
```
```
design/entities/{entity}/ui.md
```
relevant component specs under
```
design/components/
```

If docs MCP or equivalent documentation context is available, use it only when the implementation depends on framework, component-library, or accessibility API specifics.

Read the repository codebase before changing UI code.

Responsibilities

translate artifacts into working code
preserve interaction intent and state coverage
align implementation with the design system
avoid generic visual drift during implementation

Workflow

Inspect the existing codebase and identify the target files.
Read the relevant IxLab artifacts before changing code.
Decide whether the design entity covers a single surface, multiple pages, or a multi-step flow.
Implement the interface and behavior described in the artifacts.
If the entity spans multiple pages or steps, preserve the shared structure, naming, and state model from the unified artifact instead of re-scoping it page by page.
Cover states explicitly:
- default
- empty
- loading
- error
- success
- disabled or permission-gated when relevant
Reuse existing components when they fit the spec.
If implementation details depend on framework or library behavior, consult docs MCP or equivalent official documentation context when available.
If the artifacts are incomplete, call out the gap and make the narrowest reasonable assumption.
If the user asks for only one slice of a multi-surface entity, state the partial scope clearly instead of silently rewriting the artifact boundary.

Quality Rules

Do not treat the design artifact as optional.
Do not silently discard states or interaction rules.
Preserve consistency with the rest of the codebase.
Prefer small, reviewable changes over broad rewrites.
If the codebase and the artifact conflict, explain the conflict and resolve it deliberately.
Do not collapse a multi-page entity into an isolated page implementation without saying so.
Do not rename or fragment the entity model unless there is a deliberate reason.
Prefer official documentation over memory when using docs MCP for concrete implementation details.

Finish Condition

The implementation should feel traceable back to the IxLab artifacts instead of looking like a generic approximation.