「ar」の検索結果

Brand voice, visual identity, messaging frameworks, asset management, brand consistency. Activate for branded content, tone of voice, marketing assets, brand compliance, style guides.

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

Implements API contract testing to ensure provider-consumer compatibility using Pact or similar tools. Prevents breaking changes with contract specifications and bi-directional verification. Use for "contract testing", "API contracts", "Pact", or "consumer-driven contracts".

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

Plans safe API evolution with versioning strategies, client migration guides, deprecation timelines, and backward compatibility considerations. Use for "API versioning", "deprecation planning", "API evolution", or "breaking changes".

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

Use when serving as a peer reviewer and deciding whether and how AI may assist, when a manuscript under review must never be pasted into an external tool, or when a confidentiality-preserving review and disclosure are needed.

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

Use when a study's materials, data, code, or preprint need an open-science release: license choice, a persistent DOI (Zenodo/OSF), README and metadata, and an access-and-embargo decision that respects ethics constraints.

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

Use when a research proposal needs work packages, milestones, deliverables, a timeline, a risk register, and budget-justification scaffolding, while keeping scientific claims and feasibility honest and human-owned.

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

Use when paired tr.md and en.md files need a parity verdict, when titles, frontmatter, headings, or DOI sets may have drifted between languages, or when a bilingual document is approaching release and its translation coverage needs an audit.

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

Use when a study needs a preregistration or a frozen analysis plan, when confirmatory and exploratory analyses must be separated, or when every deviation from the registered plan must be logged before the result is reported.

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

Use when reviewer comments arrive and each one needs a tracked decision, when a revise and resubmit letter must map every comment to a manuscript change, or when contradictory reviewer demands need evidence-based, editor-facing framing.

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

Use when choosing a journal for a finished or nearly finished manuscript, when index status in Scopus, SSCI, ESCI, or TR Dizin must be confirmed, when a venue looks predatory, or when a cover letter needs drafting from the manuscript's actual claims.

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

Use before a tag, GitHub release, or Zenodo archive, when README, CATALOG, CHANGELOG, CITATION.cff, the disclosure aggregate, and skill discovery must agree, or when a go or no-go release verdict needs recorded evidence behind it.

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

Use when authorship order, CRediT contribution roles, or AI-assistance attribution must be recorded transparently for a manuscript, when an author dispute needs an evidence trail, or before a contributorship statement is required at submission; this skill maintains the human-attribution ledger of who contributed what and in which role (authorship order, CRediT taxonomy, revision responsibilities), which is distinct from the disclosure-metadata audit owned by ai-disclosure-auditor.

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

Use when a systematic, scoping, or rapid review needs a reproducible pipeline: protocol framing (PICO/SPIDER/PCC), a logged search string, title/abstract and full-text screening with recorded exclusion reasons, and PRISMA flow counts, with the human as the deciding screener.

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

Use when sources must stay traceable across sessions and years, when each reference needs a passport recording where it was found, how it was verified, and where it is cited, or when a draft needs a cited-but-unverified sweep before submission.

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

This skill should be used when the user asks about "parallel agents", "background tasks", "run_in_background", "non-blocking agents", "check agent progress", "TaskOutput", "retrieve agent results", or discusses running multiple agents concurrently. Covers patterns for launching agents in background, monitoring progress, and retrieving results.

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

This skill should be used when the user asks to "improve test coverage", "add unit tests", "TDD", "test this module", "write tests for", "increase coverage", "/ut command", or discusses unit testing strategies. Covers the unit test loop workflow, React Testing Library best practices, query priorities, and coverage improvement strategies.

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

Transform brain dumps into polished blog posts in Nick Nisi's voice. Use when the user wants to write a blog post with scattered ideas, talking points, and conclusions that need organization into a cohesive narrative with Nick's conversational, authentic, and thoughtful tone.

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

Manage git worktrees using a centralized worktrees folder. Use for parallel development, PR reviews, or isolated work.

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

You are helping a penetration tester exploit authenticated access to Apache

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

You are helping a penetration tester exploit server-side request forgery. The

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

You are helping a penetration tester discover vulnerabilities in a web

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

You are helping a penetration tester exploit Java deserialization

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

You are helping a penetration tester exploit Insecure Direct Object Reference

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

You are helping a penetration tester exploit stacked query SQL injection

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