「conventions」の検索結果

Defines baseline C# conventions loaded first -- naming, file layout, style rules.

日本語の概要は準備中です。原文の説明を表示しています。

Code implementation, refactoring, and bugfixes. USE FOR: implementing features; refactoring code; fixing bugs; modifying existing code. DO NOT USE FOR: writing tests (separate skill); documentation (separate skill); commit conventions (separate skill).

日本語の概要は準備中です。原文の説明を表示しています。

Unit and integration testing strategy. USE FOR: writing tests; coverage improvements; vitest specs; test refactoring. DO NOT USE FOR: production code changes (use code-implementation skill); documentation (use documentation skill); commits (use commit-conventions skill).

日本語の概要は準備中です。原文の説明を表示しています。

Mark an ADR as Implemented (or Superseded) and archive it, following INDEX.md conventions.

日本語の概要は準備中です。原文の説明を表示しています。

Review code changes for correctness, consistency, performance, accessibility, and adherence to repo conventions.

日本語の概要は準備中です。原文の説明を表示しています。

Creates new Claude Code skills following repository conventions with proper structure, frontmatter, workflows, code examples, and reference files. Use when users request "create a skill", "new skill", "generate skill", or "add skill to collection".

日本語の概要は準備中です。原文の説明を表示しています。

Audits database schemas for naming conventions, type consistency, nullability patterns, and missing constraints. Provides violations report with recommended fixes. Use for "schema validation", "database linting", "schema standards", or "consistency checks".

日本語の概要は準備中です。原文の説明を表示しています。

Generates complete starter repositories for various tech stacks (Next.js, Vite, Nest, FastAPI, etc.) with best-practice conventions, folder structure, baseline code, configs, scripts, and setup documentation. Use when users request to "scaffold a project", "create a starter repo", "initialize a new project", or specify a tech stack to begin with.

日本語の概要は準備中です。原文の説明を表示しています。

Creates stable mocks for APIs, services, and UI components using MSW (Mock Service Worker), fixture conventions, and example patterns. Use for "API mocking", "MSW", "test mocks", or "service mocking".

日本語の概要は準備中です。原文の説明を表示しています。

Unifies API response patterns across endpoints including pagination format, error structure, status codes, response envelopes, and versioning strategy. Provides contract documentation, shared TypeScript types, middleware utilities, and migration plan. Use when standardizing "API contracts", "response formats", "API conventions", or "API consistency".

日本語の概要は準備中です。原文の説明を表示しています。

Creates and manages Biome GritQL custom lint rules to enforce coding patterns. Use when creating linter rules, enforcing code conventions, preventing anti-patterns, or when the user mentions Biome, GritQL, custom lint rules, or AST-based linting.

日本語の概要は準備中です。原文の説明を表示しています。

Mandatory skills, conventions, and behavioral rules for Avalonia UI development using the Zafiro toolkit.

日本語の概要は準備中です。原文の説明を表示しています。

Discovers and injects project-specific coding guidelines from .trellis/spec/ before implementation begins. Reads spec indexes, pre-development checklists, and shared thinking guides for the target package. Use when starting a new coding task, before writing any code, switching to a different package, or needing to refresh project conventions and standards.

日本語の概要は準備中です。原文の説明を表示しています。

Captures executable contracts and coding conventions into .trellis/spec/ documents. Use when learning something valuable from debugging, implementing, or discussion that should be preserved for future sessions.

日本語の概要は準備中です。原文の説明を表示しています。

Use when applying Cloudflare D1 migrations, fighting Supabase migration history vs SQL execution, choosing direct psql over CLI, designing idempotent migrations, debugging schema drift between local and remote, or recovering after a half-applied migration. Triggers: supabase migration repair instructions appearing, table missing after "applied" status, "Tenant or user not found" when running psql, --remote vs --local D1 confusion, NOT NULL on a populated column, foreign key constraint failures, drift between staging and prod schemas. NOT for Mongo/document migrations, ORM-managed migrations specifically (Prisma/Drizzle have their own conventions), or pure data backfills.

日本語の概要は準備中です。原文の説明を表示しています。

Cross-platform desktop development for macOS and Windows -- platform abstractions, UI convention differences, and multi-platform CI/CD. Activate on: cross-platform app, macOS and Windows, platform differences, DMG installer, MSI installer, NSIS installer, Cmd vs Ctrl, platform abstractions, menu bar differences, native conventions. NOT for: mobile apps, web-only apps, Tauri-specific internals (use rust-tauri-development).

日本語の概要は準備中です。原文の説明を表示しています。

Generates shell completion scripts for CLI tools. Parses command structure from help output, commander/yargs configs, or manual specification. Produces completions for bash, zsh, and fish that follow each shell's conventions.

日本語の概要は準備中です。原文の説明を表示しています。

Design decisions for when and what sounds to use in web apps, mobile apps, and desktop native apps — plus how to create them with AI. Covers UI sound vocabulary (confirms, alerts, transitions, errors), platform conventions (iOS, macOS, Material), creating sounds with AI tools (ElevenLabs, AudioCraft, Stable Audio), Web Audio API for procedural sounds, haptic-audio pairing, and the psychology of satisfying vs. annoying UI sounds. Activate on 'app sounds', 'UI sounds', 'notification sound', 'sound design app', 'earcons', 'sonic branding', 'interaction sounds', 'feedback sounds', 'app audio', 'satisfying sounds'. NOT for professional audio engineering (use sound-engineer), Windows 3.1 retro sounds specifically (use win31-audio-design), music composition (use sound-engineer).

日本語の概要は準備中です。原文の説明を表示しています。