aiblueprint-cli 1.4.99 → 1.4.101

package/agents-config/skills/prompt-creator/references/openai-best-practices.md

@@ -1,50 +0,0 @@
-<overview>
-GPT-specific prompting techniques from OpenAI's official documentation.
-</overview>
-
-<six_strategies>
-<strategy name="clear_instructions">
-Be specific about format, length, style:
-- Include details for relevant answers
-- Ask model to adopt a persona
-- Use delimiters for distinct parts
-- Specify steps required
-- Provide examples (few-shot)
-</strategy>
-
-<strategy name="reference_text">
-Ground answers with reference material:
-- Instruct to answer using reference
-- Reduces hallucinations
-</strategy>
-
-<strategy name="split_tasks">
-Break complex tasks into subtasks:
-- Use intent classification
-- Summarize long documents piecewise
-</strategy>
-
-<strategy name="time_to_think">
-Let the model reason step-by-step:
-- Instruct to work out solution first
-- Ask if it missed anything
-</strategy>
-
-<strategy name="external_tools">
-Offload to specialized systems:
-- Code execution for calculations
-- Embeddings for retrieval
-</strategy>
-
-<strategy name="test_systematically">
-Iterate and evaluate:
-- Test against gold-standard answers
-- A/B test variations
-</strategy>
-</six_strategies>
-
-<additional>
-- Few-shot: Include input/output examples
-- Temperature 0 for factual tasks
-- Markdown headers for structure (GPT-4+)
-</additional>

package/agents-config/skills/prompt-creator/references/prompt-templates.md

@@ -1,110 +0,0 @@
-<overview>
-Ready-to-use prompt templates for common tasks.
-</overview>
-
-<templates>
-<template name="analysis">
-```xml
-<context>
-[Background information]
-</context>
-
-<objective>
-Analyze [subject] to identify [what to find].
-</objective>
-
-<data>
-[Content to analyze]
-</data>
-
-<output_format>
-## Key Findings
-- Finding 1 with evidence
-- Finding 2 with evidence
-
-## Recommendations
-1. Action item
-2. Action item
-</output_format>
-```
-</template>
-
-<template name="transformation">
-```xml
-<objective>
-Transform [input type] to [output type].
-</objective>
-
-<input>
-[Data to transform]
-</input>
-
-<rules>
-1. [Transformation rule]
-2. [Transformation rule]
-</rules>
-
-<edge_cases>
-- If [condition], then [action]
-- If [condition], then [action]
-</edge_cases>
-
-<example>
-<input>[Sample input]</input>
-<output>[Expected output]</output>
-</example>
-```
-</template>
-
-<template name="generation">
-```xml
-<context>
-[Background and purpose]
-</context>
-
-<task>
-Generate [what to create] for [audience/purpose].
-</task>
-
-<requirements>
-- [Requirement 1]
-- [Requirement 2]
-</requirements>
-
-<style>
-- Tone: [formal/casual/technical]
-- Length: [specific constraints]
-- Format: [structure requirements]
-</style>
-
-<example>
-[Sample of desired output]
-</example>
-```
-</template>
-
-<template name="code_review">
-```xml
-<objective>
-Review code for [bugs/security/performance/style].
-</objective>
-
-<code>
-[Code to review]
-</code>
-
-<focus_areas>
-- [Area 1]
-- [Area 2]
-</focus_areas>
-
-<output_format>
-For each issue:
-- Location: [file:line]
-- Severity: [critical/warning/suggestion]
-- Issue: [description]
-- Fix: [code example]
-</output_format>
-```
-</template>
-</templates>

package/agents-config/skills/prompt-creator/references/reasoning-techniques.md

@@ -1,52 +0,0 @@
-<overview>
-Chain of thought and reasoning techniques improve performance on complex tasks.
-</overview>
-
-<chain_of_thought>
-**Basic**: Add "Think step by step before answering"
-
-**Guided**: Structure the reasoning process:
-"First analyze the requirements, then identify potential approaches, evaluate trade-offs, and finally recommend a solution."
-</chain_of_thought>
-
-<extended_thinking>
-For Claude, use thinking tags:
-```xml
-<thinking>
-Analyze the problem...
-Consider options...
-Evaluate trade-offs...
-</thinking>
-
-<answer>
-Based on analysis, the recommendation is...
-</answer>
-```
-</extended_thinking>
-
-<when_to_use>
-- Math and logic problems
-- Multi-step analysis
-- Complex decisions with trade-offs
-- Code debugging
-- Comparative evaluation
-</when_to_use>
-
-<structured_reasoning>
-For specific domains:
-
-```xml
-<analysis_framework>
-1. Identify the core problem
-2. List constraints and requirements
-3. Generate 2-3 potential solutions
-4. Evaluate each against criteria
-5. Recommend with justification
-</analysis_framework>
-```
-</structured_reasoning>
-
-<inner_monologue>
-Hide reasoning from final output when needed:
-"Work through your reasoning internally, then provide only the final answer."
-</inner_monologue>

package/agents-config/skills/prompt-creator/references/system-prompt-patterns.md

@@ -1,48 +0,0 @@
-<overview>
-System prompts establish persistent behavior, role, and constraints.
-</overview>
-
-<structure>
-```xml
-<role>
-You are an expert [domain] assistant specializing in [specific area].
-</role>
-
-<behavior>
-- Always [key behavior]
-- Never [prohibited action]
-- When uncertain, [fallback behavior]
-</behavior>
-
-<output_style>
-- Tone: [professional/casual/technical]
-- Format: [structured/conversational]
-- Length: [concise/detailed]
-</output_style>
-
-<constraints>
-- Do not [limitation]
-- Always verify [requirement]
-- Prioritize [priority]
-</constraints>
-```
-</structure>
-
-<patterns>
-<pattern name="expert_role">
-"You are a senior software engineer with 10+ years of experience in distributed systems. You prioritize code quality, maintainability, and performance."
-</pattern>
-
-<pattern name="task_specific">
-"You are a code reviewer. Analyze code for bugs, security issues, and performance problems. Provide specific, actionable feedback with code examples."
-</pattern>
-
-<pattern name="constrained">
-"You are a technical writer. Write documentation in plain language. Avoid jargon. Use examples liberally. Keep paragraphs under 3 sentences."
-</pattern>
-</patterns>
-
-<placement>
-- System message: Role, persistent behavior, high-level context
-- User message: Specific task, details, data to process
-</placement>

package/agents-config/skills/prompt-creator/references/xml-structure.md

@@ -1,36 +0,0 @@
-<overview>
-XML tags provide consistent parsing and semantic meaning for Claude.
-</overview>
-
-<benefits>
-- Clear section boundaries
-- Semantic meaning built-in
-- Lower token usage than markdown
-- Programmatically parseable
-</benefits>
-
-<common_tags>
-- `<context>` - Background information
-- `<objective>` - What to accomplish
-- `<instructions>` - Step-by-step task
-- `<constraints>` - Rules and limitations
-- `<document>` - Content to process
-- `<example>` - Input/output pairs
-- `<output>` - Expected format
-- `<success_criteria>` - Verification criteria
-</common_tags>
-
-<nesting>
-```xml
-<examples>
-<example number="1">
-<input>User input</input>
-<output>Expected output</output>
-</example>
-</examples>
-```
-</nesting>
-
-<reference_pattern>
-Reference tags by name: "Using the schema in `<schema>` tags..."
-</reference_pattern>