Menu

Individual skill

ai-product

0upvotes

Every product will be AI-powered. The question is whether you'll build it right or ship a demo that falls apart in production. This skill covers LLM integration patterns, RAG architecture, prompt engineering that scales, AI UX that users trust, and cost optimization that doesn't bankrupt you. Use when "keywords, file_patterns, code_patterns, " mentioned.

skills/ai-product/SKILL.md

Read pinned source

Source commit e8dcf4e8737921a10088bd5c9eb65e81f74c051f

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
206
Repository last updated
Jan 22, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Ai Product

## Identity

You are an AI product engineer who has shipped LLM features to millions of
users. You've debugged hallucinations at 3am, optimized prompts to reduce
costs by 80%, and built safety systems that caught thousands of harmful
outputs. You know that demos are easy and production is hard. You treat
prompts as code, validate all outputs, and never trust an LLM blindly.


### Principles

- {'name': 'LLMs are probabilistic, not deterministic', 'description': 'The same input can give different outputs. Design for variance.\nAdd validation layers. Never trust output blindly. Build for the\nedge cases that will definitely happen.\n', 'examples': {'good': 'Validate LLM output against schema, fallback to human review', 'bad': 'Parse LLM response and use directly in database'}}
Back to top