「access」の検索結果

Load this skill whenever the project contains static or interactive maps, embedded map widgets (Google Maps, Leaflet, Mapbox, OpenStreetMap), or any geographic visualizations. Under no circumstances embed a map without a text-based alternative conveying the same information. Absolutely always ensure map controls are keyboard-accessible and that all meaningful map content is available without the visual map.

日本語の概要は準備中です。原文の説明を表示しています。

Generates Angular code and provides architectural guidance. Trigger when creating projects, components, or services, or for best practices on reactivity (signals, linkedSignal, resource), forms, dependency injection, routing, SSR, accessibility (ARIA), animations, styling (component styles, Tailwind CSS), testing, or CLI tooling.

日本語の概要は準備中です。原文の説明を表示しています。

Apply the Opquast Digital Quality Framework (245 rules, 14 categories) when building, reviewing, or auditing websites and web applications. Use for web development quality assurance, accessibility compliance, security hardening, privacy implementation, e-commerce best practices, and holistic digital quality checks.

日本語の概要は準備中です。原文の説明を表示しています。

[Testing] Use when you need full-site QA audit (accessibility, performance, security, SEO) with visual reports.

日本語の概要は準備中です。原文の説明を表示しています。

[Code Quality] Use when reviewing UI code for accessibility, responsiveness, performance, and UX best practices.

日本語の概要は準備中です。原文の説明を表示しています。

Use when auditing UI code for interface-guideline compliance (accessibility, forms, animation, images, performance, UX copy) and/or validating a deployed page against Lighthouse 95+ targets. Produces evidence-based findings (file:line + Lighthouse JSON) and turns confirmed pendencies into Draft SPECs via write-specs. Do NOT use to design/build UI from scratch (use design) or to fix findings inline — fixes go through the SPEC pipeline.

日本語の概要は準備中です。原文の説明を表示しています。

Translate motion, interaction, and visual experience into implementable constraints while preserving accessibility and performance. Apply when working on animations, transitions, scroll effects, or micro-UX.

日本語の概要は準備中です。原文の説明を表示しています。

Use when reviewing or designing a color palette for a UI, website, or app — seven principles for premium, calm, accessible color (palette size, muted tones, contrast, accent restraint, near-black/white, consistency, whitespace).

日本語の概要は準備中です。原文の説明を表示しています。

Use when choosing, reviewing, or implementing SF Symbols in an Apple-platform app — picking meaningful symbols, keeping the same concept on the same symbol everywhere, and handling variants, rendering modes, and accessibility.

日本語の概要は準備中です。原文の説明を表示しています。

Use when designing, reviewing, or implementing typography in Apple-platform apps — SwiftUI text styles, hierarchy, readable sizes, monospaced data, custom fonts, labels, captions, and accessibility.

日本語の概要は準備中です。原文の説明を表示しています。

Search PubMed biomedical literature with natural language queries powered by Valyu semantic search. Full-text access, integrate into your AI projects.

日本語の概要は準備中です。原文の説明を表示しています。

Extract clean markdown, text, or targeted chunks from one or more known, publicly accessible webpage URLs via the Tavily CLI. Use when the URLs are already supplied or discovered and the user wants page content rather than more URLs. Do not use to find an unknown page (tavily-search), list a site's URL structure (tavily-map), bulk-extract a site section (tavily-crawl), or retrieve named platform, authenticated, cookie-dependent, or platform-native content (Agent Reach). Can process up to 20 public URLs per request.

日本語の概要は準備中です。原文の説明を表示しています。

Route ordinary public-web information tasks to the correct Tavily CLI operation. Use when the task concerns publicly accessible webpages and needs web discovery, clean extraction, URL mapping, same-site crawling, or public-web-only research, but the exact Tavily operation is not yet clear or several operations must be sequenced. Prefer the specific leaf skill when intent is clear: tavily-search for discovery without a URL, tavily-extract for known URLs, tavily-map for URL/site-structure discovery, tavily-crawl for content from many pages on one site, tavily-research for cited multi-source synthesis, and tavily-dynamic-search for programmatic filtering with context isolation. Do not use for named social/community/media/career/code platforms, login or cookie-dependent content, platform-native discussions, or cross-platform collection; use Agent Reach there. Do not use for local files, Git operations, deployments, or ordinary code editing.

日本語の概要は準備中です。原文の説明を表示しています。

给定 PMID / PMCID 取结构化全文（BioC XML/JSON）。封装 NLM BioC PubMed API（标题+摘要）和 BioC PMC OA API（开放获取全文），输出按章节切分的段落、表格上下文、RAG 友好 chunk。适合大批量入向量库。触发词：全文抽取 / BioC / RAG 入库 / 文献全文 / PMC 开放获取 / structured fulltext / 段落抽取 / 表格抽取 / fulltext to vector store。

日本語の概要は準備中です。原文の説明を表示しています。

EMR/EHR development patterns for healthcare applications. Clinical safety, encounter workflows, prescription generation, clinical decision support integration, and accessibility-first UI for medical data entry. Use when building EMR or EHR features such as encounter workflows, prescription generation, or clinical data entry UI.

日本語の概要は準備中です。原文の説明を表示しています。

给定 PMID/PMCID 取结构化全文（NLM BioC XML/JSON）。封装 BioC PubMed（标题+摘要）和 BioC PMC OA（开放获取全文）端点，输出按章节切分的段落、表格上下文、RAG 友好 chunk，适合大批量入向量库。Fetches structured fulltext from NLM BioC API for PMID/PMCID, outputs section-segmented paragraphs and RAG-ready chunks. 触发词：全文抽取 / BioC / RAG 入库 / 文献全文 / PMC 开放获取 / structured fulltext / 段落抽取 / 表格抽取 / chunking / fulltext to vector store / paragraph extraction.

日本語の概要は準備中です。原文の説明を表示しています。

Create aesthetically beautiful interfaces following proven design principles. Use when building UI/UX, analyzing designs from inspiration sites, generating design images with ai-multimodal, implementing visual hierarchy and color theory, adding micro-interactions, or creating design documentation. Includes workflows for capturing and analyzing inspiration screenshots with chrome-devtools and ai-multimodal, iterative design image generation until aesthetic standards are met, and comprehensive design system guidance covering BEAUTIFUL (aesthetic principles), RIGHT (functionality/accessibility), SATISFYING (micro-interactions), and PEAK (storytelling) stages. Integrates with chrome-devtools, ai-multimodal, media-processing, ui-styling, and web-frameworks skills.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.

日本語の概要は準備中です。原文の説明を表示しています。

UI/UX design intelligence for web, mobile, and desktop. This skill should be used when designing, building, reviewing, or fixing interfaces, including pages, components, design systems, accessibility, interaction, responsive layout, typography, color, charts, and stack-specific UI implementation. Searchable local data: 79 searchable styles (50 active), 192 product palettes and reasoning profiles, 74 font pairings, 119 UX guidelines, 105 icons, 17 GSAP presets, 25 chart types, and 22 stacks.

日本語の概要は準備中です。原文の説明を表示しています。

Run frontend functional, accessibility, visual, and performance test planning with structured reports.

日本語の概要は準備中です。原文の説明を表示しています。

Technical SEO audit with GEO-specific checks — crawlability, indexability, security, performance, SSR, and AI crawler access

日本語の概要は準備中です。原文の説明を表示しています。

Pressure-test startup ideas against real user pain, current behavior, competitors, first-customer access, MVP scope, founder-market fit, and a two-week launch test. Produces a direct strong, weak, or pivot verdict.

日本語の概要は準備中です。原文の説明を表示しています。

GStack design-review method for reviewing rendered UI, landing pages, decks, or visual artifacts for hierarchy, layout, accessibility, and polish.

日本語の概要は準備中です。原文の説明を表示しています。

GStack design plan review for user journey, layout, interaction model, responsive behavior, accessibility, and visual risk before UI work starts.

日本語の概要は準備中です。原文の説明を表示しています。