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.
Установить с помощью моего Агента
Скопируйте этот запрос в своего Агента. Он содержит каноническую страницу Skill и манифест.
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.Ваш Агент по-прежнему должен показать план и запросить все подтверждения, требуемые политикой безопасности.
Ресурсы для AI-агентов
Используйте эти ссылки, когда AI-агенту, crawler или script нужен чистый контекст вместо полной страницы.
Протестировать
Использование «break». Stress-test the product card component.
Ожидаемый результат:
- 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». Test the status badge across relevant scenarios.
Ожидаемый результат:
Everything survived. The report page includes empty, typical, long, RTL, narrow-container, and disabled scenarios.
Использование «break». Check the results list with realistic quantities and states.
Ожидаемый результат:
- 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.
Аудит безопасности
БезопасноAll 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.
Факторы риска
⚙️ Внешние команды (5)
Поделиться и цитировать этот отчет
Делитесь версионным отчетом об оценке, нейтральным значком, встраиваемой карточкой и цитатами. Skillstore публикует доказательства, не решая, безопасен ли этот Skill.
Копировать ссылку на отчёт
https://skillstore.io/skills/jakubkrehel-break/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportЗначок Markdown
[](https://skillstore.io/skills/jakubkrehel-break?utm_source=security_passport_badge)Значок HTML
<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>Встраиваемая карточка
<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>Академические ссылки (APA · BibTeX · CFF)
Цитата APA
jakubkrehel. (2026). break security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/jakubkrehel-break/audits/1Цитата BibTeX
@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
Почему такая оценка Достоверность доказательств: СреднийЧто вы можете построить
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.
Попробуйте эти промпты
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.
Лучшие практики
- 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.
Избегать
- 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.
Часто задаваемые вопросы
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?
Сведения для разработчиков
Автор
jakubkrehelЛицензия
MIT
Ревизия Skillstore
r1
Примечание о версии
Автор не указал версию.
Репозиторий
https://github.com/jakubkrehel/skills/tree/267330e1adfc66a718fb65fa6918c1f06d0a689e/skills/breakСсылка
096c7daa4d0d974771dad12d81c3d0d4688617b9
Актуальность поддержки
08.09.2026
Использование
1 загрузок · 0 просмотров
Структура файлов