skills

Trigger: backup memories, restore memories, máquina nueva, respaldar engram, sync memoria, engram-memories. Backup/restore Engram chunks + Claude auto-memory to gonaas/engram-memories. Skip: in-session mem_save/search (use engram MCP).

Trigger: gentle-ai, configurar agentes, ecosystem doctor, actualizar gentle-ai, sdd status, sdd continue, gga review, skill-registry. Drive the Gentle-AI ecosystem CLI from Claude Code. Skip: running SDD phases (use sdd-* skills).

Trigger: Claude Code, CLAUDE.md, plan mode, shift+tab, MCP, worktrees, hooks, /loop, /schedule, voice mode, permissions, auto mode. Tips from Boris Cherny. Invoke proactively during work — surface tips as user edits.

Create pull requests with Conventional Commits and issue-first checks. Trigger: creating branches, opening PRs, or preparing changes for review.

Trigger: PRs over 400 lines, stacked PRs, review slices. Split oversized changes into chained PRs that protect review focus.

Design docs that reduce cognitive load. Trigger: writing guides, READMEs, RFCs, onboarding, architecture, or review-facing docs.

Write warm, direct collaboration comments. Trigger: PR feedback, issue replies, reviews, Slack messages, or GitHub comments.

Trigger: dot-notation components, Modal.Header, Tabs.Panel, shared state without prop drilling, composable widgets, Radix UI style, shadcn/ui. Build Compound Component pattern with React Context.

Trigger: designing API, interface, hook, undecided on shape, want alternatives, which pattern to choose. 3 parallel designs: minimal, flexible, ergonomic — recommends one. Skip: implementation tasks.

any input (code, docs, papers, images, videos) to knowledge graph. Use when user asks any question about a codebase, documents, or project content - especially if graphify-out/ exists, treat the question as a /graphify query.

Trigger: Next.js App Router, data fetching, Server vs Client components, images, fonts, SEO metadata, Suspense. Next.js 13+ best practices. Skip: non-Next.js React questions.

Trigger: how do I approach X, cómo lo abordo, scope this, help me plan, por dónde empiezo. Bound the problem and recommend approach before writing code. Skip: execution tasks.

Trigger: how to structure a project, architecture choice, hexagonal, clean arch, DDD, vertical slice, feature folders, cómo estructuro, qué arquitectura. Recommends pattern + directory tree for your stack.

Trigger: broken system, 500s, crashes, slow endpoint, failing test, tried multiple fixes. Reproduce first, trace backward, hypothesize once, verify. Skip: new features, refactoring, code review.

Activate when someone is about to write code and tests must come before production code — the Red-Green-Refactor cycle. Explicit triggers: user says "TDD" or "test first"; wants tests written against a spec/interface before the implementation exists. Implicit triggers: any bug fix or hotfix (a failing test capturing the regression always comes first, even for emergencies); implementing a feature or method "correctly" or "the right way." This is a development workflow skill, not a test generator — it guides the implementation process. Skip for: testing theory questions, test framework setup, code review of existing code, and documentation tasks.

Trigger: create a skill, new skill, skill types, how to write a skill, skill best practices, skill design. 9 skill categories, authoring tips, description rules, progressive disclosure.

Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.

Trigger: judgment day, dual review, adversarial review, juzgar. Run blind dual review, fix confirmed issues, then re-judge.

Archive a completed SDD change by syncing delta specs. Trigger: orchestrator launches archive after implementation and verification.

Create the SDD technical design and architecture approach. Trigger: orchestrator launches design for a change.

Explore SDD ideas before committing to a change. Trigger: orchestrator launches exploration or requirement clarification.

Trigger: sdd init, iniciar sdd, openspec init. Initialize SDD context, testing capabilities, registry, and persistence.

Walk users through the SDD workflow on the real codebase. Trigger: orchestrator launches onboarding for the full SDD cycle.

Create an SDD change proposal with intent, scope, and approach. Trigger: orchestrator launches proposal work for a change.

Write SDD delta specs with requirements and scenarios. Trigger: orchestrator launches spec work for a change.

Break an SDD change into implementation tasks. Trigger: orchestrator launches task planning for a change.

Shared SDD references for installed skills. Not invokable.

Invoke this skill immediately when the user wants to: create a new Claude Code skill for any purpose, convert a workflow or conversation into a reusable skill, edit or improve an existing skill, run evals or benchmark skill performance, compare skill versions, or optimize skill triggering. This applies whether the user says "make a skill", "turn this into a skill", "I need a skill for X", or any variation in any language. Do not attempt skill creation, evaluation, or optimization without this skill — it provides the full methodology, eval scripts, and review tooling you need.