proof-theory
Problem-solving strategies for proof theory in mathematical logic
Problem-solving strategies for proof theory in mathematical logic
Document modeling, aggregation pipeline, indexing strategy, change streams, and multi-document transactions.
Use this skill when context compression is imminent, when resuming a session, or when preserving critical decisions across long tasks. Provides a durable notepad that survives compaction and lets any agent pick up exactly where the previous context left off.
External research workflow for docs, web, APIs - NOT codebase exploration
IWSDK project planning and best practices guide. Use when planning new IWSDK features, designing systems/components, reviewing IWSDK code architecture, or when the user asks about IWSDK patterns, ECS design, signals, or reactive programming in this codebase.
Multi-step web research, compilation, and synthesis workflow. Scrapes multiple sources, cross-references claims, and produces a structured research brief.
Use when given a Linear issue ID, URL, identifier, or project name/URL to analyze and plan work. For issues, fetches the issue, classifies it, explores relevant code, proposes an approach, and orchestrates the right skills. For projects, fetches the project with milestones and issues, builds a prioritized execution plan, and systematically works through issues respecting project structure and dependencies.
Ensures Jupyter notebooks have required metadata and nbformat. Use when adding, creating, or modifying .ipynb files, or when the user asks about notebook structure or validation.
Codex-native entry skill for reflecting first and then updating llmdoc. Use this when you want the /llmdoc:update workflow in Codex.
Add a new paper to the WarpX science highlights documentation (`Docs/source/highlights.rst`).
MindOS is the user's local knowledge assistant and shared knowledge base. It keeps decisions, meeting notes, SOPs, debugging lessons, architecture choices, research findings, and preferences available across sessions and agents. ๆดๆฐ็ฌ่ฎฐ, ๆ็ดข็ฅ่ฏๅบ, ๆด็ๆไปถ, ๆง่กSOP/ๅทฅไฝๆต, ๅค็, ่ฟฝๅ CSV, ่ทจAgentไบคๆฅ, ่ทฏ็ฑ้็ปๆๅ่พๅ ฅๅฐๅฏนๅบๆไปถ, ๆ็ผ็ป้ช, ๅๆญฅๅ ณ่ๆๆกฃ. NOT for editing app source, project docs, or paths outside the KB. Core concepts: Space, Instruction (INSTRUCTION.md), Skill (SKILL.md); notes can embody both. Trigger on: save or record anything, search for prior notes or context, update or edit a file, organize notes, run a workflow or SOP, capture decisions, append rows to a table or CSV, hand off context to another agent, check if something was discussed before, look up a past decision, distill lessons learned, prepare context for a meeting, quick-capture to staging area, organize inbox, check knowledge health, detect conflicts or contradictions, find stale content. Chinese triggers: ๅธฎๆ่ฎฐไธๆฅ, ๆไธไธ็ฌ่ฎฐ, ๆดๆฐ็ฅ่ฏๅบ, ๆด็ๆไปถ, ๅค็, ๆ็ผ็ป้ช, ไฟๅญ, ่ฎฐๅฝ, ไบคๆฅ, ๆฅไธไธไนๅ็, ๆๆฒกๆ็ธๅ ณ็ฌ่ฎฐ, ๆ่ฟไธช
MindOS is the user's local knowledge assistant and global memory layer. It keeps decisions, meeting notes, SOPs, debugging lessons, architecture choices, research findings, preferences, and conversation summaries available to every connected agent. PROACTIVE USE โ do not wait for the user to say "save to knowledge base": (1) Before answering any question about past decisions, discussions, or context โ search MindOS first. (2) After any valuable output (decision made, bug fixed, lesson learned, meeting summarized) โ offer to save it. (3) When handing off to another agent or ending a session โ persist key context to MindOS. Trigger on ALL of these, even without explicit "MindOS" mention: save/record anything, search prior notes, update files, organize/restructure, run SOPs or workflows, retrospective, append CSV/table data, cross-agent handoff, distill experience, sync related docs, check if something was discussed before, look up a past decision, find a template, prepare meeting context, daily logging, track g
Operate a MindOS knowledge base: update notes, search, organize files, execute SOPs/workflows, retrospective, append CSV, cross-agent handoff, route unstructured input to the right files, distill experience, sync related docs. Use when the task targets files inside the user's MindOS KB (mindRoot). NOT for editing app source, project docs, or paths outside the KB. Core concepts: Space, Instruction (INSTRUCTION.md), Skill (SKILL.md); notes can embody both. Trigger when user asks to: save or record a note, search their knowledge base, update or edit a file, organize notes, run a workflow or SOP, capture decisions from a session, append rows to a table or CSV, hand off context to another agent.
MindOS is the user's local knowledge assistant and shared knowledge base. It keeps decisions, meeting notes, SOPs, debugging lessons, architecture choices, research findings, and preferences available across sessions and agents. ๆดๆฐ็ฌ่ฎฐ, ๆ็ดข็ฅ่ฏๅบ, ๆด็ๆไปถ, ๆง่กSOP/ๅทฅไฝๆต, ๅค็, ่ฟฝๅ CSV, ่ทจAgentไบคๆฅ, ่ทฏ็ฑ้็ปๆๅ่พๅ ฅๅฐๅฏนๅบๆไปถ, ๆ็ผ็ป้ช, ๅๆญฅๅ ณ่ๆๆกฃ. NOT for editing app source, project docs, or paths outside the KB. Core concepts: Space, Instruction (INSTRUCTION.md), Skill (SKILL.md); notes can embody both. Trigger on: save or record anything, search for prior notes or context, update or edit a file, organize notes, run a workflow or SOP, capture decisions, append rows to a table or CSV, hand off context to another agent, check if something was discussed before, look up a past decision, distill lessons learned, prepare context for a meeting, quick-capture to staging area, organize inbox, check knowledge health, detect conflicts or contradictions, find stale content. Chinese triggers: ๅธฎๆ่ฎฐไธๆฅ, ๆไธไธ็ฌ่ฎฐ, ๆดๆฐ็ฅ่ฏๅบ, ๆด็ๆไปถ, ๅค็, ๆ็ผ็ป้ช, ไฟๅญ, ่ฎฐๅฝ, ไบคๆฅ, ๆฅไธไธไนๅ็, ๆๆฒกๆ็ธๅ ณ็ฌ่ฎฐ, ๆ่ฟไธช
็ป็ปๅ็ปดๆค Vibe Coding ้กน็ฎ็ wiki ๆๆกฃไฝ็ณปใๅฝ็จๆท่ฆๆฑๅๅงๅ/้ๆ wiki ็ปๆใ่ฟๅ ฅๆฐ้กน็ฎไธ wiki/ ไธๅญๅจใ้่ฆ่ฏๆญๅไฟฎๅคๆๆกฃ่ ๅใๆ้่ฆ็ฎก็ specs/refs/reviews ๅญ็ฎๅฝ็็ๅฝๅจๆๆถ่งฆๅใ
Expertise in creating detailed, atomic, and safe implementation plans. Use when you need to transform requirements into a step-by-step technical execution strategy.
Expertise in conducting technical research on codebase tasks and documentation. Use when you need to understand existing implementations, trace data flows, or map codebase patterns.
Conduct Neovim configuration research using plugin docs and codebase exploration. Invoke for neovim research tasks.
Scan codebase for FIX:/NOTE:/TODO:/QUESTION: tags and create structured tasks with interactive selection. Invoke for /fix-it command.
Conduct Neovim configuration research using plugin docs and codebase exploration. Invoke for neovim research tasks.
Scan files for FIX:/NOTE:/TODO:/QUESTION: tags and create structured tasks with interactive selection and topic grouping. Invoke for /fix-it command.
Tabular Editor documentation search and configuration file guidance (.tmuo, Preferences.json, UiPreferences.json, Layouts.json). Automatically invoke when the user asks about "TE docs", "Tabular Editor features", "TE3 preferences", ".tmuo files", "workspace database settings", "DAX editor settings", "per-model TE3 configuration", or needs to search Tabular Editor documentation for how-to guidance.