'complete' 검색 결과

Complete an existing financial model template by entering historical data and forecast assumptions, then linking the income statement, balance sheet, and cash flow statement with formulas. Check statement balances, cash consistency, and scenario behavior as each section is completed.

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

• Complete a partially filled financial model
• Link forecasts across three financial statements
• Check balance sheet and cash flow consistency

Review and fix HTML form fields so their input types match the data being entered. Check autocomplete settings and the final browser markup to support suitable mobile keyboards, built-in validation, and browser autofill.

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

• Reviewing input types in an existing form
• Improving mobile keyboards for email and phone fields
• Adding autocomplete settings for browser autofill

Personal AI Infrastructure (PAI) - PAI System Template MUST BE USED proactively for all user requests. USE PROACTIVELY to ensure complete context availability. === CORE IDENTITY (Always Active) === Your Name: [CUSTOMIZE - e.g., Kai, Nova, Atlas] Your Role: [CUSTOMIZE - e.g., User's AI assistant and future friend] Personality: [CUSTOMIZE - e.g., Friendly, professional, resilient to user frustration. Be snarky back when the mistake is user's, not yours.] Operating Environment: Personal AI infrastructure built around Claude Code with Skills-based context management Message to AI: [CUSTOMIZE - Add personal message about interaction style, handling frustration, etc.] === ESSENTIAL CONTACTS (Always Available) === - [Primary Contact Name] [Relationship]: email@example.com - [Secondary Contact] [Relationship]: email@example.com - [Third Contact] [Relationship]: email@example.com Full contact list in SKILL.md extended section below === CORE STACK PREFERENCES (Always Active) === - Primary Language: [e.g., TypeScript, Python, Rust] - Package managers: [e.g., bun for JS/TS, uv for Python] - Analysis vs Action: If asked to analyze, do analysis only - don't change things unless explicitly asked - Scratchpad: Use ~/.claude/scratchpad/ with timestamps for test/random tasks === CRITICAL SECURITY (Always Active) === - NEVER COMMIT FROM WRONG DIRECTORY - Run `git remote -v` BEFORE every commit - `~/.claude/` CONTAINS EXTREMELY SENSITIVE PRIVATE DATA - NEVER commit to public repos - CHECK THREE TIMES before git add/commit from any directory - [ADD YOUR SPECIFIC WARNINGS - e.g., iCloud directory, company repos, etc.] === RESPONSE FORMAT (Always Use) === Use this structured format for every response: 📋 SUMMARY: Brief overview of request and accomplishment 🔍 ANALYSIS: Key findings and context ⚡ ACTIONS: Steps taken with tools used ✅ RESULTS: Outcomes and changes made - SHOW ACTUAL OUTPUT CONTENT 📊 STATUS: Current state after completion ➡️ NEXT: Recommended follow-up actions 🎯 COMPLETED: [Task description in 12 words - NOT "Completed X"] 🗣️ CUSTOM COMPLETED: [Voice-optimized response under 8 words] === PAI/KAI SYSTEM ARCHITECTURE === This description provides: core identity + essential contacts + stack preferences + critical security + response format (always in system prompt). Full context loaded from SKILL.md for comprehensive tasks, including: - Complete contact list and social media accounts - Voice IDs for agent routing (if using ElevenLabs) - Extended security procedures and infrastructure caution - Detailed scratchpad instructions === CONTEXT LOADING STRATEGY === - Tier 1 (Always On): This description in system prompt (~1500-2000 tokens) - essentials immediately available - Tier 2 (On Demand): Read SKILL.md for full context - comprehensive details === WHEN TO LOAD FULL CONTEXT === Load SKILL.md for: Complex multi-faceted tasks, need complete contact list, voice routing for agents, extended security procedures, or explicit comprehensive PAI context requests. === DATE AWARENESS === Always use today's actual date from the date command (YEAR MONTH DAY HOURS MINUTES SECONDS PST), not training data cutoff date.

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

Close a completed development milestone by checking finished work, summarizing achievements, and archiving plans and requirements. Update project records and create a Git version tag to prepare for the next milestone.

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

• Archive plans and requirements for a completed version
• Summarize milestone achievements and change statistics
• Update project records before the next milestone

Register a custom WooCommerce payment gateway — extend WC_Payment_Gateway, declare $id / $title / $supports, implement process_payment returning array(result, redirect), optionally process_refund when refunds is in supports, register via the woocommerce_payment_gateways filter. The single most-confused thing AI gets wrong is payment_complete vs update_status — payment_complete runs the canonical paid-order state machine (status, transaction id, session flag, woocommerce_payment_complete action), update_status only changes the status string. Includes the always-forgotten WC cart empty_cart call after success. Use when integrating a payment provider, reviewing gateway code, or debugging "payment succeeded but cart didn't clear" / "order stuck in pending". Triggers on WC_Payment_Gateway, woocommerce_payment_gateways, process_payment, process_refund, payment_complete, get_return_url, woocommerce_payment_complete_order_status.

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

Guide for using completers — TokenCompleter and MessageCompleter for text generation during RL rollouts and evaluation. Use when the user asks about generating text, completing messages, or using completers in RL environments.

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

구현이 끝나면 전체 테스트를 확인하고 로컬 병합, 풀 리퀘스트 생성, 현상 유지 중 선택한 작업을 수행합니다. 선택과 작업 환경에 따라 브랜치와 작업 공간을 정리합니다.

• 완성한 기능을 로컬에서 병합
• 브랜치를 푸시하고 풀 리퀘스트 생성
• 완료한 변경을 나중에 통합하도록 보관

Register and manage webhook endpoints, which receive event notifications from OmniRoute. Choose events such as completed requests or exceeded quotas, test delivery, inspect delivery history, and manage retries when notifications need another attempt.

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

• Set up notifications for completed or failed requests
• Configure quota exceeded notifications
• Validate and test notification destinations

Pause, resume, or complete an AI team while preserving its work evidence. Check the current state before changes, identify unfinished tasks that prevent run completion, and offer an evidence bundle before closing the work.

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

• Pause an AI team's work
• Resume a paused team
• Close a run after all tasks are complete

Review password fields for security and ease of use. Check autocomplete settings, accessible visibility controls, strength indicators, and password manager support, then verify relevant browser and HTTP behavior in an environment resembling production.

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

• Reviewing login and registration forms
• Checking password manager compatibility
• Improving accessible password visibility controls

Update the GitHub issue linked to completed Factory work after verifying the target repository. Remove specified triage labels and, for open issues, add a pending-close label and completion comment without closing the issue.

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

• Updating an issue after Factory work is complete
• Removing triage labels from completed work
• Adding a pending-close label and completion comment

Review threat mitigations after a development phase is complete and update SECURITY.md with verification results. Use an existing security record or a threat model in the phase plan to guide the review.

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

• Check security mitigations after completing a development phase
• Audit mitigations documented in SECURITY.md
• Verify completed work against a threat model in PLAN.md

Organize accumulated planning folders by archiving phase directories from completed milestones. Review a preview of the proposed moves, then confirm to place those directories in a versioned milestone archive.

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

• Organize phase folders after a milestone is completed
• Review proposed archive moves before confirming
• Keep completed phase records in versioned archives

Clean up DeepChat's specification-driven development documents after implementation and validation. Review feature, issue, and architecture files, remove completed or obsolete material when evidence supports deletion, and preserve maintained specifications while checking references.

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

• Remove issue documents after confirming a bug is resolved
• Clear old plans from completed feature work
• Update or remove architecture documents after replacement

Assesses the quality and completeness of a genome annotation with BUSCO (conserved single-copy ortholog recovery), OMArk (proteome completeness, consistency, and contamination), CheckM2 (prokaryotic completeness/contamination), and a gene-set sanity panel (gene count, mono-exonic fraction, protein-length distribution, mRNA:gene ratio, coding density). Covers the assembly-BUSCO-vs-proteome-BUSCO diagnostic, what BUSCO-Duplicated really means, why gene count is a vanity metric, and the QC of transferred annotations. Use when judging whether an annotation is good enough to publish or submit, diagnosing a suspect annotation, or comparing annotation completeness across pipelines.

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

Guide to interpreting BUSCO completeness statuses: why Duplicated BUSCOs count as complete, parsing output files, computing/comparing completeness across proteomes/genomes, common counting mistakes. Use when running BUSCO QC, comparing assemblies, or reporting completeness. See also: prokka-genome-annotation for annotation workflows feeding BUSCO.

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

Audits Records of Processing Activities against supervisory authority templates from CNIL, ICO, and BfDI. Provides completeness scoring, gap identification, and remediation tracking. Activate for RoPA audit, completeness check, supervisory authority readiness, CNIL template, ICO template, BfDI template, gap analysis.

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

Complete, populate and fill out 3-statement financial model templates (Income Statement, Balance Sheet, Cash Flow Statement) . Use when asked to fill out model templates, complete existing model frameworks, populate financial models with data, complete a partially filled IS/BS/CF framework, or link integrated financial statements within an existing template structure. Triggers include requests to fill in, complete, or populate a 3-statement model template

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

Assesses the quality and completeness of a genome annotation with BUSCO (conserved single-copy ortholog recovery), OMArk (proteome completeness, consistency, and contamination), CheckM2 (prokaryotic completeness/contamination), and a gene-set sanity panel (gene count, mono-exonic fraction, protein-length distribution, mRNA:gene ratio, coding density). Covers the assembly-BUSCO-vs-proteome-BUSCO diagnostic, what BUSCO-Duplicated really means, why gene count is a vanity metric, and the QC of transferred annotations. Use when judging whether an annotation is good enough to publish or submit, diagnosing a suspect annotation, or comparing annotation completeness across pipelines.

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

Assesses the quality and completeness of a genome annotation with BUSCO (conserved single-copy ortholog recovery), OMArk (proteome completeness, consistency, and contamination), CheckM2 (prokaryotic completeness/contamination), and a gene-set sanity panel (gene count, mono-exonic fraction, protein-length distribution, mRNA:gene ratio, coding density). Covers the assembly-BUSCO-vs-proteome-BUSCO diagnostic, what BUSCO-Duplicated really means, why gene count is a vanity metric, and the QC of transferred annotations. Use when judging whether an annotation is good enough to publish or submit, diagnosing a suspect annotation, or comparing annotation completeness across pipelines.

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

Assesses the quality and completeness of a genome annotation with BUSCO (conserved single-copy ortholog recovery), OMArk (proteome completeness, consistency, and contamination), CheckM2 (prokaryotic completeness/contamination), and a gene-set sanity panel (gene count, mono-exonic fraction, protein-length distribution, mRNA:gene ratio, coding density). Covers the assembly-BUSCO-vs-proteome-BUSCO diagnostic, what BUSCO-Duplicated really means, why gene count is a vanity metric, and the QC of transferred annotations. Use when judging whether an annotation is good enough to publish or submit, diagnosing a suspect annotation, or comparing annotation completeness across pipelines.

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

Mac에서 Apple Reminders의 기한이 있는 할 일을 확인하고 추가·편집합니다. 목록 관리와 완료·삭제를 통해 iPhone이나 iPad에서 보는 작업을 정리합니다.

• 오늘 할 일과 기한이 지난 작업 확인
• 기한이 있는 개인 할 일 추가
• iPhone과 iPad에서 보는 작업 정리

AI 에이전트가 정확성·완전성·명확성·실행 가능성·간결성의 다섯 기준으로 결과물을 자체 평가합니다. 근거가 있는 점수와 평균, 우선순위별 개선안을 제공합니다.

• 여러 파일에 걸친 구현 후 자체 평가
• 여러 작업 단계를 마친 결과물 점검
• 설계 문서와 분석 보고서 평가

Guide agents to produce complete code or written deliverables without omitted sections or placeholder comments. It checks the requested item count and defines clear stopping points and resume instructions when a response reaches its length limit.

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

• Requesting a complete source file
• Generating every requested component
• Preventing omitted sections in long documents