'complexity' 검색 결과

Compares code relationships before and after a branch, pull request, or release change using Trailmark. Flags structural security regressions, such as removed authorization checks or newly reachable sensitive operations, and provides evidence for reviewers.

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

• Checking structural security changes before merging a PR
• Reviewing call paths after a security fix
• Assessing attack surface changes in a release

Assesses smart contract and blockchain codebases against Trail of Bits’ nine-category maturity framework. Produces evidence-backed ratings covering areas such as arithmetic, access controls, documentation, and testing, plus a prioritized improvement roadmap with effort estimates.

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

• Assessing the maturity of a smart contract project
• Identifying gaps in tests and documentation
• Reviewing access controls and operational practices together

Assess API business workflows for flaws that automated scanners can miss. The skill examines skipped steps, simultaneous transactions, authentication tokens, GraphQL, and webhooks, helping testers document weaknesses and their financial or operational impact during authorized assessments.

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

• Reviewing order and payment workflow integrity
• Testing concurrent coupon redemption or transfers
• Assessing JWT validation and GraphQL controls

Plan stakeholder conversations before retiring a product or feature. Get an ordered sequence of meetings, with questions, commitments, warning signs, and required outcomes, adjusted to the scale and complexity of the retirement.

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

• Planning conversations before a product retirement
• Checking promises made by Sales before announcing
• Coordinating a retirement involving resellers

Choose a sales approach based on product price, complexity, and buyer needs. This skill helps plan self-service trials, human sales involvement, and experiences that let prospects recognize value before purchasing.

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

• Choosing between product-led and sales-led growth
• Improving conversion from free users to paying customers
• Reducing the time until users first experience value

Guide an AI agent through code changes with explicit assumptions, simple implementations, focused edits, and testable goals. Use it for bug fixes, features, refactoring, or reviews to reduce guesswork and unnecessary changes.

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

• Fixing a bug with a test that reproduces it
• Adding a feature without expanding its scope
• Refactoring while preserving existing behavior

Choose a visual direction for landing pages using WebGL, a browser graphics technology. Balance brand style with readable copy, clear calls to action, mobile performance, accessibility, and implementation effort, then define fallbacks and build priorities.

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

• Choosing a visual direction for a WebGL landing page
• Planning a launch page around a 3D product model
• Improving mobile performance and reducing motion

Work through repeated failed fixes or difficult technical choices using five perspectives: practical action, missing information, simplification, architecture, and challenged assumptions. Compare alternatives and disagreements, then receive a recommendation while keeping the final decision with the user.

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

• Reconsider a fix that has failed repeatedly
• Compare difficult database or architecture choices
• Reduce scope when complexity blocks progress

Analyze files or modules for duplicated code, excessive complexity, and violations of SOLID, five software design principles. Get prioritized refactoring suggestions with affected locations, risks, estimated effort, and testing needs to guide code improvements.

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

• Reviewing responsibilities in oversized files and classes
• Finding duplicated code and deeply nested logic
• Prioritizing refactoring by impact, risk, and effort

Simplify cluttered interfaces by reviewing information, visual styling, interactions, copy, and code. Keep essential functionality and accessibility while clarifying the main action, consolidating related elements, and revealing secondary details only when needed.

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

• Decluttering a screen with too many competing buttons
• Reducing unnecessary colors, borders, and nested cards
• Shortening forms and simplifying interaction steps

Design modules that expose simple interfaces while hiding substantial behavior. Use shared terms and principles to assess interface complexity, decide where behavior can be swapped, and organize code so callers and tests use the same interface.

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

• Simplify a module interface
• Review module structure during refactoring
• Decide where behavior should be swappable

Explore a codebase to find tightly coupled or fragmented modules, then compare interface designs that hide complexity behind simpler entry points. Produces a GitHub issue proposing a refactor, including dependency handling, testing impact, and design trade-offs.

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

• Finding architectural refactoring opportunities
• Consolidating tightly coupled modules
• Comparing interfaces for easier boundary testing

Create background workers that analyze code, detect exposed secrets, learn code patterns, or generate API documentation. Combine predefined processing stages or start from presets, configure target files in YAML, and inspect worker status and analysis results.

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

• Scan authentication code for security issues and exposed secrets
• Generate API documentation from endpoints and types
• Analyze code complexity and dependencies

Compare estimated AI model costs for a task using its complexity and expected text volume. Get a suitable low-cost recommendation, a cheaper but riskier alternative, and a premium option, with explicit assumptions behind the estimates.

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

• Choosing a model for a bulk code refactor
• Comparing model costs for a security review
• Estimating costs for long-document analysis

Review progress while solving a math problem by organizing previous attempts, checking intermediate results, and assessing growing complexity. The skill recommends whether to continue, adjust the approach, switch strategies, or tackle a smaller problem first.

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

• Review an approach when stuck on a math problem
• Assess calculations that keep getting more complicated
• Check intermediate results

Explore code through structured summaries of functions, calls, branches, and variable usage. Use the tldr commands to locate relevant files, trace change impacts, find affected tests, and identify potentially unused code before inspecting the implementation.

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

• Understanding an unfamiliar codebase
• Tracing callers and the impact of a change
• Investigating bugs across multiple files

Define the scope of SDK behavior changes, including required behavior, compatibility obligations, unsupported cases, and existing alternatives. Guide implementation toward existing code paths, and reassess the design when review feedback introduces repeated complexity or expands supported behavior.

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

• Define the supported scope before changing SDK behavior
• Assess compatibility with released APIs and saved data
• Revisit a design as review findings accumulate

Cleans redundant comments, dead code, duplication, and unnecessary complexity from branch changes or selected files. Establishes passing regression tests first, then checks that cleanup preserves existing behavior and public APIs using the project's quality tools.

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

• Cleaning up recent AI-generated code changes
• Simplifying redundant code in selected files
• Adding regression coverage before cleanup

Create or update hierarchical AGENTS.md files that explain a project's structure, commands, and conventions. Analyze directory complexity to choose useful locations, then keep local guidance concise and avoid repeating parent instructions.

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

• Documenting project conventions for coding agents
• Adding guidance for complex directories
• Updating existing AGENTS.md files

Look up current research information using Perplexity's Sonar Pro Search or Sonar Reasoning Pro models through OpenRouter. Automatically selects the best model based on query complexity. Search academic papers, recent studies, technical documentation, and general research information with citations.

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

Medicinal chemistry filters. Apply drug-likeness rules (Lipinski, Veber), PAINS filters, structural alerts, complexity metrics, for compound prioritization and library filtering.

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

Comprehensive biosignal processing toolkit for analyzing physiological data including ECG, EEG, EDA, RSP, PPG, EMG, and EOG signals. Use this skill when processing cardiovascular signals, brain activity, electrodermal responses, respiratory patterns, muscle activity, or eye movements. Applicable for heart rate variability analysis, event-related potentials, complexity measures, autonomic nervous system assessment, psychophysiology research, and multi-modal physiological signal integration.

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

Query the OFR (Office of Financial Research) Hedge Fund Monitor API for hedge fund data including SEC Form PF aggregated statistics, CFTC Traders in Financial Futures, FICC Sponsored Repo volumes, and FRB SCOOS dealer financing terms. Access time series data on hedge fund size, leverage, counterparties, liquidity, complexity, and risk management. No API key or registration required. Use when working with hedge fund data, systemic risk monitoring, financial stability research, hedge fund leverage or leverage ratios, counterparty concentration, Form PF statistics, repo market data, or OFR financial research data.

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

Apply John Ousterhout-inspired software design rules when reducing complexity, designing module boundaries, or reviewing APIs and abstractions.

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