skills/truncation-stress-checklist/SKILL.md
# name Truncation Stress Checklist ## description Evaluates overflow and truncation resilience for long localized strings. ## when to use - Before localization release. - After locale files are updated. ## inputs - Translated strings - UI breakpoints - Component width constraints ## strict output template ```md ## Truncation Stress Checklist - [ ] Primary CTAs render fully - severity if failed: `Blocker` - [ ] Form labels do not clip - severity if failed: `Major` - [ ] Navigation items do no
npx skillsauth add aramidefemi/cursor-sentinel skills/truncation-stress-checklistInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Truncation Stress Checklist
Evaluates overflow and truncation resilience for long localized strings.
## Truncation Stress Checklist
- [ ] Primary CTAs render fully - severity if failed: `Blocker`
- [ ] Form labels do not clip - severity if failed: `Major`
- [ ] Navigation items do not overflow - severity if failed: `Major`
- [ ] Error messages remain readable - severity if failed: `Major`
- [ ] Minor copy truncation documented - severity if failed: `Minor`
development
# name Visual Diff Report Format ## description Enforces a consistent severity-based visual diff reporting structure. ## when to use - Any screenshot vs implementation comparison. - QA gate before sign-off. ## inputs - Baseline screenshot - Current screenshot - Optional approved specs ## strict output template ```md ## Diff Report ### Severity Summary - Blocker: `<count>` - Major: `<count>` - Minor: `<count>` ### Findings - `<location>` - `<difference>` - severity: `<Blocker|Major|Minor>`
testing
# name System Defender Regression Scan ## description Assesses regression risk from dependencies, shared modules, and side effects. ## when to use - After a draft minimal plan exists. - Before any implementer agent runs. ## inputs - Proposed change path - Shared module map - Critical flows ## strict output template ```md ## Regression Scan ### Shared Modules At Risk - `<module>` - severity: `<Blocker|Major|Minor>` - reason: `<short>` ### Side Effects - `<effect>` - severity: `<Blocker|Major
testing
# name System Defender Minimal Change Path ## description Converts analysis into a minimal approved execution path. ## when to use - After reuse and regression scans. - Before calling implementers. ## inputs - Reuse report - Regression report - Test/gap report ## strict output template ```md ## Minimal Change Path ### Approved Reuse Path - `<path/module>` ### Ordered Steps 1. `<step>` 2. `<step>` ### Risk Notes - `<risk>` - severity: `<Blocker|Major|Minor>` ### Minor Items To Skip - `<ite
tools
# name System Defender Feature Checklist ## description Creates a reuse-first readiness checklist for a requested feature. ## when to use - Before any implementation planning. - When validating if existing modules can be extended. ## inputs - Feature request - Acceptance criteria - Known touched modules ## strict output template ```md ## Feature Checklist - [ ] Existing module candidate identified (`Blocker` if none) - [ ] Extension path defined - [ ] New abstraction necessity justified - [