'uis' 검색 결과

World-class growth strategy expertise combining Andrew Chen's marketplace and network effects wisdom, Brian Balfour's growth frameworks, Casey Winters' Pinterest/Grubhub playbooks, and the best of Silicon Valley growth thinking. Growth is not marketing. Growth is the systematic application of product, engineering, and data to create compounding user acquisition, activation, and retention. It's a mindset, not a department. Use when "growth strategy, how do we grow, acquisition strategy, retention strategy, viral growth, network effects, growth loops, product-led growth, plg, ltv cac, unit economics, growth model, flywheel, compound growth, channel strategy, referral program, activation rate, magic moment, aha moment, growth experimentation, growth, strategy, acquisition, retention, viral, network-effects, plg, loops, experimentation" mentioned.

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

Build a learning progression showing prerequisite-to-mastery steps for a target skill or understanding. Use when sequencing content, designing diagnostics, or mapping prerequisite gaps.

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

Guide agency acquisitions. TRIGGERS - Use when user needs help with insurance-agency-acquisition related tasks.

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

Evaluates bolt-on acquisitions for existing platforms with strategic fit, synergy quantification, and return contribution analysis. Use when screening add-on targets, building platform acquisition strategies, or modeling tuck-in economics.

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

Prepare for acquisition. TRIGGERS - Use when user needs help with acquisition-prep related tasks.

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

Design, mock up, build and review terminal UIs — full-screen TUIs, interactive CLIs and pickers, and plugin panels or popups inside a host (herdr, tmux, Neovim, k9s, lazygit). Use when designing, reviewing (from code, a live capture or a screenshot) or redesigning a TUI's layout, keybindings, states or colors, including requests that name a known TUI (lazygit, k9s, btop, yazi, helix, fzf); writing terminal mockups; building or fixing one in Ink, Textual, Bubble Tea, Ratatui or gum; mapping a color scheme (Catppuccin, Dracula, Nord, Gruvbox, Tokyo Night, Rosé Pine…) onto a TUI's theme; fixing misaligned glyphs, flicker, NO_COLOR, exit codes, signals, pipes or a broken terminal after exit; suspend or $EDITOR handoff; or profiling a slow TUI. Not for web or native GUIs, terminal-emulator, editor or shell-prompt themes.

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

Test-to-requirement coverage mapping. Reads plan acceptance criteria and test files, produces a coverage gap report showing which requirements have no tests. Use during Phase 2 (Test) or Phase 4 (Review) to verify test completeness. Named after the Nyquist sampling theorem — sufficient test coverage prevents aliased (missed) requirements. NOT for running tests (see mk:testing); NOT for structural code review (see mk:review).

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

Oracle-bound spec-review check that every structured Rollout prerequisite binds to an enforcement-type acceptance criterion. A prerequisite whose `enforced-by` is missing, dangling, or points at a non-enforcement AC is a BLOCKER (hard-blocks implementation entry via the checker fan-out verdict); a prerequisite left in free prose is ADVISORY. Read-only. Runs in the spec-review fan-out before implementation.

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

Planifie le prochain sprint : calcule la capacité (vélocité glissante 3 sprints), reporte les tickets non livrés du sprint courant, puis complète depuis le backlog par priorité jusqu'à la capacité. Présente le plan, attend validation, puis assigne les tickets au sprint. Usage: /plan-sprint [<titre-sprint-cible>]

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

Kit de ferramentas de pesquisa e design UX para Senior UX Designer/Researcher, incluindo geração de personas orientada por dados, mapeamento de jornada, frameworks de testes de usabilidade e síntese de pesquisa. Use para pesquisa do usuário, criação de personas, mapeamento de jornada e validação de design.

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

Busca web e pesquisa usando Perplexity AI. Use quando o usuário disser "pesquisar", "encontrar", "procurar", "perguntar", "pesquisar" ou "qual é o mais recente" para consultas genéricas. NÃO para docs de biblioteca/framework (use Context7) ou perguntas do workspace.

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

採用・人材戦略の専門スキル。職務記述書（JD）作成、採用計画策定、コンピテンシーモデル設計、 面接評価基準設計、オンボーディング計画をサポート。採用要件の明確化から内定後のフォローまで 一貫した人材獲得プロセスを支援。日英両言語のテンプレートを提供し、グローバル採用にも対応。 Use when: creating job descriptions, designing competency models, planning recruitment strategies, developing interview evaluation criteria, or creating onboarding plans. Triggers: "JD作成", "採用計画", "面接評価", "オンボーディング", "コンピテンシー", "人材獲得", "job description", "recruitment plan", "interview evaluation", "hiring", "talent acquisition"

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

Envoyer un vrai courrier papier — lettre PDF, carte illustrée (carte postale, carte pliée, carte carrée, carte géante), suivi, recommandé avec accusé de réception, recommandé électronique eIDAS — depuis une application, via l'API Merci Facteur. Utiliser dès qu'il s'agit d'envoyer, poster, imprimer ou expédier du courrier physique depuis du code, d'envoyer une carte depuis une application, de brancher un envoi postal sur un événement, un formulaire, un cron ou un webhook, ou de déboguer un appel sendCourrier. Couvre le contrat exact, les pièges de nommage qui font échouer l'appel, l'idempotence et le comportement en cas d'échec.

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

Knowledge base from the NASA Digital Engineering Acquisition Framework Handbook (NASA-HDBK-1004). Use for acquiring digital/model-based data under contract: the Data Requirements Description (DRD) instrument and the Appendix A DRD suite (TDP, MBx, CDMP, CSA, CR, FCA/PCA, SDT, EMDAL, REF, MRI); the Data Type 1-5 control scale; SOW/RFP/Cost-Volume contract language and data rights (FAR/DFARS, Table 3 license categories); the Requirements Exchange Format (REF/ReqIF, UUID schema) and Master Records Index; model-based data definition (MBSE, CAD/PMI, M&S credibility, BOM, release-state mapping, PLM); digital data collaboration, the four owned architectures, and interoperability standards (MIL-STD-31000, STEP/ISO 10303, ASME Y14); the four MBE interoperability use cases; and MBE Plan development. Scope is the acquisition and contracting side of digital engineering. Does not reproduce ISO/STEP/ASME/MIL-STD/SAE standard text, and the companion NASA-HDBK-1009A carries the deeper digital-engineering practitioner detail this handbook defers to.

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

Knowledge base from the FAA AMS Lifecycle V&V Guidelines (verification and validation), Version 3.0, dated April 2017. Use for applying verification and validation across the FAA Acquisition Management System (AMS) lifecycle: the verify-vs-validate distinction (built right vs. right thing), the work-product/component/product tiers, the nine V&V planning elements, the four method catalogs (Appendix C), decision-point-gated V&V (SASP, CRD, Investment Analysis, Solution Implementation, In-Service Management), the Appendix B document checklists (PRD/APB/ISPD/PMP), and the DT/OT/IOA test triad. Scope limits: this is an FAA acquisition-V&V doctrine, NOT a general SE process model, requirements-engineering manual, or test-design textbook. It borrows its core V&V definitions from CMMI v1.2 (SEI, paraphrased) and presumes the surrounding AMS lifecycle (see the FAA SEM pack); its phase tables are policy snapshots as of April 2017 and it is thin on detailed test methods, tool specifics, and anything outside FAA acquisition governance.

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

Knowledge base from the DoD Test & Evaluation Enterprise Guidebook (OUSD R&E, August 2022). Use for DoD test and evaluation (T&E) across the Adaptive Acquisition Framework — the four test communities (contractor testing, developmental DT&E, operational OT&E, live-fire LFT&E); the five operational events (Operational Demonstration, EOA, OA, IOT&E, FOT&E) and the OTRR gate; the T&E Strategy / TEMP and its IDSK, with the upstream documents that feed it and the test plans that decompose it; the T&E organizations and oversight roles (USD(R&E), DOT&E, TRMC, the Service Executives and OTAs, the T&E WIPT, CDT); and pathway-specific T&E for all six acquisition pathways (Urgent Capability, Middle Tier, Major Capability, Software, Defense Business Systems). Statutory anchors include 10 U.S.C. §4171 (IOT&E) and §4172 (LFT&E/FUSL). This is guidance, not policy: it points outward to DoDI 5000.89 and the DoDI 5000-series for binding detail, and is thin on detailed test statistics/design-of-experiments methodology, cost estimating, the Acquisition of Services pathway, and any CUI/CAC-gated companion guides.

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

Análisis de requisitos de documentos: Analiza los documentos de concepto y requisitos en la carpeta docs/, verifica los requisitos con el código actual y crea un informe de diferencias consolidado.

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

Build, refactor, or review macOS menubar apps that use Tuist and SwiftUI. Use when creating or maintaining LSUIElement menubar utilities, defining Tuist targets/manifests, implementing model-client-store-view architecture, adding script-based launch flows, or validating reliable local build/run behavior without Xcode-first workflows.

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

Prepare for acquisition. TRIGGERS - Use when user needs help with acquisition-prep related tasks.

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

Pesquisa de Voz do Cliente (VOC) antes de escrever qualquer copy — coleta a linguagem literal do público em avaliações, fóruns, redes sociais, tickets de suporte e transcrições de vendas. Use quando o usuário disser "pesquisa de público", "voz do cliente", "VOC", "o que os clientes falam", "pesquisar concorrente", "analisar reviews", "levantar objeções", "não sei o que escrever", ou quando pedir copy sem que exista seção 6 preenchida em .claude/pwdev-copy-context.md. Produz frases verbatim, não paráfrases.

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

Genera o actualiza una especificación SDD (spec.md) para HagamosTech. Úsala cuando haya que definir una nueva funcionalidad o vertical antes de tocar código, entrevistando al usuario y produciendo requisitos funcionales en notación EARS. Trigger: crear/actualizar spec, nuevo requisito, /spec.

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

Slack 인증과 메시지 작업, OpenClaw의 수신·응답을 검증합니다. API 확인과 실제 화면 조작을 구분하고 증거와 테스트 후 정리 결과를 확인합니다.

• Slack 인증과 접근 권한을 확인할 때
• 메시지 작성·편집·삭제를 시험할 때
• OpenClaw의 수신·응답을 검증할 때

OpenClaw 테스트의 메모리 증가와 부족 원인을 조사합니다. 측정값과 메모리 객체 기록을 비교해 실제 해제 누락과 테스트 프로세스의 모듈 보존을 구분하고 수정 결과를 검증합니다.

• Vitest 메모리 부족 원인을 조사합니다
• 같은 프로세스의 메모리 기록을 비교합니다
• 해제 누락과 모듈 보존을 구분합니다

유사 기업의 매출, 이익률, 가치평가 배수를 비교하는 Excel을 만듭니다. 수식, 중앙값, 사분위수와 데이터 출처를 정리해 투자나 인수 검토 자료를 준비합니다.

• 동종 기업과 기업가치 비교
• 인수 검토용 비교 자료 작성
• 업계 성장성과 수익성 비교