'structural analysis' 검색 결과

End-to-end finite element analysis in MATLAB PDE Toolbox — geometry creation, model setup, solve, and post-processing in one skill. Use when building geometry from primitives or file import, setting up femodel with BCs/loads/materials, solving thermal/structural/EM problems, and extracting or visualizing results. Covers fegeometry, multicuboid, multicylinder, multisphere, decsg, boolean ops, mesh generation, femodel, all AnalysisTypes (thermalSteady, thermalTransient, structuralStatic, structuralTransient, structuralModal, structuralFrequency, electrostatic, magnetostatic, dcConduction, harmonic EM), materialProperties, faceBC, faceLoad, cellLoad, vertexLoad, solve, interpolation, von Mises stress, principal stress, reaction forces, heat flux, pdeplot3D visualization. Triggers on: PDE Toolbox, finite element, FEA, thermal analysis, structural analysis, electromagnetic analysis, femodel, mesh, boundary conditions, stress, displacement, heat transfer, post-processing.

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

Analyze code structure with Trailmark to identify complex functions, trace input flow, assess impact across connected code, and locate privilege boundaries. The resulting JSON provides detailed evidence for deciding where to focus a code audit.

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

• Prioritizing code audit targets
• Tracing input flow and assessing impact
• Inspecting unresolved calls and type references

Prepare and run molecular dynamics simulations with OpenMM, then analyze molecular motion with MDAnalysis. Examine protein flexibility, structural changes, and protein–ligand contacts through calculations and plots of simulated trajectories.

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

• Investigating protein stability after a mutation
• Measuring structural changes and flexibility
• Tracking protein–ligand contacts

Get a quick structural overview of a codebase with Trailmark. The skill identifies programming languages, counts entry points where execution begins, and returns dependency information to support orientation before deeper analysis.

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

• Getting oriented in an unfamiliar codebase
• Checking languages and entry point counts before analysis
• Preparing a structural overview for Vivisect or Galvanize

Build a competitive analysis presentation covering market context, company performance, strengths, and weaknesses. Compare competitors using consistent metrics, visualize their market positions, and summarize lasting advantages and structural risks for strategic or investment discussions.

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

• Mapping competitors and their market positions
• Comparing peer companies using shared metrics
• Preparing a strategic review presentation

Business model classification, business model analysis, structural analysis of how a company makes money, product offering decomposition, distribution channel analysis, customer segment analysis, revenue model identification, market sizing TAM SAM SOM, competitive positioning, business unit performance, management team & leadership analysis, what does the company sell, how does the company go to market, business model type platform service product, channel mix direct vs indirect, revenue concentration risk, CEO CFO executive backgrounds and changes

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

Expert-level bioinformatics covering sequence analysis, structural bioinformatics, database searching, phylogenetic analysis, NGS data processing, single-cell analysis, and machine learning in biology.

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

Uses a known or suspected vulnerability to find related code through Trailmark's graph of calls, types, and implementations. Produces ranked review targets with reasons and limitations for follow-up security analysis.

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

• Finding variants of a known vulnerability
• Prioritizing code that shares sensitive operations
• Preparing candidates for Semgrep or CodeQL review

Compare your page with competitors ranking higher for a target query. Identify missing topics, structural differences, search intent gaps, and other page-level SEO issues, then produce a concrete brief describing what to add or change.

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

• Investigating why a competitor ranks above your page
• Finding topics missing from an existing article
• Comparing headings, tables, and media with competing pages

mdtraj molecular dynamics trajectory analysis (Python). Reads DCD/XTC/TRR/NetCDF/H5/PDB topologies and trajectories; computes RMSD vs time, radius of gyration, per-residue RMSF, residue-residue contact frequency maps, phi/psi torsions for Ramachandran plots (general + Gly/Pro), and 8-state DSSP secondary structure. Modules: trajectory I/O, geometry (distances/angles/dihedrals), structural analysis (RMSD/Rg/RMSF/SASA), contacts, hydrogen bonds, secondary structure (DSSP), NMR observables. For broader atom-selection grammar use mdanalysis-trajectory; for running MD simulations use OpenMM/GROMACS.

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

Musical form and structural analysis covering binary, ternary, rondo, sonata, theme-and-variations, and popular song forms. Covers formal archetypes (AB, ABA, ABACA, sonata-allegro), 12-bar blues, arch form, minimalist process forms, strophic and through-composed designs, and formal analysis methodology for both score study and listening. Use when determining the structural plan of a piece, analyzing sectional relationships, or understanding how form shapes musical narrative.

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

Statics, dynamics, stress-strain analysis, materials selection, failure modes, and finite element analysis concepts for engineered structures. Covers free-body diagrams, equilibrium, internal forces (shear and moment), beam deflection, column buckling, material properties, factor of safety, fatigue, fracture mechanics, and FEA workflow. Use when analyzing loads on structures, selecting materials, predicting failure, or interpreting structural behavior.

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

Use this skill when the user wants to turn code graph analysis into tracked GitHub issues — "audit the architecture", "find god nodes", "triage architectural debt", "run graphify and log issues", "what's over-coupled in this codebase", "create issues from graphify findings", "check for structural problems", "scan for architectural smells", or any request that combines codebase topology analysis with issue tracking. This skill runs graphify to build a dependency graph, parses GRAPH_REPORT.md for god nodes and structural patterns, converts findings into GitHub issue payloads, and optionally pushes them to the repo. It bridges static analysis and project management in a single automated pass. Requires graphify and gh CLI.

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

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

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

Investigate recurring problems by mapping feedback loops, the cycles through which effects influence their causes. Identify underlying structures, match known patterns, and assess where changes could help and what unintended effects they might produce.

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

• Investigating recurring incidents
• Understanding coordination problems as teams grow
• Assessing unintended effects before changing a policy

Analyze a monolithic codebase before splitting it into modules or services. The skill inventories components, examines duplication, hierarchy, and dependencies, then proposes groupings aligned with business domains, with optional checks against business terminology and boundaries.

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

• Assessing component sizes before splitting a monolith
• Finding duplicated business logic across modules
• Reviewing module hierarchy and dependencies

Analyze strategic interactions in markets, including firm entry, pricing, auctions, and bargaining. Guides equilibrium selection and computation, explains how to handle multiple possible outcomes, and helps assess whether data can identify the model's parameters.

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

• Choosing and computing an equilibrium
• Planning an analysis of firm entry or price competition
• Handling multiple equilibria in empirical models

Evaluate code (especially LLM-generated) for structural simplicity using Rich Hickey's "Simple Made Easy" framework. Use this skill whenever reviewing a PR, diff, or code snippet for accidental complexity — particularly when the code was generated by an AI coding assistant and line-by-line review isn't feasible. Also use when the user asks about complecting, simplicity vs. easiness, structural coupling, or concept deduplication. Trigger on phrases like "is this simple", "does this complect", "review for complexity", "structural analysis", or any reference to Hickey, Simple Made Easy, or grey-box review.

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

Brief statutes and legislative Acts using the MAPS + RULES framework. Use when briefing statutes, analyzing legislative text, mapping statutory structure, extracting rule-modules from provisions, applying statutes to scenarios, or any statutory analysis task. Triggers include "brief this statute," "analyze this Act," "map the statute," "apply [statute] to [scenario]," "what are the elements of [provision]," "statutory analysis," or references to codified sections (such as 42 U.S.C. sections or Texas Health & Safety Code). Supports two modes - (A) text-only briefing for structural analysis, and (B) scenario-driven briefing that applies statutory provisions to specific facts.

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

Methodology for exploratory data analysis on scientific files. Decision frameworks by data type (tabular, sequence, image, spectral, structural, omics), quality assessment, report generation, format detection across 200+ formats. Use when given a data file for initial exploration or to pick an analysis before a pipeline.

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

Evidence-based investigation of issues, bugs, API calls, integrations, and other aspects of software development that need a deep dive to find the root cause and solutions. Use when you need to debug, troubleshoot, diagnose, or figure out why something is broken. Does not review code for quality or style — use code-review for auditing changes or post-code-review-to-pr for posting review feedback to GitHub. Does not assess architectural health or structural risk — use architectural-analysis for architectural concerns. Does not research open-ended options, prior art, or how something works when nothing is broken — use research for that. Does not plan the structural change a root cause calls for — use plan-a-change. Does not map bounded contexts or domain boundaries — use ddd-analysis. Does not capture feedback on Han's own skills — use han-feedback for that.

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

Performs deep architectural analysis of a specified module, directory, or feature area by examining structural coupling, data flow, concurrency patterns, risk, and SOLID alignment. Use when the user wants to assess, evaluate, or review the architecture, design quality, dependency structure, coupling, cohesion, or technical debt of an existing part of the codebase. Not for investigating specific bugs, runtime errors, or failures — use investigate. Not for test planning — use automated-test-planning. Not for file-level code review — use code-review. Not for researching open-ended options, prior art, or how something works — use research. Not for designing a new interface or contract — use design-an-api. Not for planning the change its findings imply — use plan-a-change. Not for discovering bounded contexts, ubiquitous language, or where code boundaries diverge from domain boundaries — use ddd-analysis. Not for writing documentation or architectural decision records.

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

Evaluate code (especially LLM-generated) for structural simplicity using Rich Hickey's "Simple Made Easy" framework. Use this skill whenever reviewing a PR, diff, or code snippet for accidental complexity — particularly when the code was generated by an AI coding assistant and line-by-line review isn't feasible. Also use when the user asks about complecting, simplicity vs. easiness, structural coupling, or concept deduplication. Trigger on phrases like "is this simple", "does this complect", "review for complexity", "structural analysis", or any reference to Hickey, Simple Made Easy, or grey-box review.

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

Structural pattern analysis for writing-mode review. Performs paragraph-level decomposition and pattern aggregation. Invoked by the team lead during editorial review.

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