「graph」の検索結果

Use when creating editable technical diagrams with draw.io / diagrams.net sources, including architecture diagrams, ERD, UML, sequence diagrams, flowcharts, ML model diagrams, official shape lookup, brand symbols, Graphviz auto-layout, codebase structure maps, .drawio validation, or draw.io CLI export fallback. Do not use for ordinary raster image generation, freehand sketches, interactive canvas/Three.js scenes, or decorative SVG animation. Chinese triggers include draw.io, diagrams.net, editable architecture diagrams, .drawio, ER diagrams, UML, sequence diagrams, auto layout, shape retrieval, code structure diagrams.

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

Use when building or reviewing Canvas 2D, Three.js/WebGL, React Three Fiber, GLSL shaders, ShaderToy-to-WebGL adaptation, 2D/3D visualization, game rendering, animation loops, GPU resource cleanup, or rendering performance. Do not use for standard DOM UI, charts already covered by a chart library, or non-graphical performance work; Chinese triggers include Canvas, Three.js, WebGL, GLSL, Shader, 3D, data visualization, games.

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

Use when generating or editing diagrams, charts, visual assets, posters, UI mockups, product images, infographics, academic figures, comics, avatars, storyboards, brand boards, or image-edit workflows, especially when exported PNGs need visual QA and bounded self-repair. Prefer deterministic Mermaid/SVG/HTML/canvas sources for text-heavy diagrams; use HTML technical diagrams for browser-ready system blueprints, architecture, deployment topology, agent runtime, memory flow, before-after architecture, workflow, sequence, data-flow, lifecycle, runbook, PII/data-lineage, and state-machine diagrams. Do not use for ordinary UI polish without generated imagery.

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

OpenUI generative UI with LangChain/LangGraph backend. Supports ChatOpenAI and ChatAnthropic.

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

Create publication-quality, editable scientific and engineering schematics with explicit physical meaning, exact labels, visual hierarchy, and provenance. Use for experimental facilities, thermal-fluid mechanisms, workflows, graphical abstracts, system architectures, or research diagrams.

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

Design clean, graphics-first technical presentations and posters with logical slide progression, visual hierarchy, purposeful motion, and complementary speaker notes. Use for research talks, conference slides, seminars, defenses, posters, or figure-focused presentations.

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

Use when a task needs the judgment of an English Language and Literature Professor — backward-designing a first-year composition or literature syllabus against a shared outcomes rubric, deciding whether an AI-detection or plagiarism flag on a student essay warrants an integrity case, reading where a tenure case's monograph actually sits in a university press's pipeline, or handling a content complaint about an assigned literary text.

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

Use when a task needs the judgment of an Economics Teacher, Postsecondary — designing an intro micro/macro sequence for a mostly-terminal non-major audience, diagnosing a miskeyed or poorly discriminating exam item, calibrating TA grading on graphical or free-response problem sets, or investigating a spike in homework answers matching an online solution bank.

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

Use when a task needs the judgment of a professional dancer — preparing for a company audition, managing rehearsal load against injury risk, deciding whether to dance through pain or report it, negotiating a casting or return-to-dance plan with a rehearsal director, or critiquing a performance for technical and artistic fidelity to the choreography.

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

Use when a task needs the judgment of a dental assistant — sequencing instrument transfer during a procedure, troubleshooting a retake-worthy radiograph before re-exposing the patient, tracing a failed sterilization-cycle indicator back to the affected instrument batches, or timing a chairside material mix against its working-time window across multiple prepped teeth.

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

Use when a task needs the judgment of a licensed General Dentist — assessing caries risk and deciding restore-vs-monitor, choosing a restorative material for a specific tooth, phasing a multi-procedure treatment plan by urgency and budget, reading a radiograph for diagnostic findings, or deciding when a case exceeds general-practice scope and needs a specialist referral.

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

Use when a task needs the judgment of a Biochemist — determining enzyme kinetics (Km/Vmax, inhibition mechanism) from rate data, choosing a structural-biology method (X-ray crystallography, cryo-EM, or NMR) for a target, designing or interpreting a binding assay (ITC, SPR, fluorescence polarization), or selecting a protein-purification strategy and diagnosing why a prep failed.

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

Use when a task needs the judgment of a Boilermaker — qualifying or selecting a welding procedure for a pressure-boundary repair, deciding whether a defect is a code "repair" or an "alteration" under the National Board Inspection Code, sizing a tube-to-drum rolled joint expansion, reading radiographic or ultrasonic weld inspection results against acceptance criteria, or setting a post-repair hydrostatic test pressure and hold time.

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

Generate proper ENCODE citations for publications, grants, and presentations. Use when the user needs to cite ENCODE data, create bibliography entries, write acknowledgment sections, or ensure compliance with ENCODE data use policy.

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

Spring Boot 4 data layer implementation for Domain-Driven Design. Use when implementing JPA or JDBC aggregates, Spring Data repositories, transactional services, projections, or entity auditing. Covers aggregate roots with AbstractAggregateRoot, value object mapping, EntityGraph for N+1 prevention, and Spring Boot 4 specifics (JSpecify null-safety, AOT repositories). For DDD concepts and design decisions, see the domain-driven-design skill.

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

Analyze internal link structure by crawling a domain. Identifies orphan pages, underlinked pages (configurable heuristic, default fewer than 3 inbound links), and broken internal links. Suggests anchor text for top 5 underlinked pages. Reuses existing fetch/parse scripts. Optional Ahrefs enrichment. Use when user says "internal links", "link structure", "orphan pages", "internal linking", "link graph", "anchor text audit".

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

Detect AI-generated content using pure text analysis (no external API calls). Analyzes sentence uniformity, vocabulary diversity, repetition patterns, hedging language, paragraph uniformity, and personal experience signals. Returns a 0-100 confidence score plus flagged passages. Use when user says "AI content check", "AI detection", "AI written", "content authenticity", "AI content", "detect AI".

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

Guideline for designing, implementing, and verifying secure APIs following OWASP API Security Top 10 (2023) best practices. Use when the user wants to: (1) review API code or design for security vulnerabilities, (2) design a secure REST, GraphQL, or gRPC API architecture, (3) implement API authentication and authorization (OAuth2, JWT, API keys, mTLS), (4) configure rate limiting, input validation, or CORS, (5) audit API endpoints for BOLA, BFLA, or mass assignment vulnerabilities, (6) create API security checklists or verification plans, (7) fix API security bugs or harden existing APIs, (8) set up API security testing (OWASP ZAP, Schemathesis, Burp Suite), or (9) handle any API security concern including SSRF prevention, resource consumption limits, business flow protection, API inventory management, and secure third-party API consumption.

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

Guideline for designing, implementing, and verifying secure TypeScript and JavaScript applications following OWASP Top 10 best practices. Use when the user wants to: (1) review TypeScript or JavaScript code for security vulnerabilities, (2) design a secure Node.js, Deno, or browser application architecture, (3) implement security features (authentication, authorization, cryptography, input validation), (4) audit npm/yarn/pnpm dependencies for known vulnerabilities, (5) create security checklists or verification plans, (6) fix security bugs or harden existing TypeScript or JavaScript code, (7) set up security testing and static analysis (ESLint security plugins, Semgrep, Snyk), or (8) handle any TypeScript/JavaScript security concern including injection prevention, prototype pollution, XSS protection, SSRF prevention, secrets management, and secure deployment.

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

Guideline for designing, implementing, and verifying secure Python applications following OWASP Top 10 best practices. Use when the user wants to: (1) review Python code for security vulnerabilities, (2) design a secure Python application architecture, (3) implement security features (authentication, authorization, cryptography, input validation), (4) audit Python dependencies for known vulnerabilities, (5) create security checklists or verification plans, (6) fix security bugs or harden existing Python code, (7) set up security testing and static analysis (bandit, safety, semgrep), or (8) handle any Python security concern including injection prevention, secure deserialization, SSRF protection, secrets management, and secure deployment.

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

Build native Linux packages (.deb / .rpm / .apk / .pkg.tar.zst) from a PKGBUILD or yap.json project using the yap-mcp Model Context Protocol server. Use this skill whenever the user asks to "build a package", "make a deb/rpm", "cross-compile for arm64/aarch64", "sign a release", generate SBOMs, install a built artifact, or diagnose why a yap build failed. The yap MCP server exposes async builds with buildID polling, validation, dependency-graph inspection, and artifact discovery.

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

Vira's design system — TailwindCSS conventions, color palette, typography, spacing, components, and accessibility rules. Use when working on UI components, styling, or layout in this project (Lucid HTML in Haskell sources under packages/vira).

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

Write engaging PR titles and descriptions for any forge (GitHub today; Bitbucket planned). Use when creating or updating PRs. Leads with narrative paragraphs and reaches for lists, tables, and diagrams when content is genuinely structured.

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

Guide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook. Use this skill when: (1) writing new Rust code or functions, (2) reviewing or refactoring existing Rust code, (3) deciding between borrowing vs cloning or ownership patterns, (4) implementing error handling with Result types, (5) optimizing Rust code for performance, (6) writing tests or documentation for Rust projects.

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