「hie」の検索結果

Design a CDN configuration — caching rules, TTLs, and origin shield setup. Use when asked to "configure the CDN", "set cache headers", or "set up an origin shield".

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

Information architecture — design navigation structure, content hierarchy, sitemap, and taxonomy for a product or feature set. Use when asked to "organize the navigation", "information architecture", "how should content be structured", "sitemap", "nav redesign", "where should X live", or "content hierarchy".

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

Applies Human Interface Guidelines (HIG) principles — Hierarchy, Harmony, and Consistency — to UI/UX designs to ensure intuitive and cohesive interfaces / Menerapkan prinsip Human Interface Guidelines (HIG) — Hierarchy, Harmony, dan Consistency — pada desain UI/UX untuk memastikan antarmuka yang intuitif dan kohesif.

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

Naming and classifying organisms through binomial nomenclature, the Linnaean hierarchy, type specimens, and the rules governing taxonomic authority and revision. Covers the structure of a scientific name, the ranks from domain to subspecies, the codes (ICZN, ICN, ICNP), and the modern phylogenetic refinements that reshape the classical system. Use when the task is to place a known organism in its formal hierarchy or to reason about how names change over time.

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

Certifies that a feature achieves its original objectives via goal-backward verification (SAM Stage 7). Use when all tasks pass forensic review — starts from expected outcomes, works backwards to verify each was achieved, and returns CERTIFIED or NOT_CERTIFIED with specific gaps.

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

Badge design and selection knowledge base for shields.io badges in README files. Use when writing or updating READMEs, choosing badge layouts, selecting badge styles, adding project health indicators, or picking Simple Icons logo slugs. Covers shields.io URL encoding rules, static vs dynamic badge selection, style variants (flat/flat-square/for-the-badge/social/plastic), layout patterns (two-tier/inline/centered), project-type badge sets for Python/JS/Rust/Claude plugins, color reference, non-obvious logo slugs, and common anti-patterns to avoid.

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

Generate hierarchical AGENTS.md structures for codebases. Use when user asks to create AGENTS.md files, analyze codebase for AI agent documentation, set up AI-friendly project documentation, or generate context files for AI coding assistants. Triggers on "create AGENTS.md", "generate agents", "analyze codebase for AI", "AI documentation setup", "hierarchical agents".

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

Generate visual hierarchy diagrams of agent system showing levels and delegation. Use for documentation or onboarding.

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

Decision matrix for selecting multi-agent topologies (Supervisor, Swarm, Hierarchical, Conductor) with token economics, failure modes, and escalation paths

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

Structural code graph queries via CodeGraphContext MCP (tree-sitter + KuzuDB). Find callers, callees, class hierarchies, dead code, and module dependencies.

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

Clarify priority and emphasis by fixing unclear primary actions, competing visual weight, loud section titles, and weak label/value treatment. Use when the user mentions hierarchy, prioritization, too much competition, grayscale confusion, loud headings, or unclear primary actions.

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

Build or refine UI color systems, warmth, semantic color, and color-based hierarchy in designs that are too gray, monochromatic, or missing color meaning. Use when the user mentions dull colors, gray UI, missing warmth, weak semantic color, or a need for stronger color hierarchy.

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

Improve UI typography by fixing font choices, type scale, hierarchy, weight, and readability so text feels intentional. Use when the user mentions fonts, typography, type scale, readability, text hierarchy, or sizing that feels off.

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

Hunt file upload vulnerabilities — bypass content-type/extension/magic-byte/size filters, achieve XSS via SVG/HTML upload, achieve RCE via .phtml/.jsp/.htaccess, exploit path traversal in filenames, and use polyglot files. Use when an endpoint accepts file uploads.

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

Si attiva quando l'utente chiede di scrivere, redigere, tradurre o revisionare testi italiani per uso pubblico, editoriale, blog, social, newsletter, marketing, narrativa, saggistica o divulgazione. Si attiva anche quando l'utente chiede di umanizzare testi italiani, eliminare pattern AI, correggere lessico da chatbot, catturare o calibrare la voce di un autore su un corpus di suoi testi, rispondere a un rilevatore automatico che ha segnalato come generato un testo scritto da una persona, o quando rivede testi italiani generati da modelli linguistici.

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

Use when the user needs to design, run, or audit product or GTM analytics — metric hierarchies and north stars, funnels, cohort retention, churn, pipeline velocity, forecasting, lead scoring, NRR, A/B tests, or analytical SQL — or uploads a dataset to analyze. Triggers on questions like "why did activation drop", "is this metric meaningful", "review my dashboard", or "what should I measure". For writing the spec that defines a feature's success metrics, use product-spec.

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

Review web design for layout quality, typography, colour usage, spacing, responsive behaviour, brand consistency, and visual hierarchy. Covers design principles evaluation and improvement recommendations. Use when reviewing a design mockup before development, assessing an implemented site for design quality, providing feedback during a design review session, evaluating brand consistency, or checking responsive behaviour across breakpoints.

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

Create, merge, and deduplicate BibTeX bibliography files using R packages (RefManageR, bibtex). Parse .bib files into structured R objects, merge multiple bibliographies with deduplication by DOI or title similarity, generate entries from DOI/ISBN/arXiv ID, and export clean sorted .bib files. Use when creating a new .bib file for an R Markdown or Quarto project, merging bibliographies from multiple collaborators, deduplicating a .bib that has grown through copy-paste accumulation, or generating BibTeX entries programmatically from DOIs or other identifiers.

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

Modern Java idioms for any JVM project (Java 17+): records, sealed types, text blocks, pattern matching, Optional discipline, streams, immutability, null safety, package layout, var usage, and code organisation. Apply when the project is a Java 17+ project. Stack-agnostic — referenced by every Java plugin in the marketplace. Use this skill to: - Write self-documenting, immutable-by-default value types with records. - Model closed type hierarchies with sealed classes and interfaces. - Handle optionality explicitly with Optional instead of returning null. - Write expressive pipelines with Stream API without performance footguns. - Lay out packages consistently (feature-first or layer-first) and keep class responsibilities tight. Do NOT use this skill for: - Framework-specific idioms (Spring annotations, JPA mappings — those live in framework plugin skills). - Build tooling (Maven/Gradle) — see java-foundation:build-tooling. - Testing patterns — see java-foundation:jvm-testing.

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

Analyze and engineer protein glycosylation. Scan sequences for canonical N-glycosylation sequons (N-X-S/T with X not proline, including overlapping sites), predict O-GalNAc hotspots, read glycan notation, and reach the curated external tooling (NetNGlyc, NetOGlyc, GlycoShield, GlycoWorkbench, GlyTouCan, GlyConnect). Use this skill for therapeutic antibody glycoengineering and afucosylation for ADCC, Fc glycan control, glycan shielding in vaccine immunogen design, sequon removal or insertion, and half-life engineering through sialylation. Also trigger on N-glycosylation, sequon, NXS/NXT, O-glycosylation, glycoform heterogeneity, afucosylation, high-mannose, GlyTouCan, or WURCS.

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

草稿审稿人（明鉴秋 Ming）。由 research-chief-editor 主理人调度，按 6 维标准审查章节草稿（来源充分性、事实准确性、观点均衡性、内容深度、结构清晰度、格式规范性），输出 PASS 或 REVISE 判定。尊重 3 轮循环规则：第 3 轮强制 PASS。 触发词：由 research-chief-editor 主理人调度执行，不直接面向用户。当主理人下发 Phase 3.2 审稿任务时激活。

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

报告发布员（傅梓铭 Fu）。由 research-chief-editor 主理人在 Phase 5 调度，整合所有部分（标题/日期/目录/引言/章节正文/结论/参考文献/审稿警告）输出最终 Markdown 研究报告。执行终校：格式统一、章节编号连续、分隔线、超链接检查、参考文献去重、术语一致性检查。不修改研究内容本身。 触发词：由 research-chief-editor 主理人调度执行，不直接面向用户。当 Phase 4 完成后，主理人下发 Phase 5 发布任务时激活。

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

内容修订员（任润泽 Ren）。由 research-chief-editor 主理人调度，根据 draft-reviewer 的 REVISE 反馈对章节草稿进行修改。逐条回应审稿意见，补充来源、纠正事实、补充反方观点、深化分析，保持未受批评部分不变。 触发词：由 research-chief-editor 主理人调度执行，不直接面向用户。当主理人收到 Phase 3.2 的 REVISE 判定后激活。

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

研究编辑（季要纲 Ji）。由 research-chief-editor 主理人调度，分析 Phase 1 初步调研摘要，提取核心观点，确定报告标题，规划章节大纲（3-5 章），管理章节不重叠、逻辑递进。也负责根据用户反馈修改大纲。 触发词：由 research-chief-editor 主理人调度执行，不直接面向用户。当主理人下发 Phase 2 规划任务时激活。

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