'systematic' 검색 결과

Systematically test authorized targets for SQL, XSS, SSTI, XXE, command, and request-smuggling injection classes.

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

Token architecture, component specifications, and slide generation. Three-layer tokens (primitive→semantic→component), CSS variables, spacing/typography scales, component specs, strategic slide creation. Use for design tokens, systematic design, brand-compliant presentations.

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

Systematic competitor tracking that feeds CMO positioning, CRO battlecards, and CPO roadmap decisions. Use when analyzing competitors, building sales battlecards, tracking market moves, positioning against alternatives, or when user mentions competitive intelligence, competitive analysis, competitor research, battlecards, win/loss, or market positioning.

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

Track Two / internal innovation system for running small, fast experiments outside the core business. Runs in three modes — Diagnostic for designing the full Protoloop from scratch (intake channels, loop structure, team, exit paths), Review for running the monthly heartbeat meeting (loop-by-loop decisions, forward-loading, portfolio health), and Alert Triggers for defining tripwires that protect, feed, and maintain momentum in the system. Updates company-context.md after every run. Triggers on questions about innovation pipelines, intrapreneurship, Track Two strategy, experimentation systems, handling ideas that don't fit the core business, or building systematic exploration alongside exploitation. Based on 20 years of practice by Eterdis (eterdis.com).

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

Use for bugs, test failures, broken behavior, or unexpected results; enforces 4-phase root-cause debugging before fixes.

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

Extract and consolidate reusable components, design tokens, and patterns into your design system. Identifies opportunities for systematic reuse and enriches your component library. Use when the user asks to create components, refactor repeated UI patterns, build a design system, or extract tokens.

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

Extract and consolidate reusable components, design tokens, and patterns into your design system. Identifies opportunities for systematic reuse and enriches your component library. Use when the user asks to create components, refactor repeated UI patterns, build a design system, or extract tokens.

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

Systematic improvement of existing agents through performance analysis, prompt engineering, and continuous iteration.

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

Systematically deobfuscate multi-layer PowerShell malware using AST analysis, dynamic tracing, and tools like PSDecode and PowerDecode to reveal hidden payloads and C2 infrastructure.

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

Systematically collects, categorizes, and distributes indicators of compromise (IOCs) during and after security incidents to enable detection, blocking, and threat intelligence sharing. Covers network, host, email, and behavioral indicators using STIX/TAXII formats and threat intelligence platforms. Activates for requests involving IOC collection, indicator extraction, threat indicator sharing, compromise indicators, STIX export, or IOC enrichment.

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

Build a systematic threat hunt hypothesis framework that transforms threat intelligence, attack patterns, and environmental data into testable hunting hypotheses.

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

MITRE ATT&CK is a globally-accessible knowledge base of adversary tactics, techniques, and procedures (TTPs) based on real-world observations. This skill covers systematically mapping threat actor beh

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

Systematically audit AWS S3 bucket permissions to identify publicly accessible buckets, overly permissive ACLs, misconfigured bucket policies, and missing encryption settings using AWS CLI, S3audit, and Prowler to enforce least-privilege data access controls.

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

Use Sysinternals Autoruns to systematically identify and analyze malware persistence mechanisms across registry keys, scheduled tasks, services, drivers, and startup locations on Windows systems.

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

Campaign attribution analysis involves systematically evaluating evidence to determine which threat actor or group is responsible for a cyber operation. This skill covers collecting and weighting attr

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

Execute all tasks from the task breakdown to build the feature. Use after task generation to systematically implement the planned solution following TDD approach where applicable.

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

This skill should be used when creating RFQ (Request for Quotation) documents for software development projects to send to vendors. Use this skill when you have received vague requirements from clients and need to structure them into clear, comprehensive RFQs that enable vendors to provide accurate estimates. Supports Japanese (default) and English, with systematic requirements elicitation, clarification, and markdown-formatted output.

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

This skill should be used when creating cost estimates and quotations for software development projects. Use this skill when you have an RFQ (Request for Quotation), project requirements, or a project description and need to create a comprehensive estimate with WBS, effort calculations, cost breakdowns, and ROI analysis. Supports Japanese (default) and English, with systematic work breakdown, effort estimation, and markdown-formatted estimate documents.

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

Professional contract review skill for business agreements including NDAs, MSAs, SLAs, SOWs, and software license agreements. Provides systematic clause-by-clause analysis, risk assessment with quantified scoring, red flag detection, and negotiation guidance. Use this skill when reviewing vendor contracts, partnership agreements, service agreements, or any business contract requiring risk evaluation and negotiation preparation. Triggers include "review this contract", "analyze this NDA", "check this agreement for risks", "prepare for contract negotiation", or when evaluating terms and conditions.

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

Use when evaluating, designing, drafting, revising, stress-testing, or preparing academic articles, empirical research reports, literature reviews, systematic reviews, meta-analyses, journal submissions, reviewer responses, research methods, sampling, measurement, analysis, publication readiness, or citation/source audits.

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

4-phase root cause debugging: understand bugs before fixing.

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

Ciclo de desarrollo de 8 fases: solicitudes de funciones, estado actual, planificación funcional, frontend, planificación de backend, código de backend, pruebas, casos de uso. Marco iterativo para el desarrollo sistemático de software.

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

8フェーズの開発サイクル：機能リクエスト、現状確認、機能計画、フロントエンド、バックエンド計画、バックエンドコード、テスト、ユースケース。体系的なソフトウェア開発のための反復フレームワーク。

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

8阶段开发周期：功能需求、现状检查、功能规划、前端实现、后端规划、后端代码、测试与用例。系统化软件开发的迭代框架。

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