3,693 件 ・ 関連度順
概要と使いどころ
Use for Nauthilus authentication and identity-provider work touching OIDC, OAuth2, SAML, MFA, TOTP, WebAuthn, recovery codes, LDAP-backed identity, browser login and consent flows, token/session/flow state, `private_key_jwt`, introspection, discovery metadata, endpoint-specific client authentication, and security-sensitive auth tests.
日本語の概要は準備中です。原文の説明を表示しています。
Plan or review FriendlyBet architecture, implementation, schema, data flows, scoring, provider integrations, static/PWA behavior, Supabase/RLS impact, migrations, automation, and technical sequencing. Use when a task asks how to build, refactor, generalize, integrate, test, or safely ship FriendlyBet code.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," or "SEO health check." For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Dbt Cloud — dbt Cloud management — monitor projects, environments, job runs, model status, and data freshness. Use when reviewing job run health, debugging failed models, inspecting run artifacts, or auditing project configuration.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Dbt — dbt (data build tool) project management and monitoring. Covers model runs, test results, source freshness, documentation generation, manifest analysis, and dbt Cloud API integration. Use when checking dbt run status, investigating test failures, analyzing model lineage, or managing dbt Cloud jobs.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Confluence Deep — deep Confluence management covering spaces, pages, content analytics, permissions, and workspace health. Use when performing deep audits of Confluence usage, analyzing content freshness, reviewing space permissions, or assessing documentation coverage across an Atlassian Confluence instance.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Coveo — coveo enterprise search platform management including sources, indexes, query pipelines, machine learning models, usage analytics, and security providers. Covers indexing health, query performance, ML model status, content freshness, and license utilization.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Codescene — codeScene behavioral code analysis including code health scoring, hotspot detection, change coupling analysis, and PR integration for code quality gates. Use when configuring CodeScene for codebase visualization, technical debt prioritization, and automated code review feedback.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Apptio — apptio and Cloudability IT financial management and cloud cost optimization. Covers IT cost allocation, cloud cost analysis, benchmarking, budget forecasting, showback/chargeback reports, and technology business management. Use when managing IT financial planning, benchmarking cloud spend, or creating chargeback models.
日本語の概要は準備中です。原文の説明を表示しています。
Structured decision-making framework for technical proposals and trade-off analysis. When the user faces a choice between multiple approaches (architecture decisions, tool selection, refactoring strategies, migration paths), this skill produces a 1-3-1 format: one clear problem statement, three distinct options with pros/cons, and one concrete recommendation with definition of done and implementation plan. Use when the user asks for a "1-3-1", says "give me options", or needs help choosing between competing approaches.
日本語の概要は準備中です。原文の説明を表示しています。
Prompt Injection Defense 2026: 8 Tested Techniques … — 20. Apr. 2026 · Prompt injection is still the
日本語の概要は準備中です。原文の説明を表示しています。
Mamba-3 ist schneller als Transformer beim Decode und stärker als Mamba-2 — open source. Mein Qwen3.5 nutzt Hybrid-Mamba; ein Upgrade-Pfad auf Mamba-3
日本語の概要は準備中です。原文の説明を表示しています。
FutureSearch: Search the Future — AI forecasting with a public track record. First in Metaculus's Summer 2026 FutureEval tournament, above the superfo
日本語の概要は準備中です。原文の説明を表示しています。
Hijacking, Red-Team Evals, and Continuous Evaluation A technical reference on agent hijacking, red-t
日本語の概要は準備中です。原文の説明を表示しています。
Neuromorphic Computing - Fraunhofer Institute for … — Neuromorphic computing is a field of technology aimed at designing computer architectures that m
日本語の概要は準備中です。原文の説明を表示しています。
Topics on Secure Hardware, Fall 2018 Decentralized Technologies Decentralized Finance MOOC, Fall 202
日本語の概要は準備中です。原文の説明を表示しています。
Model Quantization Guide: Run 70B LLMs in 4 Bits — … — 12. Okt. 2025 · Run 70B parameter LLMs on con
日本語の概要は準備中です。原文の説明を表示しています。
Cold start — every GPU, every model size GPU Model ZSE vLLM Speedup NVIDIA T4 (16 GB) Qwen2.
日本語の概要は準備中です。原文の説明を表示しています。
Dispatch to the right problem-solving technique based on how you're stuck
日本語の概要は準備中です。原文の説明を表示しています。
Implement WCAG 2.2 compliant interfaces with mobile accessibility, inclusive design patterns, and assistive technology support. Use when auditing accessibility, implementing ARIA patterns, building for screen readers, or ensuring inclusive user experiences.
日本語の概要は準備中です。原文の説明を表示しています。
Receive and act on code review feedback with technical rigor, not performative agreement or blind implementation
日本語の概要は準備中です。原文の説明を表示しています。
Create structured docs from scratch — PRDs, technical specs, design docs, decision records, knowledge bases. Use when drafting documentation, writing proposals, defining requirements, or planning features.
日本語の概要は準備中です。原文の説明を表示しています。
two-stage review (spec compliance first, then code quality), refactoring, and quality improvement. Use when reviewing code, eliminating code smells, reducing technical debt, refactoring methods, running self-critique loops, or improving maintainability and readability.
日本語の概要は準備中です。原文の説明を表示しています。