「consistency」の検索結果

Use when shaping brand voice — voice attributes, tone-by-context matrix, consistency review. Triggers on 'define our voice', 'why does our copy sound different on every surface'.

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

Generate an image from a brief — provider-agnostic blueprint then provider-specific translation, with ref-image/seed reuse for consistency. Use when generating/creating an image.

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

Use when a character must stay visually identical across AI video scenes — locks identity tokens (silhouette, palette, wardrobe, prop) in JSON. Triggers 'character lock', 'same character'.

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

[Code Quality] Use when reviewing architecture compliance for layers, messaging, service boundaries, CQRS, repos, entity events, and data/consistency/tenancy boundaries. Universal architecture laws, coupling taxonomy and the anti-pattern catalog live in `.claude/docs/architecture-knowledge.md` (project docs always outrank it).

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

[Architecture] Use when designing solution architecture across backend, frontend, data & consistency, integration & APIs, deployment, monitoring, testing, and code quality. Architecture laws, style-selection triggers, coupling taxonomy, trade-off tables and the anti-pattern catalog live in `.claude/docs/architecture-knowledge.md`.

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

[Code Quality] Use when you need to simplify and refine code for clarity, consistency, and maintainability while preserving all functionality.

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

Normalizes and improves the consistency of prospect-list data. Use when the user provides a messy prospect or lead export and wants standardized records, flagged issues, and a cleanup summary.

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

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).

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

对认知结构运行完整的C1-C10一致性验证，输出验证报告并修复发现的不一致。触发词：「一致性检查」「自洽检查」「验证认知结构」「检查有没有问题」「跑一遍验证」。批量操作完成后自动触发。

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

置信度校准（元认知监控）。追踪L1文档和L2碎片中「AI生成/推断」的内容是否事后得到了验证，定期向用户提问「这段内容当时是AI推断，现在有没有实际证据？」。触发词：「验证历史内容」「校准知识置信度」「哪些内容还没验证」「cognitive-calibrate」。也被 cognitive-consistency-check 内部调用（月度维护）。

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

Elite mobile app image-generation skill for creating premium, app-native screen concepts and flows. Designed for iOS, Android, and cross-platform mobile products. Prioritizes clean hierarchy, comfortably readable text, strong multi-screen consistency, controlled color palettes, non-generic creative direction, textured surfaces, image-led composition, tasteful custom iconography, and clean phone mockup framing. By default, screens should be shown inside a subtle premium iPhone or similar phone mockup with a visible frame, while the main focus stays on the app content itself. This skill generates images only. It does not write code.

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

Audits and realigns UI to match design system standards, spacing, tokens, and patterns. Use when the user mentions consistency, design drift, mismatched styles, tokens, or wants to bring a feature back in line with the system.

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

Performs a final quality pass fixing alignment, spacing, consistency, and micro-detail issues before shipping. Use when the user mentions polish, finishing touches, pre-launch review, something looks off, or wants to go from good to great.

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

Performs a final quality pass fixing alignment, spacing, consistency, and micro-detail issues before shipping. Use when the user mentions polish, finishing touches, pre-launch review, something looks off, or wants to go from good to great.

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

Audits and realigns UI to match design system standards, spacing, tokens, and patterns. Use when the user mentions consistency, design drift, mismatched styles, tokens, or wants to bring a feature back in line with the system.

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

Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credib...

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

Head-to-head comparison of coding agents (Claude Code, Aider, Codex, etc.) on custom tasks with pass rate, cost, time, and consistency metrics

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

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

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

Perform cross-artifact consistency analysis across spec.md, plan.md, and tasks.md. Use after task generation to identify gaps, duplications, and inconsistencies before implementation.

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

Review meeting minutes documents for completeness, action item clarity, decision documentation, and consistency with source materials like hearing sheets. Use when validating meeting minutes quality or preparing minutes for distribution.

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

Review audit-related documents (control design documents, bottleneck analyses, requirements definitions, etc.) for quality, scoring them 0-100 with a severity-rated findings list. Use when reviewing audit documents, checking control design quality, or verifying cross-document consistency. Supports documents governed by US GAAP, IFRS, or J-GAAP.

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

Knowledge base from the Expanded Guidance for NASA Systems Engineering (NASA/SP-2016-6105-SUPPL, Volume 1, March 2016) — the practitioner-depth supplement to the NASA SE Handbook. Use for the load-bearing mechanics the handbook compresses: the SE Engine's per-phase cadence and the iterative-vs-recursive distinction, the AS9100 crosswalk, life-cycle tailoring vs. customization and the Compliance Matrix, the recursive system-design consistency loop (ConOps vs. Operations Concept, requirement flow/type/ownership, successive refinement), product realization (verify/qualify/accept/certify cardinality, protoflight, 'test the way we fly' coverage, two-form transition), and the crosscutting technical-management procedures (six-step scheduling, cost-estimating method selection, JCL, interface document family, RIDM/CRM, CM baselines, EVM arithmetic, MOE/MOP/KPP/TPM, the three required leading indicators, and the decision-analysis method catalog). This is the DEPTH layer — it deliberately does NOT restate the base definitions; pair it with the nasa-se-handbook pack. Scope: NASA space-flight SE practice (Vol 1 Practices); thin on the Vol 2 process-appendix detail, on non-NASA/commercial life cycles, and on software-engineering methodology.

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

Runs twice in a PFD to P&ID job. Part 1, before gate G3, validates the discipline proposals for provenance, UNKNOWN handling, conflicts, prohibited content and cross-section consistency and returns results and blocking items. Part 2, before gate G5, assembles the review package, with job header, gate record, every register and proposal, consolidated UNKNOWN list, feedback log and closing statement. Use when the user asks to "validate the enrichment", "run validation before G3", "assemble the review package" or "build the G5 package". Do not use for the readiness map, use pid-tool-readiness-mapping instead; do not use to produce a missing discipline section, use the discipline skill that owns it. Drafts for human review; never approves, authorises or signs off.

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

Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Use when asked to "simplify code", "clean up code", "refactor for clarity", "improve readability", or review recently modified code for elegance. Focuses on project-specific best practices.

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