839 件 ・ 関連度順
概要と使いどころ
Use when a skill isn't triggering as expected, before adding a new skill (to check for a name collision), during periodic cleanup of an accumulated skills directory, or when asked to review skill quality — checks frontmatter validity, description quality against Skill Discovery Optimization conventions, body size, and cross-scope name collisions.
日本語の概要は準備中です。原文の説明を表示しています。
Derive this project's own integration conventions from what the code already does, draft them as a wiring contract, and hold new work to it. Closes the built-but-not-wired gap at L3 (walking skeleton) — a mechanism that ships and is never called reads green in every other check.
日本語の概要は準備中です。原文の説明を表示しています。
Render `.claude/canvas/opportunities.yml` as a diagram or structured list. Read-only. Default format Mermaid mindmap. Consults the attribution registry per `${CLAUDE_PLUGIN_ROOT}/engine/render-conventions.md` consent + privacy gate. Second specialist in the render fleet.
日本語の概要は準備中です。原文の説明を表示しています。
Render `.claude/canvas/cycle-history.yml` as a Gantt chart + outcome distribution pie (or ascii / json). Read-only. Consults the attribution registry per `${CLAUDE_PLUGIN_ROOT}/engine/render-conventions.md` consent + privacy gate. Third specialist in the render fleet.
日本語の概要は準備中です。原文の説明を表示しています。
Implement or modify Python, JavaScript, SCSS, templates, CLI, HTTP, logging, or tests. Use for code changes that require architecture, style, testing, and verification conventions.
日本語の概要は準備中です。原文の説明を表示しています。
Author and modify documentation for projects that use Gehtsoft's docgen utility. Use this skill whenever the user mentions docgen, .ds files, the doc/ directory of a repository, project.xml or project.proj for documentation, or wants to write/edit/build/debug API documentation in any codebase that uses docgen. Also use it whenever the user asks about generating C#, C++, or Java API documentation that follows Gehtsoft conventions, even if they don't say "docgen" explicitly.
日本語の概要は準備中です。原文の説明を表示しています。
Meta-skill for creating new stitch-kit skills. Enforces naming conventions, SKILL.md structure, examples format, and the Design-First SOP. Use when adding new framework support, a new domain-specific prompt architect, or any new capability to the stitch-kit plugin.
日本語の概要は準備中です。原文の説明を表示しています。
Reference for Claude Code's 6 Task Management tools — TaskCreate, TaskGet, TaskList, TaskUpdate (structured tracking) and TaskOutput, TaskStop (background execution). Covers tool parameters, status lifecycle, completion rules, dependency management, and conventions
日本語の概要は準備中です。原文の説明を表示しています。
Use Stylelint in .NET repositories that ship CSS, SCSS, or other stylesheet assets alongside web frontends. Use when a repo needs a dedicated CLI lint gate for selectors, properties, duplicate styles, naming conventions, or design-system rule enforcement.
日本語の概要は準備中です。原文の説明を表示しています。
Use the open-source free `StyleCop.Analyzers` package for naming, layout, documentation, and style rules in .NET projects. Use when a repo wants stricter style conventions than the SDK analyzers alone provide.
日本語の概要は準備中です。原文の説明を表示しています。
Defines the structure and implementation of service classes, enforcing the use of interfaces, ServiceImpl classes, DTOs for data transfer, and transactional management.
日本語の概要は準備中です。原文の説明を表示しています。
Specifies standards for RestController classes, including API route mappings, HTTP method annotations, dependency injection, and error handling with ApiResponse and GlobalExceptionHandler.
日本語の概要は準備中です。原文の説明を表示しています。
Outlines the monorepo structure and tooling conventions, emphasizing the use of Taskfile.yml, and proper handling of environment variables.
日本語の概要は準備中です。原文の説明を表示しています。
Specifies best practices and conventions for Expo-based mobile app development.
日本語の概要は準備中です。原文の説明を表示しています。
Sets standards for Data Transfer Objects (DTOs), typically records, including parameter validation in compact canonical constructors.
日本語の概要は準備中です。原文の説明を表示しています。
Operating guide for construction project documents — load before reading drawings, specs, schedules, RFIs, submittals or bids. Data-access rules (never read PDFs directly; rasterize first), AgentCM graph-guided vision, drawing and cross-reference conventions, document precedence. Triggers: 'construction project', 'drawings', 'specs', 'sheet', 'RFI', 'submittal'.
日本語の概要は準備中です。原文の説明を表示しています。
Review a GitHub Pull Request or GitLab Merge Request against the conventions that repo has taught this plugin, and post exactly one review. Use when handed a PR or MR URL; never edits code.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "create a plugin", "scaffold a plugin", "understand plugin structure", "organize plugin components", "set up plugin.json", "use ${CLAUDE_PLUGIN_ROOT}", "add commands/agents/skills/hooks", "configure auto-discovery", or needs guidance on plugin directory layout, manifest configuration, component organization, file naming conventions, or Claude Code plugin architecture best practices.
日本語の概要は準備中です。原文の説明を表示しています。
Backend conventions and patterns. Use when working on API routes, dependency injection, or hexagonal architecture in the backend.
日本語の概要は準備中です。原文の説明を表示しています。
Create or improve documentation based on the current conversation. Use this when a plan has been created and changes were requested because it didn’t follow the repository’s conventions.
日本語の概要は準備中です。原文の説明を表示しています。
Database conventions and patterns. Use when working on database schemas, migrations, or data modeling.
日本語の概要は準備中です。原文の説明を表示しています。
Testing conventions and patterns. Use when writing or modifying tests, creating mocks, or using object mothers.
日本語の概要は準備中です。原文の説明を表示しています。
Create, track, switch, sync, and clean up Git branches. Covers naming conventions, safe branch switching with stash, upstream synchronization, and pruning merged branches. Use when starting work on a new feature or bug fix, switching between tasks on different branches, keeping a feature branch up to date with main, or cleaning up branches after merging pull requests.
日本語の概要は準備中です。原文の説明を表示しています。
Design a generative recipe DSL so agents emit small validated JSON documents and ONE audited interpreter renders them all — data, not code. Covers the N-artifacts threshold for choosing a DSL over bespoke code, designing roles as style slots so a single recipe renders unchanged in every output style, the validator gate (compile + bounds + real render in all styles, plus a --fast mode for corpus-wide sweeps), hand-authored seed recipes, and the emergent conventions that keep a corpus of hundreds consistent without per-item steering. Use when many similar artifacts (icons, status badges, diagram nodes, test fixtures) must be generated by agents, when per-item bespoke code is multiplying unreviewable code paths, or when a whole corpus must be re-rendered cheaply into new styles.
日本語の概要は準備中です。原文の説明を表示しています。