Cloud cost optimization, token/API cost tracking, build time optimization, and FinOps patterns
npx skills add https://github.com/vibeeval/vibecosystem --skill cost-optimization-patterns
# AWS - Compute Optimizer önerileri
aws compute-optimizer get-ec2-instance-recommendations
# CPU/Memory utilization < 20% → downsize
# CPU/Memory utilization > 80% → upsize veya auto-scale
| Strateji | Tasarruf | Risk | Use Case |
|----------|---------|------|----------|
| On-Demand | 0% | Düşük | Değişken workload |
| Reserved (1yr) | %30-40 | Orta | Steady-state |
| Reserved (3yr) | %50-60 | Yüksek | Uzun vadeli |
| Spot/Preemptible | %60-90 | Yüksek | Batch, CI/CD |
| Savings Plans | %30-50 | Düşük | Flexible commitment |
Lambda cost = (requests × $0.20/1M) + (GB-seconds × $0.0000166)
Optimizasyon:
1. Memory right-sizing (power tuning)
2. Provisioned concurrency (cold start vs cost tradeoff)
3. ARM architecture (%20 ucuz)
4. Batch processing (SQS batch size)
// Token maliyet takibi
const MODEL_COSTS = {
'claude-opus-4-6': { input: 15.0, output: 75.0 }, // per 1M tokens
'claude-sonnet-4-6': { input: 3.0, output: 15.0 },
'claude-haiku-4-5': { input: 0.80, output: 4.0 }
} as const
function estimateCost(model: string, inputTokens: number, outputTokens: number) {
const costs = MODEL_COSTS[model]
return (inputTokens * costs.input + outputTokens * costs.output) / 1_000_000
}
| Teknik | Tasarruf | Karmaşıklık |
|--------|---------|-------------|
| Dependency caching | %30-50 | Düşük |
| Parallel test execution | %40-60 | Düşük |
| Incremental builds | %50-70 | Orta |
| Docker layer caching | %20-40 | Düşük |
| Affected-only (monorepo) | %60-80 | Orta |
-- Pahalı query'leri bul
SELECT query, calls, mean_exec_time, total_exec_time
FROM pg_stat_statements
ORDER BY total_exec_time DESC
LIMIT 20;
-- Unused index'leri bul (gereksiz storage + write overhead)
SELECT indexrelname, idx_scan
FROM pg_stat_user_indexes
WHERE idx_scan = 0 AND indexrelname NOT LIKE '%pkey%';
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
Take vibeeval/cost-optimization-patterns from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.