2d-games
Free2D game development principles. Sprites, tilemaps, physics, camera.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
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.
Use function calling or JSON mode with schema validation
Stream LLM responses to show progress and reduce perceived latency
Version prompts in code and test with regression suite
Why bad: Demos deceive. Production reveals truth. Users lose trust fast.
Why bad: Expensive, slow, hits limits. Dilutes relevant context with noise.
Why bad: Breaks randomly. Inconsistent formats. Injection risks.
| Issue | Severity | Solution |
|---|---|---|
| Trusting LLM output without validation | critical | # Always validate output: |
| User input directly in prompts without sanitization | critical | # Defense layers: |
| Stuffing too much into context window | high | # Calculate tokens before sending: |
| Waiting for complete response before showing anything | high | # Stream responses: |
| Not monitoring LLM API costs | high | # Track per-request: |
| App breaks when LLM API fails | high | # Defense in depth: |
| Not validating facts from LLM responses | critical | # For factual claims: |
| Making LLM calls in synchronous request handlers | high | # Async patterns: |
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
2D game development principles. Sprites, tilemaps, physics, camera.
The English summary is being prepared. Showing the original description.
3D game development principles. Rendering, shaders, physics, cameras.
The English summary is being prepared. Showing the original description.
Expert in building 3D experiences for the web - Three.js, React Three Fiber, Spline, WebGL, and interactive 3D scenes. Covers product configurators, 3D portfolios, immersive websites, and bringing depth to web experiences. Use when: 3D website, three.js, WebGL, react three fiber, 3D experience.
The English summary is being prepared. Showing the original description.
Structured guide for setting up A/B tests with mandatory gates for hypothesis, metrics, and execution readiness.
The English summary is being prepared. Showing the original description.
This skill should be used when the user asks to "attack Active Directory", "exploit AD", "Kerberoasting", "DCSync", "pass-the-hash", "BloodHound enumeration", "Golden Ticket", "Silver Ticket", "AS-REP roasting", "NTLM relay", or needs guidance on Windows domain penetration testing.
The English summary is being prepared. Showing the original description.
Use when you need to address review or issue comments on an open GitHub Pull Request using the gh CLI.
The English summary is being prepared. Showing the original description.