Claude Skills

Explore and understand Nx workspaces. USE WHEN answering any questions about the nx workspace, the projects in it or tasks to run. EXAMPLES: 'What projects are in this workspace?', 'How is project X configured?', 'What targets can I run?', 'What's affected by my changes?', 'Which projects depend on library Y?', or any questions about Nx workspace structure, project configuration, or available tasks.

Use when transforming synthesis insights into explicit decisions with documented trade-offs. Guides interactive decision-making and risk identification.

Use when starting a new product development project that needs traceable evidence and explicit decisions. Creates workspace structure from a project brief.

Use when generating PRD and architecture documents that must trace back to explicit decisions. Enforces citation requirements so no spec content exists without DEC-* references.

Use when researching a specific pillar and need to create traceable evidence objects. Guides creation of YAML evidence files with semantic IDs, confidence scores, and assumptions.

Design and implement wide-event logging with tail sampling for context-rich, queryable observability

Use before workflow execution to discover available agents, skills, and quality commands in the project environment. Use when adapting gh-workflow commands to project-specific tooling.

Use when asked for "deep research", "thorough analysis", "comprehensive report", "investigate", "due diligence", or when multiple sources are needed to answer complex questions. Produces well-sourced research reports through iterative refinement.

This skill should be used when the user asks to "export Claude session history", "extract my Claude messages", "get Claude session transcript", "save my messages from this Claude session", "preserve Claude session context", "extract user messages from Claude sessions", mentions "Claude Code session.jsonl files", or needs to retrieve user messages and session summaries from Claude Code session transcript files for documentation or debugging purposes.

This skill should be used when the user asks to "explain changes", "explain what was done", "explain the diff", "describe modifications", "what did I change", "summarize changes", "explain my code changes", "review my changes", "what happened", "walk me through the changes", or needs detailed explanation of git changes with educational insights.

Complete project generation pipeline with Task tool multi-agent orchestration. Requirements -> Design -> Tasks -> Project -> Implementation.

AIDA pipeline orchestration with Task tool multi-agent delegation. Manages 5-phase workflow with Leader/Player subagents.

This skill should be used when the user invokes /gtr:* commands to manage git worktrees using git-worktree-runner (gtr). Enables parallel branch development through worktree creation, editor/AI integration, and lifecycle management.

Link triplet entities to soul nodes - connects knowledge layers

RLM-style recursive memory exploration - dynamically navigate the memory graph

Soul system health check with remediation

Expertise in terminal command execution, shell scripting patterns, and command-line workflows. Use when executing commands via ~~terminal, debugging command failures, or building shell pipelines.

Soul self-examination (Svadhyaya)