「structure」の検索結果

Use when answering factual or explanatory questions about the current project — codebase, architecture, conventions, workflows, constraints — with minimal cited evidence. Triggers on "how does X work here", "what does X mean", "why is X structured this way", "is this claim true in the repo", "explain X with sources". NOT for brainstorming or comparing approaches (mk:brainstorming), trade-off decisions (mk:party), debugging/root cause (mk:investigate), code review (mk:review), plans (mk:plan-creator), security audits (mk:cso), visual explanations/diagrams (mk:preview --explain), test-coverage gaps (mk:nyquist), library docs (mk:docs-finder), or workflow navigation (mk:help).

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

Full Jira ticket context analysis via the jira-analyst agent — including media (attached images / PDFs / screenshots) and linked issues. Produces structured findings suitable for posting back as a Jira comment. Read-only. Triggers: 'analyze KEY', 'rca for KEY', 'describe KEY with media'. NOT for complexity scoring (mk:jira-evaluator); NOT for story-point estimation (mk:jira-estimator).

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

Structured second-pass reasoning after code review or plan evaluation. Offers named reasoning methods (pre-mortem, inversion, red team, Socratic, etc.) to re-examine findings through a specific lens. Use after /mk:review verdict or any time deeper analysis is needed on an existing output. NOT for initial review (see mk:review); NOT for creating implementation plans (see mk:plan-creator).

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

Fetch daily arXiv announcements (cs.RO), filter by research relevance, generate a structured markdown digest, and sync matched papers to a Zotero collection with arXiv PDFs attached.

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

Structured logging conventions for DraftForge backend (Django/Celery/Daphne) and frontend (React). This skill should be used when adding log statements, creating new modules, debugging with logs, or reviewing logging patterns. Covers structlog usage, system/subsystem taxonomy, required fields, log levels, and Grafana query patterns.

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

DraftForge test infrastructure for writing backend unit tests, Playwright E2E tests, and managing test data population. This skill should be used when writing new tests, adding test fixtures, creating populate functions for new features, adding Playwright E2E specs, using login/auth fixtures, creating test users/orgs/leagues/tournaments, or understanding the test data architecture. Covers backend Django tests via Docker, Playwright config (projects, workers, sharding), test auth endpoints that expose backend login to frontend, and feature-isolated test data patterns.

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

Sync documentation with project structure

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

Multi-agent structured debate with anti-groupthink mechanisms — Devil's Advocate, minority opinion protection, 2-round hard cap. Use when divergent perspectives matter more than consensus (architecture decisions, design tradeoffs, contested specifications).

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

Redis best practices for caching, data structures, and in-memory data architecture

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

Generate structured release notes from git history and closed issues within Claude Code session

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

Structured SE task evaluation using 15 benchmark definitions from claude-code-harness research

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

Analyze a natural language idea against the project codebase and return structured issue specs

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

Refactor code for better structure and patterns

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

Create a new agent with complete structure

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

Guide setup for and verify a reviewed, read-only Grafana Observability profile and its activated capability packs. Use when a user asks to set up Grafana access, verify profile readiness, discover available infrastructure, APM, log, IoT or business KPI packs, or troubleshoot why a Grafana pack cannot run.

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

Establish, author, restructure, or audit human-first processor Architecture, Design, Research, Review, and Verification documentation. Use for progressive documentation scaffolding, authority maps, reading paths, document-type content contracts, length-budgeted splitting, or maintainability reviews. Do not use as a substitute for cycle-accurate microarchitecture analysis or RTL implementation.

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

Turn a live website into a working local frontend you can edit. Fetches the page, extracts its design system and structure, and rebuilds it locally in your stack, then screenshot-compares to the original. Use when the user says "url to code", "clone this site locally", "make it look like linear.app", "rebuild this page", or provides a live URL to recreate. Part of the Product Design set. Uses web-fetch + browser automation.

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

Use when splitting a domain Skill into Phase-Aware File Structure (SKILL.md / design.md / constraints.md). Defines the splitting criteria, procedures, sync procedures, and validation rules. Invoked by /skill-format command or manually when restructuring domain Skills.

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

Apply or adapt a complete dual-theme UI specification board for product interfaces. Use when Codex should build or restyle dashboard, admin, workspace, settings, or system UI with both light and dark themes, shared semantic tokens, structured component states, and a full preview board covering foundations, controls, navigation, data display, and feedback patterns.

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

Analyze suspicious SMS/email messages, phishing links, redirects, domains, payloads, malware indicators, and suspected C2 infrastructure safely. Use when the user provides spam, smishing/phishing content, raw .eml headers, URLs, QR links, attachments, hashes, strange payloads, redirect chains, DNS/WHOIS/RDAP questions, C2 clues, exploit-chain questions, or asks what defenses to apply.

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

Create and scaffold plugin directories for Codex with a required `.codex-plugin/plugin.json`, optional plugin folders/files, and baseline placeholders you can edit before publishing or testing. Use when Codex needs to create a new local plugin, add optional plugin structure, or generate or update repo-root `.agents/plugins/marketplace.json` entries for plugin ordering and availability metadata.

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

Handles batch effects in bulk RNA-seq via design-matrix inclusion (the correct path for DE), ComBat/ComBat-seq for visualization, SVA for unknown latent factors, RUVSeq for negative-control-gene-anchored unwanted variation, and limma::removeBatchEffect for plotting only. Encodes the Nygaard 2016 cardinal sin against testing on a batch-corrected matrix, the choice between SVA/RUVg/RUVs/RUVr, the confounding non-identifiability problem, the single-cell boundary (Harmony/MNN are NOT for bulk), and the Goh 2017 harmonization critique. Use when designing a DE analysis with batch structure, troubleshooting batch-dominated PCA, choosing ComBat vs ComBat-seq, handling unknown batch via SVA, integrating across studies, or deciding when (rarely) to subtract batch.

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

Analyzes time-series and longitudinal RNA-seq for differential expression and trajectory structure. Covers DESeq2 LRT with reduced models, time as factor vs continuous vs natural splines, maSigPro (Nueda 2014 for RNA-seq), ImpulseDE2 with explicit impulse-model failure modes, DREAM for repeated measures via linear mixed models, pseudoreplication avoidance, conditional vs marginal modeling, and trajectory clustering with DPGP, Mfuzz (with Schwämmle 2010 fuzzifier estimation), and splines+k-means. Use when modeling time-course or longitudinal expression, choosing factor vs spline, handling repeated measures from the same subject, avoiding pseudoreplication, clustering temporal trajectories, or selecting between dedicated time-course tools and pairwise+LRT.

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

Find cross-database references between NCBI databases using Biopython Bio.Entrez (ELink). Use when navigating gene to protein/structure, sequence to publication, PubMed to GEO, BioProject to SRA runs, or discovering all link relationships for a record. Covers linkname semantics, cmd= variants, asymmetric link warnings, neighbor_history for >200 input IDs, and per-database link tables.

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