「format」の検索結果

当用户犹豫是否分享敏感信息、询问领导者应该多透明、公司存在信息孤岛、或即将进行组织变革时触发。基于Netflix开卷管理哲学：默认公开一切。

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

Compress natural language memory files (CLAUDE.md, todos, preferences) into caveman format to save input tokens. Preserves all technical substance, code, URLs, and structure. Compressed version overwrites the original file. Human-readable backup saved as FILE.original.md. Trigger: /caveman:compress <filepath> or "compress memory file"

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

Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes /caveman-commit. Auto-triggers when staging changes.

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

Compress natural language memory files (CLAUDE.md, todos, preferences) into caveman format to save input tokens. Preserves all technical substance, code, URLs, and structure. Compressed version overwrites the original file. Human-readable backup saved as FILE.original.md. Trigger: /caveman:compress <filepath> or "compress memory file"

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

学术论文参考文献管理与格式核对。输入是参考文献列表（混乱格式）、BibTeX/RIS 文件、DOI 列表、或正文+引用混合时使用。功能包括：统一格式（format）、格式检查（check）、生成 BibTeX（bibtex）、格式互转（convert）、DOI 验证（verify）、正文引用位置核对（inline）。覆盖期刊/会议/学位/标准/数据集/预发表/网页 7 种文献类型，GB/T 7714 与 APA/IEEE/Nature 多种风格。不适用于：正文段落润色（用 academic-writing）、图表生成（用 academic-figure）。

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

Prices research, tests, surveys, dashboards and experiments before running them, by computing how much the result would raise expected utility - which is zero whenever no outcome would change the decision. Use when someone proposes an A/B test, user survey, market study, competitor analysis, analytics build, consultant, pilot, or "let's gather more data", and when deciding how large a study needs to be.

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

Pressure-test an existing plan or design artifact until it is coherent enough for the next workflow step or plainly blocked. Use when the user wants to be grilled on a plan, design doc, PRD, ADR, rollout plan, migration runbook, rolling-wave project shape, or slice contract; when they say "grill me"; or when Codex should interrogate a source-of-truth artifact, inspect code and adjacent docs before asking, auto-answer evidence-backed questions, ask only about conflicts or low-confidence recommendations, edit the original file in place, preserve the artifact's existing format, and keep conclusions, blockers, readiness, and deferred work synchronized in the document.

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

Guides AI agents through Senzing entity resolution workflows using the Senzing MCP server. Covers data mapping to Senzing format, SDK code generation (Python, Java, C#, Rust, TypeScript/Node.js), documentation search, error troubleshooting, sample data access, reporting and visualization, SDK setup guides, and V3-to-V4 migration. Use when working with entity resolution, record matching, record linkage, deduplication, Senzing SDK integration, data mapping for Senzing ingestion, or troubleshooting Senzing error codes. Also use when the user mentions matching records across data sources, finding duplicate entities, identity resolution, master data management, or needs to resolve who is who across datasets.

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

Draft a CHANGELOG.md entry for the current changes in Keep a Changelog format. Use when releasing, tagging a version, or updating CHANGELOG.md.

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

Draft the changelog entry for all unreleased commits in Keep a Changelog format. Groups commits into Added, Changed, Fixed, Removed, and Security. Use before releasing a new version or when updating CHANGELOG.md.

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

Error handling patterns for API endpoints. Use when implementing error handling, writing middleware, or reviewing how errors are caught and formatted in API code.

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

Summarizes uncommitted git changes in a concise machine-readable format. Use in CI pipelines, scripts, or headless invocations where the output will be piped or captured.

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

REST API design conventions for this codebase. Use when writing or reviewing API endpoints, route definitions, response formatting, or client code that calls the API.

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

Expert-level computer graphics covering the rendering pipeline, rasterization, ray tracing, shaders, transformations, lighting models, and GPU programming.

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

Expert-level astrophysics covering stellar physics, galaxy formation, high-energy astrophysics, observational techniques, and the electromagnetic spectrum across wavelengths.

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

Expert-level planetary science covering solar system formation, planetary interiors, atmospheres, surface processes, astrobiology, and planetary exploration missions.

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

Expert-level black hole physics covering formation, spacetime structure, accretion disks, jets, Hawking radiation, gravitational waves from mergers, and observational evidence.

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

Expert-level complex analysis knowledge. Use when working with complex functions, holomorphic functions, Cauchy's theorem, contour integration, Laurent series, residues, conformal mappings, or analytic continuation. Also use when the user mentions 'holomorphic', 'analytic', 'Cauchy theorem', 'residue', 'contour integral', 'Laurent series', 'conformal map', 'Riemann mapping', 'Mobius transformation', 'harmonic function', 'entire function', or 'meromorphic'.

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

Comprehensive quality control for U.S. patent application filing documents. Use when the user asks to QC, check, validate, or review patent filing documents before submission to the USPTO. Performs 70+ automated and manual checks across specification, drawings, ADS, declaration, assignment, and power of attorney documents. Detects cross-document inconsistencies, formatting issues, missing required fields, and common errors.

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

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

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

Review a written plan or design doc through a designer's lens before implementation - seven passes over information architecture, interaction states, emotional arc, AI-slop risk, design-system alignment, responsive and accessibility coverage, and unresolved decisions. Each dimension is rated 0-10 with an explicit statement of what would make it a 10, then the plan is edited to get there. Use when a plan has a UI surface and you want the design gaps closed before code is written. Not for auditing a live site.

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

Search the web and open-source code for library usage, API syntax, and documentation via Exa. Use this whenever verifying an API signature, looking up how a library is used, checking a config file format, or resolving an error from a third-party dependency -- including when you think you already know the answer, since library APIs drift. Also use for questions documentation cannot answer: release timing, breaking changes, "is X still maintained", licensing, security advisories, and ecosystem comparisons.

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

Diagnoses failing GitHub Actions runs by reading logs, identifying the root cause, and suggesting fixes. Use this skill whenever a user shares a GHA run URL, pastes runner log output, mentions a failing workflow, asks why a CI job is broken, or says anything like "my GHA is failing", "workflow failed", "can you check my run", or "CI is broken". Also trigger when raw log text is detected in the conversation that appears to come from a GitHub Actions runner. Do NOT use for general GHA workflow authoring questions, YAML formatting help, or passing runs with no failure context.

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

Frontend UI design, critique, audit, polish. 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.

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