How do I install the UX UI Bug Intake skill?

Run npx skillmds@latest add maggielerman/ux-ui-bug-intake-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the UX UI Bug Intake skill do?

Use when asked to set up, use, triage, or maintain Context Layer UX/UI bug intake for user, agent, or subagent-detected UI defects. It is listed under AI & ML on SkillMD.

Is UX UI Bug Intake safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with UX UI Bug Intake?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is UX UI Bug Intake free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published UX UI Bug Intake?

maggielerman (@maggielerman) published this skill. Their other Agent Skills are listed on their SkillMD profile.

UX UI Bug Intake by maggielerman — Agent Skill

Name: UX UI Bug Intake
Rating: 4.5 (4 reviews)
Author: maggielerman

File contents

UX/UI Bug Intake

Use this skill for a lightweight docs-backed UX/UI bug register that complements project docs without becoming a heavyweight issue tracker.

First Checks

Locate DOCS/.
Look for DOCS/ux-ui-bugs/.
Read AGENTS.md and the active project doc when present.

If DOCS/ is missing, offer $context-layer-scaffold.

Setup

Preferred folder:

DOCS/ux-ui-bugs/README.md
DOCS/ux-ui-bugs/INBOX.md
DOCS/ux-ui-bugs/TRIAGED.md
DOCS/ux-ui-bugs/ARCHIVE.md

Use lowercase folder naming to match Context Layer conventions. Keep the register lightweight and do not create one file per bug.

Operating Model

Users, main agents, and subagents may detect bugs.
The main agent is the canonical logger/router.
Subagents report concise bug candidates; the main agent de-duplicates and records canonical entries.

Entry Fields

ID
Reported
Detected by
Actor
Surface
Summary
Severity
Status
Likely owner
Related project
Evidence path
Superseded by migration?
Notes

Statuses

new
triaged
scheduled
in active slice
fixed
wont-fix
superseded

Severities

blocker
high
medium
low

Evidence

The bug register is an operating workflow, not the evidence store. Screenshots, recordings, audits, or reproduction packets should live under:

DOCS/evidence/active/<project-id>/ux-ui-bugs/<bug-id>/

Link evidence paths from the bug entry and the owning project doc when the bug affects project state or sign-off.

Frequently asked questions

UX UI Bug Intake