'engineering' 검색 결과

UBNT/UniFi 企业 Wi-Fi 工程 (UniFi/UBNT Enterprise Wi-Fi Engineering) Master OS — automated mastery of UniFi/UBNT Enterprise Wi-Fi Engineering: top builders' mental models, tool stack, current workflows, jargon, and where to keep up. Trigger this skill when the user works on UniFi/UBNT Enterprise Wi-Fi Engineering problems and wants industry-grade thinking, tool selection, or workflow guidance. 触发词：「造大师 UBNT Wi-Fi」「UBNT WiFi 工程」「UniFi 高密度部署」「我做企业 Wi-Fi」「80 人办公网慢」

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

Orchestrate evidence-first engineering for WeChat and other mini programs from a vague idea or existing repository through project discovery, product specification, architecture, implementation, debugging, device adaptation, verification, and release readiness. Use when users ask to build a mini program from zero to one, take over an existing mini-program project, deliver a cross-stage feature, diagnose project status, coordinate development and testing, or judge whether a mini program is ready to upload or release. Enforces fact discovery, change boundaries, stage gates, evidence-calibrated status, sensitive-information redaction, and continuity after side questions.

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

Use when a product brief is finalized and ready to hand off to the engineering team, or when asked to send a brief to Apex, kick off engineering work, or start development on a product spec. Examples: "hand this off to engineering", "send brief to Apex", "start building this", "kick off dev on this spec".

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

Audit existing resilience — identify untested failure modes and chaos engineering gaps. Use when asked "how resilient are we", "what failure modes are untested", or "find our chaos engineering gaps".

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

Provides chaos engineering best practices for resilience testing, fault injection, and game day planning. Use when designing resilience experiments, configuring chaos tools, planning game days, or when user mentions 'chaos engineering', 'resilience', 'litmus', 'game day', 'fault injection', 'chaos monkey', 'blast radius', 'steady state', 'failure mode'.

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

Systems engineering covering requirements management, the V-model lifecycle, integration planning, verification and validation (V&V), interface control, trade studies, and the NASA Systems Engineering Handbook. Spans the full lifecycle from concept through operations and disposal. Includes requirements decomposition, traceability matrices, configuration management, and technical performance measures. Use when managing complex system development, writing requirements, planning integration, or conducting V&V activities.

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

[Deprecated] engineering bridge merged. Use `cm-mcp-engineering` instead.

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

Nature-style engineering manuscript reviewer skill for testing devices, robots, platforms, systems, algorithms embodied in physical systems and engineering methods against requirements, validation, benchmarking, uncertainty, robustness and failure modes.

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

Analyze and engineer protein glycosylation. Scan sequences for canonical N-glycosylation sequons (N-X-S/T with X not proline, including overlapping sites), predict O-GalNAc hotspots, read glycan notation, and reach the curated external tooling (NetNGlyc, NetOGlyc, GlycoShield, GlycoWorkbench, GlyTouCan, GlyConnect). Use this skill for therapeutic antibody glycoengineering and afucosylation for ADCC, Fc glycan control, glycan shielding in vaccine immunogen design, sequon removal or insertion, and half-life engineering through sialylation. Also trigger on N-glycosylation, sequon, NXS/NXT, O-glycosylation, glycoform heterogeneity, afucosylation, high-mannose, GlyTouCan, or WURCS.

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

Reverse engineers malware binaries using NSA's Ghidra disassembler and decompiler to understand internal logic, cryptographic routines, C2 protocols, and evasion techniques at the assembly and pseudo-C level. Activates for requests involving malware reverse engineering, disassembly analysis, decompilation, binary analysis, or understanding malware internals.

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

Executes authorized phishing simulation campaigns to assess an organization's susceptibility to email-based social engineering attacks. The tester designs realistic phishing scenarios, builds credential harvesting infrastructure, sends targeted phishing emails, and tracks open rates, click-through rates, and credential submission rates to measure human security awareness. Activates for requests involving phishing simulation, social engineering assessment, email security testing, or security awareness measurement.

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

Prevents overengineering when designing, implementing, refactoring, or reviewing software. Use when the user asks to implement a feature, add an abstraction, refactor code, review a design, simplify existing code, or make an architectural decision. Also triggers when the user asks if code is too complex, whether to abstract something, or how to structure something. Do not use for deployment, infrastructure configuration, or debugging runtime errors unrelated to code structure.

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

Use when a task needs the judgment of an Automotive Engineering Technician — setting up and instrumenting test equipment (strain-gauge bridges, thermocouples, load/torque sensors) to an engineer's written test plan, selecting DAQ sample rate and an SAE J211 CFC filter class for a vehicle test channel, verifying instrument calibration (torque wrench, thermocouple, load cell, shunt-cal check on a strain bridge) against a traceable standard before a test run, reducing dyno or road-load test data (SAE J1349 power correction, rainflow-counted durability damage fraction) into engineering units, and documenting test results against the engineer's target with stated margin. Distinct from an automotive engineer (owns the system-level design decisions — structure, powertrain sizing, suspension geometry, NVH) — this role installs the sensors, configures the DAQ, executes the instrumented test, and reduces the data under a design and test plan the engineer specified.

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

Generates structured engineering specs (backend or frontend) from feature descriptions, designs, or ticket references. Triggers on "spec", "story", "ticket", "engineering spec", "write a story for", "write a spec for", "create a ticket for".

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

Patterns for vibe coding that produce production-quality output instead of garbage. Covers prompt engineering for AI coding, verification without reading every line, accept/reject/refine decision framework, architectural guardrails, context management (CLAUDE.md, .cursor/rules), TDD-driven vibe coding, screenshot-driven development, diff review discipline, and the anti-patterns that destroy quality. Activate on: "vibe coding", "AI coding quality", "Claude Code workflow", "AI-assisted development", "how to use AI for coding", "coding with AI", "agentic engineering workflow", "AI code quality", "vibe code without garbage", "production quality AI code", "CLAUDE.md setup", "cursorrules setup", "pre-commit hooks for AI", "TDD with AI", "test-driven vibe coding". NOT for: multi-person collaborative coding sessions (use cooperative-vibe-coding), building AI/LLM applications (use ai-engineer), prompt engineering for non-coding LLM use cases (use prompt-engineer).

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

Runtime router for context decisions during a task — decide read-more / stop / ask / assume / delegate, pick a minimal read-set, and time compaction. Front-page mental model is Write / Select / Compress / Isolate; a lazy pattern index routes to 25 context-engineering patterns, one reference per decision. Use when context is near budget, a long session is degrading, you must choose what to read for a task, or you are deciding /compact vs /clear vs a sub-agent. NOT for structural .claude/ overhead audits (see mk:context-audit); NOT for owning persistence (see mk:memory); NOT for USD cost (see mk:budget).

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

Expert-level tissue engineering covering scaffold design, cell culture, bioreactors, stem cells, vascularization, and clinical translation of engineered tissues.

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

Expert-level structural engineering covering structural analysis, steel and concrete design, load combinations, deflection, connections, and building codes.

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

Expert-level neural engineering covering neural interfaces, brain-computer interfaces, neural signal processing, deep brain stimulation, and neuroprosthetics.

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

Expert-level reaction engineering covering reaction kinetics, reactor design, ideal and non-ideal reactors, catalysis, and reactor scale-up.

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

Expert-level environmental engineering covering water treatment, wastewater treatment, air quality, solid waste, site remediation, and environmental regulations.

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

Expert-level clinical engineering covering medical equipment management, hospital technology systems, healthcare IT integration, safety standards, and health technology assessment.

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

Design, audit, harden, review, or upgrade MCP servers and MCP Apps with revision-aware protocol profiles, explicit HTTP/deployment boundaries, capability-centered validation, bilingual reporting, and reproducible evidence. Use for MCP server architecture, JSON-RPC or Streamable HTTP bugs, security hardening, protocol-version migration, MCP Apps widget boundaries, review reconciliation, test planning, and public engineering evidence.

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

Plan and execute authorized vishing (voice phishing) pretext calls to assess employee susceptibility to social engineering and evaluate security awareness controls.

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