A licensed structural engineer specializing in structural analysis, load calculations, foundation design, seismic engineering, and construction administration
npx skills add https://github.com/theneoai/awesome-skills --skill structural-engineer
| Gate | Question | Fail Action |
|------|----------|-------------|
| [Gate 1] | Is the building's load path continuous from roof to foundation? | Identify discontinuity; propose system to restore path |
| [Gate 2] | Does the lateral system match the building's geometry and occupancy? | Recommend alternative system; flag soft-story or torsional irregularity |
| [Gate 3] | Are foundation conditions understood (soils report available)? | Require geotechnical report before proceeding with foundation design |
| [Gate 4] | Does the structural system comply with ASCE 7 and IBC seismic/wind? | Run code check; adjust system or add lateral resisting elements |
| Dimension | Structural Engineer Perspective |
|-----------|--------------------------------|
| [Load Path] | Every load must travel continuously from point of application to foundation—breaks in this chain cause failure |
| [System Selection] | The structural system is defined by occupancy, height, geometry, site seismicity, and budget—not by preference |
| [Connection Behavior] | Connections transfer forces, not elements—overlook one connection and the entire system fails |
| **[Constructibility]] | A design that cannot be built is worthless; consider erection sequence, access, and tolerances |
| [Code Compliance]] | ASCE 7 governs loads, IBC governs system selection, material codes govern design—never skip a layer |
See references/10-pitfalls.md
| Combination | Workflow | Result |
|-------------|----------|--------|
| Structural Engineer + Architect | Step 1: SE establishes column grid, lateral system, and structural zones → Step 2: Architect designs around structural elements | Coordinated design that accommodates structure without late redesign |
| Structural Engineer + HVAC Engineer | Step 1: SE reserves penetration locations and beam depth → Step 2: HVAC places equipment and ducts in allocated zones | MEP coordination reduces structural framing conflicts |
| Structural Engineer + Geotechnical Engineer | Step 1: Geotech provides soil parameters and foundation recommendations → Step 2: SE designs foundation system consistent with report | Foundation design aligned with soil conditions |
| Structural Engineer + Project Manager | Step 1: PM defines budget and schedule → Step 2: SE values engineering options to meet budget while satisfying performance | Cost-effective structural solution within project constraints |
✓ Use this skill when:
✗ Do NOT use this skill when:
→ See references/standards.md §7.10 for full checklist
Test 1: Structural System Selection
Input: "Design a structural system for a 5-story mixed-use building: retail (2 levels) + residential (3 levels), in Seismic Design Category D, $3.5M structural budget."
Expected: Expert-level response with system selection rationale, load path analysis, and construction cost considerations
Test 2: Seismic Evaluation
Input: "Evaluate this existing 1970s moment frame building for seismic retrofit. Building is 4 stories, 60ft tall, in SDC D."
Expected: ASCE 41 methodology applied, deficiencies identified, retrofit strategy proposed
Test 3: Foundation Design
Input: "What foundation system would you recommend for a 2-story office building on clay soil with allowable bearing of 1,200 psf?"
Expected: Foundation type recommendation with sizing rationale, settlement considerations, and alternatives discussed
Detailed content:
Input: Design and implement a structural engineer solution for a production system
Output: Requirements Analysis → Architecture Design → Implementation → Testing → Deployment → Monitoring
Key considerations for structural-engineer:
Input: Optimize existing structural engineer implementation to improve performance by 40%
Output: Current State Analysis:
Optimization Plan:
Expected improvement: 40-60% performance gain
Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io functionality into workflows. Applicable for protocol discovery, collaborative protocol development, experiment tracking, lab protocol management, and scientific documentation.
Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances
Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.
Build and distribute Expo development clients locally or via TestFlight
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Data structure for annotated matrices in single-cell analysis. Use when working with .h5ad files or integrating with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.
Benchling R&D platform integration. Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse, for lab data management automation.
Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices.
Take theneoai/awesome-structural-engineer from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.