Skill for Claude
Use this workflow when Claude is helping with VeltoKit, Triki UI, and game integration docs.
Download AI skills
One-file prompts for Cursor or Claude. In a clone they are at website/static/skills/. Use the docs Search box in the navbar (⌘K / Ctrl+K) to find SDK topics quickly.
PL: Wyszukiwarka — pole Search w prawym górnym rogu (`⌘K` / `Ctrl+K`). Pobranie skilli — przyciski poniżej lub menu AI Skills → ↓ Download Cursor (.md) / ↓ Download Claude (.md).
Direct links (copy)
- On this site: https://koderhack.github.io/veltokit/skills/cursor-skill.md
- On this site: https://koderhack.github.io/veltokit/skills/claude-skill.md
- GitHub raw: https://raw.githubusercontent.com/koderhack/veltokit/main/website/static/skills/cursor-skill.md
- GitHub raw: https://raw.githubusercontent.com/koderhack/veltokit/main/website/static/skills/claude-skill.md
Best for understanding the repo: open AGENTS.md at the repo root (already in clone). Cursor: skill is at .cursor/skills/veltokit/SKILL.md or paste downloaded file into chat. Claude: attach AGENTS.md or add Project instructions from the downloaded file.
Analysis priorities
- Build architecture context first:
- Verify API intent from usage sites in
app/Gamesandapp/UI. - When documenting, prefer concise developer language over generic text.
Claude execution checklist
- Map all impacted files.
- Separate behavior change from documentation change.
- Keep patches small and composable.
- Add/update Swift
///documentation for touched APIs. - Update docs pages that explain changed behavior (
sdk/*, examples). - Provide clear test/verification notes.
Claude-style prompt templates
1) Deep codebase explanation
Analyze the full flow from BLE ingress to GameInput to game UI behavior.
Focus on MotionSDK, MotionEngine, TrikiInputAdapter, and trikiUIScreen.
Return a concise architecture explanation and risk points.
2) Production-grade documentation pass
Generate high-quality Swift /// documentation for all touched public/internal APIs.
For functions include parameters, return value, side effects, and practical examples.
Do not modify code logic.
3) Safe refactor preparation
Prepare a no-risk refactor plan with explicit file list, acceptance criteria, and rollback strategy.
Then implement in small commits preserving behavior.
Quality bar
- Every explanation should map to concrete symbols/files.
- Examples should mirror real game flows (Pong, Dart, Bowling, Quiz).
- Triki UI docs must cover lifecycle (
isActive), focus mapping, and activation side effects.