obsidian-dev-skills 1.0.4 → 1.0.5

package/README.md

@@ -12,19 +12,42 @@ obsidian-dev-skills/
 └── obsidian-ref/             # Technical references
 ```
 
-## Getting Started
+## Installation & Usage
 
-### For Developers
+This package can be used as a development dependency in your Obsidian project.
 
-This repository is automatically set up by the `setup-ref-links` script in the template projects.
+### 1. Install to your project
+```bash
+# Using pnpm (Recommended)
+pnpm add -D obsidian-dev-skills
 
-### For Users
+# Using npm
+npm install --save-dev obsidian-dev-skills
 
-This repository is automatically managed by the template projects. Simply run the `setup-ref-links` script in your template project to get started.
+# Using yarn
+yarn add -D obsidian-dev-skills
+```
+
+### 2. Initialize localized skills
+Run the initialization script to seed the `.agent/skills/` folder. This also creates a project-specific skill template if one is missing.
 
-### For Developers
+```bash
+# Using pnpm (Standard entry point)
+pnpm obsidian-dev-skills
 
-The `setup-ref-links` script clones this repository to your `.ref` folder and creates the necessary symlinks.
+# Using npx (Universal entry point)
+npx obsidian-dev-skills
+
+# Manual execution
+node node_modules/obsidian-dev-skills/scripts/init.mjs
+```
+
+### 3. Sync AI Agents
+Ensure `AGENTS.md` is aligned with the localized skills.
+
+```bash
+npx openskills sync
+```
 
 ## Skills Overview
 

package/obsidian-ops/references/sync-procedure.md

@@ -61,9 +61,15 @@ if ($item.LinkType -eq "Junction" -or $item.LinkType -eq "SymbolicLink") {
 ```bash
 # Check if a specific repo is a symlink
 if [ -L .ref/obsidian-api ]; then
-    echo "Symlink detected - target: $(readlink .ref/obsidian-api)"
+    # Portable approach for macOS/BSD and Linux
+    if command -v realpath >/dev/null 2>&1; then
+        TARGET=$(realpath .ref/obsidian-api)
+    else
+        TARGET=$(readlink .ref/obsidian-api)
+    fi
+    echo "Symlink detected - target: $TARGET"
     # Navigate to the actual target location
-    cd "$(readlink -f .ref/obsidian-api)"
+    cd "$TARGET"
 else
     echo "Regular directory - can use .ref/obsidian-api directly"
     cd .ref/obsidian-api
@@ -97,7 +103,12 @@ cd eslint-plugin; git pull; cd ..
 **macOS/Linux**:
 ```bash
 # First, check where symlinks point (usually ../.ref/obsidian-dev)
-TARGET=$(readlink -f .ref/obsidian-api | sed 's|/obsidian-api$||')
+if command -v realpath >/dev/null 2>&1; then
+    TARGET_REPO=$(realpath .ref/obsidian-api)
+else
+    TARGET_REPO=$(readlink .ref/obsidian-api)
+fi
+TARGET=$(echo "$TARGET_REPO" | sed 's|/obsidian-api$||')
 echo "Symlinks point to: $TARGET"
 
 # Navigate to central location and update all repos

package/obsidian-ops/references/troubleshooting.md

@@ -25,7 +25,7 @@ Update frequency: Update as common issues are identified
 - Use `list_dir` with the project root to see hidden directories
 - Use `glob_file_search` with pattern `.ref/**` to search recursively
 - Try direct paths like `.ref/obsidian-api/README.md`
-- See [ref-instructions.md](ref-instructions.md) for detailed search strategies
+- See [sync-procedure.md](sync-procedure.md) for detailed search strategies
 
 **For AI agents**: When user asks about `.ref`, actively search using multiple methods. Don't assume it doesn't exist if first search fails.
 

package/obsidian-ops/references/versioning-releases.md

@@ -6,11 +6,19 @@ Update frequency: Check Obsidian Sample Theme repo for updates
 
 # Versioning & releases
 
-**Before releasing**: Use the comprehensive [release-readiness.md](release-readiness.md) checklist to verify your theme is ready for release.
+**Before releasing**: Use the comprehensive [release-readiness.md](release-readiness.md) checklist to verify your project is ready for release.
 
 - Bump `version` in `manifest.json` (SemVer).
 - Create a GitHub release whose tag exactly matches `manifest.json`'s `version`. Do not use a leading `v`.
+### Theme Releases
 - Attach `manifest.json` and `theme.css` to the release as individual assets.
 - After the initial release, follow the process to add/update your theme in the community catalog as required.
 
+### Plugin Releases
+- Attach `main.js`, `manifest.json`, and `styles.css` to the release as individual assets.
+- Follow the plugin submission process to add/update your plugin in the community catalog.
+
+> [!NOTE]
+> Themes and plugins have different asset requirements and submission paths. Ensure you follow the correct flow for your project type.
+
 

package/obsidian-ref/references/file-conventions.md

@@ -12,7 +12,7 @@ Update frequency: Check Obsidian Sample Theme repo for updates
   - **Complex theme with build tools** (for themes using SCSS, Grunt, etc.): `src/scss/` directory with SCSS source files that compile to `theme.css`
   - **CRITICAL**: Never have both `theme.css` as source AND `src/scss/` - choose one pattern
 
-### Simple CSS Theme Structure
+## Simple CSS Theme Structure
 
 **Recommended for simple themes** (like the sample theme template):
 ```
@@ -25,7 +25,7 @@ package.json
 - Changes take effect when Obsidian reloads the theme
 - Perfect for learning and simple themes
 
-### Complex Theme Structure (SCSS + Build Tools)
+## Complex Theme Structure (SCSS + Build Tools)
 
 **For themes using SCSS, Grunt, npm scripts, or other build tools**:
 ```
@@ -47,7 +47,7 @@ package.json
 - Run build command after making changes (see [build-workflow.md](build-workflow.md))
 - **Example**: The `obsidian-oxygen` theme uses this pattern with Grunt
 
-### Wrong Structure (Common Mistakes)
+## Wrong Structure (Common Mistakes)
 
 ```
 theme.css         # ❌ DON'T have both

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "obsidian-dev-skills",
-  "version": "1.0.4",
+  "version": "1.0.5",
   "description": "Agent skills for Obsidian plugin and theme development",
   "keywords": [
     "obsidian",

package/scripts/init.mjs

@@ -127,9 +127,25 @@ name: project
 description: Project-specific architecture, maintenance tasks, and unique conventions. Load when performing project-wide maintenance or working with the core architecture.
 ---
 
-# Project Skill
+# Project Context
 
-Provide a high-level overview of this project's specific goals and architecture here.
+This skill provides the unique context and architectural details for this repository.
+
+## Purpose
+
+To provide guidance on project-specific structures and tasks that differ from general Obsidian development patterns.
+
+## When to Use
+
+Load this skill when:
+- Understanding the repository's unique architecture.
+- Performing recurring maintenance tasks.
+- Following project-specific coding conventions.
+
+## Project Overview
+
+- **Architecture**: Organized structure with main code in \`src/main.ts\` and settings in \`src/settings.ts\`.
+- **Reference Management**: Uses a \`.ref\` folder with symlinks to centralized Obsidian repositories for API and documentation.
 
 ## Core Architecture
 

package/scripts/setup-local.ps1

@@ -1,4 +1,4 @@
-# Setup skills symlinks for Obsidian Sample Plugin Plus
+# Setup skills symlinks for this repository
 # This script creates symlinks to the obsidian-dev-skills repository
 
 param(