failure-analysis
Systematic failure analysis methodology for mechanical component failures
What this skill does
# Failure Analysis Skill
## Purpose
The Failure Analysis skill provides systematic methodology for investigating mechanical component failures, enabling root cause identification through fractography, metallography, stress analysis, and structured problem-solving approaches.
## Capabilities
- Fractography interpretation (SEM, optical)
- Metallographic examination guidance
- Root cause analysis frameworks (5-Why, Fishbone)
- Failure mode identification (fatigue, corrosion, overload)
- Stress analysis correlation to failure location
- Chemical analysis interpretation
- Corrective action development
- Failure analysis report generation
## Usage Guidelines
### Investigation Process
#### Phase 1: Evidence Preservation
1. **Documentation**
- Photograph failed components as-received
- Document orientation and assembly position
- Record operating conditions at failure
- Preserve all fragments
2. **Chain of Custody**
- Log all handling
- Secure storage
- Controlled access
- Document any cleaning or cutting
#### Phase 2: Visual Examination
1. **Macroscopic Features**
| Feature | Indication |
|---------|------------|
| Beach marks | Fatigue |
| Chevron marks | Brittle fracture |
| Shear lips | Ductile overload |
| Corrosion products | Environmental attack |
| Wear patterns | Tribological failure |
2. **Fracture Origin**
- Identify initiation site
- Look for stress concentrations
- Check for material defects
- Document surface conditions
#### Phase 3: Fractography
1. **Optical Microscopy**
- Low magnification overview
- Document fracture features
- Identify regions of interest
2. **Scanning Electron Microscopy (SEM)**
| Fracture Feature | Failure Mode |
|------------------|--------------|
| Striations | Fatigue crack growth |
| Dimples | Ductile overload |
| Cleavage facets | Brittle fracture |
| Intergranular | Creep, SCC, hydrogen |
| Quasi-cleavage | Mixed mode |
3. **EDS Analysis**
- Identify corrosion products
- Detect contamination
- Verify material composition
#### Phase 4: Metallography
1. **Sample Preparation**
- Section perpendicular to fracture
- Mount in appropriate media
- Grind and polish
- Select appropriate etchant
2. **Examination**
- Grain structure
- Heat treatment condition
- Inclusions and defects
- Microcracking
- Decarburization
### Failure Mode Identification
#### Fatigue Failure
```
Characteristics:
- Beach marks (macroscopic)
- Striations (microscopic)
- Origin at stress concentration
- Minimal plastic deformation
- Flat fracture surface
Contributing Factors:
- Cyclic loading
- Stress concentration
- Residual stress
- Material defects
- Environmental effects
```
#### Overload Failure
```
Ductile:
- Significant plastic deformation
- Cup-and-cone fracture (tensile)
- Shear lips
- Dimpled fracture surface
Brittle:
- Little plastic deformation
- Flat fracture surface
- Chevron marks pointing to origin
- Cleavage or intergranular fracture
```
#### Corrosion Failures
| Type | Characteristics | Environment |
|------|-----------------|-------------|
| Uniform | General metal loss | Acids, bases |
| Pitting | Localized attack | Chlorides |
| SCC | Branching cracks | Specific ion + stress |
| Corrosion fatigue | Accelerated fatigue | Cyclic + corrosive |
| Hydrogen embrittlement | Intergranular fracture | Hydrogen source |
#### Wear Failures
| Type | Mechanism | Evidence |
|------|-----------|----------|
| Adhesive | Material transfer | Galling, scoring |
| Abrasive | Hard particle cutting | Grooves, scratches |
| Erosive | Fluid/particle impact | Surface damage pattern |
| Fretting | Small amplitude motion | Oxide debris, pitting |
### Root Cause Analysis
#### 5-Why Method
```
Problem: Shaft failure
Why 1: Fatigue fracture
Why 2: High stress concentration at keyway
Why 3: Sharp corner radius
Why 4: Drawing did not specify radius
Why 5: Design review did not catch omission
Root Cause: Inadequate design review process
```
#### Fishbone Diagram Categories
- Material: Composition, defects, properties
- Machine: Equipment condition, maintenance
- Method: Process, procedure, design
- Man: Training, error, supervision
- Environment: Temperature, humidity, contamination
- Measurement: Calibration, accuracy
## Process Integration
- ME-016: Failure Analysis Investigation
## Input Schema
```json
{
"failed_component": {
"part_number": "string",
"material": "string",
"service_history": "string",
"failure_date": "date"
},
"operating_conditions": {
"loads": "string",
"environment": "string",
"temperature": "number (C)",
"cycles_or_hours": "number"
},
"available_evidence": {
"fracture_surfaces": "boolean",
"mating_parts": "boolean",
"lubricant_samples": "boolean",
"maintenance_records": "boolean"
},
"analysis_scope": "preliminary|comprehensive"
}
```
## Output Schema
```json
{
"failure_mode": "fatigue|overload|corrosion|wear|other",
"root_cause": "string",
"contributing_factors": "array",
"evidence_summary": {
"visual": "string",
"fractography": "string",
"metallography": "string",
"chemical": "string"
},
"corrective_actions": [
{
"action": "string",
"category": "design|material|process|maintenance",
"priority": "high|medium|low"
}
],
"preventive_recommendations": "array",
"report_reference": "string"
}
```
## Best Practices
1. Preserve evidence before any destructive examination
2. Document all observations photographically
3. Follow systematic investigation process
4. Consider multiple failure mechanisms
5. Correlate fracture features with stress analysis
6. Validate root cause with evidence
## Integration Points
- Connects with FEA Structural for stress analysis
- Feeds into Material Selection for improved materials
- Supports Design Review for lessons learned
- Integrates with Quality for corrective actions
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.