break-ui
Stress-Test UI With Realistic Edge Cases
Demo data can hide layout failures, missing states, and incorrect formatting. This skill guides realistic fixture creation, development-only comparisons, and reports with targeted fixes.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "break-ui" from https://skillstore.io/skills/emilkowalski-break-ui.md and its manifest at https://skillstore.io/api/skills/emilkowalski-break-ui/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "break-ui". Stress-test a member list with long emails and missing avatars.
Expected outcome:
- Illustrative finding: a long email pushes the action menu outside a narrow row, making the action unreachable.
- Proposed fix: allow the text column to shrink and wrap while preserving the action width.
- Design decision: wrap the full email or shorten it with access to the complete value.
- What held up: the missing-avatar fallback retained its size in the tested state.
Using "break-ui". Review counts and empty states in a dashboard.
Expected outcome:
- Illustrative finding: a count of one displays a plural label.
- Proposed fix: use locale-aware pluralization and verify zero, one, and larger counts.
- Illustrative finding: zero items leaves a blank content region.
- Design decision: choose an empty-state message and an appropriate next action.
Using "break-ui". Create data only for a project card grid.
Expected outcome:
- Fixture plan: spread long titles, missing images, duplicate names, and large counts across separate cards.
- Comparison states: Demo, Worst case, Empty, One, and a realistic large collection.
- Delivery: a development-only fixture switch, or a self-contained HTML comparison when no project exists.
Security Audit
SafeAll 44 static findings are false positives: Markdown backticks describe UI examples, and reconnaissance matches concern layout dimensions. The quoted injection phrase warns against obeying repository instructions rather than requesting an override. No evidence found of malicious instruction overrides, credential access, data exfiltration, or executable shell payloads in the two reviewed files.
Risk Factors
⚙️ External commands (41)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/emilkowalski-break-ui/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/emilkowalski-break-ui?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/emilkowalski-break-ui?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/emilkowalski-break-ui/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/emilkowalski-break-ui.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
emilkowalski. (2026). break-ui security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/emilkowalski-break-ui/audits/1BibTeX citation
@techreport{emilkowalski-emilkowalski-break-ui-2026,
author = {emilkowalski},
title = {break-ui security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/emilkowalski-break-ui/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "break-ui security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "emilkowalski"
date-released: "2026-10-02"
url: "https://skillstore.io/skills/emilkowalski-break-ui/audits/1"
identifiers:
- type: other
value: "skillstore:emilkowalski-break-ui:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Check a Component Before Release
Test member rows with long emails, short names, missing avatars, and mixed statuses before shipping.
Compare Layout Decisions
Use a fixture toggle to compare wrapping, truncation, empty states, and narrow layouts before approving design changes.
Reproduce Data-Dependent Failures
Create reusable fixtures for localization, collection boundaries, and missing data, then verify requested fixes across every state.
Try These Prompts
Stress-test [component] with realistic worst-case data. Add a development-only comparison toggle and report failures before applying fixes.
Data only [component]. Map its fields and limits, then create demo, worst-case, empty, and single-item fixtures with a development-only toggle.
Stress-test [screen] at its real container width, 320 pixels, and its widest supported layout. Check 200 percent zoom and supported RTL and dark mode. Separate visually verified findings from inferred findings.
Fix findings 1 and 3 from the previous report using existing project conventions. Recheck every fixture state and supported layout. Keep fixtures for regression checks and keep the toggle development-only.
Best Practices
- Use plausible examples or actual validation limits, and use reserved example domains for fixture emails and URLs.
- Inject fixtures at the existing data boundary and keep the comparison toggle out of production.
- Review proposed fixes first, then verify approved changes against both demo and worst-case states.
Avoid
- Using arbitrary oversized strings instead of plausible values or schema-backed limits.
- Editing markup or CSS to manufacture failures rather than changing the input data.
- Stopping after long-text tests while ignoring empty lists, singular counts, missing media, and translated labels.
Frequently Asked Questions
What does this skill test?
Does it fix problems automatically?
Does it require a running application?
Can it work without browser tooling?
Should the toggle remain in production?
Is this a complete security or accessibility audit?
Developer Details
Author
emilkowalskiLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Repository
https://github.com/emilkowalski/skills/tree/e8a175de22ae1e49370fc144c1f3bb9aeedf988d/skills/break-uiRef
03f20c3ac209656c882df2c2afa710a6d8e08828
Maintenance freshness
10/2/2026
Usage
0 downloads · 0 views
File structure
📄 SKILL.md