'documentation' 검색 결과

Use when preparing Australian international related-party transaction records and documentation gaps for specialist review.

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

Add, change, or translate user-facing text in the Lyrion Dashboard, which ships bilingual FR/EN. Use this whenever a task introduces a new visible string (a label, tooltip, aria-label, empty state, stat name), changes wording, or touches the README or a `docs/` page — so every string lands in both languages and the EN/FR documentation pairs stay in sync. Covers `i18n.py`, how templates and JS consume translations, and the parity rule.

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

Inspect README portability, publication assets and command risks with deterministic evidence. Use when reviewing package documentation, preparing an npm release, or diagnosing first run instructions.

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

Run the API contract workflow for public interface changes, compatibility constraints, contract tests, documentation, and review.

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

Run the full feature workflow — task validation, technical design, implementation, testing, review, and documentation.

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

Run the API contract workflow for request/response shape changes, compatibility constraints, contract tests, documentation, and review.

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

Full-stack Convex development guidelines covering React, Vite, TypeScript, mutations, auth, design system, and documentation practices. Use when building features, writing Convex functions, or making code changes in this project.

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

Writing style guide for technical content, social media, blog posts, READMEs, git commits, and developer documentation. Optimized to avoid AI detection patterns. Use when writing any content beyond code.

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

Project workflow for PRDs, task tracking, changelog sync, and documentation updates. Use for any non-trivial task that spans multiple steps, touches several files, changes architecture, or needs project tracking updates. Also activates with @update to sync task.md, changelog.md, and files.md after completing work.

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

Write copy following Sentry brand guidelines. Use when writing UI text, error messages, empty states, onboarding flows, 404 pages, documentation, marketing copy, or any user-facing content. Covers both Plain Speech (default) and Sentry Voice tones.

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

Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.

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

Transform audio recordings into professional Markdown documentation with intelligent summaries using LLM integration

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

Builds production-ready REST API endpoints with validation, error handling, authentication, and documentation. Follows best practices for security and scalability.

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

Master API documentation with OpenAPI 3.1, AI-powered tools, and modern developer experience practices. Create interactive docs, generate SDKs, and build comprehensive developer portals.

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

This skill should be used when the user asks to "create AGENTS.md", "update AGENTS.md", "maintain agent docs", "set up CLAUDE.md", or needs to keep agent instructions concise. Enforces research-backed best practices for minimal, high-signal agent documentation.

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

Generate production-ready Next.js/React components from design specifications. Use this skill when you have a design specification document and need to create React/TypeScript components with Tailwind CSS styling, Vitest tests, and Storybook documentation.

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

Generate spectrograms and audio feature visualizations (mel, chroma, MFCC, tempogram, etc.) from audio files via CLI. Useful for audio analysis, music production debugging, and visual documentation.

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

Create a detailed, phased implementation plan with documentation discovery. Use when asked to plan a feature, task, or multi-step implementation — especially before executing with do.

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

Definition, documentation, and application of design tokens for Vue 3 + shadcn-vue. Use when configuring a new project, extracting tokens from Figma, or ensuring token consistency across Vue components.

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

Read Haskell package documentation, Haddock HTML, Hackage pages, or dependency source for cabal nix-style projects. Prefer locally built/cached docs and source from the cabal store, dist-newstyle, plan.json, and repo-cache; fall back to Hackage only for packages outside the project dependency set or when local docs are unavailable.

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

Search Haskell APIs using Hoogle. Use when working with Haskell projects to look up function signatures, find functions by type, discover library documentation, or identify which module exports an item.

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

Create well-structured, comprehensive Claude skills with clear activation criteria, detailed descriptions, usage examples, and proper documentation following best practices. Use when documenting new workflows, creating reusable skill patterns, establishing coding standards as skills, building team knowledge base, or expanding the skills library with new capabilities.

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

Design clean, scalable, and maintainable REST and GraphQL APIs following industry best practices. Use when designing public or internal APIs, planning endpoint structures, defining request/response contracts, establishing versioning strategies, implementing authentication patterns, designing data models, creating API documentation, ensuring consistent error handling, optimizing for performance, or establishing service contracts between microservices.

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

Generate comprehensive changelogs from Git history, commit messages, pull requests, and issue tracking for release documentation. Use when preparing releases, documenting changes, creating release notes, categorizing commits, generating version summaries, maintaining project history, or automating changelog updates.

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