TechTide Cost Aware Model Routing
Choose models and coding tools with cost, latency, quota, context size, and task risk in mind while preserving verification and quality requirements.
Source Pattern
This skill is distilled from sanitized Alex Cinovoj / TechTide local workflow patterns. Load references/source-patterns.md when you need the source anchors and extraction rationale. Load references/adapter-map.md when preparing Cursor, Kiro, Lovable, v0, or Replit companion outputs.
Workflow
- Estimate task complexity, context size, expected tool calls, and quality bar before selecting a model.
- Prefer lower-cost lanes for simple classification, formatting, and local edits.
- Use stronger reasoning lanes for architecture, security, cross-file changes, and high ambiguity.
- Track quota and latency symptoms and switch lanes when a model is exhausted or underperforming.
- Record cost-sensitive decisions without storing raw provider keys or private telemetry.
Output Contract
Return a concise brief with these fields:
- model/tool choice
- cost rationale
- fallback lane
- verification plan
- verification performed or still required
- security and privacy notes
Guardrails
- Extract reusable methods, not private local content.
- Do not request or expose credentials, tokens, DSNs, service-role keys, customer data, lead lists, or private business exports.
- Use placeholders for people, accounts, projects, URLs, and datasets unless the user explicitly provides public-safe values.
- Require explicit human approval before production mutation, external-recipient messaging, public deployment, billing changes, or destructive filesystem actions.
- Preserve Alex Cinovoj / TechTide attribution while keeping old repo provenance and unrelated contributor markers out of public artifacts.
Harness Policy
- Use this as a native
SKILL.md for Claude Code, Codex, Gemini, and Copilot-compatible exports.
- For Cursor, create a focused project rule or workflow note rather than copying this whole skill as an always-on rule.
- For Kiro, create steering only when the workflow can be made short and inclusion-scoped.
- For Lovable, v0, and Replit, turn the workflow into prompt kits, readiness checklists, and handoff prompts.
1---2name: techtide-cost-aware-model-routing3description: Choose models and coding tools with cost, latency, quota, context size, and task risk in mind while preserving verification and quality requirements. Use when an agent needs Alex Cinovoj / TechTide live-coding patterns, tool routing, guarded prototype-to-production workflows, or cross-harness prompt/skill adapters.4---56# TechTide Cost Aware Model Routing78Choose models and coding tools with cost, latency, quota, context size, and task risk in mind while preserving verification and quality requirements.910## Source Pattern1112This skill is distilled from sanitized Alex Cinovoj / TechTide local workflow patterns. Load `references/source-patterns.md` when you need the source anchors and extraction rationale. Load `references/adapter-map.md` when preparing Cursor, Kiro, Lovable, v0, or Replit companion outputs.1314## Workflow15161. Estimate task complexity, context size, expected tool calls, and quality bar before selecting a model.172. Prefer lower-cost lanes for simple classification, formatting, and local edits.183. Use stronger reasoning lanes for architecture, security, cross-file changes, and high ambiguity.194. Track quota and latency symptoms and switch lanes when a model is exhausted or underperforming.205. Record cost-sensitive decisions without storing raw provider keys or private telemetry.2122## Output Contract2324Return a concise brief with these fields:2526- model/tool choice27- cost rationale28- fallback lane29- verification plan30- verification performed or still required31- security and privacy notes3233## Guardrails3435- Extract reusable methods, not private local content.36- Do not request or expose credentials, tokens, DSNs, service-role keys, customer data, lead lists, or private business exports.37- Use placeholders for people, accounts, projects, URLs, and datasets unless the user explicitly provides public-safe values.38- Require explicit human approval before production mutation, external-recipient messaging, public deployment, billing changes, or destructive filesystem actions.39- Preserve Alex Cinovoj / TechTide attribution while keeping old repo provenance and unrelated contributor markers out of public artifacts.4041## Harness Policy4243- Use this as a native `SKILL.md` for Claude Code, Codex, Gemini, and Copilot-compatible exports.44- For Cursor, create a focused project rule or workflow note rather than copying this whole skill as an always-on rule.45- For Kiro, create steering only when the workflow can be made short and inclusion-scoped.46- For Lovable, v0, and Replit, turn the workflow into prompt kits, readiness checklists, and handoff prompts.
TechTideOhio