Discover Business skills, compare source repositories and read the instructions for each workflow.
Discover available effects, actions, and placeholders in a Sandestin project. Use when asking what effects exist, searching for functionality, or needing example invocations. Keywords: effects, actions, dispatc...
Create new Sandestin effect registries following project conventions. Use when adding effects, actions, or placeholders. Keywords: registry, effect, action, placeholder, handler, create, new.
Create new Sandestin effect registries following project conventions. Use when adding effects, actions, or placeholders. Keywords: registry, effect, action, placeholder, handler, create, new.
Discover available effects, actions, and placeholders in a Sandestin project. Use when asking what effects exist, searching for functionality, or needing example invocations. Keywords: effects, actions, dispatc...
engineering.fyi、hatena.blog/dev等から技術記事をキュレーション。ニュース、技術ブログ、エンジニアリング記事のピックアップ時に使用。
This skill should be used when developing with the Hono web framework, including CLI tool usage, project scaffolding, routing, middleware configuration, testing, optimization, and deployment across multiple Jav...
gh CLI の高度な使い方、使用頻度の低いサブコマンド、便利なオプションを提供。trigger「gh の使い方」「GitHub API を叩きたい」「gh」「use gh」
Use when generate test coverage, or when asked "generate test coverage", "generate coverage", "find coverage". Provide how to get test coverage of specific component.
セッションコンテキストを表示。タブを離れて戻ってきた時に「何をやっていたか」「何を依頼したか」「次に何をすべきか」を思い出すために使用。
Codex CLIでレビュー・分析をする。「codexにレビューして」「レビューして」「review my changes」と依頼された際に使用
This skill shoudl be used when the user ask to "behaviors", "specification", "read implementation", "analyze component", "振る舞いを分析", "振る舞いを理解". Analyze component(module, package, class, function) b...
buildNpmPackage を使った Nix パッケージの作成手順。「npm パッケージを追加」「buildNpmPackage でパッケージ作成」と依頼された際に使用
Security best practices and guidelines for the Jarvy CLI codebase - a cross-platform development environment provisioning tool that executes system commands with elevated privileges
Code quality guidelines for Jarvy CLI - Rust formatting, Clippy linting, error handling patterns, documentation standards, and Conventional Commits.
Testing guidelines for Jarvy CLI - unit testing patterns, integration tests with assert_cmd, test environment variables, platform-specific testing, and CI coverage strategies.
Log key learnings to progress.txt during PRD iteration. Use when you discover codebase patterns, encounter gotchas, make important decisions, or learn something that would help future work sessions. Triggers on...
Analyze code changes and recommend appropriate documentation. Evaluates git diffs to determine if changes warrant README updates, inline doc additions, or dedicated documentation files. Triggers on: document ch...
Convert a PRD markdown file to a structured JSON task file with progress tracking. Use when converting a PRD to JSON, creating trackable tasks from a PRD, or when asked to make a PRD actionable. Triggers on: co...
Create Architecture Decision Records for important technical decisions. Guides you through trade-off analysis, fact-checks claims, and generates a structured ADR document. Triggers on: create adr, architecture...
Architecture guidelines for Jarvy CLI - codebase structure, tool implementation patterns, registry system, platform-specific code organization, and module conventions.
Performance optimization guidelines for Rust CLI tools. Covers efficient command execution, parallel processing, lazy initialization, allocation minimization, config parsing, and build optimizations for cross-p...
Dependency management guidelines for Jarvy - crate selection criteria, feature flag best practices, version management, security auditing with cargo-audit and cargo-deny.
Standards for API development, documentation, and maintenance using OpenAPI 3.0.
Guidelines for version control, commit conventions, and repository management.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.