「case」の検索結果

Twig coding standards and conventions for Craft CMS 5 templates. ALWAYS load this skill when writing, editing, or reviewing any .twig file in a Craft CMS project — even for small edits. Covers: variable naming (camelCase, no abbreviations), null handling (?? operator, ??? with empty-coalesce plugin), whitespace control ({%- trimming, NOT {%- minify -%}), include isolation (always use 'only'), Craft Twig helpers ({% tag %}, tag(), attr(), |attr filter, |parseAttr, |append, svg()), collect() for props and class collections, .implode(), comment headers with ========= separators on component files, and common pitfalls (snake_case, macros as components, hardcoded colors).

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

Plan and run manual tests of the project's running app. Runs a session in one of five modes: exploratory, verification, smoke, assessment (UX, localization, accessibility, improvement review), or AI probe. Also writes a manual test plan that holds only what automated tests cannot judge. Use whenever the user asks, in any language, for something to be tested by hand or for a manual test plan — "manual test", "exploratory test", "bug hunt", "verify the bug fix", "smoke test", "QA this screen", "review this screen's UX", "what would you improve", "check the localized copy", "test the AI agent's answers", "write manual test cases", "kịch bản test manual" — or assigns a test design, test plan or test-case IDs to execute by hand. Not for writing automated tests.

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

Generates a structured initial contact summary memorandum from a potential client's first interaction with the firm. Captures case facts, liability indicators, damages, insurance details, and screening criteria. Use during client intake to support conflict checks, case evaluation, and engagement decisions.

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

Content Marketing engineer — blog strategy, SEO, thought leadership, developer content, case studies, and content calendar. Use when asked to "write a blog post", "plan our SEO", "build a content calendar", or "write a case study".

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

Legal research on a specific question — case law, statutes, regulatory guidance. Use when asked to "research this legal question", "what does case law say", or "find the relevant statute".

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

Expert guide for creating high-converting application promotional media — App Store & Google Play screenshots, social promo graphics, dynamic Open Graph banners, Remotion programmatic video teasers, and AI promo showcases / Panduan ahli pembuatan media promosi aplikasi — mockup screenshot App Store & Google Play, kartu promo media sosial, banner Open Graph dinamis, video teaser terprogram Remotion, dan showcase promo berbasis AI.

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

Create and improve Odoo custom module tests using the Odoo test framework. Use when the user asks to add tests, create TransactionCase/HttpCase tests, test Odoo business logic, mock external APIs, use Form helper, test access rules, test workflows, or improve Odoo test coverage.

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

根据 MAS + verification_plan + RTL 接口描述生成 SystemVerilog UVM 或 cocotb 测试平台与 test cases 清单。触发场景：(1) bba-guru-verification 在 plan 完成后；(2) 补充 corner case TB；(3) 显式 /bb-generate-tb。

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

Use when the user asks for a client report, a monthly or activity report, a case study draft, or says 'what did i ship this month'. Turns the site audit log into a written report in one of six framings: agency client report, case study, internal recap, testimonial draft, build-in-public, personal recap.

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

Quantifies revenue and cost synergies with build-up methodology, realization timelines, and integration cost offsets. Use when estimating deal synergies, modeling cost savings, or building synergy cases for IC.

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

Evaluates regulated utility rate-setting with RAB methodology, allowed return analysis, and regulatory reset risk assessment. Use when analyzing regulatory frameworks, modeling rate cases, or evaluating allowed return mechanics.

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

Improve interface resilience through better error handling, i18n support, text overflow handling, and edge case management, making interfaces robust and production-ready. Use when the user asks to harden, make production-ready, handle edge cases, add error states, or fix overflow and i18n issues.

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

Reverse-engineer raw materials (Sparse idea, Dense idea, experimental log) from an existing AI research paper to build a benchmark case for evaluating paper-writing pipelines. Replicates the PaperWritingBench dataset construction procedure from arXiv:2604.05018 §3 / App. C. TRIGGER when the user asks to "build a benchmark case from this paper", "reverse-engineer raw materials", or "evaluate my pipeline against PaperWritingBench".

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

Generate interactive Three.js canvases in six modes: narrative particle phase cycles, WebGPU spinner/loaders, infinite gallery tunnels, animated glTF specimens, vinyl showcase with webcam reflection, glass hero sections with physically-accurate refraction/dispersion/iridescence. Ships a reusable Phosphor Vigil FX post-processing module (CRT composite, scanlines, chromatic aberration). Self-contained HTML output. Triggers on particle system, ambient 3D canvas, WebGL art, spinner, loader, infinite tunnel, glTF animation, CRT post-processing, vinyl record, webcam reflection, 3D product showcase, glass hero, 3D glass, refraction, dispersion, iridescent glass, frosted glass panes, glass material.

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

Specialized business strategy prompt methodology for Claude. Provides 11 tested approaches (3 identity, 4 reasoning, 4 output formats) for consulting, M&A, corporate strategy, and strategic planning tasks. Use when building prompts for deal evaluation, due diligence, portfolio strategy, business model analysis, board narratives, investment cases, market entry plans, or strategic options assessments. Trigger on: "build a prompt for M&A analysis," "due diligence prompt," "board narrative," "investment case," "market entry strategy," "strategic options," "portfolio strategy prompt," "business model analysis prompt," "consulting-style analysis." Do NOT use for evaluating or scoring existing prompts (use rootnode-prompt-validation if available) or for auditing Claude Projects (use rootnode-project-audit if available).

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

Consolidated Symfony conventions (Symfony 6.4 / 7.x): attribute routing, controllers as services, autowiring/DI, Form types, Validation constraints, Voters for authorization, the Serializer/DTO contract, and Messenger. Apply when writing or reviewing Symfony backend code. Activated automatically by symfony-plugin/stack.md as a convention skill for the development phase. Apply when: writing or reviewing Symfony controllers, services, forms, validators, voters, and serialization. Do NOT use this skill for: - PHP language idioms (strict_types, enums, readonly) — see php-foundation:php-conventions. - Doctrine queries / entities — see symfony-plugin:doctrine-patterns. - Testing — injected by the QA phase (WebTestCase/KernelTestCase) + php-foundation:php-testing.

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

Modern Python idioms for any Python 3.10+ project: PEP 8 style, PEP 484/526 type hints, dataclasses, pathlib, enums, f-strings, structural pattern matching (match/case), context managers, exception handling, and null discipline. Stack-agnostic — referenced by every Python plugin in the marketplace. Use this skill to: - Write strongly-typed code with type hints on every function signature and class attribute. - Replace isinstance chains and magic constants with match/case and enums. - Use dataclasses or NamedTuple for value objects and data containers. - Handle resources safely with context managers and pathlib for all file paths. - Apply PEP 8 naming and structure conventions consistently. Do NOT use this skill for: - Framework-specific idioms (Django ORM, FastAPI routers, Flask blueprints — those live in framework plugin skills). - Packaging and dependency management — see python-foundation:python-tooling. - Testing patterns — see python-foundation:pytest-testing.

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

pytest testing patterns for any Python project: test structure, fixtures, parametrize, conftest.py, monkeypatch, tmp_path, markers, unittest.mock (MagicMock, patch), pytest-cov coverage, and best practices. Stack-agnostic — referenced by every Python plugin in the marketplace. Use this skill to: - Organise tests with conftest.py shared fixtures and a clear test/src layout. - Write parametrized tests to cover multiple inputs without duplication. - Mock external dependencies (HTTP, DB, filesystem) with unittest.mock and monkeypatch. - Measure and enforce code coverage with pytest-cov. Do NOT use this skill for: - Framework-specific test types (Django TestCase / WebTestCase, FastAPI TestClient, Flask test client — see framework plugin skills). - Language idioms — see python-foundation:python-conventions.

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

Modern C# idioms for any .NET project (C# 10+, .NET 6+): nullable reference types, records, readonly structs, primary constructors, pattern matching, async/await with CancellationToken, IDisposable/IAsyncDisposable, file-scoped namespaces, var usage, naming conventions (PascalCase members, _camelCase fields, I-prefixed interfaces), and class design rules. Apply whenever the project is a .NET 6+ project. Stack-agnostic — referenced by every .NET plugin in the marketplace. Use this skill to: - Write self-documenting immutable value types with records and readonly structs. - Handle nullable reference types explicitly to eliminate NullReferenceException at compile time. - Implement async/await correctly with CancellationToken propagation and ConfigureAwait(false) in libraries. - Dispose unmanaged resources correctly via IDisposable / IAsyncDisposable and using statements. - Apply C# pattern matching (switch expressions, property patterns, list patterns) for cleaner branching logic. Do NOT use this skill for: - Framework-specific idioms (ASP.NET Core controllers, minimal APIs, EF Core — those live in aspnet-core-plugin skills). - Build tooling (dotnet CLI, NuGet, csproj) — see csharp-foundation:dotnet-tooling. - Testing patterns — see csharp-foundation:dotnet-testing.

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

Use when concrete Odylith failure evidence needs a Casebook bug with grounded repro details.

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

Use when an Odylith Casebook bug create or update needs prerequisite checks.

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

Capture a new Odylith Casebook bug from concrete failure evidence and grounded repro details.

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

Check Odylith Casebook bug prerequisites before creating or updating a bug record.

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

Use when challenging a prevailing analytical judgment, the user asks "what is the opposing case?" / "argue the other side" / "play devil's advocate", or wants an assessment stress-tested before release. Takes the team's own lead judgment and builds the strongest case that it is wrong. A contrarian technique. It does not model what an adversary would do next, which is Red Team Analysis. Formerly /red-team-analysis.

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