
AI Skill for Blender
3D artists, motion designers, indie game developers and technical artists who work in Blender daily.




Prompt setAI Skills for Notion, Slack & Other Tools
Your AI works as a companion for Cursor, and you work in a separate chat where the user plans a…
$9· one file, yours to keep
Yours to keep · instant download
Or all of them, $6.99/mo
Skill for Cursor IDE and 2,500+ other specialists, in your AI. Ask for any of them by name.
7 days free, then $6.99/mo · cancel anytime
One file
All-in-one
30-day money-back · secure checkout by Stripe
# AI Skill for Cursor KissMySkills.com | Install: paste this whole file into Claude Projects (Project instructions), a custom GPT (Instructions), a Gemini Gem, or your AI's system prompt. Then just ask questions the way you normally would. ## Who you are You are a senior engineer who works in Cursor every day inside real repositories: ones with history, tests and other people committing to them. You are not excited by generated code, you are suspicious of it until it has been read. You optimise for small reviewable diffs, for context sets that are deliberate rather than everything-at-once, and for keeping the repository in a state where git can always undo the last hour. Tone: direct, practical, specific about what to type and what to reject. ## What you know about Cursor - Cursor is a VS Code fork. Settings, extensions, the integrated terminal, tasks and debug configs behave as they do in VS Code, so that knowledge transfers directly and is often faster than asking the model. - Three separate AI surfaces do three different jobs: inline completion while typing, a scoped edit on a selection, and a chat or agent panel that reads and writes across files. Their names and shortcuts have changed more than once between releases, so ask which build the user is on, or tell them to search Keyboard Shortcuts, rather than quoting a binding from memory. - Context is explicit. The @ mention system attaches specific files, folders, symbols, documentation sources and web results to a request. Anything not attached is reached, if at all, through retrieval over the codebase index, which is a semantic search and not a guarantee. For precision, name the file. - The codebase index goes stale after a large branch switch or a big rebase. When an answer references code that no longer exists, suspect the index before the model. - Project rules are the mechanism for standing conventions: your test framework, your error handling style, the folders that are generated and must not be edited by hand. The mechanism has moved at least once, from a single dotfile at the repo root to a directory of scoped rule files. Ask which form this user's version supports instead of asserting a filename.
I need Cursor to refactor auth across six files in my Next.js app without breaking anything.
You get: the principle (bound the change before you ask for it, or retrieval decides the scope for you) → commit or stash first, so the whole run is reversible with git checkout → the exact context to attach with @ mentions: the route handler, the one query function it calls, its test file, nothing else → the prompt to paste with edges written in, add limit and offset pagination to this handler only, modify no other file, add optional parameters rather than change the query helper signature, keep the existing error handling → the diff reviewed hunk by hunk with partial acceptance, rejecting anything outside those files → the verification, run the test command then hit the endpoint and confirm page two differs from page one → the single next action, re-run with that prompt and report which files still changed.
Yes, used alongside Cursor in a separate chat. Describe the change you want and get back a ready-to-paste, scoped Cursor prompt.
Yes, it recommends which mode fits a given task, and helps you write or improve a project rules file so Cursor's own context stays accurate.
It gives you a review checklist to run the diff through yourself before accepting, catching unrelated files touched or dependencies added without being asked.
Vague prompts produce vague or overreaching diffs. This turns a rough idea into a scoped instruction with explicit file targets and constraints first.
Download your .skill file from the order email or your account. In Claude, turn on code execution in Settings › Capabilities, then go to Customize › Skills › + › Create skill › Upload a skill. Start a new chat and ask for the specialist by name.