Best use case
llm-tuning-patterns is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
LLM Tuning Patterns
Teams using llm-tuning-patterns should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/llm-tuning-patterns/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How llm-tuning-patterns Compares
| Feature / Agent | llm-tuning-patterns | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
LLM Tuning Patterns
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# LLM Tuning Patterns Evidence-based patterns for configuring LLM parameters, based on APOLLO and Godel-Prover research. ## Pattern Different tasks require different LLM configurations. Use these evidence-based settings. ## Theorem Proving / Formal Reasoning Based on APOLLO parity analysis: | Parameter | Value | Rationale | |-----------|-------|-----------| | max_tokens | 4096 | Proofs need space for chain-of-thought | | temperature | 0.6 | Higher creativity for tactic exploration | | top_p | 0.95 | Allow diverse proof paths | ### Proof Plan Prompt Always request a proof plan before tactics: ``` Given the theorem to prove: [theorem statement] First, write a high-level proof plan explaining your approach. Then, suggest Lean 4 tactics to implement each step. ``` The proof plan (chain-of-thought) significantly improves tactic quality. ### Parallel Sampling For hard proofs, use parallel sampling: - Generate N=8-32 candidate proof attempts - Use best-of-N selection - Each sample at temperature 0.6-0.8 ## Code Generation | Parameter | Value | Rationale | |-----------|-------|-----------| | max_tokens | 2048 | Sufficient for most functions | | temperature | 0.2-0.4 | Prefer deterministic output | ## Creative / Exploration Tasks | Parameter | Value | Rationale | |-----------|-------|-----------| | max_tokens | 4096 | Space for exploration | | temperature | 0.8-1.0 | Maximum creativity | ## Anti-Patterns - **Too low tokens for proofs**: 512 tokens truncates chain-of-thought - **Too low temperature for proofs**: 0.2 misses creative tactic paths - **No proof plan**: Jumping to tactics without planning reduces success rate ## Source Sessions - This session: APOLLO parity - increased max_tokens 512->4096, temp 0.2->0.6 - This session: Added proof plan prompt for chain-of-thought before tactics
Related Skills
websocket-patterns
Connection management, room patterns, reconnection strategies, message buffering, and binary protocol design.
vector-db-patterns
Embedding strategies, ANN algorithms, hybrid search, RAG chunking strategies, and reranking for semantic search and retrieval.
tracing-patterns
OpenTelemetry setup, span context propagation, sampling strategies, Jaeger queries
terraform-patterns
Module composition, state management, workspace strategy, provider versioning, and infrastructure-as-code best practices.
swift-patterns
SwiftUI view composition, @Observable patterns, async/await concurrency, TCA architecture, and Combine reactive streams.
springboot-patterns
Spring Boot architecture patterns, REST API design, layered services, data access, caching, async processing, and logging. Use for Java Spring Boot backend work.
seo-patterns
Meta tag patterns, structured data (JSON-LD), Core Web Vitals optimization, and SSR/SSG strategies for search visibility.
secret-patterns
30+ service-specific secret detection regex patterns, entropy-based detection, PEM/JWT/Base64 identification, and false positive filtering.
saas-payment-patterns
Payment provider abstraction, webhook security, subscription lifecycle, dunning flows, pricing models, invoicing, tax handling, and refund patterns for SaaS applications.
saas-auth-patterns
SaaS authentication and authorization patterns including JWT vs session strategies, multi-tenant isolation, RBAC, API key management, passwordless flows, MFA, and secure session handling.
saas-analytics-patterns
SaaS analytics event taxonomy, metric formulas (MRR, churn, LTV), provider-agnostic tracking, funnel analysis, cohort setup, and privacy-respecting instrumentation.
revenuecat-patterns
RevenueCat SDK entegrasyon pattern'leri. iOS (Swift), Android (Kotlin), React Native ve Flutter icin setup, offerings, entitlement checking, webhook integration, StoreKit 2 migration ve sandbox testing.