@jakkrichm/create-nexus-devflow 2.0.1 → 2.0.2

package/template/.agents/skills/devflow-wiki/SKILL.md

@@ -1,75 +0,0 @@
----
-name: devflow-wiki
-description: Use when creating, updating, linting, querying, or deciding whether to ingest Nexus-DevFlow framework or project wiki knowledge under devflow/wiki.
----
-
-# DevFlow Wiki
-
-Use DevFlow Wiki to compile reusable knowledge from source artifacts into small, source-backed Markdown pages.
-
-## Core Rules
-
-- Treat wiki pages as compiled knowledge, not source truth.
-- Keep `framework` and `project` namespaces separate.
-- Include `## Sources` on every page.
-- Use `_drafts/` for generated or unreviewed project pages.
-- Prefer one focused page over broad rewrites.
-- Do not ingest noisy logs, unverified hypotheses, or routine edits with no reusable lesson.
-
-## Namespace Decision
-
-| Scope | Use For | Path |
-| :--- | :--- | :--- |
-| `framework` | DevFlow workflows, agents, commands, install behavior, output contracts, token/context rules | `devflow/wiki/framework/` |
-| `project` | Target project architecture, domain concepts, decisions, patterns, gotchas, task lessons | `devflow/wiki/project/` |
-
-Promote project pages to framework only when the lesson applies beyond one project.
-
-## Commands
-
-Initialize and maintain wiki pages through the documented markdown structure under `devflow/wiki/`. Do not rely on the retired PRP runtime for wiki commands.
-
-Use `Wiki {scope} ingest {source}` for workflow-level ingestion and route reporting.
-
-## Project Wiki Contract
-
-Every project wiki uses:
-
-```text
-devflow/wiki/project/
-|-- index.md
-|-- architecture/
-|-- decisions/
-|-- domain/
-|-- gotchas/
-|-- patterns/
-|-- tasks/
-|-- token-context/
-`-- _drafts/
-```
-
-Each published page should follow `.agent/resources/schemas/wiki_page.template.md`.
-
-## Ingest Heuristics
-
-Ingest when the source contains reusable knowledge:
-
-- verified QA evidence
-- confirmed root cause and prevention
-- durable project decision
-- stable architecture or domain concept
-- repeated gotcha or risk pattern
-- context/token optimization lesson
-
-Skip ingest when the source is one-off, unverified, noisy, or already represented in a focused page.
-
-## Output Expectation
-
-Always report:
-
-- pages created or updated
-- source artifacts used
-- lint result or remaining issue
-- next workflow recommendation
-- wiki update recommendation
-

package/template/.agents/skills/english-to-thai-translator/SKILL.md

@@ -1,125 +0,0 @@
----
-name: english-to-thai-translator
-description: English to Thai translation with context awareness for software development documentation and user interfaces.
-allowed-tools: Read, Grep, Glob
----
-
-# 🇹🇭 English to Thai Translation Skill
-
-This skill enables AI agents to translate English text to Thai while maintaining technical accuracy and contextual meaning. It's designed specifically for software development environments where precise terminology is crucial.
-
-## 🎯 When to Use This Skill
-
-- Translating technical documentation from English to Thai
-- Localizing user interface elements (buttons, labels, messages)
-- Converting code comments and developer notes
-- Creating multilingual project specifications
-- Translating API documentation or technical requirements
-
-## 📝 Translation Guidelines
-
-### Technical Terminology
-- Maintain consistency with existing project terminology
-- Use appropriate Thai technical terms for software concepts
-- Preserve acronyms and abbreviations when they're standard in Thai context
-- When no direct Thai equivalent exists, use transliteration + explanation
-
-### Style and Tone
-- Keep formal tone for documentation and specifications
-- Use conversational tone for user-facing interfaces
-- Maintain consistent terminology throughout the document
-- Ensure translations are culturally appropriate for Thai audience
-
-### Special Considerations
-- **Code Comments**: Preserve code structure, translate only comments
-- **API Documentation**: Maintain parameter names and technical descriptions
-- **UI Text**: Follow Thai text direction (left-to-right) and spacing conventions
-- **Numbers and Dates**: Use Thai number formats and date conventions
-
-## 🛠️ Usage Examples
-
-### Example 1: Translating Documentation
-```
-Original English:
-"Configure the database connection parameters in the config file."
-
-Thai Translation:
-"ตั้งค่าพารามิเตอร์การเชื่อมต่อฐานข้อมูลในไฟล์กำหนดค่า"
-```
-
-### Example 2: Translating UI Elements
-```
-Original English:
-"Save Changes"
-
-Thai Translation:
-"บันทึกการเปลี่ยนแปลง"
-```
-
-### Example 3: Translating Technical Specifications
-```
-Original English:
-"The system shall validate user input before processing."
-
-Thai Translation:
-"ระบบจะต้องตรวจสอบข้อมูลที่ผู้ใช้ป้อนก่อนประมวลผล"
-```
-
-## 📚 Best Practices
-
-### DO ✅
-- Use proper Thai punctuation and spacing conventions
-- Maintain technical accuracy over literal translation
-- Ensure consistency with existing Thai terminology in the project
-- Preserve code formatting when translating comments
-
-### DON'T ❌
-- Don't translate technical terms without context consideration
-- Don't ignore cultural appropriateness for Thai audience
-- Don't break existing code structure or syntax
-- Don't create overly literal translations that lose meaning
-
-## 🧪 Quality Checks
-
-Before completing translation tasks, verify:
-1. Technical accuracy of translated terminology
-2. Cultural appropriateness of the translation
-3. Consistency with project's existing Thai documentation
-4. Proper formatting and spacing for UI elements
-5. No broken links or references in translated content
-
-## 🔄 Integration with PRPs Framework
-
-This skill works within the DevFlow 2.0 workflow:
-1. During `/10-Define` or `/20-Spec`, it can help create multilingual specifications
-2. In `/30-Plan`, it helps explain technical requirements in Thai
-3. During `/40-Implement`, it translates comments and documentation when needed
-4. In `/50-Verify` or `/60-Report`, it helps ensure translated content remains clear and correct
-
-## 📁 File Structure
-
-The skill is designed to work with:
-- Documentation files (`.md`, `.txt`)
-- Code comments (`.js`, `.ts`, `.py`, `.java`)
-- Configuration files that contain text to be translated
-- User interface text resources
-
-## ⚠️ Limitations
-
-This skill provides general translation capabilities but may require human review for:
-- Highly specialized technical domains
-- Cultural nuances and idioms
-- Creative content requiring artistic interpretation
-- Legal or regulatory documents requiring official translations
-
-## 📋 Language Constraints
-
-This skill is strictly limited to translating between English and Thai languages only. All output must be exclusively in either English or Thai, with no inclusion of:
-- Chinese (or any other language)
-- Mixed language content
-- Transliterations that include non-Thai characters
-- Any foreign language elements
-
-The translation must maintain pure English-to-Thai conversion without introducing additional languages or mixed scripts.
-
-*Generated by Nexus-DevFlow Specialist*

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

@@ -1,506 +0,0 @@
----
-name: obsidian-bases
-description: Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries. Use when working with .base files, creating database-like views of notes, or when the user mentions Bases, table views, card views, filters, or formulas in Obsidian.
-risk: unknown
-source: "https://github.com/kepano/obsidian-skills"
-date_added: "2026-03-21"
----
-
-# Obsidian Bases Skill
-
-## When to Use
-
-- Use when creating or editing `.base` files in Obsidian.
-- Use for database-like note views with filters, formulas, summaries, or cards/tables.
-- Use when the user asks about Obsidian Bases specifically.
-
-## Workflow
-
-1. **Create the file**: Create a `.base` file in the vault with valid YAML content
-2. **Define scope**: Add `filters` to select which notes appear (by tag, folder, property, or date)
-3. **Add formulas** (optional): Define computed properties in the `formulas` section
-4. **Configure views**: Add one or more views (`table`, `cards`, `list`, or `map`) with `order` specifying which properties to display
-5. **Validate**: Verify the file is valid YAML with no syntax errors. Check that all referenced properties and formulas exist. Common issues: unquoted strings containing special YAML characters, mismatched quotes in formula expressions, referencing `formula.X` without defining `X` in `formulas`
-6. **Test in Obsidian**: Open the `.base` file in Obsidian to confirm the view renders correctly. If it shows a YAML error, check quoting rules below
-
-## Schema
-
-Base files use the `.base` extension and contain valid YAML.
-
-```yaml
-# Global filters apply to ALL views in the base
-filters:
-  # Can be a single filter string
-  # OR a recursive filter object with and/or/not
-  and: []
-  or: []
-  not: []
-
-# Define formula properties that can be used across all views
-formulas:
-  formula_name: 'expression'
-
-# Configure display names and settings for properties
-properties:
-  property_name:
-    displayName: "Display Name"
-  formula.formula_name:
-    displayName: "Formula Display Name"
-  file.ext:
-    displayName: "Extension"
-
-# Define custom summary formulas
-summaries:
-  custom_summary_name: 'values.mean().round(3)'
-
-# Define one or more views
-views:
-  - type: table | cards | list | map
-    name: "View Name"
-    limit: 10                    # Optional: limit results
-    groupBy:                     # Optional: group results
-      property: property_name
-      direction: ASC | DESC
-    filters:                     # View-specific filters
-      and: []
-    order:                       # Properties to display in order
-      - file.name
-      - property_name
-      - formula.formula_name
-    summaries:                   # Map properties to summary formulas
-      property_name: Average
-```
-
-## Filter Syntax
-
-Filters narrow down results. They can be applied globally or per-view.
-
-### Filter Structure
-
-```yaml
-# Single filter
-filters: 'status == "done"'
-
-# AND - all conditions must be true
-filters:
-  and:
-    - 'status == "done"'
-    - 'priority > 3'
-
-# OR - any condition can be true
-filters:
-  or:
-    - 'file.hasTag("book")'
-    - 'file.hasTag("article")'
-
-# NOT - exclude matching items
-filters:
-  not:
-    - 'file.hasTag("archived")'
-
-# Nested filters
-filters:
-  or:
-    - file.hasTag("tag")
-    - and:
-        - file.hasTag("book")
-        - file.hasLink("Textbook")
-    - not:
-        - file.hasTag("book")
-        - file.inFolder("Required Reading")
-```
-
-### Filter Operators
-
-| Operator | Description |
-|----------|-------------|
-| `==` | equals |
-| `!=` | not equal |
-| `>` | greater than |
-| `<` | less than |
-| `>=` | greater than or equal |
-| `<=` | less than or equal |
-| `&&` | logical and |
-| `\|\|` | logical or |
-| <code>!</code> | logical not |
-
-## Properties
-
-### Three Types of Properties
-
-1. **Note properties** - From frontmatter: `note.author` or just `author`
-2. **File properties** - File metadata: `file.name`, `file.mtime`, etc.
-3. **Formula properties** - Computed values: `formula.my_formula`
-
-### File Properties Reference
-
-| Property | Type | Description |
-|----------|------|-------------|
-| `file.name` | String | File name |
-| `file.basename` | String | File name without extension |
-| `file.path` | String | Full path to file |
-| `file.folder` | String | Parent folder path |
-| `file.ext` | String | File extension |
-| `file.size` | Number | File size in bytes |
-| `file.ctime` | Date | Created time |
-| `file.mtime` | Date | Modified time |
-| `file.tags` | List | All tags in file |
-| `file.links` | List | Internal links in file |
-| `file.backlinks` | List | Files linking to this file |
-| `file.embeds` | List | Embeds in the note |
-| `file.properties` | Object | All frontmatter properties |
-
-### The `this` Keyword
-
-- In main content area: refers to the base file itself
-- When embedded: refers to the embedding file
-- In sidebar: refers to the active file in main content
-
-## Formula Syntax
-
-Formulas compute values from properties. Defined in the `formulas` section.
-
-```yaml
-formulas:
-  # Simple arithmetic
-  total: "price * quantity"
-
-  # Conditional logic
-  status_icon: 'if(done, "✅", "⏳")'
-
-  # String formatting
-  formatted_price: 'if(price, price.toFixed(2) + " dollars")'
-
-  # Date formatting
-  created: 'file.ctime.format("YYYY-MM-DD")'
-
-  # Calculate days since created (use .days for Duration)
-  days_old: '(now() - file.ctime).days'
-
-  # Calculate days until due date
-  days_until_due: 'if(due_date, (date(due_date) - today()).days, "")'
-```
-
-## Key Functions
-
-Most commonly used functions. For the complete reference of all types (Date, String, Number, List, File, Link, Object, RegExp), see [FUNCTIONS_REFERENCE.md](references/FUNCTIONS_REFERENCE.md).
-
-| Function | Signature | Description |
-|----------|-----------|-------------|
-| `date()` | `date(string): date` | Parse string to date (`YYYY-MM-DD HH:mm:ss`) |
-| `now()` | `now(): date` | Current date and time |
-| `today()` | `today(): date` | Current date (time = 00:00:00) |
-| `if()` | `if(condition, trueResult, falseResult?)` | Conditional |
-| `duration()` | `duration(string): duration` | Parse duration string |
-| `file()` | `file(path): file` | Get file object |
-| `link()` | `link(path, display?): Link` | Create a link |
-
-### Duration Type
-
-When subtracting two dates, the result is a **Duration** type (not a number).
-
-**Duration Fields:** `duration.days`, `duration.hours`, `duration.minutes`, `duration.seconds`, `duration.milliseconds`
-
-**IMPORTANT:** Duration does NOT support `.round()`, `.floor()`, `.ceil()` directly. 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
-"(date(due_date) - today()).days.round(0)"           # Rounded days
-
-# 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
-"now() + \"1 day\""       # Tomorrow
-"today() + \"7d\""        # A week from today
-"now() - file.ctime"      # Returns Duration
-"(now() - file.ctime).days"  # Get days as number
-```
-
-## View Types
-
-### Table View
-
-```yaml
-views:
-  - type: table
-    name: "My Table"
-    order:
-      - file.name
-      - status
-      - due_date
-    summaries:
-      price: Sum
-      count: Average
-```
-
-### Cards View
-
-```yaml
-views:
-  - type: cards
-    name: "Gallery"
-    order:
-      - file.name
-      - cover_image
-      - description
-```
-
-### List View
-
-```yaml
-views:
-  - type: list
-    name: "Simple List"
-    order:
-      - file.name
-      - status
-```
-
-### Map View
-
-Requires latitude/longitude properties and the Maps community plugin.
-
-```yaml
-views:
-  - type: map
-    name: "Locations"
-    # Map-specific settings for lat/lng properties
-```
-
-## Default Summary Formulas
-
-| Name | Input Type | Description |
-|------|------------|-------------|
-| `Average` | Number | Mathematical mean |
-| `Min` | Number | Smallest number |
-| `Max` | Number | Largest number |
-| `Sum` | Number | Sum of all numbers |
-| `Range` | Number | Max - Min |
-| `Median` | Number | Mathematical median |
-| `Stddev` | Number | Standard deviation |
-| `Earliest` | Date | Earliest date |
-| `Latest` | Date | Latest date |
-| `Range` | Date | Latest - Earliest |
-| `Checked` | Boolean | Count of true values |
-| `Unchecked` | Boolean | Count of false values |
-| `Empty` | Any | Count of empty values |
-| `Filled` | Any | Count of non-empty values |
-| `Unique` | Any | Count of unique values |
-
-## Complete Examples
-
-### Task Tracker Base
-
-```yaml
-filters:
-  and:
-    - file.hasTag("task")
-    - 'file.ext == "md"'
-
-formulas:
-  days_until_due: 'if(due, (date(due) - today()).days, "")'
-  is_overdue: 'if(due, date(due) < today() && status != "done", false)'
-  priority_label: 'if(priority == 1, "🔴 High", if(priority == 2, "🟡 Medium", "🟢 Low"))'
-
-properties:
-  status:
-    displayName: Status
-  formula.days_until_due:
-    displayName: "Days Until Due"
-  formula.priority_label:
-    displayName: Priority
-
-views:
-  - type: table
-    name: "Active Tasks"
-    filters:
-      and:
-        - 'status != "done"'
-    order:
-      - file.name
-      - status
-      - formula.priority_label
-      - due
-      - formula.days_until_due
-    groupBy:
-      property: status
-      direction: ASC
-    summaries:
-      formula.days_until_due: Average
-
-  - type: table
-    name: "Completed"
-    filters:
-      and:
-        - 'status == "done"'
-    order:
-      - file.name
-      - completed_date
-```
-
-### Reading List Base
-
-```yaml
-filters:
-  or:
-    - file.hasTag("book")
-    - file.hasTag("article")
-
-formulas:
-  reading_time: 'if(pages, (pages * 2).toString() + " min", "")'
-  status_icon: 'if(status == "reading", "📖", if(status == "done", "✅", "📚"))'
-  year_read: 'if(finished_date, date(finished_date).year, "")'
-
-properties:
-  author:
-    displayName: Author
-  formula.status_icon:
-    displayName: ""
-  formula.reading_time:
-    displayName: "Est. Time"
-
-views:
-  - type: cards
-    name: "Library"
-    order:
-      - cover
-      - file.name
-      - author
-      - formula.status_icon
-    filters:
-      not:
-        - 'status == "dropped"'
-
-  - type: table
-    name: "Reading List"
-    filters:
-      and:
-        - 'status == "to-read"'
-    order:
-      - file.name
-      - author
-      - pages
-      - formula.reading_time
-```
-
-### Daily Notes Index
-
-```yaml
-filters:
-  and:
-    - file.inFolder("Daily Notes")
-    - '/^\d{4}-\d{2}-\d{2}$/.matches(file.basename)'
-
-formulas:
-  word_estimate: '(file.size / 5).round(0)'
-  day_of_week: 'date(file.basename).format("dddd")'
-
-properties:
-  formula.day_of_week:
-    displayName: "Day"
-  formula.word_estimate:
-    displayName: "~Words"
-
-views:
-  - type: table
-    name: "Recent Notes"
-    limit: 30
-    order:
-      - file.name
-      - formula.day_of_week
-      - formula.word_estimate
-      - file.mtime
-```
-
-## Embedding Bases
-
-Embed in Markdown files:
-
-```markdown
-![[MyBase.base]]
-
-<!-- Specific view -->
-![[MyBase.base#View Name]]
-```
-
-## YAML Quoting Rules
-
-- Use single quotes for formulas containing double quotes: `'if(done, "Yes", "No")'`
-- Use double quotes for simple strings: `"My View Name"`
-- Escape nested quotes properly in complex expressions
-
-## Troubleshooting
-
-### YAML Syntax Errors
-
-**Unquoted special characters**: Strings containing `:`, `{`, `}`, `[`, `]`, `,`, `&`, `*`, `#`, `?`, `|`, `-`, `<`, `>`, `=`, `!`, `%`, `@`, `` ` `` must be quoted.
-
-```yaml
-# WRONG - colon in unquoted string
-displayName: Status: Active
-
-# CORRECT
-displayName: "Status: Active"
-```
-
-**Mismatched quotes in formulas**: When a formula contains double quotes, wrap the entire formula in single quotes.
-
-```yaml
-# WRONG - double quotes inside double quotes
-formulas:
-  label: "if(done, "Yes", "No")"
-
-# CORRECT - single quotes wrapping double quotes
-formulas:
-  label: 'if(done, "Yes", "No")'
-```
-
-### Common Formula Errors
-
-**Duration math without field access**: Subtracting dates returns a Duration, not a number. Always access `.days`, `.hours`, etc.
-
-```yaml
-# WRONG - Duration is not a number
-"(now() - file.ctime).round(0)"
-
-# CORRECT - access .days first, then round
-"(now() - file.ctime).days.round(0)"
-```
-
-**Missing null checks**: Properties may not exist on all notes. Use `if()` to guard.
-
-```yaml
-# WRONG - crashes if due_date is empty
-"(date(due_date) - today()).days"
-
-# CORRECT - guard with if()
-'if(due_date, (date(due_date) - today()).days, "")'
-```
-
-**Referencing undefined formulas**: Ensure every `formula.X` in `order` or `properties` has a matching entry in `formulas`.
-
-```yaml
-# This will fail silently if 'total' is not defined in formulas
-order:
-  - formula.total
-
-# Fix: define it
-formulas:
-  total: "price * quantity"
-```
-
-## References
-
-- [Bases Syntax](https://help.obsidian.md/bases/syntax)
-- [Functions](https://help.obsidian.md/bases/functions)
-- [Views](https://help.obsidian.md/bases/views)
-- [Formulas](https://help.obsidian.md/formulas)
-- [Complete Functions Reference](references/FUNCTIONS_REFERENCE.md)