continuous-learning-construction
Automatically extract patterns, best practices, and reusable knowledge from construction automation sessions to improve future performance.
What this skill does
# Continuous Learning for Construction Automation
This skill enables automatic extraction of valuable patterns, solutions, and best practices from construction automation sessions to build institutional knowledge.
## When to Use
Activate this skill:
- At the end of complex estimation sessions
- After solving non-trivial data processing problems
- When discovering new integration patterns
- After completing successful document processing
- When developing new automation workflows
## Pattern Extraction Framework
### 1. Session Analysis
```python
class ConstructionSessionAnalyzer:
"""Extract learnings from automation sessions"""
# Categories of learnable patterns
PATTERN_CATEGORIES = [
'data_processing', # Data transformation patterns
'estimation', # Cost estimation techniques
'scheduling', # Schedule optimization patterns
'integration', # API/system integration patterns
'document_processing', # Document handling patterns
'quality_assurance', # Validation and QA patterns
'error_handling', # Error resolution patterns
'optimization' # Performance optimization patterns
]
def analyze_session(self, session_log: list) -> dict:
"""Extract patterns from session history"""
patterns = {
'successful_solutions': [],
'error_resolutions': [],
'optimization_discoveries': [],
'integration_patterns': [],
'reusable_code': [],
'decision_rationales': []
}
for entry in session_log:
if self._is_solution(entry):
patterns['successful_solutions'].append(
self._extract_solution_pattern(entry)
)
if self._is_error_resolution(entry):
patterns['error_resolutions'].append(
self._extract_error_pattern(entry)
)
if self._is_optimization(entry):
patterns['optimization_discoveries'].append(
self._extract_optimization(entry)
)
return patterns
```
### 2. Knowledge Categories for Construction
#### 2.1 Cost Estimation Patterns
```yaml
# Example learned pattern
pattern:
name: "electrical_cost_adjustment_pattern"
category: "estimation"
context: "When estimating electrical work for high-rise buildings"
problem: "Standard rates don't account for vertical transportation costs"
solution: |
Apply height factor multiplier:
- Floors 1-5: 1.0x base rate
- Floors 6-15: 1.15x base rate
- Floors 16-30: 1.25x base rate
- Floors 30+: 1.35x base rate
confidence: 0.85
source_sessions: ["session_2026_01_15", "session_2026_01_20"]
validations: 3
```
#### 2.2 BIM Data Processing Patterns
```yaml
pattern:
name: "revit_level_extraction"
category: "data_processing"
context: "Extracting elements by level from Revit exports"
problem: "Elements sometimes missing level association"
solution: |
1. First check 'Level' parameter
2. If missing, check 'Reference Level' parameter
3. If still missing, derive from bounding box Z coordinate
4. Map Z ranges to known level elevations
code_snippet: |
def get_element_level(element: dict, levels: list) -> str:
# Direct level parameter
if level := element.get('Level'):
return level
# Reference level fallback
if ref_level := element.get('Reference Level'):
return ref_level
# Derive from geometry
z_coord = element['BoundingBox']['Min']['Z']
return find_nearest_level(z_coord, levels)
confidence: 0.92
```
#### 2.3 Integration Patterns
```yaml
pattern:
name: "procore_rate_limit_handling"
category: "integration"
context: "Syncing data with Procore API"
problem: "API returns 429 Too Many Requests during bulk operations"
solution: |
Implement exponential backoff with jitter:
1. Initial delay: 1 second
2. Multiply by 2 on each retry
3. Add random jitter (0-500ms)
4. Max retries: 5
5. Max delay: 32 seconds
code_snippet: |
async def procore_request_with_retry(url, data):
delay = 1
for attempt in range(5):
try:
response = await procore_api.post(url, data)
return response
except RateLimitError:
jitter = random.uniform(0, 0.5)
await asyncio.sleep(delay + jitter)
delay *= 2
raise MaxRetriesExceeded()
confidence: 0.95
```
#### 2.4 Error Resolution Patterns
```yaml
pattern:
name: "cwicr_no_match_resolution"
category: "error_handling"
context: "CWICR semantic search returns no relevant matches"
problem: "Query too specific or uses non-standard terminology"
solution: |
Resolution steps:
1. Simplify query to core concepts
2. Remove brand names and specifications
3. Try alternative terminology (US vs UK terms)
4. Expand search to parent category
5. If still no match, flag for manual mapping
examples:
- original: "Kohler K-4519 wall-mounted water closet"
simplified: "wall mounted toilet"
- original: "Lutron Caseta wireless dimmer switch"
simplified: "dimmer switch"
confidence: 0.88
```
### 3. Learning Pipeline
```python
class ConstructionLearningPipeline:
"""Continuous learning pipeline for construction automation"""
def __init__(self, knowledge_base_path: str):
self.kb_path = knowledge_base_path
self.patterns = self._load_patterns()
def learn_from_session(self, session: dict) -> list:
"""Extract and store learnings from session"""
# Analyze session
analyzer = ConstructionSessionAnalyzer()
new_patterns = analyzer.analyze_session(session['log'])
# Validate patterns
validated = []
for pattern in new_patterns['successful_solutions']:
if self._validate_pattern(pattern):
# Check if similar pattern exists
existing = self._find_similar_pattern(pattern)
if existing:
# Reinforce existing pattern
self._reinforce_pattern(existing, pattern)
else:
# Add new pattern
self._add_pattern(pattern)
validated.append(pattern)
# Persist to knowledge base
self._save_patterns()
return validated
def apply_learnings(self, context: dict) -> list:
"""Retrieve relevant patterns for current context"""
relevant_patterns = []
for pattern in self.patterns:
similarity = self._calculate_similarity(pattern['context'], context)
if similarity > 0.7:
relevant_patterns.append({
'pattern': pattern,
'relevance': similarity
})
return sorted(relevant_patterns, key=lambda x: x['relevance'], reverse=True)
def _validate_pattern(self, pattern: dict) -> bool:
"""Validate pattern before adding to knowledge base"""
# Check minimum confidence
if pattern.get('confidence', 0) < 0.6:
return False
# Check for code quality (if code snippet)
if code := pattern.get('code_snippet'):
if not self._is_valid_code(code):
return False
# Check for completeness
required_fields = ['name', 'category', 'context', 'solution']
if not all(f in pattern for f in required_fields):
return False
return True
```
### 4. Knowledge Base Structure
```
knowledge_base/
├── patterns/
│ ├── estimation/
│ │ ├── height_factors.yaml
│ │ ├── material_adjustments.yaml
│ │ └── labor_productivity.yaml
│ ├── data_processing/
│ │ ├── revit_extraction.yaml
│ │ ├── ifc_parsing.yaml
│ │ └── excel_traRelated in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.