Llm App Dev

This is a Hermes-native llm-app-dev workflow skill.

Why This Exists

llm-app-dev exists because the failure modes of an LLM feature are not the failure modes of the code around it. A floating model alias, a prompt buried in a string literal, an output scraped out of prose with a regex, and a retrieval layer nobody measured all pass code review and all fail in production, and without a golden set nobody can tell whether the next prompt edit helped or hurt.

Do Not Use When

• The subject is comparing executors or agent harnesses - Codex against Claude Code against Hermes coding - rather than evaluating the product's own model calls; use agent-evaluation.
• An agent run is already stuck, looping, or drifting and needs diagnosis; use agent-debug.
• The subject is the harness's own context window, prompt caching, or token budget rather than the application being built; use context-budget-review.
• The request is a prompt-injection, secret-handling, or dependency risk gate on work that already exists; use security-safety-review.
• The feature makes no model call - the LLM is only mentioned as the subject being discussed - so this is a direct answer, not a build handoff.

Examples

Good example: