2,133 件 ・ 関連度順
概要と使いどころ
Use when adding or reviewing keyboard shortcuts in a macOS app — in-app vs global, RegisterEventHotKey vs the KeyboardShortcuts package vs NSEvent monitors, user-configurable recording, conflict handling, and which defaults won't collide with the system.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants the full package on a repo, says run my project workflow, project check-in, or is overwhelmed opening an old or new folder. Runs the project onboarding checklist—explain-new-project, project-worth-my-time, and project-catch-up—in order or on demand.
日本語の概要は準備中です。原文の説明を表示しています。
Manage agent-skill lifecycles across local, global, project, Skill Hub, skills.sh, GitHub, plugin-cache, and system roots. Use when searching, recommending, installing, updating, upgrading, syncing, merging, auditing, deduplicating, cleaning, packaging, publishing, or validating skills; choosing project versus global scope; verifying upstream source, stars, or installs; or working with skill-upgrade, check_upstreams.ps1, sync-pull/push, junctions, skills-lock.json, or skill-upstreams.json. Do not use for ordinary software-package upgrades or non-skill file cleanup.
日本語の概要は準備中です。原文の説明を表示しています。
Use Lingzao creator-content tools for Xiaohongshu/XHS, Douyin, and WeChat official-account public content. Lingzao supports XHS SEO, Xiaohongshu account analysis, benchmark account discovery, viral note breakdown, keyword research, one-stop content packages from keyword/link/image/inspiration material, title and cover optimization, hand-drawn route-map cards, city food maps, travel itinerary maps, life checklist maps, workflow manual maps, creator content workflow, note search, creator search, profile lookup, recent posts, deep profile copy/subtitle analysis, note/article detail, post comments, article stats, related articles, short-video copy extraction, and prompt-based creator image generation.
日本語の概要は準備中です。原文の説明を表示しています。
Upgrade or synchronize Agent Skills, or determine a Skill's source and ownership across runtimes and roots. Use only for those lifecycle decisions. Do not use for installation, creation or editing, validation, inventory, usage statistics, general audits, cleanup, packaging, publishing, or ordinary file and package work.
日本語の概要は準備中です。原文の説明を表示しています。
Use when auditing or fixing prose that reads like a leaked reasoning transcript — dead design-session citations such as (decision N), audit item codes, or §N of uncommitted drafts; change narration such as "used to", "no longer", "this cut"; stack or review vantage ("a later PR in this stack", "rejected in review"); reviewer-addressed justifications; control-flow narration; or hedged planning residue in comments, JSDoc, docs, or Agent Notes.
日本語の概要は準備中です。原文の説明を表示しています。
Use when Invoice-Downloader work involves mailbox batch tests, truth audit, regression validation, P0/P1/P2 decisions, packaged frontend acceptance, or clean reruns.
日本語の概要は準備中です。原文の説明を表示しています。
Use for Electron desktop application implementation, local packaging, and macOS Electron installer builds in GitHub Actions. Covers secure IPC, preload and multi-process architecture, electron-builder/Forge configuration, native modules, signing/notarization setup, DMG/ZIP packaging, mounted packaged smoke, and macOS qualification evidence. For cloud releases, this Skill owns macOS build and qualification; use github-desktop-release for Windows GitHub Actions qualification and for shared artifact promotion, GitHub Release publication, resume, or authoritative readback. Do not use this Skill to build or qualify Windows installers in GitHub Actions.
日本語の概要は準備中です。原文の説明を表示しています。
Manage Agent Skills across Codex, Claude Code, local/global/project roots, Skill Hubs, GitHub, skills.sh, and managed plugin caches. Use when searching, installing, updating, upgrading, syncing, merging, auditing, deduplicating, cleaning, packaging, publishing, validating, resolving upstream sources, choosing runtime or scope, or working with skill-upgrade, check_upstreams.ps1, Claude Code plugins, skills-lock.json, or skill-upstreams.json. Do not use for ordinary software-package upgrades or non-skill file cleanup.
日本語の概要は準備中です。原文の説明を表示しています。
Evidence-grounded AI research workflow for turning supplied economics, finance, management, and social-science papers or structured records into versioned PaperReading artifacts. Use when Codex must ingest text, Markdown, or a text-based PDF; separate source-grounded claims from researcher analysis; bind findings to evidence IDs and locators; review extraction candidates; migrate v0.2 PaperRecord JSON; validate or verify a v0.3 PaperPackage; generate research extensions; export reviewable JSON or Markdown; or safely update a compatible 13-field literature workbook.
日本語の概要は準備中です。原文の説明を表示しています。
Auto-generate a professional, client-ready GEO service proposal from audit data. Creates a full proposal in markdown and PDF including executive summary, findings, recommended service packages (Basic/Standard/Premium), pricing, timeline, and terms. Use when user says "proposal", "proposta", "offerta", "preventivo", "generate proposal", or after completing a GEO audit for a prospect.
日本語の概要は準備中です。原文の説明を表示しています。
Prepare copy-ready Xiaohongshu/Rednote publish materials from a local XHS article package. Use when the user asks for "输出发布格式", "小红书发布格式", "准备发布", "二次编辑发布格式", or needs title/body/tags/output image directory/checks without browser automation or clicking publish.
日本語の概要は準備中です。原文の説明を表示しています。
Read-only workflow for discovering uploaded deployment artifacts, comparing them with current deployment state, and preparing a safe update and rollback plan.
日本語の概要は準備中です。原文の説明を表示しています。
Appwrite Rust SDK skill. Use when building server-side Rust applications with Appwrite. Covers async client setup with API keys, user management, TablesDB database/table/row operations, file storage, function executions, permissions, queries, and error handling. Uses the crates.io `appwrite` package and Tokio.
日本語の概要は準備中です。原文の説明を表示しています。
Appwrite Go SDK skill. Use when building server-side Go applications with Appwrite. Covers user management, database/table CRUD, file storage, and functions via API keys. Uses per-service packages and functional options pattern.
日本語の概要は準備中です。原文の説明を表示しています。
Idiomatic programming style, patterns, and conventions for TypeScript and JavaScript development. Trigger when: - Writing, refactoring, reviewing, or debugging TypeScript or JavaScript code. - Files matching the patterns **/*.ts, **/*.tsx, **/*.js, **/*.jsx, package.json are in the workspace or referenced. - Tasks involve: tsc, npm, yarn, pnpm, bun, eslint, prettier, vite, next.js. - Prompt contains keywords: typescript, ts, js, javascript, interface, type, async, await, promise, es6, node, deno.
日本語の概要は準備中です。原文の説明を表示しています。
Which docs in nuxt-crouton to trust and how to resolve contradictions between them. Use when two docs disagree, when a doc's claim doesn't match the code ("the README says packages/nuxt-crouton but that dir doesn't exist"), when deciding whether a guide/writeup is authoritative before following it, or when asked "is this doc current", "which doc wins", "why does CLAUDE.md say X but the code says Y". Also the reference for the supersession-banner practice.
日本語の概要は準備中です。原文の説明を表示しています。
The crouton-conformance gate — the SECOND acceptance axis of graduation (the first is the experience side-by-side, /graduate stage C1). Checks a graduated app is a REAL crouton app — CLI-scaffolded, real collections, consumes the correct packages without reinventing them — by composing the existing probes (frontend-review, a11y, e2e-smoke, typecheck) plus crouton-structural checks, then renders a required, signed-off checklist on the graduation PR. Use at /graduate stage C2, or when asked "is this app crouton-native", "run the conformance gate", "check graduation conformance".
日本語の概要は準備中です。原文の説明を表示しています。
Accessibility review for Vue surfaces — the code-cleaning analog of /code-review and /simplify, pointed at WCAG/ARIA. Reviews just your diff (or a package/file), rates findings by severity, and either comments inline on the PR (--comment) or applies the safe fixes for you (--fix). Steers the depth-aware `a11y` subagent. Use when asked to "check accessibility", "a11y this", "audit ARIA/keyboard", or run /a11y.
日本語の概要は準備中です。原文の説明を表示しています。
How to actually run every kind of test in nuxt-crouton (unit/e2e/typecheck/lint, verified commands) plus the HONEST coverage picture — which packages have real tests vs zero, the dormant skipped/todo cases behind three mocking walls, and what CI truly gates vs what CLAUDE.md claims. Use when asked "how do I run the tests", "is X covered by tests", "what does CI actually check", "why is this suite skipped", "where do I add a test", or before trusting a green build as evidence that something works.
日本語の概要は準備中です。原文の説明を表示しています。
Front-end conventions review for Vue surfaces — the component-usage analog of /a11y, pointed at Nuxt UI 4 + crouton conventions instead of WCAG. Reviews just your diff (or a package/file) for v3 component names, the v4 overlay pattern, Options API, raw-HTML re-implementations, and hardcoded colors; rates findings by severity; and either comments inline on the PR (--comment) or applies the safe fixes for you (--fix). Steers the depth-aware `frontend-review` subagent. Use when asked to "check the frontend", "are we using Nuxt UI right", "review component usage", "frontend-review this", or run /frontend-review.
日本語の概要は準備中です。原文の説明を表示しています。
Track work as GitHub issues in this monorepo — create epics + child/sub-issues, label them consistently by package/app, and tie them into the commit workflow. Use when planning a feature, breaking work into tasks, or asked to "track this in GitHub", "make issues", "set up tracking".
日本語の概要は準備中です。原文の説明を表示しています。
Adversarially probe this monorepo for security flaws at the right depth. Steers the red-team subagent — picks quick/standard/deep from the request, spawns it (fanning out for a wide deep sweep), collates findings into a dated report, and files security/sec:* issues for confirmed high/critical findings. Use when asked to "red-team", "try to hack this", "find security holes", "pentest this package/app", or as the brain behind the CI + daily security runs.
日本語の概要は準備中です。原文の説明を表示しています。
Recreate the nuxt-crouton dev environment from scratch and survive its install/build traps — the pnpm toolchain, the cold-start sequence (why packages must build before apps prepare), the version catalog and workaround pins, the per-app typecheck rule, required env vars, and the known environment traps. Use when setting up a fresh clone/worktree, when "pnpm install" or "nuxt prepare" fails, when an app won't boot after install, when typecheck output looks insane, or when a tool "isn't available". Trigger phrases: "set up the repo from scratch", "why does typecheck show thousands of errors", "playwright install fails", "what pnpm/node version". (Exact error strings — "Could not load '@fyit/crouton'", "Cannot find module '@vue/compiler-sfc'" — route via crouton-diagnostics-index first; it points back here for depth.)
日本語の概要は準備中です。原文の説明を表示しています。