Research-backed principles for writing prose that avoids AI tells. Apply when writing articles, blog posts, emails, marketing copy, social media, or any prose content. Covers vocabulary, structure, tone, rhythm, and craft techniques that make writing feel authentically human. Not for code, commit messages, or technical documentation.
Generate a comprehensive epic with child stories from a feature description
Generate a well-structured user story from a plain English description
Use when tempted to predict, analyze, or debate whether something will work instead of testing it. When facing uncertainty about a decision, product, hire, or opportunity and relying on gut feeling or expert opinions.
Use when facing a significant decision, evaluating options, or feeling stuck between choices. Especially when the decision is high-stakes, irreversible, or involves uncertainty about outcomes. Triggers on phrases like "should I", "I don't know whether to", "I'm torn between", or "help me decide".
Figure things out together — any topic, problem, or idea. Collaborative thinking partner that investigates before claiming, builds shared truth through evidence not inference. Use when you need to truly understand something before acting, or when figuring it out IS the goal. Triggers: figure out, help me think through, dig deeper, what is really going on, investigate, understand, why does, work through.
Create weekly age-appropriate child activities balanced across developmental domains.
Standard format for logging ML experiments including hypothesis, config, results, and learnings. Use when running experiments to maintain a consistent record.
Operate and maintain the local Symphony factory from this repository checkout. Use this skill when monitoring the live factory, repairing stalled runs, handling PR review and CI follow-up, or improving the operator loop itself.
Iterative keep/discard experiment workflow over one explicitly configured repo, editable file, run command, and metric rule. Any agent may use it, but the `autoresearch` specialist is the default owner for sustained experiment-loop work.
Comprehensive collection of 128+ ready-to-use scientific skills for Claude enabling research across biology, chemistry, medicine, genomics, and advanced analysis domains.
Autonome Verbesserung nach dem Autoresearch-Paradigma (Karpathy). Zwei Modi: (1) Skill-Modus — optimiert eine SKILL.md durch iterative Mutation und Evaluation. (2) Generic-Modus — optimiert beliebige Dateien gegen jede mechanische Metrik (Testabdeckung, Bundle-Size, Lighthouse-Score, Docker-Image-Größe, etc.). Zwei Ausführungsmodi: Auto (vollautonomer Loop, ideal für Overnight-Runs) und Guided (interaktiv, User entscheidet bei jedem Schritt mit). Führt einen Experiment-Loop durch: analysieren → Hypothese bilden → mutieren → verifizieren → Score messen → keep/revert → wiederholen. Kann über Nacht als Scheduled Task laufen und liefert morgens einen Experiment-Report. IMMER verwenden bei: Skill autonom verbessern, Skill optimieren ohne manuelles Feedback, Skill optimieren mit Feedback, Autoresearch, autonomer Verbesserungsloop, Skill-Evolution, overnight optimization, Skill-Experiment, "lass den Skill über Nacht besser werden", Skill-Score verbessern, automatische Skill-Iteration, Code-Metrik verbessern, Testabd
Verify observability posture — audit monitoring coverage, find blind spots, prioritize gaps. Use when asked "is monitoring sufficient", "observability review", "are we covered", or "pre-launch monitoring check".
Testing reconnaissance — inventory all tests, frameworks, coverage, CI integration, and assess testing maturity for project takeover. Use when asked to "understand the tests", "testing assessment", "what's tested", or "test inventory".
Instrument a service with OpenTelemetry — RED metrics, structured logs, distributed tracing, and health checks. Outputs actual code and config, not a plan. Use when asked to "add monitoring", "instrument this", "add logging", "set up tracing", or "observability".
Observability reconnaissance — inventory what monitoring exists, map coverage, highlight blind spots. Use when asked "what monitoring exists", "observability assessment", or "what can we see".
Write Verilog-A behavioral modules for analog/mixed-signal IC design (Cadence Virtuoso / Spectre). Covers 12 circuit categories. TRIGGER FIRST (before evas-sim) when the user needs to write or generate a new .va file. Key trigger phrases: "write", "create", "generate", "code", "implement" + "Verilog-A / veriloga / va / .va / behavioral model". Also triggers on: review/fix Verilog-A, "behavioral model", "veriloga", "analog HDL", circuit spec → behavioral model, "voltage-domain", "current-domain". Do NOT defer to evas-sim for authoring — evas-sim is for running an already-written file.
Observability reconnaissance — inventory what monitoring exists, map coverage, highlight blind spots. Use when asked "what monitoring exists", "observability assessment", or "what can we see".
