metidos

Guided wizard workflow for installing Metidos in Docker or Podman, configuring runtime access through a reverse proxy or Tailscale, importing Codex, selecting core plugins, creating model-provider plugins, wiring env secrets, and enabling Telegram/Gmail integrations.

Use for accessibility implementation, audits, remediation, validation, WCAG-oriented reviews, keyboard and screen-reader support, inclusive UI decisions, or when the user mentions a11y.

Follow the canonical Metidos repository commit workflow, including atomic commits, validation policy, documentation sync, and detailed commit messages. Use when committing changes, preparing a commit, validating a change before commit, or updating repository workflow guidance.

Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.

Use when running or reviewing accessibility tests, validating WCAG conformance, checking keyboard/screen-reader/mobile usability, or verifying that fixes work in practice.

Use when documenting accessibility issues, writing remediation guidance, prioritizing fixes, or translating audit findings into actionable engineering/design work.

Use when evaluating or improving screen reader support, checking announcements, landmarks, labels, reading order, or dynamic updates for blind and low-vision users.

Use when designing or reviewing touch interactions, gesture-based controls, swipe patterns, or alternatives for users who cannot perform complex gestures.

Use when checking compatibility with mobile screen readers, switch access, voice control, magnification, or platform accessibility features on iOS and Android.

Use when designing or reviewing form entry on mobile, including keyboards, autofill, error recovery, input modes, and data entry for users with motor, cognitive, or visual impairments.

Use when adapting experiences for small screens, responsive layouts, orientation changes, zoom, and varying input contexts without losing accessibility.

Use when designing or reviewing motion, haptic cues, transitions, or feedback patterns on mobile, especially for users with vestibular, sensory, or cognitive sensitivities.

Use when optimizing mobile experiences for screen reader users on small screens, including navigation density, swipe burden, labels, and content chunking.

Use when reviewing tap target size, spacing, control density, or accidental activation risk on mobile and touch interfaces.

Use when tailoring interfaces to diverse cognitive needs, allowing users to adjust complexity, pacing, layout, reminders, or sensory load without penalty.

Use when evaluating cognitive burden in interfaces, identifying overload risks, and improving usability for users with ADHD, dyslexia, low literacy, memory impairments, or general overwhelm.

Use when adding instructions, tips, examples, or just-in-time help that supports users without interrupting flow or increasing cognitive burden.

Use when designing workflows, forms, or interactions that reduce mistakes and make recovery easier for users with cognitive disabilities, stress, or inattention.

Use when reviewing distractions, interruptions, competing calls to action, or interfaces that demand sustained attention from users with ADHD, brain injury, or cognitive fatigue.

Use when reducing recall demands in navigation, onboarding, forms, or multi-step tasks for users with memory impairments, dyslexia, cognitive fatigue, or stress.

Use when simplifying wording, instructions, labels, or system messages so users with low literacy, dyslexia, cognitive disabilities, or limited language proficiency can understand them.

Use when improving orientation, navigation, and task flow so users with cognitive disabilities, low digital confidence, or stress can understand where they are and what to do next.

Use when reviewing contrast, color reliance, readability, visual hierarchy, or low-vision usability in interfaces and content.

Use when considering a wide range of disability, age, language, literacy, situational, and environmental needs in product decisions or design reviews.

Use when analyzing experiences from the perspective of disabled users, mapping likely pain points, barriers, emotions, and tradeoffs in real-world journeys.

Use when reviewing forms, data entry, validation, and input workflows for accessibility, clarity, and error resilience across diverse users.

Use when reviewing copy for clarity, inclusivity, accessibility, cultural sensitivity, and respect across diverse audiences.

Use when designing or reviewing confirmations, alerts, errors, and status changes so important information is conveyed through more than one sensory channel.

Use when designing for real-world constraints such as glare, noise, low bandwidth, interruptions, stress, fatigue, one-handed use, or temporary impairments.

Use when planning or reviewing user research, usability testing, recruitment, or validation to ensure disabled users and diverse contexts are meaningfully included.

Use when reviewing captions, transcripts, audio descriptions, media controls, or the overall accessibility of audio and video content.

Use when designing or reviewing experiences for deaf and hard-of-hearing users, including alternatives to audio cues, media accessibility, and communication clarity.

Use when designing alerts, confirmations, warnings, or feedback that should be perceivable through multiple sensory channels.

Use when reviewing flashing, flickering, strobing, or high-intensity visual effects that may trigger seizures, migraines, or sensory distress.

Use when reviewing environments, interfaces, or workflows for users with sensory sensitivities, autism, ADHD, migraines, or overwhelm related to noise, motion, clutter, or intensity.

Use when reviewing vibration, haptic feedback, tactile signaling, or mobile/device interactions that depend on touch-based sensory cues.

Use when reviewing designs for low vision, color vision deficiencies, zoom support, readability, visual hierarchy, and non-visual alternatives.

Use when organizing content, page structure, or information architecture so users can understand relationships, scan effectively, and navigate with assistive technologies.

Use when designing or reviewing tables, grids, sortable data displays, or complex tabular information for accessibility and comprehension.

Use when reviewing live updates, async content, state changes, modals, expanding regions, or JavaScript-driven interfaces for accessibility.