@jakkrichm/create-nexus-devflow 2.0.1 → 2.0.2

package/template/.agents/skills/obsidian-bases/references/FUNCTIONS_REFERENCE.md

@@ -1,173 +0,0 @@
-# Functions Reference
-
-## Global Functions
-
-| Function | Signature | Description |
-|----------|-----------|-------------|
-| `date()` | `date(string): date` | Parse string to date. Format: `YYYY-MM-DD HH:mm:ss` |
-| `duration()` | `duration(string): duration` | Parse duration string |
-| `now()` | `now(): date` | Current date and time |
-| `today()` | `today(): date` | Current date (time = 00:00:00) |
-| `if()` | `if(condition, trueResult, falseResult?)` | Conditional |
-| `min()` | `min(n1, n2, ...): number` | Smallest number |
-| `max()` | `max(n1, n2, ...): number` | Largest number |
-| `number()` | `number(any): number` | Convert to number |
-| `link()` | `link(path, display?): Link` | Create a link |
-| `list()` | `list(element): List` | Wrap in list if not already |
-| `file()` | `file(path): file` | Get file object |
-| `image()` | `image(path): image` | Create image for rendering |
-| `icon()` | `icon(name): icon` | Lucide icon by name |
-| `html()` | `html(string): html` | Render as HTML |
-| `escapeHTML()` | `escapeHTML(string): string` | Escape HTML characters |
-
-## Any Type Functions
-
-| Function | Signature | Description |
-|----------|-----------|-------------|
-| `isTruthy()` | `any.isTruthy(): boolean` | Coerce to boolean |
-| `isType()` | `any.isType(type): boolean` | Check type |
-| `toString()` | `any.toString(): string` | Convert to string |
-
-## Date Functions & Fields
-
-**Fields:** `date.year`, `date.month`, `date.day`, `date.hour`, `date.minute`, `date.second`, `date.millisecond`
-
-| Function | Signature | Description |
-|----------|-----------|-------------|
-| `date()` | `date.date(): date` | Remove time portion |
-| `format()` | `date.format(string): string` | Format with Moment.js pattern |
-| `time()` | `date.time(): string` | Get time as string |
-| `relative()` | `date.relative(): string` | Human-readable relative time |
-| `isEmpty()` | `date.isEmpty(): boolean` | Always false for dates |
-
-## Duration Type
-
-When subtracting two dates, the result is a **Duration** type (not a number). Duration has its own properties and methods.
-
-**Duration Fields:**
-| Field | Type | Description |
-|-------|------|-------------|
-| `duration.days` | Number | Total days in duration |
-| `duration.hours` | Number | Total hours in duration |
-| `duration.minutes` | Number | Total minutes in duration |
-| `duration.seconds` | Number | Total seconds in duration |
-| `duration.milliseconds` | Number | Total milliseconds in duration |
-
-**IMPORTANT:** Duration does NOT support `.round()`, `.floor()`, `.ceil()` directly. You must access a numeric field first (like `.days`), then apply number functions.
-
-```yaml
-# CORRECT: Calculate days between dates
-"(date(due_date) - today()).days"                    # Returns number of days
-"(now() - file.ctime).days"                          # Days since created
-
-# CORRECT: Round the numeric result if needed
-"(date(due_date) - today()).days.round(0)"           # Rounded days
-"(now() - file.ctime).hours.round(0)"                # Rounded hours
-
-# WRONG - will cause error:
-# "((date(due) - today()) / 86400000).round(0)"      # Duration doesn't support division then round
-```
-
-## Date Arithmetic
-
-```yaml
-# Duration units: y/year/years, M/month/months, d/day/days,
-#                 w/week/weeks, h/hour/hours, m/minute/minutes, s/second/seconds
-
-# Add/subtract durations
-"date + \"1M\""           # Add 1 month
-"date - \"2h\""           # Subtract 2 hours
-"now() + \"1 day\""       # Tomorrow
-"today() + \"7d\""        # A week from today
-
-# Subtract dates returns Duration type
-"now() - file.ctime"                    # Returns Duration
-"(now() - file.ctime).days"             # Get days as number
-"(now() - file.ctime).hours"            # Get hours as number
-
-# Complex duration arithmetic
-"now() + (duration('1d') * 2)"
-```
-
-## String Functions
-
-**Field:** `string.length`
-
-| Function | Signature | Description |
-|----------|-----------|-------------|
-| `contains()` | `string.contains(value): boolean` | Check substring |
-| `containsAll()` | `string.containsAll(...values): boolean` | All substrings present |
-| `containsAny()` | `string.containsAny(...values): boolean` | Any substring present |
-| `startsWith()` | `string.startsWith(query): boolean` | Starts with query |
-| `endsWith()` | `string.endsWith(query): boolean` | Ends with query |
-| `isEmpty()` | `string.isEmpty(): boolean` | Empty or not present |
-| `lower()` | `string.lower(): string` | To lowercase |
-| `title()` | `string.title(): string` | To Title Case |
-| `trim()` | `string.trim(): string` | Remove whitespace |
-| `replace()` | `string.replace(pattern, replacement): string` | Replace pattern |
-| `repeat()` | `string.repeat(count): string` | Repeat string |
-| `reverse()` | `string.reverse(): string` | Reverse string |
-| `slice()` | `string.slice(start, end?): string` | Substring |
-| `split()` | `string.split(separator, n?): list` | Split to list |
-
-## Number Functions
-
-| Function | Signature | Description |
-|----------|-----------|-------------|
-| `abs()` | `number.abs(): number` | Absolute value |
-| `ceil()` | `number.ceil(): number` | Round up |
-| `floor()` | `number.floor(): number` | Round down |
-| `round()` | `number.round(digits?): number` | Round to digits |
-| `toFixed()` | `number.toFixed(precision): string` | Fixed-point notation |
-| `isEmpty()` | `number.isEmpty(): boolean` | Not present |
-
-## List Functions
-
-**Field:** `list.length`
-
-| Function | Signature | Description |
-|----------|-----------|-------------|
-| `contains()` | `list.contains(value): boolean` | Element exists |
-| `containsAll()` | `list.containsAll(...values): boolean` | All elements exist |
-| `containsAny()` | `list.containsAny(...values): boolean` | Any element exists |
-| `filter()` | `list.filter(expression): list` | Filter by condition (uses `value`, `index`) |
-| `map()` | `list.map(expression): list` | Transform elements (uses `value`, `index`) |
-| `reduce()` | `list.reduce(expression, initial): any` | Reduce to single value (uses `value`, `index`, `acc`) |
-| `flat()` | `list.flat(): list` | Flatten nested lists |
-| `join()` | `list.join(separator): string` | Join to string |
-| `reverse()` | `list.reverse(): list` | Reverse order |
-| `slice()` | `list.slice(start, end?): list` | Sublist |
-| `sort()` | `list.sort(): list` | Sort ascending |
-| `unique()` | `list.unique(): list` | Remove duplicates |
-| `isEmpty()` | `list.isEmpty(): boolean` | No elements |
-
-## File Functions
-
-| Function | Signature | Description |
-|----------|-----------|-------------|
-| `asLink()` | `file.asLink(display?): Link` | Convert to link |
-| `hasLink()` | `file.hasLink(otherFile): boolean` | Has link to file |
-| `hasTag()` | `file.hasTag(...tags): boolean` | Has any of the tags |
-| `hasProperty()` | `file.hasProperty(name): boolean` | Has property |
-| `inFolder()` | `file.inFolder(folder): boolean` | In folder or subfolder |
-
-## Link Functions
-
-| Function | Signature | Description |
-|----------|-----------|-------------|
-| `asFile()` | `link.asFile(): file` | Get file object |
-| `linksTo()` | `link.linksTo(file): boolean` | Links to file |
-
-## Object Functions
-
-| Function | Signature | Description |
-|----------|-----------|-------------|
-| `isEmpty()` | `object.isEmpty(): boolean` | No properties |
-| `keys()` | `object.keys(): list` | List of keys |
-| `values()` | `object.values(): list` | List of values |
-
-## Regular Expression Functions
-
-| Function | Signature | Description |
-|----------|-----------|-------------|
-| `matches()` | `regexp.matches(string): boolean` | Test if matches |

package/template/.agents/skills/obsidian-cli/SKILL.md

@@ -1,115 +0,0 @@
----
-name: obsidian-cli
-description: "Use the Obsidian CLI to read, create, search, and manage vault content, or to develop and debug Obsidian plugins and themes from the command line."
-risk: unknown
-source: "https://github.com/kepano/obsidian-skills"
-date_added: "2026-03-21"
----
-
-# Obsidian CLI
-
-Use the `obsidian` CLI to interact with a running Obsidian instance. Requires Obsidian to be open.
-
-## When to Use
-
-- Use when managing vault content through the Obsidian CLI.
-- Use when developing or debugging Obsidian plugins and themes from the command line.
-- Use when the user wants shell-driven interaction with a running Obsidian app.
-
-## Command reference
-
-Run `obsidian help` to see all available commands. This is always up to date. Full docs: https://help.obsidian.md/cli
-
-## Syntax
-
-**Parameters** take a value with `=`. Quote values with spaces:
-
-```bash
-obsidian create name="My Note" content="Hello world"
-```
-
-**Flags** are boolean switches with no value:
-
-```bash
-obsidian create name="My Note" silent overwrite
-```
-
-For multiline content use `\n` for newline and `\t` for tab.
-
-## File targeting
-
-Many commands accept `file` or `path` to target a file. Without either, the active file is used.
-
-- `file=<name>` — resolves like a wikilink (name only, no path or extension needed)
-- `path=<path>` — exact path from vault root, e.g. `folder/note.md`
-
-## Vault targeting
-
-Commands target the most recently focused vault by default. Use `vault=<name>` as the first parameter to target a specific vault:
-
-```bash
-obsidian vault="My Vault" search query="test"
-```
-
-## Common patterns
-
-```bash
-obsidian read file="My Note"
-obsidian create name="New Note" content="# Hello" template="Template" silent
-obsidian append file="My Note" content="New line"
-obsidian search query="search term" limit=10
-obsidian daily:read
-obsidian daily:append content="- [ ] New task"
-obsidian property:set name="status" value="done" file="My Note"
-obsidian tasks daily todo
-obsidian tags sort=count counts
-obsidian backlinks file="My Note"
-```
-
-Use `--copy` on any command to copy output to clipboard. Use `silent` to prevent files from opening. Use `total` on list commands to get a count.
-
-## Plugin development
-
-### Develop/test cycle
-
-After making code changes to a plugin or theme, follow this workflow:
-
-1. **Reload** the plugin to pick up changes:
-   ```bash
-   obsidian plugin:reload id=my-plugin
-   ```
-2. **Check for errors** — if errors appear, fix and repeat from step 1:
-   ```bash
-   obsidian dev:errors
-   ```
-3. **Verify visually** with a screenshot or DOM inspection:
-   ```bash
-   obsidian dev:screenshot path=screenshot.png
-   obsidian dev:dom selector=".workspace-leaf" text
-   ```
-4. **Check console output** for warnings or unexpected logs:
-   ```bash
-   obsidian dev:console level=error
-   ```
-
-### Additional developer commands
-
-Run JavaScript in the app context:
-
-```bash
-obsidian eval code="app.vault.getFiles().length"
-```
-
-Inspect CSS values:
-
-```bash
-obsidian dev:css selector=".workspace-leaf" prop=background-color
-```
-
-Toggle mobile emulation:
-
-```bash
-obsidian dev:mobile on
-```
-
-Run `obsidian help` to see additional developer commands including CDP and debugger controls.

package/template/.agents/skills/obsidian-clipper-template-creator/SKILL.md

@@ -1,73 +0,0 @@
----
-name: obsidian-clipper-template-creator
-description: Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.
-risk: safe
-source: community
-date_added: "2026-02-27"
----
-
-# Obsidian Web Clipper Template Creator
-
-This skill helps you create importable JSON templates for the Obsidian Web Clipper.
-
-## Workflow
-
-1. **Identify User Intent:** specific site (YouTube), specific type (Recipe), or general clipping?
-2. **Check Existing Bases:** The user likely has a "Base" schema defined in `Bases/`.
-    - **Action:** Read `Bases/*.base` to find a matching category (e.g., `Recipes.base`).
-    - **Action:** Use the properties defined in the Base to structure the Clipper template properties.
-    - See [references/bases-workflow.md](references/bases-workflow.md) for details.
-3. **Fetch & Analyze Reference URL:** Validate variables against a real page.
-    - **Action:** Ask the user for a sample URL of the content they want to clip (if not provided).
-    - **Action (REQUIRED):** Use **WebFetch** to retrieve page content; if WebFetch is not available, use a browser DOM snapshot. See [references/analysis-workflow.md](references/analysis-workflow.md).
-    - **Action:** Analyze the HTML for Schema.org JSON, Meta tags, and CSS selectors.
-    - **Action (REQUIRED):** Verify each selector against the fetched content. Do not guess selectors.
-    - See [references/analysis-workflow.md](references/analysis-workflow.md) for analysis techniques.
-4. **Draft the JSON:** Create a valid JSON object following the schema.
-    - See [references/json-schema.md](references/json-schema.md).
-5. **Consider template logic:** Use conditionals for optional blocks (e.g. show nutrition only if present), loops for list data, variable assignment to avoid repeating expressions, and fallbacks for missing variables. Use logic only when it improves the template; keep simple templates simple. See [references/logic.md](references/logic.md).
-6. **Verify Variables:** Ensure the chosen variables (Preset, Schema, Selector) exist in your analysis.
-    - **Action (REQUIRED):** If a selector cannot be verified from the fetched content, state that explicitly and ask for another URL.
-    - See [references/variables.md](references/variables.md).
-
-## Selector Verification Rules
-
-- **Always verify selectors** against live page content before responding.
-- **Never guess selectors.** If the DOM cannot be accessed or the element is missing, ask for another URL or a screenshot.
-- **Prefer stable selectors** (data attributes, semantic roles, unique IDs) over fragile class chains.
-- **Document the target element** in your reasoning (e.g., "About sidebar paragraph") to reduce mismatch.
-
-## Output Format
-
-**ALWAYS** output the final result as a JSON code block that the user can copy and import.
-
-The Clipper template editor validates template syntax.
-If you use template logic (conditionals, loops, variable assignment), ensure it follows the syntax in [references/logic.md](references/logic.md) and the official [Logic](https://help.obsidian.md/web-clipper/logic) docs so the template passes validation.
-
-```json
-{
-  "schemaVersion": "0.1.0",
-  "name": "My Template",
-  ...
-}
-```
-
-## Resources
-
-- [references/variables.md](references/variables.md) - Available data variables.
-- [references/filters.md](references/filters.md) - Formatting filters.
-- [references/json-schema.md](references/json-schema.md) - JSON structure documentation.
-- [references/logic.md](references/logic.md) - Template logic.
-- [references/bases-workflow.md](references/bases-workflow.md) - How to map Bases to Templates.
-- [references/analysis-workflow.md](references/analysis-workflow.md) - How to validate page data.
-
-### Official Documentation
-
-- [Variables](https://help.obsidian.md/web-clipper/variables)
-- [Filters](https://help.obsidian.md/web-clipper/filters)
-- [Logic](https://help.obsidian.md/web-clipper/logic)
-- [Templates](https://help.obsidian.md/web-clipper/templates)
-
-## Examples
-
-See [assets/](assets/) for JSON examples.

package/template/.agents/skills/obsidian-clipper-template-creator/assets/clipping-template.json

@@ -1,51 +0,0 @@
-{
-	"schemaVersion": "0.1.0",
-	"name": "General Clipping",
-	"behavior": "create",
-	"noteContentFormat": "{{content}}",
-	"properties": [
-		{
-			"name": "categories",
-			"value": "[[Clippings]]",
-			"type": "multitext"
-		},
-		{
-			"name": "author",
-			"value": "[[{{author}}]]",
-			"type": "multitext"
-		},
-		{
-			"name": "source",
-			"value": "{{url}}",
-			"type": "text"
-		},
-		{
-			"name": "via",
-			"value": "",
-			"type": "text"
-		},
-		{
-			"name": "published",
-			"value": "{{published}}",
-			"type": "datetime"
-		},
-		{
-			"name": "created",
-			"value": "{{date}}",
-			"type": "datetime"
-		},
-		{
-			"name": "topics",
-			"value": "",
-			"type": "multitext"
-		},
-		{
-			"name": "description",
-			"value": "{{description}}",
-			"type": "text"
-		}
-	],
-	"triggers": [],
-	"noteNameFormat": "{{title}}",
-	"path": "Clippings/"
-}

package/template/.agents/skills/obsidian-clipper-template-creator/assets/recipe-template.json

@@ -1,48 +0,0 @@
-{
-	"schemaVersion": "0.1.0",
-	"name": "Recipe",
-	"behavior": "create",
-	"noteContentFormat": "![{{schema:Recipe:image|first}}]\n\n## Description\n{{schema:Recipe:description}}\n\n## Ingredients\n{{schema:Recipe:recipeIngredient|list}}\n\n## Instructions\n{{schema:Recipe:recipeInstructions|map:step =>> step.text|list}}\n\n## Nutrition\n- Calories: {{schema:Recipe:nutrition.calories}}",
-	"properties": [
-		{
-			"name": "categories",
-			"value": "[[Recipes]]",
-			"type": "multitext"
-		},
-		{
-			"name": "author",
-			"value": "[[{{schema:Recipe:author.name}}]]",
-			"type": "text"
-		},
-		{
-			"name": "source",
-			"value": "{{url}}",
-			"type": "text"
-		},
-		{
-			"name": "ingredients",
-			"value": "{{schema:Recipe:recipeIngredient}}",
-			"type": "multitext"
-		},
-		{
-			"name": "cuisine",
-			"value": "{{schema:Recipe:recipeCuisine}}",
-			"type": "text"
-		},
-		{
-			"name": "rating",
-			"value": "",
-			"type": "number"
-		},
-		{
-			"name": "type",
-			"value": "Recipe",
-			"type": "text"
-		}
-	],
-	"triggers": [
-		"schema:Recipe"
-	],
-	"noteNameFormat": "{{schema:Recipe:name}}",
-	"path": "Recipes/"
-}

package/template/.agents/skills/obsidian-clipper-template-creator/references/analysis-workflow.md

@@ -1,79 +0,0 @@
-# Analysis Workflow: Validating Variables
-
-To ensure your template works correctly, you must validate that the target page actually contains the data you want to extract.
-
-## 1. Fetch the Page
-
-Use the `WebFetch` tool or a browser DOM snapshot to retrieve the content of a representative URL provided by the user.
-
-```text
-WebFetch(url="https://example.com/recipe/chocolate-cake")
-```
-
-## 2. Analyze the Output
-
-### Check for Schema.org (Recommended)
-
-Look for `<script type="application/ld+json">`. This contains structured data which is the most reliable way to extract info.
-
-**Example Found in HTML:**
-
-```html
-<script type="application/ld+json">
-{
-  "@context": "https://schema.org/",
-  "@type": "Recipe",
-  "name": "Chocolate Cake",
-  "author": {
-    "@type": "Person",
-    "name": "John Doe"
-  }
-}
-```
-
-**Conclusion:**
-
-- `{{schema:Recipe:name}}` is valid.
-- `{{schema:Recipe:author.name}}` is valid.
-- **Tip:** You can use `schema:Recipe` in the `triggers` array to automatically select this template for any page with this schema.
-
-### Check for Meta Tags
-
-Look for `<meta>` tags in the `<head>` section.
-
-**Example Found in HTML:**
-
-```html
-<meta property="og:title" content="The Best Chocolate Cake" />
-<meta name="description" content="A rich, moist chocolate cake recipe." />
-```
-
-**Conclusion:**
-
-- `{{meta:og:title}}` is valid.
-- `{{meta:description}}` is valid.
-
-### Check for CSS Selectors (Verified)
-
-If Schema and Meta tags are missing, look for HTML structure (classes and IDs) to use with `{{selector:...}}`.
-Selectors must be verified against the fetched HTML or DOM snapshot. Do not guess selectors.
-
-**Example Found in HTML:**
-
-```html
-<div class="article-body">
-  <h1 id="main-title">Chocolate Cake</h1>
-  <span class="author-name">By John Doe</span>
-</div>
-```
-
-**Conclusion:**
-
-- `{{selector:h1#main-title}}` or `{{selector:h1}}` can extract the title.
-- `{{selector:.author-name}}` can extract the author.
-
-## 3. Verify Against Base
-
-Compare the available data from your analysis with the properties required by the user's Base (see [bases-workflow.md](bases-workflow.md)).
-
-- If the Base requires `ingredients` but the page has no Schema or clear list structure, warn the user that this field might need manual entry or a prompt variable.

package/template/.agents/skills/obsidian-clipper-template-creator/references/bases-workflow.md

@@ -1,44 +0,0 @@
-# Working with Obsidian Bases
-
-The user maintains "Bases" in `Bases/*.base` which define the schema and properties for different types of notes (e.g., Recipes, Clippings, People).
-
-## Workflow
-
-1.  **Identify the Category:** Determine the type of content the user wants to clip (e.g., a Recipe, a News Article, a YouTube video).
-2.  **Find the Base:** Search `Bases/` for a matching `.base` file.
-    *   Example: For a recipe, look for `Bases/Recipes.base`.
-    *   Example: For a generic article, look for `Bases/Clippings.base`.
-3.  **Read the Base:** Read the content of the `.base` file to understand the required properties.
-
-## Interpreting .base Files
-
-Base files use a YAML-like structure. Look for the `properties` section.
-
-```yaml
-properties:
-  file.name:
-    displayName: name
-  note.author:
-    displayName: author
-  note.type:
-    displayName: type
-  note.ingredients:
-    displayName: ingredients
-```
-
-*   `note.X` corresponds to a property name `X` in the frontmatter.
-*   `displayName` helps understand the intent, but the property key (e.g., `author`, `type`, `ingredients`) is what matters for the template.
-
-## Mapping to Clipper Properties
-
-When creating the JSON for the Web Clipper, map the Base properties to the `properties` array in the JSON.
-
-| Base Property | Clipper JSON Property Name | Value Strategy |
-| :--- | :--- | :--- |
-| `note.author` | `author` | `{{author}}` or `{{schema:author.name}}` |
-| `note.source` | `source` | `{{url}}` |
-| `note.published` | `published` | `{{published}}` |
-| `note.ingredients` | `ingredients` | `{{schema:Recipe:recipeIngredient}}` |
-| `note.type` | `type` | Constant (e.g., `Recipe`) or empty |
-
-**Crucial Step:** Ask the user which properties should be automatically filled, which should be hardcoded (e.g., `type: Recipe`), and which should be left empty for manual entry.

package/template/.agents/skills/obsidian-clipper-template-creator/references/filters.md

@@ -1,51 +0,0 @@
-# Obsidian Web Clipper Filters
-
-**Official Docs:** [help.obsidian.md/web-clipper/filters](https://help.obsidian.md/web-clipper/filters)
-
-Use filters to format variables: `{{variable|filter}}`.
-
-## Text Formatting
-- `markdown`: Convert HTML to Markdown.
-- `strip_tags`: Remove HTML tags.
-- `trim`: Remove whitespace.
-- `upper`: Convert to uppercase.
-- `lower`: Convert to lowercase.
-- `title`: Title Case.
-- `capitalize`: Capitalize first letter.
-- `camel`: CamelCase.
-- `kebab`: kebab-case.
-- `snake`: snake_case.
-- `pascal`: PascalCase.
-- `replace:"old","new"`: Replace text.
-- `safe_name`: Make safe for filenames.
-- `blockquote`: Format as blockquote.
-- `link`: Create markdown link.
-- `wikilink`: Create [[wikilink]].
-- `list`: Format array as list.
-- `table`: Format array as table.
-- `callout`: Format as callout block.
-
-## Dates
-- `date:"format"`: Format date (e.g., `YYYY-MM-DD`).
-- `date_modify:"+1 day"`: Modify date.
-- `duration`: Format duration.
-
-## Numbers
-- `calc`: Perform calculations.
-- `length`: Get length of string/array.
-- `round`: Round numbers.
-
-## HTML Processing
-- `remove_html`: Remove HTML tags.
-- `remove_attr`: Remove attributes.
-- `strip_attr`: Strip specific attributes.
-
-## Arrays and Objects
-- `map`: Transform array items (e.g., `map:item =>> item.text`).
-- `join:"separator"`: Join array items.
-- `split:"separator"`: Split string into array.
-- `first`: First item.
-- `last`: Last item.
-- `slice:start,end`: Slice array.
-- `unique`: Unique items.
-- `template:"format"`: Format items using a template string.