'conventions' 검색 결과

Create or update a GitHub pull request following Medox conventions (author spicode-bot, reviewer spideystreet). Invoke manually with /pr — do NOT trigger automatically.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review database migration files for naming conventions and dangerous operations. Auto-activates for migration files.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create a git commit following project conventions. Use when: commit, commit this, make a commit, commit changes, git commit, save changes, commit my work, stage and commit, detailed commit.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Writes Next.js App Router code — Server Components, Server Actions, RSC boundaries, route handlers, caching, and streaming — matching framework conventions and project architecture.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when writing, generating, or improving Pest tests for Laravel — clear intent, good coverage, maintainable structure, and alignment with project testing conventions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a diff needs a readability review — naming, single-responsibility, DRY, dead code, mismatch with codebase conventions — dispatched by /review-changes, /do-and-judge, /judge.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when creating or editing a guideline in docs/guidelines/ — reference material cited by skills, no auto-triggers — even when the user just says 'write up our naming conventions'.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when designing APIs, planning endpoints, REST conventions, versioning, or deprecation — even when the user just says 'expose this as an endpoint' without naming API design.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when creating or modifying Artisan commands. Covers clear signatures, safe execution flow, helpful output, and project conventions for console tooling.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Implements any user intent, requirement, story, bug fix or change request by producing clean working code artifacts that follow the project's existing architecture, patterns and conventions. Use when the user wants to build, fix, tweak, refactor, add or modify any code, component or feature.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Validate current branch follows feature branch naming conventions

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Validate current branch follows feature branch naming conventions

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

[Dev Data] Use when a workflow step or the user asks for idempotent QC happy-path seeders using public commands. --mode=review audits seeder conventions read-only.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Sync reusable frontend decisions into persistent project documentation after UI work. Use when frontend changes introduce or modify component APIs, variants, design-system tokens, styling conventions, layout behavior, accessibility rules, interaction patterns, responsive behavior, or agent operating instructions; when the user asks to reflect decisions in components.md, design system docs, AGENTS.md, CLAUDE.md, GEMINI.md, or similar project memory files; or before finalizing frontend work where future consistency depends on decisions made during implementation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Finalize documentation changes for production readiness by discovering existing conventions, verifying code-doc alignment, reviewing format/terminology/tone consistency, verifying branch/worktree intent, and structuring clean commits with a post-publish branch/worktree cleanup decision. Counterpart of finalize-and-commit for documentation projects.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Compile up to five durable insights from the current conversation for possible addition to CLAUDE.md. Use before clearing context, when asked to remember lessons, or when the user wants project conventions and preferences preserved.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Name C# symbols, events, prototypes, FTL keys, resources, and compatibility surfaces consistently.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generates Angular code and provides architectural guidance. Trigger when creating projects, components, services, or HTTP communication, or for best practices on reactivity (signals, linkedSignal, resource, httpResource), forms, dependency injection, routing, SSR, accessibility (ARIA), animations, styling (component styles, Tailwind CSS), testing, naming conventions, or CLI tooling.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when reading, writing, or watching the macOS clipboard — NSPasteboard types and multiple representations, the changeCount polling pattern, the transient/concealed pasteboard conventions clipboard tools must respect, and the Sequoia paste-privacy alerts.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the user asks to create, add, convert, publish, or deploy a blog post from a draft, notes, Markdown, outline, or topic. Turns a draft into a complete, SEO/GEO-optimized post wired into the site (template, blog index, sitemap, routing) with QA and deploy. Framework-agnostic — discover the project's own conventions first.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Apply personal Git conventions when committing, creating or updating PRs, merging, rebasing, or explicitly shipping work end to end.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when reviewing a pull request in the deepseek-harness repo — orients the reviewer to this codebase's standards (AGENTS.md conventions, defensive patterns, ADRs, quality gates) and the review-specific checks that code alone can't show

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Explicit compatibility adapter for the collection's legacy PDF workflow and delivery conventions. Prefer the installed official PDF skill for generic PDF reading, generation, rendering and forms.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.