Path to Smart Connections Embeddings
- D:\10_pur3v4d3r's-vault\.smart-env\multi

Movement of Agent through PKB

Start by sending the Agent to D:\10_pur3v4d3r's-vault\.claude

CLAUDE.md and Gemini.md [Need to be read]
- CLAUDE.md -> D:\10_pur3v4d3r's-vault\.claude\CLAUDE.md
- GEMINI.md -> D:\10_pur3v4d3r's-vault\.claude\GEMINI.md
This needs to send them to D:\10_pur3v4d3r's-vault\.claude\SYSTEM_INIT.md

The Agent is sent to SYSTEM_INIT.md file.

Where the Agent is informed of the role of "Self-Agent Coordinator".

The Agent is sent to the folder D:\10_pur3v4d3r's-vault\00-meta

This contains Session Memory, Metadata Rules, Project Info, Etc.

[TASKS]

Starter Prompt for Claude Code to work on the most recent prompts

Instead of continuing the batch phases I think it would be most beneficial to us and the system if we instead start to process my most up to date and currently really active prompts. They are full prompts that need to be implemented into SPES framework.

NOTE: This is the first of three folder that require this treatment, two folders are around 500k tokens and the third i think was significantly smaller [as it doesn't have any associated documentation for the prompts] at around 200k tokens. FILE-LOCATION: D:\10_pur3v4d3r's-vault\999-v4d3r\_foundational-vader-claude-projects

These prompts have associated documentation that MUST be accessible through the prompt main file. I was thinking either we just house all the reference in there own folder in a unique location or we can have them in the same folder as the prompt main file. Either way they MUST be properly linked to each other the documents must stay connect.

Metadata

📋 CONTROLLED VOCABULARIES

Status Values

active: Currently in use, maintained
testing: Under evaluation, not production-ready
production: Proven, deployed, stable
deprecated: Replaced, no longer recommended
archived: Historical, no longer maintained

Confidence Values

speculative: Unproven, experimental
provisional: Some testing, preliminary results
moderate: Tested multiple times, generally reliable
established: Extensively tested, consistently good
high: Proven excellent, gold standard

Maturity Values

seedling: New, unrefined, needs development
developing: Growing, improving, getting tested
budding: Solid foundation, minor refinements needed
evergreen: Mature, stable, proven over time

Priority Values

low: Nice to have, no urgency
medium: Standard work priority
high: Important, needs attention soon
urgent: Critical, address immediately

Source Values

claude-sonnet-4.5: Claude Sonnet 4.5 generated
claude-opus-4.5: Claude Opus 4.5 generated
gemini-3.0-pro: Gemini 3.0 Pro generated
gemini-3.0-flash: Gemini 3.0 Flash generated
original: User-created (Pur3v4d3r)
local-llm: Local model generated
other: Other source

Component Types

persona: Role/identity frames
instruction: Task directives
constraint: Boundaries/restrictions
format: Output templates
context: Background/framing
example: Few-shot demonstrations

Domains

general: Universal, any domain
technical: Code, engineering, analysis
creative: Writing, ideation, art
educational: Teaching, explanation, tutoring
pkb: PKB/knowledge management specific

📊 UNIVERSAL FIELDS (All Types)

These fields appear in ALL notes (prompts, components, workflows, tests).

Core Identity

type: string [REQUIRED]
  # Prompt types: "prompt" | "component" | "workflow" | "test-result"

id: string [REQUIRED]
  # Unique identifier
  # Format: YYYYMMDDHHmmss (timestamp-based)
  # Generated: tp.date.now("YYYYMMDDHHmmss")

status: string [REQUIRED]
  # Options: "active" | "testing" | "production" | "deprecated" | "archived"
  # Default: "active"

version: string [REQUIRED]
  # Semantic versioning: "MAJOR.MINOR.PATCH"
  # Default: "1.0.0"
  # Bump: MAJOR (breaking), MINOR (feature), PATCH (fix)

Quality Metrics

rating: float [REQUIRED]
  # User quality assessment
  # Range: 0.0-10.0
  # Default: "0.0"
  # Update: After testing or usage

confidence: string [REQUIRED]
  # Epistemic certainty
  # Options: "speculative" | "provisional" | "moderate" | "established" | "high"
  # Default: "speculative" (new prompts)

maturity: string [REQUIRED]
  # Development stage
  # Options: "seedling" | "developing" | "budding" | "evergreen"
  # Default: "seedling"
  # Progression: seedling → developing → budding → evergreen

priority: string [OPTIONAL]
  # Work priority
  # Options: "low" | "medium" | "high" | "urgent"
  # Default: "medium"

Source & Attribution

source: string [REQUIRED]
  # Origin of content
  # Options: "claude-sonnet-4.5" | "claude-opus-4.5" | "gemini-3.0-pro" |
  #          "gemini-3.0-flash" | "original" | "local-llm" | "other"
  # Use: Track which model generated/refined the prompt

Temporal Fields

created: date [REQUIRED]
  # Creation date
  # Format: YYYY-MM-DD
  # Generated: tp.date.now("YYYY-MM-DD")

modified: date [REQUIRED]
  # Last modification date
  # Format: YYYY-MM-DD
  # Update: On every edit

Usage Tracking

usage-count: integer [REQUIRED]
  # Number of times used in production
  # Default: 0
  # Increment: Via macro or manually

last-used: string [OPTIONAL]
  # Link to daily note when last used
  # Format: "[[YYYY-MM-DD]]" or empty string ""
  # Update: When prompt is deployed

Review System (Spaced Repetition)

review-next: date [OPTIONAL]
  # Next review date
  # Format: YYYY-MM-DD
  # Calculate: Based on maturity level
  #   seedling: +7 days
  #   developing: +14 days
  #   budding: +30 days
  #   evergreen: +90 days

review-interval: integer [OPTIONAL]
  # Days between reviews
  # Default: 7
  # Adjust: Based on usage frequency and maturity

review-count: integer [OPTIONAL]
  # Number of reviews completed
  # Default: 0
  # Increment: Each review session

Categorization

tags: array [REQUIRED]
  # Hierarchical tags
  # Required tags:
  #   - "year/YYYY" (always include current year)
  #   - "prompt-engineering" (umbrella category)
  # Common tags:
  #   - "llm-capability/generation|reasoning|analysis|creative"
  #   - "prompt-workflow/creation|testing|deployment|optimization"
  #   - "component-type/persona|instruction|constraint|format|context"
  #   - "domain/general|technical|creative|educational|pkb"
  #   - "advanced-prompting/chain-of-thought|few-shot|tree-of-thoughts"

aliases: array [OPTIONAL]
  # Alternative names
  # Include: Filename, common abbreviations, synonyms
  # Default: [filename]

Graph Integration

link-up: string [OPTIONAL]
  # Parent MOC (Map of Content)
  # Format: "[[moc-name]]"
  # Default: "[[prompt-engineering-moc]]"

link-related: array [OPTIONAL]
  # Related notes
  # Suggested: ["[[YYYY-MM-DD|Daily Note]]", "[[YYYY-WW|Weekly Review]]"]
  # Add: Links to related prompts, projects, resources

🎯 PROMPT-SPECIFIC FIELDS

Additional fields for type: "prompt" notes.

components-used: array [OPTIONAL]
  # Links to component library items
  # Format: ["[[component-1]]", "[[component-2]]"]
  # Purpose: Track component reuse, enable analytics
  # Update: When inserting components

test-results: array [OPTIONAL]
  # Links to test result notes
  # Format: ["[[test-result-1]]", "[[test-result-2]]"]
  # Purpose: Track testing history
  # Update: After each test

🧩 COMPONENT-SPECIFIC FIELDS

Additional fields for type: "component" notes.

component-type: string [REQUIRED]
  # Component category
  # Options: "persona" | "instruction" | "constraint" | "format" |
  #          "context" | "example"
  # Use: Organize library, filter searches

atomic-composite: string [REQUIRED]
  # Component complexity
  # Options: "atomic" | "composite"
  # atomic: Single-purpose, indivisible
  # composite: Combines multiple atomics

domain: string [REQUIRED]
  # Application domain
  # Options: "general" | "technical" | "creative" | "educational" | "pkb"
  # Use: Domain-specific filtering

performance-score: float [OPTIONAL]
  # Average quality across uses
  # Range: 0.0-10.0
  # Calculate: Average of ratings from used-in-prompts
  # Default: "0.0"

conflicts-with: array [OPTIONAL]
  # Components that shouldn't be used together
  # Format: ["[[conflicting-component]]"]
  # Example: Different personas, contradictory constraints

synergies-with: array [OPTIONAL]
  # Components that work well together
  # Format: ["[[synergistic-component]]"]
  # Use: Recommend combos

used-in-prompts: array [OPTIONAL]
  # Links to prompts using this component
  # Format: ["[[prompt-1]]", "[[prompt-2]]"]
  # Update: Via macro or manually
  # Use: Usage analytics

🔗 WORKFLOW-SPECIFIC FIELDS

Additional fields for type: "workflow" notes.

workflow-type: string [OPTIONAL]
  # Workflow category
  # Options: "sequential" | "parallel" | "recursive" | "hybrid"

problem-types: array [OPTIONAL]
  # Problems this workflow addresses
  # Format: ["long-form-generation", "technical-analysis", "comparison"]

typical-turns: integer [OPTIONAL]
  # Average number of turns/steps
  # Range: 1-20+

context-strategy: string [OPTIONAL]
  # How context is managed across turns
  # Options: "strict-isolation" | "sequential-building" | "parallel-convergence"

🧪 TEST-RESULT-SPECIFIC FIELDS

Additional fields for type: "test-result" notes.

prompt-tested: string [REQUIRED]
  # Link to prompt being tested
  # Format: "[[prompt-name]]"

test-date: date [REQUIRED]
  # When test was conducted
  # Format: YYYY-MM-DD

test-type: string [REQUIRED]
  # Type of test
  # Options: "functional" | "quality" | "performance" | "ab-comparison"

success: boolean [REQUIRED]
  # Did prompt meet objectives?
  # Options: true | false

quality-score: float [OPTIONAL]
  # Numeric quality assessment
  # Range: 0.0-10.0

issues-found: array [OPTIONAL]
  # List of problems identified
  # Format: ["Issue 1 description", "Issue 2 description"]

recommendations: array [OPTIONAL]
  # Suggested improvements
  # Format: ["Recommendation 1", "Recommendation 2"]






























































Review the files in your Knowledge, with the *ultimate goal* of instilling these techniques into the meta prompt engineer named: Vader that you will be designing and building.







I need to take the Prompt engineering specialist and the master Yaml document, and have the best prompt engineering agent [prob.spec] 
- Combine the two systems so that every prompt generated from now on has these things:
  1. Full Metadata [Both-YAML-in-prompt-&-dataview-top-of-the-note-metadata] [complete-example(s)-provided-below]
  2. Custom Comment markers [complete-example(s)-provided-below]
  3. End of Prompt YAML

Name	spring-boot-resilience4j
Description	This skill should be used when implementing fault tolerance and resilience patterns in Spring Boot applications using the Resilience4j library. Apply this skill to add circuit breaker, retry, rate limiter, bulkhead, time limiter, and fallback mechanisms to prevent cascading failures, handle transient errors, and manage external service dependencies gracefully in microservices architectures.

spring-boot-resilience4j

SKILL.md