MANDATORY. DO NOT finalize an implementation plan or commit to a single solution for a complex task without calling 'activate_skill' on 'deep-brainstorming' first. This is the REQUIRED PROTOCOL for exploring multiple solutions using Tree of Thought and Red Teaming. This skill is the MANDATORY GATEWAY for any task involving 'brainstorming', 'exploring possibilities', 'thinking deeply', or 'analyzing trade-offs'. TRIGGER THIS SKILL IMMEDIATELY for all architectural exploration and divergent thinking tasks. Use it to prevent 'path lock' and ensure that the final implementation is the most robust and efficient solution. DO NOT skip for any task that involves architectural choices or complex problem-solving. Proceeding with convergent action without divergent exploration constitutes a protocol failure.
MANDATORY. DO NOT synthesize, summarize, or analyze any complex resource (PDFs, docs, web pages) without calling 'activate_skill' on 'deep-reading-agent-skill' first. This is the REQUIRED PROTOCOL for deep-dive analysis and sectional reflection. This skill is the MANDATORY GATEWAY for any task involving 'reading deeply', 'analyzing nuances', 'reflecting on the spirit', or 'extracting deep insights'. TRIGGER THIS SKILL IMMEDIATELY for all synthesis and detailed research tasks. It prevents 'surface-level reading' and ensures a comprehensive understanding of a resource's core message and underlying details through a strict section-by-section audit. Use it to maintain high-signal synthesis for long-form resources. Proceeding with analysis without this deep-reading protocol constitutes a protocol failure.
MANDATORY. DO NOT design, scaffold, audit, or modify any AI agent skills or system prompts without calling 'activate_skill' on 'engineering-agent-skills' first. This is the REQUIRED PROTOCOL to ensure production-grade 'Action-Oriented Nudging' and prevent 'Instructional Dilution'. TRIGGER IMMEDIATELY for any task involving 'modifying the extension', 'writing a new skill', or 'refining a workflow'. Use this as the exclusive mechanical gateway for all prompt engineering and agent skill lifecycle tasks. Proceeding with file modifications without this skill constitutes a protocol failure. It translates the core principles of 'Action-Oriented Nudging' and 'Context Economics' into functional system prompts and deterministic tools. MANDATORY for all extension development, prompt engineering, and agent skill lifecycle tasks. DO NOT skip this skill when building or refining any AI-facing instructions.
MANDATORY. DO NOT attempt to "patch" a bug or "fix" an error without calling 'activate_skill' on 'performing-systematic-root-cause-analysis' first. This is the REQUIRED PROTOCOL for a hypothesis-driven, adversarial-reviewed investigation cycle. It enforces a strict 5-step loop: Evidence Analysis -> Hypothesis Generation (3+) -> Adversarial Review -> Solution Selection (3+) -> Implementation with Checkpoint/Backtrack. Trigger this for all tasks involving "investigate", "bug", "error", "failure", or "root cause". Proceeding with tactical fixes without this strategic audit constitutes a protocol failure.
MANDATORY. DO NOT create a pull request, open a merge request, or submit code for review without calling 'activate_skill' on 'collaborating-on-git-projects' first. This is the REQUIRED PROTOCOL for ensuring high-signal repository history and 'No Filler' PR bodies on GitHub (gh) and GitLab (glab). This skill is the MANDATORY GATEWAY for any task involving 'creating a PR', 'opening a Merge Request', 'handling PR feedback', or 'PR standards'. TRIGGER THIS SKILL IMMEDIATELY for all code submissions and collaboration tasks. It focuses on the 'Technical Why' and ensures that every contribution is clearly communicated and grounded in established project conventions. Use it to maintain a high-quality codebase and clear communication with peers. Proceeding with PR/MR creation without this high-signal documentation gateway constitutes a protocol failure.
MANDATORY. DO NOT attempt to interact with GitHub APIs, post PR comments, or manage GitHub Actions/checks without calling 'activate_skill' on 'interacting-with-github' first. This is the REQUIRED PROTOCOL for all GitHub-related engineering tasks. TRIGGER THIS SKILL IMMEDIATELY when the user asks to "create a PR", "start a review", "submit a review", "comment on a line", "check the actions", "search GitHub", "view an issue", "check vulnerabilities", or "manage GitHub projects". It provides a specialized suite of MCP tools (github_*) that handle the full reviewer/submitter lifecycle, including PR discovery, multi-comment reviews, automated SHA discovery, search, security auditing, and deterministic pipeline monitoring. Proceeding with manual 'gh' or 'gh api' calls for these tasks constitutes a protocol failure.
MANDATORY. DO NOT attempt to interact with GitLab APIs, post line-level comments, reply to discussions, or manage GitLab pipelines/issues without calling 'activate_skill' on 'interacting-with-gitlab' first. This is the REQUIRED PROTOCOL for all GitLab-related engineering tasks. TRIGGER THIS SKILL IMMEDIATELY when the user asks to "create an MR", "start a review", "submit a review", "comment on a line", "check the pipeline", "search GitLab", "view an issue", "check vulnerabilities", "set auto-merge", or "manage GitLab projects". It provides a specialized suite of MCP tools (gitlab_*) that handle the full reviewer/submitter lifecycle, including MR discovery, multi-comment reviews, automated SHA discovery, search, security auditing, and deterministic pipeline monitoring. Proceeding with manual 'glab' or 'glab api' calls for these tasks constitutes a protocol failure.
MANDATORY. DO NOT use generic tools like 'web_fetch' or 'google_web_search' for deep-dive codebase exploration, library investigation, or repository discovery without calling 'activate_skill' on 'investigating-external-dependencies' first. This is the REQUIRED PROTOCOL for analyzing any local repository, library internals, or third-party source code. TRIGGER THIS SKILL IMMEDIATELY when the user asks 'How does [Library] work?', 'Where is [Symbol] defined?', 'Check the source for [X]', or 'read the code of this repo'. It explicitly replaces generic discovery tools with a senior-level workflow using deep file analysis and grep to find the ground truth. Use it to discover the grain of an unfamiliar codebase and ensure implementation alignment with existing patterns. MANDATORY for all repository-specific investigation tasks. Proceeding with generic search for local discovery constitutes a protocol failure.