116건 · 관련도순
Implement and troubleshoot storage recovery with DOCA Erasure Coding. The skill guides parity generation, lost-block recovery, and incremental parity updates using Reed-Solomon coding, while checking device capabilities, block limits, and memory permissions.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Compare a recreated app with its reference using weighted feature coverage, screenshot layout differences that ignore color, and workflow reviews. Generate a report showing missing functionality, release readiness, and the next five implementation priorities.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Adversarial Quarto-vs-Beamer parity QA. A critic agent compares the Quarto HTML render to the Beamer PDF benchmark for content/visual parity; a fixer agent applies fixes; loops until APPROVED or two consecutive rounds turn up nothing new (fallback cap 5 rounds). Use when user says "qa the quarto", "check parity", "does the html match the pdf?", "quarto matches beamer?", or after a translate-to-quarto run. Requires both the `.qmd` rendered and a `.pdf` benchmark.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Constructs risk parity allocation with equal risk contribution, leverage optimization, and asset class volatility targeting. Use when building risk parity, equalizing risk contribution, or designing leveraged balanced portfolios.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when migrating SaveIt.now from the old Next.js app directory to TanStack Start, restoring route parity, UI parity, API parity, and verification without leaving Next.js runtime code.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
本番と同じ失敗を本番前に検出するためのテスト階層設計スキル。 DB方言差、実依存関係、永続化確認、timezone差、packaging整合性、 adversarial regressionをunit/integration/e2e/smoke/packagingに 適切に割り振り、PR CIで最低限の本番同等性を保証する。 Use when designing production-parity tests, closing test blind spots, building smoke suites for real dependencies, verifying persistence beyond UI success, or creating adversarial regression backlogs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Solid 2로 OpenClaw 화면을 구현하고 이전하며 검토와 테스트를 진행합니다. 상태 관리, Lit과의 공존, 대화상자 표시, 성능 확인을 다룹니다.
Implement or modify Composio's Python SDK, the code used to integrate its features into Python applications. Covers tools, sessions, authentication settings, connected accounts, client integration, and shared models under python/composio.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Keep TypeScript and Python SDKs consistent when shared behavior or backend APIs change. Aligns public API names, use of generated clients, and documentation examples, including updates to the fixed versions of generated clients.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Implement or change behavior in Composio’s TypeScript SDK, the library used to integrate Composio into applications. Covers tools, sessions, authentication settings, connected accounts, and generated interfaces in @composio/core and shared TypeScript packages.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Check documentation and operator scripts against current code and command conventions. Correct confirmed mismatches in small, focused changes, publish them through a pull request, and report what was inspected when no update is needed.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Read-only audit of a folder of existing multilingual blog posts: translation coverage, parity, hreflang and canonical consistency, meta-tag parity, and stale translations, with a prioritized report. Use when the user says "locale audit", "check translations", "multilingual audit", "hreflang check", "Uebersetzungen pruefen" about posts that already exist. Not for creating or fixing translations (blog-translate, blog-localize, blog-multilingual) or for a site-wide technical hreflang crawl (claude-seo seo-hreflang).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
MANDATORY for every coding agent and contributor touching localized content — keep all five localization surfaces (dashboard UI keys, wiki page, full mirrored guides, locale-aware formatting, language switchers) in parity across every supported language. Use automatically (without being asked) whenever you add or change user-visible UI copy, add an i18n key, edit README-EN.md or a localized guide, edit wiki/index.html, or add a language surface.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Verify a rewrite slice against its obligations: preflight, capture fresh test evidence, audit translationese and parity, update the ledger. Use after /phx:work finishes a rewrite slice, or before claiming parity.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design environment strategy for testing across dev, CI, preview, staging, and production — Docker Compose test infrastructure, multi-stage Dockerfiles, seed-data lifecycle, per-PR preview environments, production parity, and external-dependency stubbing at the HTTP boundary. Use when: "set up test environment," "docker-compose for tests," "per-PR preview environment," "staging parity," "spin up test infra," "environment tiers." Not for: choosing mock-vs-stub-vs-fake per dependency — use service-virtualization; factory and fixture data patterns — use test-data-management; pipeline/Actions config — use ci-cd-integration. Related: test-data-management, ci-cd-integration, contract-testing, service-virtualization.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Define and prioritize features with strategic traceability during PRD v0.3 Commercial Model. Triggers on requests to define features, prioritize capabilities, scope MVP, map features to pricing tiers, identify parity vs. delta features, or when user asks "what features do we build?", "what's in MVP?", "which features matter?", "feature priority", "parity features", "what's our delta?". Consumes KPI- (Outcome Definition), BR- (Pricing Model, Moat), and CFD- (Market Moat Analysis) from v0.3. Outputs FEA- entries with strategic traceability and BR-FEA- governance rules. Feeds v0.4 User Journeys.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Phase E of a WinForms-to-Avalonia migration: verify behavioral parity against Phase A contracts, record intentional differences, validate supported environments and packaging, and make evidence-based legacy cutover decisions. Use only for an explicit migration when comparing the legacy and Avalonia implementations or when the orchestrator routes here. Do not delete legacy without the cutover checklist and explicit authorization.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plan, execute, investigate, and report HitKeep quality gates through hk. Use while iterating, before calling contributor work complete, when choosing change-aware versus PR-parity versus exhaustive validation, when CI parity matters, or when investigating a failed or asynchronous gate.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Builds mean-variance, Black-Litterman, and risk parity optimization models with constraint management and rebalancing rules. Use when optimizing portfolios, implementing risk parity, or applying Black-Litterman views.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Read-only audit of a folder of existing multilingual blog posts: translation coverage, parity, hreflang and canonical consistency, meta-tag parity, and stale translations, with a prioritized report. Use when the user says "locale audit", "check translations", "multilingual audit", "hreflang check", "Uebersetzungen pruefen" about posts that already exist. Not for creating or fixing translations (blog-translate, blog-localize, blog-multilingual) or for a site-wide technical hreflang crawl (claude-seo seo-hreflang).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
serial-evidence-merge-target-parity
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
contract-gate-parity-check
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
parallel-overlay-receipt-parity
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Verify one approved SwiftUI feature slice against its behavioral parity contract with deterministic and conditional Apple-platform checks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.