'rust' 검색 결과

Validate Rust code quality with rustfmt, clippy, cargo check, and security analysis. Use for Rust codebases to ensure idiomatic Rust code and best practices.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when writing, reviewing, or refactoring Rust code. Covers ownership, borrowing, error handling, async patterns, API design, memory optimization, performance, testing, and common anti-patterns. Targets Rust 1.80+ and Edition 2024. Invoke with /rust-core.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Writes, reviews, and debugs idiomatic Rust code with memory safety and zero-cost abstractions. Implements ownership patterns, manages lifetimes, designs trait hierarchies, builds async applications with tokio, and structures error handling with Result/Option. Use when building Rust applications, solving ownership or borrowing issues, designing trait-based APIs, implementing async/await concurrency, creating FFI bindings, or optimizing for performance and memory safety. Invoke for Rust, Cargo, ownership, borrowing, lifetimes, async Rust, tokio, zero-cost abstractions, memory safety, systems programming.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when configuring org-wide platform settings: MFA enforcement, My Domain setup and deployment, session timeout and security settings, password policies, trusted IP ranges (Network Access), and CSP Trusted Sites. Owns these settings as deployable Settings metadata (Security.settings, MyDomain.settings, Company.settings, Language.settings) and the order in which a new org is stood up. Trigger keywords: 'MFA setup', 'My Domain', 'session settings', 'password policy', 'trusted IP ranges', 'CSP trusted sites', 'Security.settings', 'SecuritySettings metadata', 'MyDomainSettings', 'settings-meta.xml', 'enhanced domains', 'deploy org settings', 'new org setup order', 'sessionTimeout enum', 'lockSessionsToIp', 'enableAdminLoginAsAnyUser'. NOT for user-level login restrictions (use user-management), NOT for permission model design (use permission-sets-vs-profiles), NOT for security audit and hardening review (use security/org-hardening-and-baseline-config).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Drafts IRC 664–compliant Charitable Remainder Trust agreements (CRAT/CRUT), covering payout math, remainder qualification, trustee powers, and tax compliance. Use when drafting a CRT, CRAT, CRUT, unitrust, annuity trust, or charitable remainder planning document, or when ensuring IRC 664 compliance.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build and extend pd-console — Port Daddy's GPU-native macOS operator console (GPUI 0.2.x, Zed's Rust UI). Covers the render-agnostic Block/Pane(Surface) contract, the two-thread reqwest↔smol refresh pipeline, Taffy flexbox layout, uniform_list virtual scroll, focus + keyboard nav, the OKLCH theme and ICS maritime flag badges, GPUI's missing text-input, and the real feature-gated cargo/CI gate. Use when adding panes, visual polish, or debugging GPUI rendering/layout/focus in core/pd-console. NOT for the TypeScript daemon, generic Rust toolchain/borrow-checker help (use rust-with-claude-code), or non-pd GPUI apps with a different theme/architecture.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Idiomatic programming style, patterns, and conventions for Rust development. Trigger when: - Writing, refactoring, reviewing, or debugging Rust code. - Files matching the pattern **/*.rs (including Cargo.toml, Cargo.lock) are in the workspace or referenced. - Tasks involve: cargo build, cargo clippy, cargo test, cargo check, rustc. - Prompt contains keywords: rust, cargo, clippy, borrow checker, lifetime, struct, enum, impl, Option, Result, match, unwrap, unsafe.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

bu skill guides organizations through implementing zero trust architecture in cloud environments following NIST SP 800-207 and Google BeyondCorp principles. It covers identity-centric access controls, micro-segmentation, continuous verification, device trust assessment, and Dağıt:ing Identity-Aware Proxy to eliminate implicit network trust in AWS, Azure, and GCP environments.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Prepare and publish standalone @cline/ui releases to npm, the package registry. Covers version updates, quality checks, production and preview channels, release verification, and the initial setup that lets GitHub Actions publish the package.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preparing a production UI package release
• Publishing a preview with an explicit prerelease version
• Checking tests and package contents before release

Record and inspect source history, trust scores, and handling labels on AI-generated or modified files. Use AKF metadata, information attached to files, to support review, handoff, and advisory audit checks without treating labels as proof of compliance.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Recording how an AI-generated file was created
• Inspecting existing metadata before editing a file
• Labeling files as public, internal, or confidential

Access and test protected Vercel deployments with agent-browser using an existing Vercel identity and a short-lived authentication token. Keep deployment protection enabled while diagnosing login redirects, environment access mismatches, and application authentication errors.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Testing a protected Preview deployment
• Diagnosing Vercel login redirects and protection errors
• Identifying access rules needed for Production testing

Add controls to AI agents that use APIs, databases, and files. Use Python patterns for tool permissions, approval requirements, call limits, suspicious input checks, audit logs, and trust scores that guide delegation between agents.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Restrict which tools an agent can call
• Check suspicious inputs before execution
• Require human approval for sensitive operations

Set up Cloudflare Access and Tunnel to protect internal applications using user identity and device health checks. Covers application access policies, WARP device enrollment, and audit logging for teams replacing VPN access.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Replace VPN access with application-specific permissions
• Expose internal apps without opening inbound ports
• Limit contractors to approved applications

Build an OpenCTI pipeline that adds external context to indicators of compromise, such as suspicious IP addresses. Connect intelligence services, relate indicators to known attackers and campaigns, and score confidence to help analysts prioritize investigations.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Deploying OpenCTI and configuring enrichment connectors
• Automatically adding context to suspicious IP addresses and domains
• Relating indicators to known attackers and campaigns

Create automated workflows that add threat intelligence to suspicious IP addresses, domains, URLs, and file hashes. Combine findings from multiple services into consistent alert context and confidence scores to support analysts reviewing security alerts.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding threat context to security alerts
• Processing indicators from phishing email submissions
• Standardizing bulk indicator lookups from threat feeds

Build an automated workflow that collects suspicious files, checks known malware records, and submits unknown samples to isolated analysis environments. Generate verdicts and indicators of compromise, then send results to security monitoring systems.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Automating analysis of quarantined email attachments
• Batch-processing files quarantined by endpoint security
• Extracting threat indicators during incident investigations

Analyze recent work history and recurring frustration to identify problems that existing skills or workflows do not address. Receive a ranked shortlist of new skill ideas, with supporting evidence, for deciding what to build next.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Choosing which skill to build next
• Investigating recurring work frustrations
• Checking whether existing skills cover a problem

Evaluate partners and opportunities by asking whether trust, knowledge, and reputation can build over ten years. This skill provides questions for weighing quick returns against lasting cooperation in which everyone benefits.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Assessing a potential long-term business partner
• Weighing quick returns against reputation
• Planning actions that build trust over time

Audit one datafusion-spark function against Apache Spark 4.2.0. Compare source code, accepted types, and edge cases, verify expected results with PySpark, then fix differences and record remaining gaps as issues and disabled tests.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Auditing a function for Spark compatibility
• Checking NULL, overflow, and ANSI mode behavior
• Finding missing SQL test coverage

Choose a programming language for a development task and find the corresponding language guide. This index maps web development, systems programming, automation, and security tools to options including Python, Go, Rust, TypeScript, Java, C/C++, and Shell.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Choosing a language for a web backend
• Finding guidance for frontend development
• Comparing languages for systems programming

Upgrade the chat app’s fast or good model slot across Rust backend code and the frontend. Updates model definitions, selection logic, generated types, and display names, then checks compilation and consistency.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Upgrade the default chat model
• Replace the smart mode model
• Align backend definitions with frontend model labels

Review research ethics, participant protection, and potential bias from planning through publication. The skill examines questionable research practices and study trustworthiness, then produces a structured report with evidence, risk levels, and prioritized recommendations.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review consent documents before collecting data
• Screen analyses for questionable research practices
• Assess trustworthiness in qualitative research

Master Rust 1.75+ with modern async patterns, advanced type system features, and production-ready systems programming. Expert in the latest Rust ecosystem including Tokio, axum, and cutting-edge crates. Use PROACTIVELY for Rust development, performance optimization, or systems programming.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when writing, modifying, or reviewing Rust code. ALWAYS invoke before Rust edits; covers Microsoft Pragmatic Rust guidance for error handling, API design, performance, and idiomatic patterns.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.