「rules」の検索結果

Runs several language models as independent coders on one labeling or discovery task and treats disagreement as data. Covers diverse panel assembly, independent voting, consensus rules, Cohen’s and Fleiss kappa, Krippendorff’s alpha, correlated-error limits on validity claims, human validation, and reporting. Use when the user asks about a council, panel, ensemble, or jury of models, how to combine model labels, or what kappa or alpha to report for model coders. Single-model codebook and validation work goes to text-classification, per-item confidence to llm-calibration-logprobs.

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

Designs survey instruments, covering question wording, scale construction and index reliability, flow and treatment placement, pretesting and soft launches, respondent burden with attention and speeding rules, sensitive questions and social-desirability bias, and treatment delivery. Use when the user writes or revises survey questions, chooses a scale, orders blocks, plans a pilot, or worries respondents will not answer honestly. Indirect measurement goes to list-experiment, multi-country instruments to cross-national-design, and live-survey operations to qualtrics-ops.

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

Writes or reviews a pre-analysis plan before data collection — registry choice (OSF, AEA RCT Registry, AsPredicted, registered reports), PAP structure, models and decision rules locked in advance, analysis code run on simulated data, contingencies for attrition, failed manipulations, and exclusions, deviation records, and timeline. Operationalizes the pre-data-collection side of DA-RT. Use when the user asks to draft or audit a pre-registration or PAP, choose a registry, decide what to lock versus leave exploratory, or handle a later deviation. Hypotheses and estimands come from hypothesis-building, post-hoc reporting from methods-reporting.

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

Designs survey instruments: question wording, scales and index reliability, flow and treatment placement, pretesting, attention and speeding rules, and sensitive questions. Use when writing or revising survey questions, choosing scales, ordering blocks, or planning a pilot.

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

Writes or reviews a pre-analysis plan before data collection: registry choice (OSF, AEA, AsPredicted, registered reports), locked models and decision rules, code run on simulated data, contingencies, and deviation records. Use when drafting or auditing a pre-registration or PAP, choosing a registry, or handling a deviation.

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

House rules and craft for LaTeX Beamer decks (storyboarding, slide prose, frame budgets, layout, XeLaTeX and Korean fonts, color, figures, Overleaf hygiene, build QA). Use to write, edit, review, or build a Beamer deck.

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

Manage Alibaba Cloud Container Registry (ACR) Enterprise Edition using the @alicloud/cr20181201 TypeScript SDK. Use when working with container image registries on Alibaba Cloud, including instance management, namespaces, image repositories, image tags, build rules, image synchronization, security scanning, delivery chains, Helm charts, artifact lifecycle, and event notifications. Covers all 115 APIs of the CR 20181201 version.

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

This skill should be used when the user asks to "create a hookify rule", "write a hook rule", "configure hookify", "add a hookify rule", or needs guidance on hookify rule syntax and patterns.

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

Use when user asks to 'lint agent configs', 'validate skills', 'check CLAUDE.md', 'validate hooks', 'lint MCP'. Validates agent configuration files against 230 rules.

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

Use when testing per-client skill rules

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

Visualize whether skills, rules, and agent definitions are actually followed — auto-generates scenarios at 3 prompt strictness levels, runs agents, classifies behavioral sequences, and reports compliance rates with full tool call timelines

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

扫描技能以提取跨领域原则并将其提炼为规则——追加、修订或创建新的规则文件

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

Interactive installer for Everything Claude Code — guides users through selecting and installing skills and rules to user-level or project-level directories, verifies paths, and optionally optimizes installed files.

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

Clean Architecture patterns for Android and Kotlin Multiplatform projects — module structure, dependency rules, UseCases, Repositories, and data layer patterns.

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

[AUTO-INVOKE] MUST be invoked BEFORE creating git commits, PRs, or code reviews. Covers Conventional Commits, PR templates, review requirements, and AI-assisted development rules. Trigger: any task involving git commit, git push, PR creation, or code review.

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

Delegates coding tasks from Codex to local Claude Code in print mode while preserving Claude's normal runtime customizations by default. Use when: (1) You want Codex to call Claude Code locally, (2) You need Claude-side skills, plugins, MCP servers, custom commands, CLAUDE.md rules, or workspace settings to stay active, (3) You want resumable Claude sessions from Codex via SESSION_ID, (4) You need thin `claude mcp` / `claude plugin` passthrough from the same bridge.

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

Draws out a founder's or expert's point of view: what they believe about their market that others don't, the hot takes they'd defend, the stories behind them, and their taste. Generates interview questions, works from answers, a live call or existing content, and ends with ranked One Big Idea candidates for thought leadership and positioning. Triggers: "expert POV", "founder POV", "one big idea", "OBI", "contrarian beliefs", "what makes our founder different", "thought leadership foundation", "founder interview questions". Feeds /positioning and /tov-guidelines. Not for writing posts or articles, and not for brand voice rules (use /tov-guidelines).

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

Extracts a company's tone of voice from its own content and turns it into rules a writer or an AI can follow. Phase 1 analyses 15 to 20 pages for sentence, paragraph, word and structure patterns with frequency counts; after the user reviews it, Phase 2 writes the guidelines: tone attributes with before and after examples, a We are / We are not table, tone by context, vocabulary to use and avoid, and open questions. Triggers: "tone of voice", "brand voice", "voice guidelines", "writing style guide", "extract voice from our website", "TOV". Not for visual identity (use /brand-kit) or messaging (use /messaging).

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

Weekly review of IWE work culture (element 14 — System Evolution). Runs during Week Close.

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

Agent invocation syntax and boundary rules

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

Stop AI agents from secretly bypassing your rules. Mechanical enforcement with git hooks, secret detection, deployment verification, and import registries. Born from real production incidents: server crashes, token leaks, code rewrites. Works with Claude Code, Clawdbot, Cursor. Install once, enforce forever.

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

Review changed Anabasis v2 code for reuse, simplification, efficiency and altitude, then apply the fixes. Quality only: it hunts no bugs, which /code-review does. Starts from what the repository already finds (the lint plugins, the whole-tree census, the not-slop ledger), measures before and after with reduce-complexity's scripts, and holds a pass to its budgets and to the rules no pass trades. Use as /simplify on your own diff before a commit, or when the operator asks whether code is simple enough, why something exists, to go one layer higher, or to remove something and find another way.

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

Read or maintain MotherDuck Guides for business definitions, join rules, and reusable warehouse conventions.

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

Review touched subsystems for layering, crate boundaries, single-source-of-truth rules, registry-driven behavior, and compiler/runtime separation. Use when a broad review needs a dedicated architecture pass or when the user asks for architectural review specifically.

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