Loading...
Loading...
Found 18 Skills
LaTeX Assistant for Chinese Academic Theses (PhD/Master's). Fields: Deep Learning, Time Series, Industrial Control. Trigger Words (call any module independently): - "compile", "compile", "xelatex" → Compilation Module - "structure", "structure", "map" → Structure Mapping Module - "format", "format", "GB/T", "national standard" → National Standard Format Checking Module - "expression", "expression", "polish", "academic expression" → Academic Expression Module - "logic", "coherence", "logic", "cohesion", "methodology", "methodology" → Logical Cohesion & Methodology Depth Module - "long sentence", "long sentence", "split" → Long & Complex Sentence Analysis Module - "bib", "bibliography", "bibliography" → Bibliography Module - "template", "template", "thuthesis", "pkuthss" → Template Detection Module - "deai", "de-AI editing", "humanize", "reduce AI traces" → De-AI Editing Module - "title", "title", "title optimization", "generate title" → Title Optimization Module
This skill analyzes code for design quality improvements across 8 dimensions: Naming, Object Calisthenics, Coupling & Cohesion, Immutability, Domain Integrity, Type System, Simplicity, and Performance. Ensures rigorous, evidence-based analysis by: (1) Understanding code flow first via implementation-analysis protocol, (2) Systematically evaluating each dimension with specific criteria, (3) Providing actionable findings with file:line references. Triggers when users request: code analysis, design review, refactoring opportunities, code quality assessment, architecture evaluation.
Orchestrate parallel implementation with coder/overseer pairs. Coders implement decomposed tasks using evanflow-tdd; overseers review each coder's output for bugs, gaps, errors, AND cohesion violations against a shared contract. A final integration overseer checks cross-coder cohesion. Use for plans with 3+ truly independent tasks that share an interface contract.
Opinionated guide to software design principles and architectural patterns. Use when reviewing code design, planning feature architecture, asking "is this the right design?", "how should I structure this?", or requesting design philosophy guidance. Triggers on questions about SOLID, DRY, KISS, YAGNI, Clean Architecture, DDD, hexagonal architecture, composition vs inheritance, coupling, cohesion, or any software design trade-off discussion.
Maps business domains and suggests service boundaries in any codebase using DDD Strategic Design. Use when asking "what are the domains in this codebase?", "where should I draw service boundaries?", "identify bounded contexts", "classify subdomains", "DDD analysis", or analyzing domain cohesion. Do NOT use for grouping existing components into domains (use domain-identification-grouping) or dependency analysis (use coupling-analysis).
Object and class design patterns following Clean Code JavaScript.