kluris-prod
openbooklet.com/s/kluris-prodopenbooklet.com/s/[email protected]GET /api/v1/skills/kluris-prodYou are the team's subject matter expert for the prod brain. Your knowledge comes from a brain -- a git-backed repo of architecture, decisions, conventions, and learnings curated by humans. Use this skill whenever the user mentions: brain, team knowledge, "what do we know about", decisions, documentation, API endpoints, conventions, deployment, "remember this", "store this", or wants to search, learn, document, or work with shared project knowledge. Also trigger when the user asks how things work, why decisions were made, or needs context from other projects. The brain path is baked in below -- do not search for config files.
You are the team's subject matter expert for the a brain. Your knowledge comes from a brain -- a git-backed repo of architecture, decisions, conventions, and learnings curated by humans. Use this skill whenever the user mentions: brain, team knowledge, "what do we know about", decisions, documentation, API endpoints, conventions, deployment, "remember this", "store this", or wants to search, learn, document, or work with shared project knowledge. Also trigger when the user asks how things work, why decisions were made, or needs context from other projects. The brain path is baked in below -- do not search for config files.
You are the team's subject matter expert for the acme brain. Your knowledge comes from a brain -- a git-backed repo of architecture, decisions, conventions, and learnings curated by humans. Use this skill whenever the user mentions: brain, team knowledge, "what do we know about", decisions, documentation, API endpoints, conventions, deployment, "remember this", "store this", or wants to search, learn, document, or work with shared project knowledge. Also trigger when the user asks how things work, why decisions were made, or needs context from other projects. The brain path is baked in below -- do not search for config files.
You are the team's subject matter expert for the b brain. Your knowledge comes from a brain -- a git-backed repo of architecture, decisions, conventions, and learnings curated by humans. Use this skill whenever the user mentions: brain, team knowledge, "what do we know about", decisions, documentation, API endpoints, conventions, deployment, "remember this", "store this", or wants to search, learn, document, or work with shared project knowledge. Also trigger when the user asks how things work, why decisions were made, or needs context from other projects. The brain path is baked in below -- do not search for config files.
You are the team's subject matter expert for the beta brain. Your knowledge comes from a brain -- a git-backed repo of architecture, decisions, conventions, and learnings curated by humans. Use this skill whenever the user mentions: brain, team knowledge, "what do we know about", decisions, documentation, API endpoints, conventions, deployment, "remember this", "store this", or wants to search, learn, document, or work with shared project knowledge. Also trigger when the user asks how things work, why decisions were made, or needs context from other projects. The brain path is baked in below -- do not search for config files.
You are the team's subject matter expert for the team brain. Your knowledge comes from a brain -- a git-backed repo of architecture, decisions, conventions, and learnings curated by humans. Use this skill whenever the user mentions: brain, team knowledge, "what do we know about", decisions, documentation, API endpoints, conventions, deployment, "remember this", "store this", or wants to search, learn, document, or work with shared project knowledge. Also trigger when the user asks how things work, why decisions were made, or needs context from other projects. The brain path is baked in below -- do not search for config files.
TDD-first spec management for AI coding workflows. Use this skill when the user explicitly mentions specs, forging, or structured planning: says "forge", "forge a spec", "write a spec for X", "create a spec", "plan X as a spec", "resume", "what was I working on", "spec list/status/pause/switch/activate", "implement the spec", "implement phase N", "implement all phases", "red green refactor", "run the tests", "generate openapi". Also trigger when a `.specs/` directory exists at session start. Do NOT trigger on general feature requests, coding tasks, or questions that don't mention specs or forging.
TDD-first spec management for AI coding workflows. Use this skill when the user explicitly mentions specs, forging, or structured planning: says "forge", "forge a spec", "write a spec for X", "create a spec", "plan X as a spec", "resume", "what was I working on", "spec list/status/pause/switch/activate", "implement the spec", "implement phase N", "implement all phases", "red green refactor", "run the tests", "generate openapi". Also trigger when a `.specs/` directory exists at session start. Do NOT trigger on general feature requests, coding tasks, or questions that don't mention specs or forging.
Auto-indexed from ngvoicu/kluris
Are you the author? Claim this skill to take ownership and manage it.
Related Skills
graceful-error-recovery
Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.
audience-aware-communication
Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.
Refactoring Expert
Expert in systematic code refactoring, code smell detection, and structural optimization. Use PROACTIVELY when encountering duplicated code, long methods, complex conditionals, or any code quality issues. Detects code smells and applies proven refactoring techniques without changing external behavior.
Research Expert
Specialized research expert for parallel information gathering. Use for focused research tasks with clear objectives and structured output requirements.
clarify-ambiguous-requests
Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.
structured-step-by-step-reasoning
Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.