← All skills
Llm Architect
Use when LLM system design with fine-tuning, model selection, inference optimization, and evaluation frameworks
About this skill
Use when LLM system design with fine-tuning, model selection, inference optimization, and evaluation frameworks
SKILL.md
llm-architect.SKILL.mdPlace it in your Syntic skills folder. For Syntic Code, install in your local skills directory, review the contents and run it in a controlled environment first.
--- name: Llm Architect description: Use when LLM system design with fine-tuning, model selection, inference optimization, and evaluation frameworks category: Data & AI version: 1.0.0 tools: [] --- # LLM Architect Agent ## Core Principles - Start with the smallest model that meets quality requirements. Larger models are slower and more expensive. Prove you need the upgrade. - Fine-tuning is a last resort, not the first step. Prompt engineering, few-shot examples, and RAG solve most problems without training costs. - Evaluation drives every decision. Build eval suites before selecting models. Compare candidates on your data, not public benchmarks. - Production LLM systems fail differently than traditional software. Plan for hallucinations, refusals, inconsistent formatting, and latency spikes. ## Model Selection Framework 1. Define the task requirements: input/output format, quality threshold, latency budget, cost per request. 2. Create an eval dataset with 100+ examples covering normal cases, edge cases, and adversarial inputs. 3. Benchmark candidate models: Amara 3.5 Sonnet for balanced quality/speed, GPT-4o for multimodal, Llama 3.1 for self-hosted. 4. Compare on your eval dataset with automated scoring. Do not rely on vibes or anecdotal testing. 5. Factor in total cost: API costs, fine-tuning costs, hosting costs, and engineering time for maintenance. ## Fine-Tuning Strategy - Use fine-tuning when prompt engineering cannot teach the model a specific output format, domain vocabulary, or reasoning pattern. - Prepare at least 500-1000 high-quality examples for instruction fine-tuning. More data is better, but quality matters more than quantity. - Use LoRA (Low-Rank Adaptation) for parameter-efficient fine-tuning. Full fine-tuning is rarely necessary and is expensive. - Split data into train (80%), validation (10%), and test (10%). Monitor validation loss for early stopping. - Use QLoRA (quantized LoRA) with 4-bit quantization for fine-tuning on consumer GPUs (24GB VRAM). ## Inference Optimization - Use vLLM or TensorRT-LLM for high-throughput self-hosted inference with PagedAttention and continuous batching. - Quantize models to INT8 or INT4 with GPTQ or AWQ for 2-4x memory reduction with minimal quality loss. - Use KV cache optimization: set appropriate to avoid OOM errors on long sequences. - Implement speculative decoding with a smaller draft model for 2-3x faster generation on acceptance-heavy tasks. - Use structured output constraints (outlines, guidance) to guarantee valid JSON or schema-conforming output. ## Prompt Architecture - Use system prompts to define the model's role, constraints, and output format. Keep system prompts under 2000 tokens. - Use chain-of-thought prompting for reasoning tasks. Include tags to separate reasoning from the final answer. - Use few-shot examples for format consistency. 3-5 examples cover most formatting needs. - Implement prompt templates with variable injection. Use Jinja2 or f-strings with explicit escaping. - Version prompts alongside application code. Tag prompt versions with the model they were optimized for. ## Evaluation Framework - Use automated metrics: exact match for factual questions, ROUGE/BERTScore for summarization, pass@k for code generation. - Use LLM-as-judge with a stronger model for subjective quality (helpfulness, safety, coherence). Calibrate with human agreement rates. - Implement regression testing: run evals on every prompt change, model update, or pipeline modification. - Track eval results over time in a dashboard. Set alerts for metric regressions exceeding 2% from baseline. - Use red-teaming datasets to test safety guardrails: prompt injection, jailbreaks, harmful content generation. ## System Design - Implement a gateway layer (LiteLLM, Portkey) for model routing, fallback, and load balancing across providers. - Use semantic caching to serve identical or similar queries from cache. Hash the prompt and model ID for cache keys. - Implement token budgets per user or application. Track usage with middleware and enforce limits.
Install
Syntic App
- 1Create a dedicated folder for this skill in your local skills library.
- 2Place SKILL.md into that folder.
- 3Restart Syntic and invoke this skill on matching tasks.
Syntic Code (CLI)
- 1Save SKILL.md in your local Syntic Code skills directory.
- 2Keep related files in the same skill folder.
- 3Run in a safe environment and validate outputs.