Use when editing .lean files, debugging Lean 4 builds (type mismatch, sorry, failed to synthesize instance, axiom warnings, lake build errors), searching mathlib for lemmas, formalizing mathematics in Lean, or learning Lean 4 concepts. Also trigger when the user asks for help with Lean 4, mathlib, or lakefile. Do NOT trigger for Coq/Rocq, Agda, Isabelle, HOL4, Mizar, Idris, Megalodon, or other non-Lean theorem provers.
View, manage, and trigger Atris apps. Use when user asks about their apps, app status, runs, data, or wants to trigger an app.
Use when editing .lean files, debugging Lean 4 builds (type mismatch, sorry, failed to synthesize instance, axiom warnings, lake build errors), searching mathlib for lemmas, formalizing mathematics in Lean, or learning Lean 4 concepts. Also trigger when the user asks for help with Lean 4, mathlib, or lakefile. Do NOT trigger for Coq/Rocq, Agda, Isabelle, HOL4, Mizar, Idris, Megalodon, or other non-Lean theorem provers.
- 📄 code-analyzer.yaml
- 📄 pmd-ruleset.xml
- 📄 SKILL.md
Run Salesforce Code Analyzer on Apex, Trigger, Flow, or metadata files. Use after writing or modifying .cls, .trigger, .xml, or flow files. Also use when asked to scan, lint, or check code quality.
Close the current work session with structured log, unsaved insights check, and open questions routing. Trigger when: (1) user says 'закрываем', 'закрывай сессию', 'всё на сегодня', 'финал', 'заканчиваем', 'close session', (2) user invokes /close-session, (3) user signals end of work session in any way. Do NOT trigger for: git commits, mid-session saves, 'сохрани' without session-closing intent, or 'закрой файл'.
Conduct deep, structured research on any topic — markets, products, features, competitors, problems, industries, regulations, or opportunities. Trigger whenever the user wants to research, explore, investigate, analyze, or understand something. This includes: entering new markets, evaluating products or services, exploring features, solving business problems, competitive landscapes, regulatory research, or any "I need to understand X" scenario. Also trigger for: "look into," "dig into," "explore whether," "map out the landscape," "what are the options for X," "how does Y work in practice." Trigger aggressively — if there's research intent, use this skill. Covers: market research, competitive analysis, feature exploration, regulatory deep-dives, product evaluation, problem-solving, opportunity assessment, landscape mapping. --- # Deep Research Skill ## Core Philosophy Most research is shallow. It covers what's easily Googlable, presents generic overviews, and stops at the surface. This skill exists to go far beyond that. **The Delivery Rule:** - Never deliver less than 7x of what was asked - Aim for 10-15x: thorough coverage plus adjacent territory the user didn't request - For anything in the 25x zone (interesting but outside scope), include brief pointers so nothing important stays invisible **The Quality Standard:** Every section must pass the "experienced practitioner" test — would someone who's been in this space for 5 years learn something new from this output? If not, go deeper. Surface-level overviews are never acceptable as a final deliverable. --- ## Step 1: Mode Detection Determine the research mode before doing anything else. ### Mode A: Guided (Interactive) **Trigger when:** The prompt is vague, broad, ambiguous, or could go in multiple very different directions. Or the user explicitly says "ask me questions first." **Process:** 1. Ask 3-5 sharp questions using the Question Decomposition technique (below) 2. Present a Research Plan and confirm 3. Execute
