940건 · 관련도순
Standardize Chinese Git commit messages and changelogs using Conventional Commits, a structured message format. The skill provides writing rules and configuration examples for message checks, interactive commit entry, and automatic changelog generation.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Compose pages and sites that read as their vertical: ecommerce-catalog storefronts that look like storefronts, hospitality-food sites that look like restaurants, b2b-manufacturer sites that look industrial. Use this skill whenever the user wants to build a site that looks like the vertical it serves, fix a build that reads as generic or off-vertical, build to an experience bar produced by competitor-experience-audit, or compose pages with the merchandising, density, and layout conventions a credible site in the category is expected to carry. Triggers on vertical conventions, storefront layout, ecommerce layout, retail conventions, merchandising layout, category page composition, site composition, build to the experience bar, make it look like the vertical, off-vertical, looks generic, build conventions for a vertical, site grammar. Also triggers when a build that is technically clean reads wrong for its category, and the cause is composition, not visual taste.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit the brand, UX, and site design of the leading sites in a vertical as a set of observable cross-site patterns, producing the experience bar a new build must meet or beat. Use this skill whenever the user wants to assess the competitive design field, capture vertical conventions, identify the design and UX bar of a category, or set the experience standard before a build. Triggers on competitor experience audit, UX audit, site design audit, brand audit, design conventions, what makes these sites good, vertical conventions, storefront patterns, merchandising patterns, layout density, primary task, design bar, category conventions, retail vs marketing register, what does the field do. Also triggers when an audit of the competitive field has captured technical signals (SEO, accessibility) but never named the brand, UX, or design conventions, and the build downstream will read as off-vertical without that bar.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Go 언어의 관례에 따라 코드 작성, 검토, 리팩터링을 돕습니다. 오류 처리, 동시성, 패키지 구성을 정리해 읽기 쉽고 유지보수하기 좋은 구현을 지향합니다.
Write, review, and refactor C# and .NET code using practical conventions for asynchronous work, configuration, and dependency injection—passing services into classes. Includes examples for data access and APIs to support maintainable applications.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
ASP.NET Core web framework conventions: Minimal API vs MVC controllers, Program.cs composition, DI lifetimes (Scoped/Singleton/Transient), Options pattern with IOptions<T>, middleware ordering (HTTPS redirect → routing → authentication → authorization), model binding and validation (FluentValidation / DataAnnotations), ProblemDetails error handling, structured logging with ILogger<T>, configuration layering (appsettings.json + environment variables + User Secrets), and health checks. Works alongside csharp-foundation:csharp-conventions and aspnet-core-plugin:efcore-patterns. Use this skill to: - Compose Program.cs correctly — register services, configure middleware in the right order, map endpoints. - Apply the Options pattern to avoid passing raw IConfiguration into services. - Write Minimal API endpoint groups with typed results and authorization. - Handle cross-cutting errors uniformly with ProblemDetails. - Configure structured logging and health checks for production readiness. Do NOT use this skill for: - EF Core entity configuration and migrations — see aspnet-core-plugin:efcore-patterns. - C# language idioms — see csharp-foundation:csharp-conventions. - Testing — see csharp-foundation:dotnet-testing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
.NET SDK and NuGet tooling conventions: dotnet CLI commands (new/build/run/test/publish/restore/format), NuGet package management (PackageReference, Directory.Packages.props central package management, packages.lock.json), project file conventions (.csproj, .sln, global.json, Directory.Build.props), multi-targeting, and dotnet format. Stack-agnostic — referenced by every .NET plugin in the marketplace. Use this skill to: - Detect the .NET SDK version and run all commands via the dotnet CLI. - Manage NuGet dependencies safely (central package management, no floating versions). - Configure project files and solution-wide properties in Directory.Build.props. - Format code consistently with dotnet format. Do NOT use this skill for: - Framework-specific tooling (dotnet ef migrations, aspnet-codegenerator — those are in aspnet-core-plugin:aspnet-conventions). - Testing patterns — see csharp-foundation:dotnet-testing. - C# language idioms — see csharp-foundation:csharp-conventions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Application and library conventions for plain Python projects (no web framework): src/ package layout, CLI tooling (argparse/click/typer), configuration management (pydantic-settings), logging setup, module design, entry points, and packaging conventions. Activated automatically by python-plugin/stack.md as a convention skill for the development phase. Use this skill to: - Organise Python application code in a src/ layout with proper package structure. - Build CLI tools with argparse, click, or typer and register them as console scripts. - Manage configuration from environment variables using pydantic-settings. - Set up structured logging for production-grade applications. - Package a Python project correctly with pyproject.toml. Do NOT use this skill for: - Language idioms (type hints, dataclasses, enums, match/case) — see python-foundation:python-conventions. - Package manager commands (ruff, mypy, pip/poetry/uv) — see python-foundation:python-tooling. - Testing patterns — see python-foundation:pytest-testing. - Web framework patterns (Django/FastAPI/Flask) — see those framework plugin skills.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Package management discipline for any JavaScript/TypeScript project: dependency declaration, semver, scripts conventions, lockfile hygiene, package-manager detection (npm/yarn/pnpm). Stack-agnostic — referenced by every JS/TS framework plugin in the marketplace. Use this skill to: - Add a dependency correctly (right field, right semver range). - Pick the project's package manager from lockfile. - Define `scripts` entries that match conventions. - Avoid lockfile mistakes (manual edits, wrong commits). Do NOT use this skill for: - Code-level conventions (see the active framework plugin's conventions skill). - Framework-specific package patterns (NestJS modules, Angular schematics, Expo SDK choice etc.).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Django web framework conventions: app layout, settings split (base/local/production), URLconf with app namespacing, CBV and DRF ViewSets, DRF serializers and permissions, form validation, signals, Django admin registration, and middleware. Activated automatically by django-plugin/stack.md. Works alongside python-foundation:python-conventions and django-plugin:django-orm-patterns. Use this skill to: - Structure a Django project with multiple apps and correct URLconf hierarchy. - Write CBVs and DRF ViewSets with appropriate permissions and serializers. - Configure settings correctly for different environments. - Use signals for decoupled event handling between apps. - Register models in Django admin with useful list_display and search_fields. Do NOT use this skill for: - Django ORM model field finalization and migration patterns — see django-plugin:django-orm-patterns. - Python language idioms (type hints, dataclasses, enums) — see python-foundation:python-conventions. - Testing patterns — see python-foundation:pytest-testing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Flask web framework conventions: app factory pattern with create_app(), Blueprint registration with url_prefix, MethodView for class-based API views, Marshmallow schema validation, WTForms for HTML forms, Flask-Login for session auth, flask-jwt-extended for stateless API auth, Jinja2 template conventions, error handlers, and extension initialization. Activated automatically by flask-plugin/stack.md. Use this skill to: - Structure Flask applications with the app factory and per-feature Blueprints. - Validate JSON request data with Marshmallow and HTML forms with WTForms. - Implement session-based auth with Flask-Login or token auth with flask-jwt-extended. - Render Jinja2 templates safely or return JSON responses for API mode. - Register global error handlers for consistent error responses. Do NOT use this skill for: - SQLAlchemy ORM model patterns and Flask-Migrate — see flask-plugin:sqlalchemy-patterns. - Python language idioms — see python-foundation:python-conventions. - Testing patterns — see python-foundation:pytest-testing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Test naming conventions and best practices specialized skill. Used when naming test methods, improving test readability, and establishing naming standards. Covers three-part naming method, Chinese naming recommendations, test class naming, etc. Keywords: test naming, test naming, naming conventions, naming conventions, three-part naming, three-part naming, method_scenario_expected, method_scenario_expected, how to name tests, test readability, naming best practices, test report, test documentation
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
변수와 함수 이름, 가독성, 데이터 갱신, 오류 처리를 공통 기준으로 검토합니다. 새 개발과 코드 리뷰에서 유지보수하기 쉬운 작성 방식을 맞춥니다.
기존 코드에 담긴 암묵적인 명명, 구성, 오류 처리 관례를 읽어 AI가 참고할 규칙으로 정리합니다. 방침의 충돌을 하나씩 확인하고 코드 변경 후 규칙 갱신도 지원합니다.
Spring Boot와 Quarkus의 Java 코드를 명명, 불변 데이터, 예외 처리, 프로젝트 구조와 테스트 규약에 따라 작성하고 검토합니다. 빌드 파일로 프레임워크를 판별합니다.
처음 접하는 코드의 구조와 처리 흐름, 개발 규칙을 조사해 프로젝트 참여 안내 자료와 CLAUDE.md를 만듭니다. 변경 작업별로 참고할 위치도 정리합니다.
공통 기준으로 코드의 명명, 가독성, 원본 데이터를 바꾸지 않는 갱신 방식과 오류 처리를 검토합니다. 중복과 복잡한 구조를 찾아 유지보수하기 쉽게 정리합니다.
Store project conventions, task outcomes, and troubleshooting lessons in a shared Hindsight Cloud memory bank. Retrieve relevant context before new work, or synthesize past experience to guide decisions and help teammates reuse what has been learned.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Store team conventions, troubleshooting notes, and project knowledge on a self-hosted Hindsight server. Retrieve relevant context before new tasks and draw on recorded experiences, including successful procedures, failed attempts, and individual preferences attributed to specific people.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Guide cross-platform app development with Avalonia UI and Zafiro using consistent architecture and coding conventions. Keep screen logic separate from UI dependencies, handle errors explicitly, and reuse existing helpers with ReactiveUI and DynamicData.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Set consistent Python conventions for naming, formatting, type checking, and documentation. Configure ruff and mypy or pyright, write clear function descriptions, and organize README and changelog content so a team can maintain shared standards.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Analyze an existing project's folders and produce a guide explaining directory purposes, naming conventions, and file placement. Choose a tree, list, or table, and optionally include templates for adding features consistently with the project's observed structure.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create project-specific rules for turning Figma designs into code. The skill examines existing components and styling, then saves conventions for naming, file locations, reusable design values, and implementation steps in the coding agent's rule file.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Prepare English pull requests for Apache SeaTunnel from a change summary, branch history, and file differences. It builds titles and bodies that follow project conventions, records actual testing, and can submit the pull request when requested.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.