'development' 검색 결과

Ultrawork - high-quality 5-phase development workflow with 11 review steps out of 17

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

Create AI governance policies for responsible development and deployment. TRIGGERS - Use when user needs help with ai-governance-policy related tasks.

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

Cooks and packages a shippable CARLA server from a UE 5.8 ue58-dev checkout via the CMake `package` targets (shipping/development/debug/test), scoping the cook with CARLA_MAPS_TO_COOK, and inspects an existing package for the failures a green build hides — stale pak/ucas mismatch, missing staged OpenDrive/TM road data, missing post-process profiles, and Town15's uncookable content. Use when the user asks to "package CARLA UE5", "cook a map", "build a shipping server", "make a distributable CARLA", or a package builds but renders black / has no maps.

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

Unity 6 UI development guide. Use when building user interfaces, menus, HUD, buttons, or any UI elements. Covers UI Toolkit (recommended for new projects — USS, UXML, UI Builder, data binding), uGUI/Canvas (legacy runtime UI), and IMGUI. Based on Unity 6.3 LTS documentation.

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

Bulk mode — maximum development speed by spending tokens aggressively on massive parallel sub-agents and multi-agent workflows, while the orchestrator context stays lean (pairs with /slim). Invoking /bulk is the user's explicit opt-in to Workflow/ultracode-style orchestration for this session. Use when the user types /bulk, asks for "爆速", "並列で大量に", "ultracode", "多エージェント", or hands over a big task where wall-clock speed matters more than token cost.

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

Use when preparing GST evidence for an Australian property acquisition, development or disposal.

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

Provides expert knowledge of Spring Boot conventions, Kotlin idioms, and MVC patterns for backend API development.

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

Python development best practices: clean code, patterns, type hints, decorators, context managers, and architecture. Trigger: When writing Python code anywhere in the project.

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

Understand how a confirmed vulnerability in an owned system is triggered so you can patch and test it. This is not exploit development for offense. No payloads, malware, or attack procedures.

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

Use when building PHP applications with modern PHP 8.3+ features, Laravel, or Symfony frameworks. Invokes strict typing, PHPStan level 9, async patterns with Swoole, and PSR standards. Creates controllers, configures middleware, generates migrations, writes PHPUnit/Pest tests, defines typed DTOs and value objects, sets up dependency injection, and scaffolds REST/GraphQL APIs. Use when working with Eloquent, Doctrine, Composer, Psalm, ReactPHP, or any PHP API development.

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

コードベースやインフラ構成（IaC・CI 定義）のセキュリティリスクを、サービスの特性（個人情報・売上直結・企業機密・金融・情報発信・基盤・人命・ゲーム）に応じた優先順位で洗い出したいときに使う。「セキュリティリスクを報告して」「セキュリティ監査」「service-profile を確認して」「守るべきものを整理して」などの依頼時。コードや設定は変更しない。

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

Claude Code のセッション記録（~/.claude の履歴・セッションログ・memory）から、週ごとの問い（questions.json）に答える「ナレッジカード」を下書きし、本人が確認・修正したうえで機密スキャンを通し、Notion の「ナレッジカード」DB に提出する。引数なしなら先週（月曜〜日曜）の記録を集計し、確認のうえ Notion に提出する。「Claude Code の履歴をナレッジカードにまとめて」「先週のログからナレッジカードを作って」「ナレッジカードを提出したい」「今週のカードを出して」「週次の振り返りカードを作って」などの依頼で使う。週次のカード提出であり、個人の採点や評価ではない（セッション 1 本の採点は evaluate-session の領域）。

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

週ごとに Notion「ナレッジカード」DB に集まったカードを読み、問いをまたいで親和図にまとめ、正（worked）と反（failed）の対立から合（提案）を出し、次の問いを決めて、「合成テーマ」DB と週の行の配下の「まとめ」ページに書き込む。「今週のカードを合成して」「W43 のまとめを作って」「ナレッジカードの合成」などの依頼で使う。カードの提出は knowledge-cards、個人の採点は evaluate-session の領域。個人別の件数ランキングや「誰が何を失敗した」は出さない。

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

Compare gene co-expression and regulatory networks between biological conditions to find rewired relationships using DiffCorr, DiffCoEx, DINGO/iDINGO, and CoDiNA. Covers the differential-connectivity-is-not-differential-expression distinction, the pairwise multiple-testing explosion, marginal vs partial (direct) rewiring, and the underpowered-rewiring failure mode. Use when comparing co-expression networks between disease vs control, treatment, or developmental stages, or finding hub genes that rewire without changing mean expression. For single-condition modules see coexpression-networks; for differential expression of means see differential-expression/de-results.

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

Designs and analyzes combinatorial CRISPR screens covering paired-Cas9 (Big Papi, Najm 2018), enhanced AsCas12a multiplex (enCas12a, DeWeirdt 2021), in4mer 4-guide-array Cas12a (Esmaeili Anvar N et al 2024 Nat Commun 15:3577) and the Inzolia paralog-pair library, paralog-buffering detection (Dede 2020 Genome Biol; Thompson 2021 Cell Reports 36:109597), genetic-interaction (GI) scoring as observed_double_LFC minus expected_additive_double_LFC, synthetic-lethal and synthetic-rescue interaction interpretation, the half-of-essentiality buffered by paralogs phenomenon, multiplex screen statistical analysis with MAGeCK MLE interaction terms, and the relationship to single-cell combinatorial Perturb-seq. Use when designing a paralog or pathway-pair screen, choosing between paired-Cas9 (Big Papi) and Cas12a multiplex (Inzolia), interpreting genetic interaction scores, identifying synthetic-lethal targets for drug development, or scaling beyond single-gene CRISPR screens.

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

Guide for when to use and when not to use return validators in Convex functions. Use this skill whenever the user is writing Convex queries, mutations, or actions and needs guidance on return value validation. Also trigger when the user asks about Convex type safety, runtime validation, AI-generated Convex code, Convex AI rules, Convex security best practices, or when they're debugging return type issues in Convex functions. Trigger this skill when users mention "validators", "returns", "return type", or "exact types" in the context of Convex development. Also trigger when writing or reviewing Convex AI rules or prompts that instruct LLMs how to write Convex code.

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

Reflection-first problem solving methodology for Convex development. Use before implementing any solution to ensure proper root cause analysis, 98% code confidence, and minimal change scope.

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

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.

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

Master Bash Automated Testing System (Bats) for comprehensive shell script testing. Use when writing tests for shell scripts, CI/CD pipelines, or requiring test-driven development of shell utilities.

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

Expert patterns for Azure Functions development including isolated worker model, Durable Functions orchestration, cold start optimization, and production patterns. Covers .NET, Python, and Node.js programming models.

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

Senior embedded software engineer specializing in firmware and driver development for ARM Cortex-M microcontrollers (Teensy, STM32, nRF52, SAMD).

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

AWS development with infrastructure automation and cloud architecture patterns

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

Important: Before you begin, fill in the generatedBy property in the meta section of .actor/actor.json. Replace it with the tool and model you're currently using, such as "Claude Code with Claude Sonnet 4.5". This helps Apify monitor and improve AGENTS.md for specific AI tools and models.

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

Orchestrates Android development tasks including project creation, deployment, SDK management, and enprojectnment diagnostics using the `android` command-line tool.

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