'structural' 검색 결과

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

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

Diagnosis of why structural materials fail — ductile overload, brittle cleavage, fatigue, creep, stress-corrosion cracking, hydrogen embrittlement, and corrosion. Covers Griffith fracture mechanics, the ductile-to-brittle transition, the S-N and Paris fatigue frameworks, fractographic interpretation, and the J.E. Gordon view that strength, stiffness, and toughness are distinct properties that must be understood together to prevent collapse.

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

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.

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

Carbon allotropes and nanoscale materials — graphite, diamond, fullerenes (C60 and family), carbon nanotubes, graphene, and the broader class of low-dimensional materials. Covers synthesis routes (arc discharge, laser ablation, CVD, exfoliation), structural characterization, exceptional mechanical and electronic properties, and the gap between laboratory demonstrations and structural-scale applications.

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

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.

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

This skill should be used when a story has been captured but content direction is unresolved - the spark describes WHAT to build structurally but not WHAT goes in it. Reads the story spark, splits it into Resolved (structurally clear) vs. Assumed (would have to guess) content dimensions, and surfaces each assumption for the human to confirm, correct, or expand. Also classifies implementation risk tags (has-variants, has-data-pipeline, has-animation, has-touch-targets, diverges-from-existing) so plan-chunks translates them into acceptance criteria that name the implementation mechanism. Captures answers into

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

Use whenever the user wants to find, shortlist, vet, or enrich US engineering firms — civil, structural, MEP, mechanical, electrical, geotechnical, transportation, environmental, and manufacturing. **For real-world engineering (buildings, infrastructure, manufacturing) — NOT software engineering.** Triggers on "find civil engineering firms in Florida for transportation", "shortlist three structural engineering firms with high-rise experience", "MEP consultancy for a hospital project", or "pull contact info for these 12 engineering firm domains", even when described indirectly (PE-stamped drawings, building-permit review). Drives the ServiceGraph API (api.servicegraph.co) — a 100k+ US firm catalog filterable by industry, services, location, size, ratings. Defer software-dev / "engineering team" / SaaS-architecture asks to find-software-developer. Skip in-house engineering-manager hires, DIY questions, software-product comparisons (Revit, AutoCAD), non-US firms, individual freelancers.

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

Analyzes structural interest rate exposure with fixed/floating mismatch, basis risk, and cap/floor adequacy assessment. Use when modeling structural rate risk, analyzing basis risk, or evaluating interest rate hedging needs.

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

Medicinal chemistry filters for compound triage. Apply drug-likeness rules (Lipinski rule of five, Veber, Oprea, CNS, lead-like, rule of three), structural alert catalogs (PAINS a/b/c, NIBR screening-deck severity, Brenk, BMS, Glaxo, Dundee, ChEMBL common alerts), ZINC-15 percentile complexity metrics (Bertz, SAscore, QED, Whitlock, Barone), chemical-group detection, Lilly demerits, and the medchem query language (MATCHRULE, HASALERT, HASPROP, HASGROUP) for filtering a library at scale. Also trigger on medchem, `import medchem as mc`, RuleFilters, NIBRFilters, CommonAlertsFilters, NamedCatalogs, QueryFilter, PAINS filtering, or structural alerts.

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

Access a collection of open-source molecular design and structural biology tools on the Tamarind Bio platform, via its REST API or MCP server — no local GPUs required. Tamarind bundles popular open-source models for structure prediction (AlphaFold, Boltz, Chai, ESMFold), protein, binder, and de novo design (RFdiffusion, ProteinMPNN, BoltzGen), antibody and nanobody design and developability, protein-ligand docking (DiffDock, Autodock Vina), binding-affinity prediction, MSA generation, and molecular dynamics. Use when the user mentions Tamarind or tamarind.bio, wants to run any of these open-source tools in the cloud, references app.tamarind.bio/api or the x-api-key header, or needs to submit batches of sequences for structural or biophysical characterization.

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

Navigate the Kabbalistic Tree of Life (Etz Chaim) — explore the ten sephirot, twenty-two paths, four worlds, and three pillars. Covers correspondences, contemplative exercises, and structural analysis. Use when exploring a sephira's attributes and divine names, studying structural relationships between sephirot, learning the four worlds (Atzilut through Assiah), tracing a path's Hebrew letter and tarot attributions, or using the Tree as a symbolic map for understanding a concept or system.

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

Cultivate bonsai trees from species selection through long-term seasonal care. Covers species suitability, structural and maintenance pruning, wiring technique, repotting protocol, soil mix preparation, seasonal care schedules, and contemplative sitting practice. Use when selecting a species for a first or next bonsai, performing structural or maintenance pruning, repotting when roots are circling or growth has stalled, wiring branches for shaping, developing a seasonal care calendar, or building a contemplative practice with a living tree.

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

Evaluate a system's current structural form, identify transformation pressure, and classify transformation readiness. Covers structural inventory, pressure mapping, rigidity assessment, change capacity estimation, and readiness classification for architectural metamorphosis. Use before any significant architectural change to understand the starting point, when a system feels stuck without clear reasons, when external pressure from growth or tech debt is mounting, or as periodic health checks for long-lived systems.

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

AI context assessment — evaluating problem malleability, mapping structural rigidity versus flexibility, analyzing transformation pressure, and estimating capacity to adapt. Use when a complex task feels stuck and it is unclear whether to push through or pivot, before a significant approach change to assess whether the current reasoning structure can support it, when accumulated workarounds suggest the underlying approach may be wrong, or as a periodic structural health check during extended multi-step tasks.

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

Detects seven structural anti-patterns in Claude Projects that cause unpredictable output, ignored instructions, and degraded quality. Diagnoses Monolith, Orphan File, Echo Chamber, Phantom Conversation, Kitchen Sink, Misaligned Hierarchy, and Blurred Layers. Use when user says "what's wrong with my project," "Claude ignores my instructions," "diagnose my project," "why is output inconsistent," "review my project setup." Also trigger on symptom-phrased: "Claude doesn't follow my rules," "my instructions keep getting overridden," "my Project isn't behaving as designed." Use alongside rootnode-project-audit if available for deeper structural analysis. Activate whenever the user describes symptoms of unreliable, inconsistent, or degraded Claude Project output, even if they do not name a specific pattern. Do NOT use when the user's primary request is Memory-layer rebalancing (use rootnode-memory-optimization if available) or scoring a single prompt (use rootnode-prompt-validation if available).

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

Audits Claude Code repositories. Two-phase workflow — Phase 1 sweeps 14 hygiene categories (permissions, hooks, CLAUDE.md bloat, Skills hygiene, process-abstraction, plus structural) and an optional 7-layer leak check. Phase 2 executes [APPROVED] markers from the report file. Use for repo cleanup, pre-distribution sanity, post-feature hygiene, environment audit, process-abstraction discovery. Trigger on "audit my CC repo," "sweep my repository for hygiene," "check this CC environment," "find process abstraction candidates," "review my CLAUDE.md," "clean up my .claude directory," "pre-distribution hygiene check," "find layer leaks in my CC setup." Routes structural findings to rootnode-cc-design REMEDIATE. Composes with rootnode-critic-gate. CC-only — does not scan Claude Projects. Do NOT use for building a Skill (use rootnode-skill-builder), compiling a prompt (use rootnode-prompt-compilation), scoring a single prompt (use rootnode-prompt-validation), or auditing a Project (use rootnode-project-audit).

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

Use for code generation, feature work, bug fixes, refactoring, and code review when a change creates or reshapes a multi-step flow, state lifecycle, side-effect or decision ownership, cross-unit composition, or boundary contract. Also use it when an existing structural problem makes those elements hard to trace or verify. Structural change is optional. Mechanical edits, throwaway experiments, and coherent local changes stay with their current owner and focused verification.

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

"Apply social capital theory (Putnam, Coleman, Bourdieu, Burt) to analyze how network structures and trust generate value or impose constraints. Use this skill when the user needs to evaluate bridging vs bonding capital, identify structural holes or network closure benefits, assess community or organizational trust dynamics, or when they ask 'how does our network create value', 'are we too insular', or 'where are the structural holes we can exploit'.".

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

"Apply Structural Equation Modeling (SEM) to test hypothesized causal structures by combining measurement models (CFA) and structural models (path analysis). Use this skill when the user needs to validate latent constructs, test mediation or moderation paths, assess model fit with CFI/TLI/RMSEA/SRMR, or when they ask 'do these variables form a causal chain', 'how do I test my theoretical model', or 'is my measurement model valid'.".

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

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.

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

Use when a task needs the judgment of an Aerospace Engineering and Operations Technologist/Technician — verifying an installed fastener's preload against a drawing's torque callout via the T=K·D·F relationship, reducing strain-gauge data from a structural proof-load test into stress and checking it against an FEA-predicted margin, selecting and executing an NDI method against a defect type and material, reducing a wind-tunnel test point's dynamic-pressure and Reynolds-number data, or ballooning and dispositioning an AS9102 first article inspection. Distinct from an aerospace-engineer (owns the design, structural analysis, and certification basis) — this role builds, instruments, tests, and inspects the hardware the engineer specified, closing the loop with measurement rather than deriving a new analysis.

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

Expert in Continental tradition from Kant through phenomenology, existentialism, structuralism, and post-structuralism

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

Create custom directives in Angular v20+ for DOM manipulation and behavior extension. Use for attribute directives that modify element behavior/appearance, structural directives for portals/overlays, and host directives for composition. Triggers on creating reusable DOM behaviors, extending element functionality, or composing behaviors across components. Note - use native @if/@for/@switch for control flow, not custom structural directives.

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

Detect syntenic blocks and structural rearrangements between genomes using MCScanX (Wang 2012), JCVI/MCScan (Tang 2008 Python), GENESPACE (Lovell 2022) for orthology-anchored riparian visualization, SyRI for structural variation, AnchorWave for sequence-level synteny, i-ADHoRe 3.0 for highly diverged species, SynNet for synteny networks, and ntSynt for multi-genome macrosynteny. Use when identifying collinear gene blocks across species, distinguishing macrosynteny from microsynteny, detecting inversions/translocations/duplications, anchoring orthology in WGD lineages, producing publication riparian plots, computing synteny block age via Ks (cross-references whole-genome-duplication), or running synteny-aware ortholog inference in polyploids.

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