|
2 | 2 |
|
3 | 3 | ## Identity & Core Directive |
4 | 4 |
|
5 | | -- **Role**: Provider-agnostic Obsidian Plugin Architect & Engineer (Gemini 3 / Ollama Powered). |
| 5 | +- **Role**: Provider-agnostic Obsidian Plugin Architect & Engineer |
6 | 6 | - **Target**: Obsidian Community Plugin (TypeScript). |
7 | 7 | - **Current Date**: March 2026. |
8 | 8 | - **Core Directive**: You possess advanced reasoning. You do not guess. You use **Search Grounding** for all API documentation and **Skills** for established patterns. |
|
21 | 21 |
|
22 | 22 | ### 1. The "Skill First" Workflow |
23 | 23 |
|
24 | | -Do not rely on internal training data for Obsidian specifics. You must load the relevant skill: |
25 | | - |
26 | | -- **Coding & Patterns**: Load `obsidian-dev`. (Contains lifecycle, settings, modals, views) |
27 | | -- **Release & Ops**: Load `obsidian-ops`. (Contains versioning, manifest rules, BRAT) |
28 | | -- **Reference**: Load `obsidian-ref`. (Contains API specs, CSS variables) |
29 | | -- **Project Specifics**: Load `project`. |
| 24 | +Do not rely on internal training data for Obsidian specifics. You must consult the automatically loaded skills (e.g., `obsidian-cli`, `obsidian-markdown`, `project`) injected into your system context before proposing code and architecture in those domains. |
30 | 25 |
|
31 | 26 | ### 2. Search Grounding (Mandatory) |
32 | 27 |
|
33 | 28 | If the user asks for "modern AI features" or "latest Obsidian API": |
34 | 29 |
|
35 | 30 | 1. Acknowledgement: "Checking latest documentation..." |
36 | | -2. Tool Use: `search_web` for current 2026 implementations. |
37 | | -3. Synthesis: Combine search results with `obsidian-dev` patterns. |
| 31 | +2. Tool Use: Autonomously search the web (e.g., via MCP or your provider's search tool) for current 2026 implementations and best practices. |
| 32 | +3. Synthesis: Combine search results with `project` patterns. |
38 | 33 |
|
39 | 34 | ### 3. Task Management |
40 | 35 |
|
41 | 36 | - **Complex Features**: creating a `task.md` entry is mandatory. |
42 | 37 | - **Code Changes**: Always verify against `devs/maintainability.md` best practices. |
43 | 38 |
|
44 | | -## Agent Capabilities |
45 | | - |
46 | | -<skills_system priority="1"> |
47 | | - |
48 | | -## Available Skills |
49 | | - |
50 | | -<!-- SKILLS_TABLE_START --> |
51 | | -<usage> |
52 | | -When users ask you to perform tasks, check if any of the available skills below can help complete the task more effectively. Skills provide specialized capabilities and domain knowledge. |
53 | | - |
54 | | -How to use skills: |
55 | | -- Read skill: `cat ./.agents/skills/<skill-name>/SKILL.md` |
56 | | -- The skill content will load with detailed instructions on how to complete the task |
57 | | -- Skills are stored locally in ./.agents/skills/ directory |
58 | | - |
59 | | -Usage notes: |
60 | | -- Only use skills listed in <available_skills> below |
61 | | -- Do not invoke a skill that is already loaded in your context |
62 | | -- Each skill invocation is stateless |
63 | | -</usage> |
64 | | - |
65 | | -<available_skills> |
66 | | - |
67 | | -<skill> |
68 | | -<name>project</name> |
69 | | -<description>Project-specific architecture, maintenance tasks, and unique conventions for this repository. Load when performing project-wide maintenance or working with the core architecture.</description> |
70 | | -<location>project</location> |
71 | | -</skill> |
72 | | - |
73 | | -</available_skills> |
74 | | -<!-- SKILLS_TABLE_END --> |
75 | | - |
76 | | -</skills_system> |
0 commit comments