39건 · 관련도순
Screen dependency names on npm, PyPI, and crates.io before installation to find lookalikes of legitimate packages. This skill compares spelling patterns and registry metadata, helping review AI-generated lists, lockfile changes, and new dependencies in CI/CD.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Use when working with Crates Io — crates.io Rust package registry management. Covers crate publishing, version management, dependency resolution, feature flags, build configurations, and crate metadata analysis. Use when managing Rust crates, publishing to crates.io, analyzing dependency trees, or configuring feature flags.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guides a Worktrunk release from testing and change review to version updates, release notes, tagging, and publication checks. Includes reviews of potential data loss, documentation accuracy, and contributor credits before the release is published.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Socratic method teaching skill that guides users to discover answers themselves through questioning, never giving direct answers. TRIGGER when: user's message contains 'socratic', 'Socrates', or '소크라테스'. Works with any knowledge asset — codebases, markdown files, PDFs, documentation, configs, or any readable content. Respond in the user's language.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implement or modify GitButler’s but commands using its established structure. It covers typed arguments, input validation, execution, and human-readable, shell, or JSON output, while keeping operations usable from the terminal interface.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create, update, run, and debug shell-based performance scenarios for the but CLI. It separates repository setup from the operation being measured, uses Hyperfine for timing, and guides focused validation and inspection of test output.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Doctrine for designing and evolving any **SDK** Grida ships — TypeScript, Rust, or otherwise. "SDK" here means a surface that crosses a foreign-or-foreign-treated boundary: published packages, separately-versioned consumers, FFI bindings, public-by-design modules. An SDK's job is to refuse; a strict, honest surface rejects the wrong contents and keeps the package testable in isolation. Default is "core, not customizable"; customization is the exception, defended by a deciding table. Use when authoring or evolving any such surface — `@grida/*` published packages, engine crates (gridaco/nothing `crates/*`) published or FFI-exported, intent/message vocabularies, any contract a second author will compile against. Internal-only helper packages are welcome to follow, not forced. Companion skill for two-sided contract work: $sdk-seam. Critique partners: $pedantic, $etiology. Related: $naming.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Fix Fastly Compute Rust build failures caused by edition2024 dependencies. Use when: (1) cargo build fails with "feature `edition2024` is required", (2) wit-bindgen or wasip2 crates fail to download/parse, (3) Fastly SDK pulls in incompatible transitive dependencies, (4) Build worked before but fails after dependency update. Solves by pinning wit-bindgen, wasip2, and related crates to pre-edition2024 versions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Applies the dialectical reasoning and intellectual humility of Socrates (ancient Greek philosopher, 470-399 BCE). Use this skill whenever the user is grappling with fundamental definitions, moral dilemmas, educational approaches, self-reflection, or making high-stakes ethical decisions. Trigger this skill when encountering topics like virtue, justice, the pursuit of truth, questioning assumptions, coaching, or when the user seems overly confident in unexamined beliefs. It helps dismantle false assumptions through probing questions and redirects focus toward the "care of the soul" and objective truth over external validation or material success.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyzes Rust-compiled malware by detecting the Rust toolchain signature, demangling Rust v0/legacy symbol names, and identifying crate dependencies from embedded paths. Activates for requests to analyze Rust malware, demangle Rust symbols, or identify a Rust binary build and its crates.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Publish crates to crates.io with pre-flight checks
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Move reusable code and its tests from OpenHuman into the appropriate tiny* submodule. Separate host responsibilities, update module interfaces, verify the migration, and align release versions and integrity hashes when a loadable module changes.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Generate an OpenShell SBOM, an inventory of software components, with Syft. Fill missing license details from public registries, export CSV files for compliance review, and inspect or validate SBOMs attached to container images.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Develop and fix OpenShell’s keyboard-driven terminal interface using guidance on screen structure, background data fetching, themes, and navigation. Follow existing implementation patterns to add features that fit the interface’s established behavior.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Reviews Rust applications and libraries for security issues involving unsafe code, memory safety, concurrency, calls across language boundaries, panics, and async runtimes. Coordinates specialized reviewers and produces Markdown and SARIF reports, a format for analysis tools.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Add, read, or remove a feature flag in the web app (`defineFlag`, PostHog, `ENABLE_*` env flags, `useFeatureFlag`, `isFeatureEnabled`, `ShowFeatureFlag`) or the Rust backend (`crates/feature_flags`, config switches). Use when gating, rolling out, or killing a feature, or when asked to "flag it".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Enforce hexagonal architecture in the Rust backend. Use before modifying crates/ or Rust services, especially inbound axum/tool/listener adapters, domain services/ports, outbound adapters, authorization, permissions, database access, or external clients.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Fetch dependency source code to give AI agents deeper implementation context. Use when the agent needs to understand how a library works internally, read source code for a package, fetch implementation details for a dependency, or explore how an npm/PyPI/crates.io package is built. Triggers include "fetch source for", "read the source of", "how does X work internally", "get the implementation of", "opensrc path", or any task requiring access to dependency source code beyond types and docs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate GitHub Actions CI/CD pipeline configurations for automated building and testing of library and package projects. Use when creating or updating CI workflows for npm packages, Python packages, Go modules, Rust crates, or other library projects that need automated build and test pipelines. Includes templates for common package ecosystems with best practices for dependency caching, matrix testing, and artifact publishing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audits a legal document against legal design principles. Scores the document on six pillars: language patterns (bureaucratese, archaisms, passive voice, nominalization), readability (Flesch Reading Ease and language-specific equivalents), structure and navigation, hidden conditions (material obligations buried away from their headings), statutory duplication (restating the law instead of citing it), and visual hierarchy where layout is available. Assessment-only; does not rewrite the document. Works on English, French, and German documents, inferring the applicable jurisdiction from the document's language and textual signals: governing-law clause, statute citations, party addresses. Use when a user shares a legal document (contract, NDA, T&C, privacy policy, internal policy) asking how good the drafting is from a legal design perspective, whether it is readable, whether it contains buried clauses or restates the law, or how it scores on Flesch / LIX / Amstad / Kandel-Moles readability metrics.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design, build, test, and distribute external Temps plugins with TypeScript/Bun; provide development and local-testing guidance for existing Rust plugins. Use for creating a plugin, adding an embedded console UI or deployment-event automation, testing host permissions and AI, installing from GitHub, or submitting a plugin to the public catalog. End-to-end publishing covers TypeScript GitHub-source plugins, not Rust native-package releases or in-process TempsPlugin backend crates.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Canonical rules for writing and reviewing Rust code in Shift's crates. Use whenever you add or change `.rs` code, especially error handling (`ok_or`, `ok_or_else`, `map_err`, `?`, `CoreError`, `StoreError`, `SlugError`, `BridgeError`), entity lookups by id, checked arithmetic and integer conversions, or helpers that several call sites repeat. Load `rustdoc` as well when the change adds or edits doc comments.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when adding or changing what the rezolus viewer exposes — an /api/v1 endpoint, a dashboard section, the metric catalog, metadata/description derivation, or the frontend data those depend on — or when editing src/viewer/ or crates/viewer/, or reviewing a viewer change. The viewer ships as two separate Rust backends (server + WASM) behind one shared frontend; changing one silently diverges them.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.