「app」の検索結果

Load this skill whenever the project has personalization features, user preference controls, theme selectors, font size adjusters, motion toggles, contrast settings, or any user-configurable accessibility accommodations. Under no circumstances override or ignore user OS-level accessibility preferences without explicit user consent. Absolutely always persist user preferences, apply them immediately, and respect prefers-reduced-motion, prefers-contrast, and similar media queries.

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

Load this skill when configuring axe-core scans, reviewing automated accessibility test results, or writing tests that use @axe-core/playwright, @axe-core/react, or similar integrations. Provides a quick reference to axe 4.x rule IDs, their WCAG mapping, and default severity levels.

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

Load this skill whenever the project contains dynamic content updates, status messages, alerts, notifications, loading indicators, or any use of aria-live, role="status", role="alert", or role="log". Under no circumstances add or modify live-region markup without applying these rules. Prioritize correct politeness levels and avoid redundant announcements. Never use a fixed-delay clear-and-reinsert workaround — no standard guarantees it works.

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

Load this skill whenever the project contains <img> elements, inline SVGs used as content images, CSS background images that convey meaning, or icon fonts. Under no circumstances omit alt text on meaningful images. Absolutely always provide a meaningful alt attribute or empty alt="" for decorative images. Apply WCAG 2.2 SC 1.1.1 — every non-text element requires a text alternative.

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

Load this skill for every project containing interactive UI elements — buttons, links, modals, dropdowns, sliders, tabs, carousels, or any custom widget. Under no circumstances create an interactive component that cannot be fully operated by keyboard alone. Absolutely always ensure visible focus indicators, logical tab order, and no keyboard traps. Apply these rules to every interactive element without exception.

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

Operational readiness checklist (security, cost, legal, data design, performance, incident response, LLM integration defenses) applied when a change touches deployment, infrastructure, external services, secrets, or user data.

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

Use when turning approved plans, specs, PRDs, or Epics into trackable GitHub Issues.

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

Use when auditing a repository for evidence-backed gaps between code, SPECs, architecture, and documentation — before a release, after a review, or when the user asks what is missing or divergent. Confirmed gaps become Draft SPECs via write-specs, a tracked GitHub Epic via create-issues, and orchestrated execution via orchestrator, with an explicit approval gate before any external action.

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

Use when the user asks to implement an approved SPEC SDD using test-driven development.

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

Use when the user asks to connect an AI agent to external apps via Composio, or when Composio CLI or MCP setup fails.

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

Use when planning the migration of a legacy system or monolith — analyzes the source codebase (current repo, or a repo URL cloned to a temp dir) and produces an evidence-based Strangler Fig migration plan with per-domain SPECs. Default target is .NET (Blazor WebAssembly, .NET MAUI, ASP.NET Core); other stacks allowed by user decision. Do NOT use to implement code or when approved SPECs already cover the migration.

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

Central entry point of the afonsoft agent harness. Use when starting a new project, resuming an existing one, planning features/Epics/releases, or running any multi-step agent-driven work. Validates and reconciles SPECs (SDD), audits the codebase and harness for gaps (security, architecture, performance, hygiene), proposes improvements, fragments work into GitHub Issues, delegates implementation/QA/review to specialized skills, and re-validates everything until delivery. Also use to review unapproved SPECs, reconcile open GitHub Issues with code, or run a final gap check before closing a release.

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

Use when the user asks for QA analysis, test planning, test cases, or root-cause analysis of a defect. Also use for post-merge PR review analysis: auditing recent closed PRs for Devin/GitHub/security bot comments, verifying whether requested corrections were applied, and turning pending fixes into SPECs.

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

Design UI as information architecture + interaction + visual tone, then translate into implementable specs. Apply when discussing screen design, component design, design systems, or visual hierarchy.

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

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.

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

Evaluate UI/flows from cognitive load, error prevention, and accessibility perspectives. Apply when reviewing UX, discussing user confusion, high drop-off, or form usability issues.

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

Translate designs and UI requirements into robust, extensible implementations. Apply when converting designs to code, implementing components, fixing broken UI, or handling responsive layouts.

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

Use the Crabbox wrapper for OpenClaw remote validation across Linux, macOS, Windows, and WSL2, including delegated Blacksmith Testbox proof. Report the actual provider and id.

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

Chooses ecosystem-native release and changelog tooling (Changesets, Melos, release-plz) plus binary distribution (GitHub Release tarballs, install.sh) when the product is an executable. Use for release CI, install.sh, versioning, CHANGELOGs, shipping MCP/CLI without clone, or meta repos that only ship skills via npx skills—not domain app tutorials.

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

Use when integrating an app with local AI models through Ollama — connection checks, model listing/selection, local-only mode, cloud-fallback consent, visible run states, and recovering from Ollama errors.

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

Use when creating a new project folder, starter pack, app scaffold, or agent-ready workspace — AGENTS.md, README, TASKS, DECISIONS, PROMPTS, an idempotent bootstrap script, and starter-pack modes.

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

Use when a macOS app needs a TCC permission or touches private data — the map of which API, Info.plist key, and entitlement each permission needs, pre-prompt explanation patterns, denied-state recovery with System Settings deep links, and honest privacy copy.

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

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 designing a user-initiated macOS emergency switch that helps the user save context before stopping, switching tasks, or leaving the computer — capture must be transparent, local-first, and easy to delete.

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