Loading...
Loading...
Found 126 Skills
LOAD THIS SKILL when: gathering requirements for new features, user mentions 'requirements', 'requirements-start', 'requirements-end', 'requirements-status', 'requirements-current', 'requirements-list', 'requirements-remind'. Covers structured Q&A workflow with 5-phase requirements gathering, codebase analysis, and spec generation.
Recursive codebase analysis using the RLM paradigm. Use when: analyzing large codebases (100+ files), investigating cross-cutting patterns, recursive decomposition of complex code questions, scanning for issues across entire repos. Triggers: analyze this codebase, how does X work across the codebase, scan all files for Y, recursive analysis, RLM.
Think through ideas, investigate problems, and clarify requirements before committing to a change using `/opsx:explore`. Use when the user says "explore an idea", "think through this", "investigate options", or wants to brainstorm before creating a formal change.
Generate a persistent .nexus-map/ knowledge base that lets any AI session instantly understand a codebase's architecture, systems, dependencies, and change hotspots. Use when starting work on an unfamiliar repository, onboarding with AI-assisted context, preparing for a major refactoring initiative, or enabling reliable cold-start AI sessions across a team. Produces INDEX.md, systems.md, concept_model.json, git_forensics.md and more. Requires shell execution and Python 3.10+. For ad-hoc file queries or instant impact analysis during active development, use nexus-query instead.
This skill should be used when the user asks to "create an implementation plan", "plan a feature", "create detailed plan", "analyze requirements", or needs comprehensive project planning with requirements gathering and architectural analysis.
Analyze codebases from the bottom up and generate a hierarchical README.md document tree. Start analysis from leaf directories, generate README.md files for each directory containing one-sentence descriptions of files, classes, and functions, and summarize layer by layer upwards to form a complete codebase documentation system. Supports state persistence and resumable analysis, suitable for scenarios such as understanding new projects, generating technical documentation, and analyzing code structures. Use this skill when you need to understand codebase structures, analyze function implementations, or generate code documentation.
Resolve implementation ambiguities before planning begins. Two modes: Discussion mode surfaces gray areas with concrete options for greenfield work. Assumptions mode reads the codebase, forms evidence-based opinions, and asks the user to correct only what's wrong (brownfield work). Use for "discuss ambiguities", "resolve gray areas", "clarify before planning", "assumptions mode", "what are the gray areas", "before we plan". Do NOT use for broad design exploration (use feature-design) or for planning itself (use feature-plan).
Generate a compact project map so Claude understands the codebase without opening every file
Analyze a codebase to figure out how it should be tested with Antithesis: map the system, identify failure-prone areas and testable properties, and produce the research artifacts needed for workload and environment planning.
Assess a Rails app's full codebase for compliance with privacy laws, like GDPR and LGPD. Generates an assessment report, not a legal audit.
Runs a trailmark summary analysis on a codebase. Returns language detection, entry point count, and dependency graph shape. Use when vivisect or galvanize needs a quick structural overview. Triggers: trailmark summary, code summary, structural overview.
Use when starting work on a new or unfamiliar project, when encountering unexpected patterns, when user corrects your assumptions, or when explicitly invoked via /learn - auto-discovers and remembers project context through structured codebase analysis