Results for “focus”

Implements keyboard, directional, and scene-level focus behavior across SwiftUI and UIKit. Use when managing @FocusState, defaultFocus, focused values, focusable interactions, focus sections, tvOS geometric focus and Siri Remote navigation, watchOS Digital Crown input, visionOS connected-device focus versus gaze hover/input targets, macOS key view loop and Full Keyboard Access, focus restoration after presentation changes, custom focus routing with UIFocusGuide, or debugging focus with UIFocusDebugger.

The English summary is being prepared. Showing the original description.

Review where keyboard focus, the current target for keyboard input, moves when dialogs open, views change, or content updates. Identify misplaced or lost focus and propose changes that help keyboard and screen reader users continue navigating.

• Checking focus when dialogs open and close
• Reviewing focus after SPA navigation
• Keeping keyboard navigation usable during content updates

Review CSS focus indicators, the visible outlines that show which element receives keyboard input. Identify missing, clipped, or misplaced indicators, check contrast and responsive states, and guide changes that make keyboard navigation easier to follow.

• Check keyboard focus visibility
• Review CSS that removes outlines
• Fix clipped or misplaced focus rings

Review forms for autofocus that moves users past introductory content when a page loads. Suggest removing it or moving focus after user interaction, while considering exceptions for login pages and pages dedicated to search.

• Reviewing forms with introductory content
• Investigating unexpected scrolling on page load
• Moving focus after a user action

Inspect hidden page regions for links, buttons, or inputs that still receive keyboard focus. Identify elements that screen readers cannot announce, suggest focus handling changes, and explain how to verify the resulting keyboard behavior.

• Checking hidden regions for focusable controls
• Investigating silent focus during keyboard navigation
• Reviewing accessibility in shared UI components

Create a browser board for daily tasks and numeric goals, then track progress alongside conversations with an AI partner. Includes focus mode, gentle task carryover, progress notes, and a recap you can save at the end of the day.

• Plan a manageable set of tasks for today
• Track reading pages or completed work sessions
• Focus on one task when getting started feels difficult

Guide changes to cmux CLI and socket commands with rules for thread use, app focus, and remote relay authorization. It helps keep frequent status updates off the main thread and preserve focus during background automation.

• Review thread handling for new socket commands
• Keep automated operations from stealing app focus
• Check focus behavior when opening panes or workspaces

Review keyboard focus, the element currently selected for interaction, to check that Tab navigation follows the page’s visual order. Identify HTML ordering issues and verify focus stays within dialogs and returns to their triggers.

• Auditing a page’s Tab navigation order
• Checking focus when dialogs open and close
• Reviewing HTML order and tabindex values

Apply Remotion Studio’s interaction conventions to buttons and links: keep the default cursor, brighten text and icons on hover, and show a visible focus indicator for keyboard navigation using shared styling helpers.

• Style a new Studio button or link
• Keep text and icons consistent on hover
• Retain visible focus for keyboard navigation

Build and review React and Next.js interfaces for keyboard use and screen readers, tools that read content aloud. Apply practical patterns for form labels, error messages, accessible controls, and focus movement.

• Making form labels and errors accessible
• Reviewing keyboard controls for dropdowns
• Managing focus when modals open and close

Create recurring blocks for focused work in Google Calendar, with selected weekdays and times. Mark those hours as busy and check the agenda to confirm the blocks appear as intended.

• Reserve weekday mornings for focused work
• Set up recurring deep work sessions
• Check that focus blocks appear as busy

ADHD-friendly output formatting. Restructures responses with chunking, visual hierarchy, and front-loaded key points. Modes: clean, flow (default), zen. Use when user says "hyperfocus", "focus mode", "adhd mode", "adhd friendly", or invokes /hyperfocus.

The English summary is being prepared. Showing the original description.

This skill should be used when the user asks for body doubling, ADHD focus sessions, accountability while working, help getting started on a task, pomodoro-style work sessions, or says things like 'I can't focus', 'I'm stuck', 'help me start', 'I need accountability', 'body double with me', 'I keep procrastinating', 'I can't get started', or 'focus session'. Provides punk-style ADHD body doubling with micro-step protocols, frequent check-ins, dopamine resets, and session history tracking. Part of the ADHD-founder.com ecosystem.

The English summary is being prepared. Showing the original description.

Review whether interactive web elements work with keyboard navigation. Check Tab order, hidden elements, and focus traps where users cannot move away, then identify specific fixes and ways to verify behavior with browser accessibility tools or assistive technology.

• Check whether all controls are reachable with Tab
• Align keyboard focus order with the visual reading order
• Remove hidden content from the Tab sequence

Review modal dialogs for keyboard and screen reader accessibility. The skill checks dialog roles, title labels, focus movement within the modal, Escape dismissal, and focus returning to the opening control, then identifies issues and ways to verify fixes.

• Reviewing keyboard operation in modal dialogs
• Checking focus movement when opening and closing modals
• Reviewing dialog titles and screen reader labels

Review medium to large code changes using checks selected for the actual patch. Analyze the change and surrounding code, assign focused reviews by function, file, or feature, and combine findings with locations, confidence levels, and supporting evidence.

• Reviewing patches of roughly 50 to 1,000 lines
• Checking risks specific to a changed feature
• Reviewing changes alongside callers and related implementations

Review selected files for bugs by reading full source code, callers, and related implementations. Apply detailed checklists and investigate suspected issues, then report evidence, confidence levels, and suggested fixes.

• Review selected files in a critical code change
• Investigate concerns raised by an initial review
• Check complex state transitions and object lifecycles

Design OpenRig watchdog policies for stalled or drifting agent work. Choose a small wake-up message, a refocus, or a broader alignment check, and separate monitoring frequency from notification frequency using evidence about owners and artifacts.

• Choosing an intervention for an inactive task owner
• Drafting messages that correct workflow drift
• Separating monitoring and notification intervals

Audit whether a "current product focus receipt" (Decision/Now/Why-now/Evidence/Not-now/Cut-suspend/First-visible-proof/ Acceptance-gate/Kill-revisit-trigger/Owner/Review-date) and the work order it gates state a real, testable decision and a real agent launch — not planning-placeholder prose that sounds like an assignment but can't be proven. Use when deciding whether to launch an agent chain against a milestone or a stated "focus," when a work order lacks explicit input/output/owner/proof-gate, or when an acceptance gate would only prove a cached UI state instead of daemon truth. NOT for distinguishing roadmap items from energy-driven sidequests (legible-roadmap-with-sidequests), reviewing a PRD/prototype for product-completeness gaps like cold start or pricing (product-reality-reviewer), or accepting already-finished work against a personal acceptance bar (port-daddy-user-surrogate-pm-review).

The English summary is being prepared. Showing the original description.

Connect Hermes to NeuroSkill to review live focus, mood, and drowsiness indicators from a brain-sensing wearable. Compare recorded sessions, explore sleep data, label notable moments, and receive suggestions for breaks or exercises for research use.

• Checking current focus and relaxation indicators
• Comparing focus across recorded sessions
• Reviewing recorded sleep stages

Review pop-ups, modals, and banners that obscure page content. Identify mobile usability and search visibility concerns, then improve dismissal controls and keyboard focus, the element currently receiving keyboard input.

• Review promotional pop-ups on mobile
• Check keyboard dismissal of modals
• Verify focus movement when dialogs open and close

Check whether sticky headers, banners, or chat widgets hide controls reached with the keyboard. Review tab order, zoomed views, and mobile layouts, then suggest spacing or scrolling changes that keep the focused control and its indicator visible.

• Checking keyboard navigation around sticky headers
• Testing pages with cookie banners and chat widgets open
• Reviewing overlap in zoomed and mobile layouts

Review links, buttons, and form fields for duplicate HTML IDs. Identify affected controls, suggest unique IDs, and explain how to verify keyboard navigation, focus movement, and screen reader behavior after the fix.

• Checking HTML IDs in forms
• Investigating unexpected keyboard focus
• Reviewing shared interactive components

Check text, input borders, meaningful icons, and other interface elements for sufficient color contrast. Guide color adjustments against WCAG accessibility thresholds and verify readability across default, hover, focus, active, and visited states.

• Checking text against background colors
• Reviewing input borders and meaningful icons
• Checking contrast during hover and keyboard focus