break
Stress-Test a UI Component
UI components often fail when content, states, or container sizes differ from the expected path. This skill builds a focused harness that exposes visible failures.
Mit meinem Agent installieren
Kopieren Sie diese Anfrage in Ihren Agent. Sie enthält die maßgebliche Skill-Seite und das Manifest.
Review the Skillstore skill "break" from https://skillstore.io/skills/jakubkrehel-break.md and its manifest at https://skillstore.io/api/skills/jakubkrehel-break/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Ihr Agent sollte weiterhin seinen Plan anzeigen und alle von der Sicherheitsrichtlinie verlangten Bestätigungen anfordern.
Agent-lesbare Ressourcen
Verwenden Sie diese Links, wenn ein KI-Agent, Crawler oder Skript sauberen Kontext benötigt, statt die vollständige Seite zu lesen.
Testen
„break“ wird verwendet. Stress-test the product card component.
Erwartetes Ergebnis:
- Long unbreakable title: text crosses the card boundary. Owner: typography.
- Zero-price state: layout remains stable.
- Narrow container: action button escapes the card. Owner: layout.
„break“ wird verwendet. Test the status badge across relevant scenarios.
Erwartetes Ergebnis:
Everything survived. The report page includes empty, typical, long, RTL, narrow-container, and disabled scenarios.
„break“ wird verwendet. Check the results list with realistic quantities and states.
Erwartetes Ergebnis:
- Zero items: the list region is blank without an empty-state message. Owner: writing.
- Large quantity: the list extends without the expected scroll boundary. Owner: layout.
Sicherheitsaudit
SicherAll seven static findings are false positives caused by ordinary prose, Markdown tables, and inline code formatting. No external command execution, system reconnaissance, prompt injection, or other malicious intent was found.
Risikofaktoren
⚙️ Externe Befehle (5)
Diesen Bericht teilen & zitieren
Teile den versionierten Bewertungsbericht, das neutrale Badge, die Einbettungskarte und Zitate. Skillstore berichtet Nachweise, ohne zu entscheiden, ob dieser Skill sicher ist.
Berichtslink kopieren
https://skillstore.io/skills/jakubkrehel-break/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown-Badge
[](https://skillstore.io/skills/jakubkrehel-break?utm_source=security_passport_badge)HTML-Badge
<a href="https://skillstore.io/skills/jakubkrehel-break?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/jakubkrehel-break/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Einbettungskarte
<iframe src="https://skillstore.io/embed/skills/jakubkrehel-break.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Wissenschaftliche Zitate (APA · BibTeX · CFF)
APA-Zitat
jakubkrehel. (2026). break security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/jakubkrehel-break/audits/1BibTeX-Zitat
@techreport{jakubkrehel-jakubkrehel-break-2026,
author = {jakubkrehel},
title = {break security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/jakubkrehel-break/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 security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "jakubkrehel"
date-released: "2026-09-04"
url: "https://skillstore.io/skills/jakubkrehel-break/audits/1"
identifiers:
- type: other
value: "skillstore:jakubkrehel-break:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore-Score
Warum dieser Score Evidenzvertrauen: MittelWas Sie erstellen können
Validate a New Component
Render a new component with realistic text, quantity, width, and state variations before review.
Review Design System Resilience
Check a shared component against narrow containers, long content, RTL text, and supported modes.
Reproduce a UI Failure
Isolate a reported component issue on a temporary page and compare related edge cases.
Diese Prompts ausprobieren
Stress-test the [component name] component. Build a temporary harness with relevant scenarios and report only visible failures.
Test [component name] with empty, typical, long, unbreakable, RTL, and mixed-direction content where its props support these cases.
Render [component name] across supported loading, error, and disabled states within narrow, constrained, full-width, and wide containers.
Inspect [component path], derive applicable scenario axes from its API, explain excluded axes, build the harness, and classify observed failures by owner.
Bewährte Praktiken
- Choose one component and state its input, output, and intended location before building the harness.
- Include only scenario axes supported by the component API, and explain why other axes were excluded.
- Use the real component, application styles, fixture data, and fixed containers without adding custom presentation.
Vermeiden
- Do not test every scenario axis when the component cannot receive that variation.
- Do not report predicted failures that were not visible on the rendered page.
- Do not connect the harness to production state, live data, or production imports.
Häufig gestellte Fragen
What does this skill test?
Does it test complete pages?
Will it change my component?
Does it use production data?
Will it fix detected problems?
When is the temporary page removed?
Entwicklerdetails
Autor
jakubkrehelLizenz
MIT
Skillstore-Revision
r1
Versionshinweis
Der Autor hat keine Version angegeben.
Repository
https://github.com/jakubkrehel/skills/tree/267330e1adfc66a718fb65fa6918c1f06d0a689e/skills/breakRef.
096c7daa4d0d974771dad12d81c3d0d4688617b9
Aktualität der Wartung
8.9.2026
Nutzung
0 Downloads · 0 Aufrufe
Dateistruktur