taruvi-app-developer

Overview

Entry-point orchestrator for all Taruvi app development. This skill detects the project context, decides whether a serverless function is needed, and routes to the right module skill before any code is written.

Default delivery standard: always build a production-ready, production-scale app. Not a demo, not an MVP, not a prototype. Every feature must be wired to real backend data, use proper error handling, and be built to handle real-world usage. The user must explicitly ask for a reduced scope if they want anything less.

⚠️ Skill Compliance — Non-Negotiable

These skills are the single source of truth for all Taruvi implementation decisions. They override existing project code, template patterns, training data, and personal shortcuts.

Rules:

1. If a skill prescribes a specific way to implement something, use that way. No exceptions, no shortcuts, no "simpler" alternatives.
2. Do not copy patterns from existing project code if they contradict the skills. Existing code may be outdated, a prototype, or pre-skill. The skills define the correct pattern.
3. Do not skip steps to save time. Every step in the skill instructions exists because skipping it causes real bugs or drift.
4. If you cannot implement a skill requirement (missing credentials, missing MCP tool, unclear API), stop and ask the user instead of silently falling back to an easier approach.
5. After implementation, verify against the skill's checklist. If any checklist item fails, fix it before presenting the work as done.