「audit」の検索結果

Use when ranking competing initiatives for a roadmap, breaking a tie between two features, or auditing a backlog for hidden low-value work via Reach × Impact × Confidence ÷ Effort.

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

Single-pass tech-stack detection with an agents/evidence/analysis/ write-up; explicit request only. Deep multi-pass audit → universal-project-analysis. Raw primitives → project-analysis-core.

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

Use when locking the market frame — category, segment, alternative, point-of-view — before messaging, launch, or pricing rides on it. Triggers on 'who are we for', 'opposable audit'.

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

Use when designing customer onboarding — time-to-first-value, milestone design, friction audit, drop-off diagnosis. Triggers on 'fix onboarding', 'why do new accounts churn fast'.

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

Performance audit — bottleneck profiling, N+1 query detection, hot-path analysis; explicit request only, not part of regular feature work.

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

Use when decomposing a company objective into team OKRs, auditing a draft OKR tree, or stress-testing an existing one for measurability and laddering.

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

Use when designing or auditing a sales pipeline — stage exit criteria, per-cell conversion, coverage reasoning, leak detection. Triggers on 'tighten our pipeline', 'where is the leak'.

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

Use when a diff may introduce security risk — authZ, injection, secrets, unsafe deserialization, SSRF, XSS, mass assignment — dispatched by /review-changes, /do-and-judge, /judge.

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

Run the offline (jscpd) and online (scanoss-py) similarity scanners on demand against a diff or path — the ONLY home of this repo's detection capability; no CI gate exists or ever ran it automatically

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

When the user says "review the design", "check the UI", or wants a comprehensive UI/UX review. 7 phases: interaction, responsiveness, accessibility. Inventory via existing-ui-audit.

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

Use to audit a past architectural decision — did the chosen option hold up, what assumptions drifted, should the ADR be superseded? Backward review only; does not lock new choices.

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

Frontend design heuristics and the loop applying them: existing-ui-audit, brief, inventory, build, review. Use when building or changing any UI, not only when planning one.

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

Use when polishing a skill/rule/command/guideline frontmatter description — pushier phrasing, trigger coverage, undertrigger audit — even if the user just says 'make this pushier'.

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

Use when defining or auditing the activation event — aha-moment selection, retention correlation, falsifiable definition. Triggers on 'what is our aha moment', 'redefine activation'.

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

Use when reviewing UI for accessibility — WCAG 2.2 AA, keyboard nav, focus, ARIA, contrast, screen-reader semantics — even on 'is this a11y-OK?' or 'mach das barrierefrei'.

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

Use when the user shares a Sentry error, Jira bug ticket, or error description and wants root cause analysis. Also for proactive bug hunting and code audits for hidden bugs.

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

Especialista em event sourcing, CQRS e padrões de arquitetura orientada por eventos. Domina design de event store, construção de projeções, orquestração de sagas e padrões de consistência eventual. Use PROATIVAMENTE para sistemas baseados em event sourcing, requisitos de trilha de auditoria ou modelagem de domínio complexa com consultas temporais.

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

Analise código da interface para conformidade com as Diretrizes de Interface Web. Use quando solicitado para "revisar minha UI", "verificar acessibilidade", "auditar design", "revisar UX" ou "verificar meu site em relação às melhores práticas".

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

Aplique práticas modernas de desenvolvimento web para segurança, compatibilidade e qualidade de código. Use quando solicitado "aplicar best practices", "auditoria de segurança", "modernizar código", "análise de qualidade de código" ou "verificar vulnerabilidades".

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

Quando o usuário quer adicionar, corrigir ou otimizar schema markup e dados estruturados no seu site. Use também quando o usuário menciona "schema markup", "dados estruturados", "JSON-LD", "rich snippets", "schema.org", "FAQ schema", "product schema", "review schema" ou "breadcrumb schema". Para problemas de SEO mais amplos, consulte seo-audit.

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

Quando o usuário quiser configurar, melhorar ou auditar rastreamento e medição de análises. Também use quando o usuário mencionar "configurar rastreamento", "GA4", "Google Analytics", "rastreamento de conversão", "rastreamento de eventos", "parâmetros UTM", "tag manager", "GTM", "implementação de análises" ou "plano de rastreamento". Para medição de testes A/B, consulte ab-test-setup.

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

Audit and fix common accessibility issues in Angular templates and Angular Material components. Use when the user mentions Lighthouse, axe, screen readers, keyboard navigation, ARIA, asks to fix a11y issues in Angular HTML templates, or after any feature, bug fix, or refactor that changed Angular templates.

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

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.

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

Write minimal, accessible web UI without over-engineering, adapting to whatever stack the project uses — React, Vue, Svelte, Angular, web components, or plain HTML. Use this skill on every project and every task that writes or reviews markup or components, builds forms, adds interactive elements like buttons, dialogs, accordions, or tabs, or audits code for accessibility — even when the user never mentions accessibility, and even inside a framework, CMS, or design system. It's non-negotiable regardless of project type, stack, or deadline. About to reach for ARIA attributes, a dialog library, a focus-trap package, or a headless UI component? Use this skill first.

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