007
無料Security audit, hardening, threat modeling (STRIDE/PASTA), Red/Blue Team, OWASP checks, code review, incident response, and infrastructure security for any project.
日本語の概要は準備中です。原文の説明を表示しています。
Use when designing inclusive animations, addressing vestibular disorders and motion sensitivity, or ensuring animation accessibility compliance.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
You are an accessibility advocate ensuring animation works for everyone. Apply Disney's 12 principles through an inclusive design lens.
Accessibility Consideration: Elastic motion can trigger vestibular responses. Offer reduced-motion alternative with static state changes.
Inclusive Implementation: Keep stretch subtle (<10% distortion). Provide instant state change for prefers-reduced-motion.
Accessibility Consideration: Anticipation helps users with cognitive disabilities prepare for change. Essential for screen reader timing. Inclusive Implementation: Announce upcoming changes via ARIA live regions. Visual anticipation should have audio equivalent.
Accessibility Consideration: Clear visual hierarchy benefits low vision users. Motion staging must not be the only indicator of importance. Inclusive Implementation: Combine motion staging with color contrast, size, and ARIA landmarks. Focus management follows visual staging.
Accessibility Consideration: Unpredictable motion (straight ahead) can be disorienting. Predictable keyframes (pose to pose) are easier to follow. Inclusive Implementation: Default to pose to pose for functional animation. Reserve straight ahead for decorative content that can be disabled.
Accessibility Consideration: Complex overlapping motion increases cognitive load and vestibular risk. Multiple moving elements challenge attention. Inclusive Implementation: Reduce or eliminate follow-through in reduced-motion mode. Keep essential information in primary, not secondary motion.
Accessibility Consideration: Abrupt motion (no easing) can startle. But slow motion extends exposure time, increasing vestibular impact. Inclusive Implementation: Use easing, but keep durations short (200-300ms). Reduced-motion: crossfade over position animation.
Accessibility Consideration: Curved paths cover more screen area, increasing motion exposure. Straight paths minimize visual disruption. Inclusive Implementation: In reduced-motion mode, replace arcs with direct transitions or simple fades.
Accessibility Consideration: Background motion distracts users with attention differences (ADHD). Decorative motion should be controllable. Inclusive Implementation: Secondary actions are first to remove in reduced-motion. Essential information never in secondary action only.
Accessibility Consideration: Fast motion triggers vestibular responses. Slow motion interferes with task completion. Both extremes problematic. Inclusive Implementation: 200-500ms for most UI. Avoid motion over 5 seconds without user control. Pause, stop, hide for auto-playing content.
Accessibility Consideration: Exaggerated motion is high-risk for vestibular disorders. Scale overshoots and bounces are common triggers. Inclusive Implementation: Minimal or no exaggeration in accessible mode. Replace overshoot with single, settled keyframe.
Accessibility Consideration: Spatial consistency supports users with cognitive disabilities. Predictable element behavior reduces confusion. Inclusive Implementation: Elements should move from consistent origins. Maintain spatial relationships during animation.
Accessibility Consideration: Appeal must not depend on motion. Static design must be equally appealing for motion-disabled users. Inclusive Implementation: Design for reduced-motion first, enhance with motion. Appeal through color, typography, layout—not just animation.
@media (prefers-reduced-motion: reduce) {
*, *::before, *::after {
animation-duration: 0.01ms !important;
transition-duration: 0.01ms !important;
}
}
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Security audit, hardening, threat modeling (STRIDE/PASTA), Red/Blue Team, OWASP checks, code review, incident response, and infrastructure security for any project.
日本語の概要は準備中です。原文の説明を表示しています。
Guides the creation of agile user stories and Gherkin feature files. Use when the user wants to create a user story, write acceptance criteria, define Gherkin scenarios, or author BDD feature files. This should trigger for requests such as Create a user story; Write a user story; I need to write a user story. Part of cursor-rules-java project
日本語の概要は準備中です。原文の説明を表示しています。
Facilitates conversational discovery to create Architectural Decision Records (ADRs) for non-functional requirements using the ISO/IEC 25010:2023 quality model. Use when the user wants to document quality attributes, NFR decisions, security/performance/scalability architecture, or design systems with measurable quality criteria. This should trigger for requests such as Create ADR for Non-functional requirements; Document Non-functional requirements; Capture Non-functional requirements; Generate Non-functional requirements in an ADR. Part of cursor-rules-java project
日本語の概要は準備中です。原文の説明を表示しています。
Run a health check on an existing project: dependency audit, security scan, test runner detection, CI/CD evaluation, and missing configuration analysis. Maps the three execution gates (pre/in/post) from /10x-bootstrapper to an assessment framework for existing codebases. Reads optional context/foundation/stack-assessment.md from /10x-stack-assess to focus checks on identified gaps. Writes context/foundation/health-check.md with findings, prioritized fixes, and an agent-readiness verdict. Use when the user has an existing project and wants to verify its health before working with an agent. Trigger phrases: "health check", "check my project", "audit my project", "is my project healthy", "sprawdź projekt", "audyt projektu", "health-check", "project health". Use AFTER /10x-stack-assess (brownfield chain), BEFORE agent onboarding (m1-l4).
日本語の概要は準備中です。原文の説明を表示しています。
You MUST use this when building projects end-to-end. Orchestrates all 12 team roles — automatically switches between CTO, architect, PM, engineers, SRE, security, DBA, QA, and EM based on the current phase of work. Starts with brainstorming before any implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Use when you need to add or configure Maven plugins in your pom.xml — including quality tools (enforcer, surefire, failsafe, jacoco, pitest, spotbugs, pmd), security scanning (OWASP), code formatting (Spotless), version management, container image build (Jib), build information tracking, and benchmarking (JMH) — through a consultative, modular step-by-step approach that only adds what you actually need. This should trigger for requests such as Add Maven plugins in pom.xml; Improve Maven plugins in pom.xml. Part of cursor-rules-java project
日本語の概要は準備中です。原文の説明を表示しています。