4,139 件 ・ 関連度順
概要と使いどころ
Use when writing, moving, reviewing, or auditing documentation in the deepseek-harness repo — choosing hierarchy and detail, separating tutorials from references, checking tutorial progression, trimming doc slop, responding to a verify-doc-budgets failure, or requests like "improve the docs", "audit the docs", "where should this be documented", or "this doc is too long".
日本語の概要は準備中です。原文の説明を表示しています。
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a CONTEXT.md, or recording or editing an ADR.
日本語の概要は準備中です。原文の説明を表示しています。
编写或精简技术文档、注释、提示词和界面文案时使用。
日本語の概要は準備中です。原文の説明を表示しています。
The HyperFrames composition contract — build one renderable project. Use for composition structure, the `data-*` timing attributes, `class="clip"`, tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Also covers Tailwind projects and the STORYBOARD.md / SCRIPT.md plan formats. Read before writing composition HTML.
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing or changing a model-facing tool definition (name, description, parameter schema, or its system-prompt section), and when designing skills, context loading, or multi-step workflows, to make information discoverable and use context efficiently.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when planning, redesigning, or reviewing Xiaohongshu carousel visuals, covers, 3:4 image posts, page-by-page visual direction, image-generation prompts, style selection, layout critique, or XHS captions. It acts as a senior visual director for 小红书图文, not a generic copywriting assistant.
日本語の概要は準備中です。原文の説明を表示しています。
Use when editing Chinese web fiction, narrative prose, or story drafts that sound AI-generated, overly polished, formulaic, explanatory, or too symmetrical; use to detect AI-writing fingerprints and revise only wording while preserving plot, facts, characters, names, and intent.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a user edits or criticizes generated copy and you need to extract durable writing-style rules instead of merely remembering surface words.
日本語の概要は準備中です。原文の説明を表示しています。
Use when editing .vue files, creating Vue 3 components, writing composables, or testing Vue code - provides Composition API patterns, props/emits best practices, VueUse integration, and reactive destructuring guidance
日本語の概要は準備中です。原文の説明を表示しています。
文献接力（ScholarRelay）：人机协作法学／中文学术论文写作工作流。解决的核心问题是——机构订阅文献库（知网等）需经校园 webvpn 的 IP 授权才能下载，Agent 无法自行走通这条链路，而让非专业用户自建浏览器自动化又门槛过高；本工作流把链路切在授权边界上：人做检索/导出题录/下载 PDF，AI 做解析/分级/精读/写作/校验/排版。并把流程固化为十阶段协议（立项定锚→题录获取→解析分级→精读笔记→分章写作→修订体检→编号校验→投稿排版→模拟审稿→选刊投递），用脚本强制保证正文引用编号与文末参考文献一一对应、不从零编造文献页码、用版本健康度监控防止补丁式迭代把论文改烂、用机械扫描清除 AI 写作痕迹与标点问题。 Trigger when user asks for 文献接力, scholarrelay, 论文合作流程, 人机协作写论文, 文献分级, 文献精读笔记, 写作启动包, 参考文献编号校验, 编号错位, 投稿排版, 模拟审稿, 征文投稿, 知网题录解析, 期刊体例 Word, 论文修订, 车轱辘话, 越改越烂, 版本对比, 文字冗余, 摘要写作, 关键词, 去AI腔, AI写作痕迹, 选刊, 投稿策略, 投稿检查清单, 法学引注手册, CSSCI期刊.
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing, testing, or deploying a Prisma Composer app. Read the official Composer skill even if the project has no local copy.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Guidelines and strategies for constructing meaningful test suites, property-based tests, metamorphic relations, and fuzzing harnesses. Trigger when: - Designing verification bounds, writing tests, creating test invariants, or implementing validation gates. - Prompt contains: testing, test design, property-based testing, PBT, metamorphic testing, fuzzing, integration tests, E2E.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Formatting, structure, and execution rules for Quarto markdown documents. Trigger when: - Writing, editing, or rendering Quarto documents, reports, presentations, or websites. - Files matching the pattern **/*.qmd are in the workspace or referenced. - Tasks involve: quarto render, quarto preview, knitr, jupyter. - Prompt contains keywords: quarto, qmd, yaml header, code chunk, callout, cross-reference.
日本語の概要は準備中です。原文の説明を表示しています。
Idiomatic programming style, patterns, and conventions for Go (Golang) development. Trigger when: - Writing, refactoring, reviewing, or debugging Go code. - Files matching the pattern **/*.go (including go.mod, go.sum) are in the workspace or referenced. - Tasks involve: go fmt, go test, go build, go vet, golangci-lint. - Prompt contains keywords: go, golang, goroutine, channel, select, interface, err != nil, defer, panic, gofmt, struct.
日本語の概要は準備中です。原文の説明を表示しています。
SOP for structured documentation lifecycle. Trigger when: - Designing, writing, reviewing, or auditing large-scale documentation structures. - Navigating phases: Audit, Plan, Draft, Review, Verify. - Prompt contains: /doc, doc workflow, audit, draft, review, verify, documentation debt.
日本語の概要は準備中です。原文の説明を表示しています。
Core technical, safety, and maintainability rules for codebase edits. Trigger when: - Writing code, refactoring, modifying files, or creating unit tests. - Proposing commits, reviewing git history, or auditing code quality. - Modifying files in any programming language (e.g. *.go, *.rs, *.py, *.ts, *.js, *.c, *.cpp). - Prompt contains keywords: refactor, build, compile, lint, test, git, commit, rule priority, type safety, error handling, defensive programming.
日本語の概要は準備中です。原文の説明を表示しています。
Idiomatic programming style, patterns, and conventions for Python development. Trigger when: - Writing, refactoring, reviewing, or debugging Python code. - Files matching the pattern **/*.py (including requirements.txt, pyproject.toml, setup.py) are in the workspace or referenced. - Tasks involve: python, pytest, pip, uv, virtualenv, flake8, black, mypy. - Prompt contains keywords: python, py, pep8, typing, list comprehension, decorator, generator, asyncio, yield, poetry.
日本語の概要は準備中です。原文の説明を表示しています。
Propose the test(s) FIRST and get a human to sign off on the behaviour before writing the code — the test analog of /schema-review and /ui-proposal. For hand-written LOGIC in packages/* (apps opt-in, pocs exempt). Renders the proposed failing test as a reviewable contract, holds for lgtm/approve, then you write the code to make it green. Use when an agent is about to implement packages/* logic, or when asked to "write the test first", "TDD this", "agree on the test", run /test-review.
日本語の概要は準備中です。原文の説明を表示しています。
When a bug or regression is reported, the FIRST step — before fixing — is to research how and when it was introduced (git archaeology), then record that finding on the tracking issue/PR. Use the moment a bug, error, broken build, or "this used to work" is reported, before writing a fix. Produces a first-bad-commit (or "not a code regression") note you paste onto the issue.
日本語の概要は準備中です。原文の説明を表示しています。
Verified lookup pack for crouton's schema→CRUD generation domain — the fieldsFile JSON format, the complete field-type catalog with aliases, the naming contract, the exact artifact list one generate run produces, the seed/default-layout pipeline, dialect defaults, and rollback semantics. Use when writing or reviewing a collection schema, when asking "what field types exist / what does `crouton config` actually generate / where did this file name come from / why did I get a pg schema", when a generated file's name or path doesn't match the docs, or when removing/regenerating a collection. Trigger phrases — "what field types are supported", "schema JSON format", "what files does crouton generate", "naming convention for collections", "rollback a collection", "dialect default". The generation WORKFLOW (steps + sign-off gates) lives in the `crouton` skill — this is the reference it doesn't carry.
日本語の概要は準備中です。原文の説明を表示しています。
Pre-PRD Research methodology combining Business Analysis, Creative Problem-Solving, Brainstorming, and Innovation Strategy. Use before writing any PRD for problem validation, market research, competitive analysis, stakeholder interviews, ideation, root cause analysis.
日本語の概要は準備中です。原文の説明を表示しています。
Cucumber BDD integration for AID methodology. Gherkin-first acceptance criteria with executable specifications. Use for writing feature files, step definitions, and running acceptance tests.
日本語の概要は準備中です。原文の説明を表示しています。