1,860 件 ・ 関連度順
概要と使いどころ
Use when debugging shared library load failures, setting RPATH or RUNPATH, applying soname versioning, writing dlopen plugins, or intercepting with LD_PRELOAD. Not for static archives: use binutils.
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing no_std Cortex-M or RISC-V firmware in Rust with cortex-m-rt, probe-rs, defmt, RTIC, or a panic handler. Not for no_std library constraints: use rust-no-std.
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing Bazel BUILD files with cc_library or cc_binary rules, Bzlmod dependencies, toolchain registration, remote execution, sandbox debugging, or bazel query and cquery graphs.
日本語の概要は準備中です。原文の説明を表示しています。
Use for ANY bug bounty, penetration test, or web/API/mobile security assessment: recon, testing endpoints, analyzing Burp traffic or any bug-bounty platform's MCP (HackerOne, Intigriti, Bugcrowd, YesWeHack, Immunefi), reviewing APKs, bypassing a WAF, enforcing scope, hunting a specific vuln class, validating findings, writing reports, or when you are stuck on a target and about to give up. Activates automatically for all bug-bounty and pentest sessions. Runs an autonomous, never-surrender predator methodology: refuses to conclude "secure", exhausts each vuln class to depth, proves a real attacker-path with impact and no false positives, tracks coverage so nothing is re-tested or skipped, diagnoses failed tooling from full logs, and hunts at maximum effort with intelligent token use until the goal is found. Activates and follows instructions in ANY language the operator writes in (the skill itself is English). Bundles a per-class web-exploitation KB, a writeup library, and PayloadsAllTheThings.
日本語の概要は準備中です。原文の説明を表示しています。
Extract, document, or normalize a product UI design system from code, screenshots, or brand sources. Use for visual tokens, theme variables, typography, spacing, colors, radii, shadows, component inventories, variants, states, or building a reusable UI library. Do not use for software architecture, database schemas, or generic system design.
日本語の概要は準備中です。原文の説明を表示しています。
Use Kanpeki component library in React projects. Activate when user wants to add, use, customize, or compose accessible UI components from Kanpeki (@kanpeki/*). Triggers: shadcn CLI, copy-paste components, Field.Root, composeRenderProps, ~/components/ui/*, React Aria Components + Tailwind CSS 4.1 + CVA. Covers installation, component patterns, forms (React Hook Form, TanStack Form), theming, and dark mode.
日本語の概要は準備中です。原文の説明を表示しています。
Build native UI with the @expo/ui package: real SwiftUI on iOS and Jetpack Compose on Android rendered from React in an Expo or React Native app. Covers universal cross-platform components (Host, Column, Row, Button, Text, List, and more imported from @expo/ui), drop-in replacements for popular React Native community libraries (BottomSheet, DateTimePicker, Slider, Menu, etc.), and platform-specific SwiftUI (@expo/ui/swift-ui, iOS only) and Jetpack Compose (@expo/ui/jetpack-compose, Android only) trees and modifiers. Use when adding or reviewing @expo/ui Host/RNHostView trees, building native-feeling UI where standard React Native components fall short (grouped settings forms with toggles, sections, menus, sheets, pickers, sliders), choosing between universal and platform-specific components, or replacing an RN community UI library with a native @expo/ui equivalent. Not for custom native modules, Expo Router navigation, Reanimated, or data fetching.
日本語の概要は準備中です。原文の説明を表示しています。
Expo's official example projects — the expo/examples repo of ~70 `with-*` integrations (Stripe, Clerk, Supabase, OpenAI, maps, Reanimated, SQLite, Skia, NativeWind, and more). Use when integrating a third-party library or service into an existing Expo app and you want the canonical, version-matched pattern to adapt, or when scaffolding a new project from one with `npx create-expo --example`.
日本語の概要は準備中です。原文の説明を表示しています。
Apply StyleKit visual styles and public assets when building, restyling, or reviewing UI. Use for named StyleKit styles, visual direction, mobile interface patterns, and component-library selection; preserve the target platform and existing product behavior.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes Android build files and R8 keep rules to identify redundancies, broad package-wide rules, and rules that subsume library consumer keep rules. Use when developers want to optimize their app's size, remove redundant or overly broad keep rules, or troubleshoot Proguard configurations.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill to migrate legacy Android camera implementations (Camera1 or raw Camera2 APIs) to CameraX. CameraX is a lifecycle-aware Jetpack library built on top of Camera2 that resolves camera rotation issues and handles device dependencies.
日本語の概要は準備中です。原文の説明を表示しています。
The complete Go development skill. REQUIRED for ALL Go work — writing, refactoring, reviewing, generating, scaffolding, or discussing Go code, including any change to .go files. Use whenever the user mentions Go, Golang, go.mod, a Go package, or asks to build a Go backend service, CLI, library, script, MCP server (Model Context Protocol), or AI/LLM agent with tool calling or ReAct-style reasoning. Routes by project type to the right architecture, conventions, and review checklist. Highly opinionated; overrides generic Go style and lint guidance on conflicts.
日本語の概要は準備中です。原文の説明を表示しています。
Generate HTML slide presentations (1 slide = 1 HTML file, 1280x720px) using Tailwind CSS, Font Awesome, and Google Fonts. Use when the user asks to create a new presentation deck or slide HTML files. Covers design guidelines, 43 layout patterns, component library, and PPTX conversion compatibility rules. Supports style selection (creative, elegant, modern, professional, minimalist) and theme selection (marketing, portfolio, business, technology, education).
日本語の概要は準備中です。原文の説明を表示しています。
Use the open-source free `NetArchTest.Rules` library for architecture rules in .NET unit tests. Use when a repo wants lightweight, fluent architecture assertions for namespaces, dependencies, or layering.
日本語の概要は準備中です。原文の説明を表示しています。
Use the open-source free `ArchUnitNET` library for architecture rules in .NET tests. Use when a repo needs richer architecture assertions than lightweight fluent rule libraries usually provide.
日本語の概要は準備中です。原文の説明を表示しています。
Investigate a topic, library, or approach before planning. Combines user context, prior knowledge, and external sources.
日本語の概要は準備中です。原文の説明を表示しています。
ライブラリ更新pull requestのレビュー。 dependabotやrenovatebotが作成したPR、または手動で作成されたライブラリ更新PRをレビューし、 release note分析、コード更新、依存関係調査、過去の失敗調査を行う。
List the skills on this machine (your Library) and the skills your team shares (the Marketplace) as Markdown boards from the terum-skills CLI. Use when the user asks what skills they have, what the team shares, what is installed, edited, untracked or missing an eval, or wants an overview of their terum-skills state.
日本語の概要は準備中です。原文の説明を表示しています。
Show one skill in full — its team record or Library folder, versions, installs, health, and its eval report when it is a team skill — as Markdown boards from the terum-skills CLI. Use when the user names a skill and asks what it is, who installed it, how it scored, or what its receipt says.
日本語の概要は準備中です。原文の説明を表示しています。
Drive the terum-skills CLI from a Claude Code or Codex session: run any verb with --format md and show its board — inspect the Library or the team Marketplace, search, fetch with sync, validate or fix a local skill, install the latest version into Global or an added project, publish a local skill as an immutable version, manage the eval queue — and prepare the verbs that belong in a terminal (project setup, skill move/copy/rename/delete, prune, reconcile, machine uninstall, team administration). Use when the user wants to manage, evaluate, publish or install skills and no narrower terum-skills skill fits.
日本語の概要は準備中です。原文の説明を表示しています。
Builds a personal voice profile so Cowork writes the way you write — not like a generic AI. Use when personalizing your writing style, for capturing your communication patterns and tone, during setup after getting generic-sounding output, when training Cowork to match your voice, or when the user says "teach claude my voice", "my writing style", "output doesn't sound like me", "brand voice", "personalize output", "make it sound like me", "it sounds too formal", "it sounds too robotic", "can cowork match my tone", or "how do I get cowork to write like me".
日本語の概要は準備中です。原文の説明を表示しています。
Discover what Cowork can do for YOUR specific role and tasks, for mapping your daily work to Cowork capabilities. Use when exploring what Cowork offers, for planning your Cowork adoption, during onboarding and role discovery, when figuring out where to start, or when the user says "what can cowork do", "what is cowork", "show me cowork features", "how can cowork help me", "what should I use cowork for", or "cowork capabilities".
日本語の概要は準備中です。原文の説明を表示しています。
A 15-minute guided setup that teaches Cowork who you are, how you work, and what tools you use — so every result feels tailored instead of generic. Use when setting up Cowork for the first time, for personalizing your workspace preferences, during onboarding after your first session, when configuring your tools and context, or when the user says "set up cowork", "configure cowork", "why is cowork giving me generic results", "cowork setup", "personalize cowork", "make cowork know me", "cowork feels like chatgpt", or "how do I get better results from cowork".
日本語の概要は準備中です。原文の説明を表示しています。
Cross-tool weekly intelligence briefing that pulls from your calendar, email, Slack, and tasks to produce a comprehensive pulse on what happened and what is coming. Useful for reviewing your week, during end-of-week wrap-ups, for preparing Monday priorities, and when catching up after time away. Use when the user says "weekly pulse", "weekly briefing", "week summary", "what happened this week", "weekly review", or "business pulse".
日本語の概要は準備中です。原文の説明を表示しています。