architect

Analyze health signals and friction patterns to propose research-backed knowledge system changes.

Updated Jan 8, 2026
One-click install
npx skills add https://github.com/lightningfastsls/London_Lab --skill architect-lightningfastsls
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/lightningfastsls/London_Lab/tree/main/.claude/skills/architect
Command: npx skills add https://github.com/lightningfastsls/London_Lab --skill architect-lightningfastsls

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Research-backed evolution advice for your knowledge system. Analyzes health reports, friction patterns, and derivation history to propose specific changes with research justification. Never auto-implements — proposals require your approval.

Core Features & Use Cases

  • Health data and friction analysis to guide principled system evolution.
  • Research-grounded justification with traceable evidence for each proposal.
  • Governance-friendly workflow: proposals require explicit user approval before changes.

Quick Start

Provide the current system context and let Architect propose three evidence-backed changes for review.

Frequently Asked Questions about architect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I propose research-backed evolution changes for a knowledge system?

To propose research-backed evolution changes for a knowledge system, identify health signals, friction patterns, and derivation drift. The process generates concrete recommendations citing supporting research with explicit impact and effort estimates for review.

What is derivation drift and how does it affect system architecture?

Derivation drift occurs when a knowledge system deviates from its intended architecture over time. Analyzing this drift alongside health data and friction patterns helps propose research-grounded architectural changes to correct the trajectory.

Can I use automated recommendations for governance and tooling scenarios?

Automated recommendations support governance and tooling scenarios, but evolution proposals require explicit human approval. The system avoids automatic changes and provides research-grounded justification with traceable evidence for each proposal.

How do I analyze friction patterns to guide system evolution?

To analyze friction patterns for system evolution, provide current system context and health reports. The analysis identifies friction points and derivation drift to generate three evidence-backed change proposals for governance review.

What are the limitations of using research-backed advice for system architecture?

A key limitation of research-backed system architecture advice is that it never auto-implements changes. Proposals remain advisory, requiring explicit user approval before applying any governance, architecture, or tooling modifications.