ln-640-pattern-evolution-auditor
Use when auditing architectural patterns through the evaluation platform with mandatory best-practice research, coordinated pattern workers, and structured summaries.
- License 许可
- MIT
- 最近更新
- 2026-06-15
- Stars
- ★ 2
- Forks
- 1
01 前言 Front Matter
- name
- ln-640-pattern-evolution-auditor
- license
- MIT
- description
- Use when auditing architectural patterns through the evaluation platform with mandatory best-practice research, coordinated pattern workers, and structured summaries.
02 资源文件 9
- 参考文档references/architecture_audit_worker_boundaries.md2.4 KB
- 参考文档references/audit_final_report_contract.md2.6 KB
- 参考文档references/epistemic_protocol.md3.4 KB
- 参考文档references/evaluation_coordinator_runtime_contract.md3.6 KB
- 参考文档references/evaluation_research_contract.md2.0 KB
- 参考文档references/evaluation_summary_contract.md1.8 KB
- 参考文档references/layer_rules.md3.9 KB
- 参考文档references/meta_analysis_protocol.md1.5 KB
- 参考文档references/research_tool_fallback.md1.2 KB
03 SKILL.md 正文
Paths: File paths (
references/,../ln-*) are relative to this skill directory.
Type: L2 Coordinator Category: 6XX Audit
Pattern Evolution Auditor
Mandatory Read
MANDATORY READ: Load references/evaluation_coordinator_runtime_contract.md, references/evaluation_summary_contract.md, references/evaluation_research_contract.md
MANDATORY READ: Load references/audit_final_report_contract.md
MANDATORY READ: Load references/architecture_audit_worker_boundaries.md
MANDATORY READ: Load references/research_tool_fallback.md
Conditional read: load references/epistemic_protocol.md only when source confidence or claim uncertainty affects issue validation.
Purpose
- audit architecture/design evolution: pattern fitness, layer ownership, service/API contracts, dependency topology, modernization, physical structure, and configuration boundaries
- coordinate exactly
ln-641throughln-647 - require research before pattern scoring
Runtime Contract
Runtime family:
evaluation-runtime
Identifier:
pattern-audit
Phase order:
PHASE_0_CONFIGPHASE_1_DISCOVERYPHASE_2_RESEARCHPHASE_3_BOUNDARY_AUDITSPHASE_4_PATTERN_ANALYSISPHASE_5_AGGREGATEPHASE_6_REPORTPHASE_7_SELF_CHECK
Worker Set
ln-641-pattern-fitness-auditorln-642-layer-ownership-boundary-auditorln-643-api-contract-auditorln-644-dependency-topology-auditorln-645-architecture-modernization-auditorln-646-project-structure-auditorln-647-configuration-boundary-auditor
Worker Invocation (MANDATORY)
Host Skill Invocation: Skill(skill: "...", args: "...") is mandatory delegation.
- Claude: call the Skill tool exactly as shown.
- Codex: if no Skill tool exists, locate the named skill in available skills, read its
SKILL.md, treatargsas$ARGUMENTS, execute that skill workflow, then return here with its result/artifact. - Do not inline worker logic or mark the worker complete without executing the target skill.
Use the Skill tool for delegated workers. Do not inline worker logic inside the coordinator.
TodoWrite format (mandatory):
Resolve audit scope and build manifestLoad architecture patterns and layersRun best-practice researchRun boundary and contract auditsAnalyze pattern compliance and gapsAggregate worker findingsGenerate final audit report and remediation planVerify cleanup and self-check
Representative invocations:
Skill(skill: "ln-641-pattern-fitness-auditor", args: "{scope}")
Skill(skill: "ln-642-layer-ownership-boundary-auditor", args: "{scope}")
Skill(skill: "ln-643-api-contract-auditor", args: "{scope}")
Skill(skill: "ln-644-dependency-topology-auditor", args: "{scope}")
Skill(skill: "ln-645-architecture-modernization-auditor", args: "{scope}")
Skill(skill: "ln-646-project-structure-auditor", args: "{scope}")
Skill(skill: "ln-647-configuration-boundary-auditor", args: "{scope}")
Workflow
- Start
evaluation-runtime. - Discover candidate patterns and applicability.
- Run mandatory research first:
- official docs or standards
- MCP Ref
- Context7 when library/framework patterns are involved
- current web best-practice research
- Run boundary audits before pattern scoring.
- Run pattern analysis only after boundary results and research exist.
- Aggregate scores and worker findings by reading every worker
report_path, normalizing actions fromreferences/architecture_audit_worker_boundaries.md, deduplicating issues, resolving worker conflicts, and validating actionable problems againstreferences/evaluation_research_contract.md. - Write
.hex-skills/runtime-artifacts/runs/{run_id}/audit-report/ln-640--final-report.mdwith remediation plan perreferences/audit_final_report_contract.md. - Remove temporary worker markdown reports and record cleanup evidence.
- Write the
evaluation-coordinatorsummary withreport_pathset to the final report.
Definition of Done
- [ ] Evaluation runtime started
- [ ] Pattern applicability resolved
- [ ] Best-practice research completed
- [ ] Boundary audit summaries recorded
- [ ] Pattern analysis summaries recorded
- [ ] Worker set remained exactly
ln-641throughln-647 - [ ] Worker conflicts resolved with
architecture_audit_worker_boundaries.md - [ ] Final report and remediation plan written
- [ ] Temporary worker markdown reports removed
- [ ]
evaluation-coordinatorsummary written - [ ] Runtime completed
Meta-Analysis
Optional reference: load references/meta_analysis_protocol.md only when the user asks for post-run meta-analysis or protocol-formatted run reflection.
When requested after the coordinator run, analyze the session per protocol section 7 and include the protocol-formatted output with the final pattern audit result.
References
- Workers:
../ln-641-pattern-fitness-auditor/SKILL.md,../ln-642-layer-ownership-boundary-auditor/SKILL.md,../ln-643-api-contract-auditor/SKILL.md,../ln-644-dependency-topology-auditor/SKILL.md,../ln-645-architecture-modernization-auditor/SKILL.md,../ln-646-project-structure-auditor/SKILL.md,../ln-647-configuration-boundary-auditor/SKILL.md - Shared pattern refs:
references/layer_rules.md; pattern and scoring manuals are local to../ln-641-pattern-fitness-auditor/references/
Version: 2.0.0 Last Updated: 2026-02-08
04 同仓库更多 Skills
solana-dev
Use when user asks to "build a Solana dapp", "write an Anchor program", "create a token", "debug Solana errors", "set up wallet connection", "test my Solana program", "deploy to devnet", or "explain Solana concepts" (rent, accounts, PDAs, CPIs, etc.). End-to-end Solana development playbook covering wallet connection, Anchor/Pinocchio programs, Codama client generation, LiteSVM/Mollusk/Surfpool testing, and security checklists. Integrates with the Solana MCP server for live documentation search. Prefers framework-kit (@solana/client + @solana/react-hooks) for UI, wallet-standard-first connection (incl. ConnectorKit), @solana/kit for client/RPC code, and @solana/web3-compat for legacy boundaries.
generating-trading-signals
Generate trading signals using technical indicators (RSI, MACD, Bollinger Bands, etc.). Combines multiple indicators into composite signals with confidence scores. Use when analyzing assets for trading opportunities or checking technical indicators. Trigger with phrases like "get trading signals", "check indicators", "analyze for entry", "scan for opportunities", "generate buy/sell signals", or "technical analysis".
prediction-monitor
Prediction Monitor - Auto-activating skill for ML Deployment. Triggers on: prediction monitor, prediction monitor Part of the ML Deployment skill category.
strategy-advisor
High-level strategic thinking and business decision guidance for planning and direction-setting. Use when: making strategic decisions, evaluating business options, setting direction, analyzing trade-offs, or when user mentions strategy, business planning, competitive analysis, or long-term planning.
app-paywall-pilot
Design, audit, debug, and implement App Store-compliant mobile paywalls, subscription flows, pricing screens, trials, offers, feature gates, and subscription lifecycle UX. Use when the user asks to audit my paywall, fix App Store 3.1.2 rejection, improve trial-to-paid, choose plans/prices/trials, review RevenueCat/Adapty/Apphud/Superwall setup, calculate LTV/ROAS, or build paywall implementation.
figma
Use the Figma MCP server to fetch design context, screenshots, variables, and assets from Figma, and to translate Figma nodes into production code. Trigger when a task involves Figma URLs, node IDs, design-to-code implementation, or Figma MCP setup and troubleshooting.