Update version to v1.4.216 and commit

Update Message Handling for Attachments and Multi-Modal content

.github/workflows/update-version-and-create-tag.yml

@@ -11,6 +11,10 @@ on:
 permissions:
   contents: write  # Ensure the workflow has write permissions
 
+concurrency:
+  group: version-update
+  cancel-in-progress: false
+
 jobs:
   update-version:
     if: github.event_name == 'push' && github.ref == 'refs/heads/main'
@@ -30,6 +34,11 @@ jobs:
           git config user.name "github-actions[bot]"
           git config user.email "github-actions[bot]@users.noreply.github.com"
 
+      - name: Pull latest main and tags
+        run: |
+          git pull --rebase origin main
+          git fetch --tags
+
       - name: Get the latest tag
         id: get_latest_tag
         run: |

Pattern_Descriptions/pattern_descriptions.json

@@ -1634,8 +1634,8 @@
       ]
     },
     {
-      "patternName": "write_essay",
-      "description": "Create essays with thesis statements and arguments.",
+      "patternName": "write_essay_pg",
+      "description": "Create essays with thesis statements and arguments in the style of Paul Graham.",
       "tags": [
         "WRITING",
         "RESEARCH",
@@ -1703,7 +1703,7 @@
     {
       "patternName": "analyze_bill",
       "description": "Analyze a legislative bill and implications.",
-      "tags": [ 
+      "tags": [
         "ANALYSIS",
         "BILL"
       ]
@@ -1711,14 +1711,14 @@
     {
       "patternName": "analyze_bill_short",
       "description": "Consended - Analyze a legislative bill and implications.",
-      "tags": [ 
+      "tags": [
         "ANALYSIS",
         "BILL"
       ]
     },
     {
       "patternName": "create_coding_feature",
-      "description": "[Description pending]",
+      "description": "Generate secure and composable code features using latest technology and best practices.",
       "tags": [
         "DEVELOPMENT"
       ]
@@ -1774,6 +1774,47 @@
       "tags": [
         "SUMMARIZE"
       ]
+    },
+    {
+      "patternName": "analyze_paper_simple",
+      "description": "Analyze research papers to determine primary findings and assess scientific rigor.",
+      "tags": [
+        "ANALYSIS",
+        "RESEARCH",
+        "WRITING"
+      ]
+    },
+    {
+      "patternName": "analyze_terraform_plan",
+      "description": "Analyze Terraform plans for infrastructure changes, security risks, and cost implications.",
+      "tags": [
+        "ANALYSIS",
+        "DEVOPS"
+      ]
+    },
+    {
+      "patternName": "create_mnemonic_phrases",
+      "description": "Create memorable mnemonic sentences using given words in exact order for memory aids.",
+      "tags": [
+        "CREATIVITY",
+        "LEARNING"
+      ]
+    },
+    {
+      "patternName": "summarize_board_meeting",
+      "description": "Convert board meeting transcripts into formal meeting notes for corporate records.",
+      "tags": [
+        "ANALYSIS",
+        "BUSINESS"
+      ]
+    },
+    {
+      "patternName": "write_essay",
+      "description": "Write essays on given topics in the distinctive style of specified authors.",
+      "tags": [
+        "WRITING",
+        "CREATIVITY"
+      ]
     }
   ]
-}
+}

README.md

@@ -13,9 +13,11 @@ Fabric is graciously supported by…
 ![GitHub last commit](https://img.shields.io/github/last-commit/danielmiessler/fabric)
 [![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
 
+<div align="center">
 <p class="align center">
 <h4><code>fabric</code> is an open-source framework for augmenting humans using AI.</h4>
 </p>
+</div>
 
 [Updates](#updates) •
 [What and Why](#what-and-why) •
@@ -32,6 +34,30 @@ Fabric is graciously supported by…
 
 </div>
 
+## What and why
+
+Since the start of modern AI in late 2022 we've seen an **_extraordinary_** number of AI applications for accomplishing tasks. There are thousands of websites, chatbots, mobile apps, and other interfaces for using all the differnet AI out there.
+
+It's all really exciting and powerful, but _it's not easy to integrate this functionality into our lives._
+
+<p class="align center">
+<h4>In other words, AI doesn't have a capabilities problem—it has an <em>integration</em> problem.</h4>
+</p>
+
+**Fabric was created to address this by creating and organizating the fundamental units of AI—the prompts themselves!**
+
+Fabric organizes prompts by real-world task, allowing people to create, collect, and organize their most important AI solutions in a single place for use in their favorite tools. And if you're command-line focused, you can use Fabric itself as the interface!
+
+## Intro videos
+
+Keep in mind that many of these were recorded when Fabric was Python-based, so remember to use the current [install instructions](#installation) below.
+
+- [Network Chuck](https://www.youtube.com/watch?v=UbDyjIIGaxQ)
+- [David Bombal](https://www.youtube.com/watch?v=vF-MQmVxnCs)
+- [My Own Intro to the Tool](https://www.youtube.com/watch?v=wPEyyigh10g)
+- [More Fabric YouTube Videos](https://www.youtube.com/results?search_query=fabric+ai)
+
+
 ## Navigation
 
 - [`fabric`](#fabric)
@@ -87,28 +113,21 @@ Fabric is graciously supported by…
 ## Updates
 
 > [!NOTE]
-> May 22, 2025
 >
-> - Fabric now supports Anthropic's Claude 4. Read the [blog post from Anthropic](https://www.anthropic.com/news/claude-4).
-
-## What and why
-
-Since the start of 2023 and GenAI we've seen a massive number of AI applications for accomplishing tasks. It's powerful, but _it's not easy to integrate this functionality into our lives._
-
-<div align="center">
-<h4>In other words, AI doesn't have a capabilities problem—it has an <em>integration</em> problem.</h4>
-</div>
-
-Fabric was created to address this by enabling everyone to granularly apply AI to everyday challenges.
-
-## Intro videos
-
-Keep in mind that many of these were recorded when Fabric was Python-based, so remember to use the current [install instructions](#installation) below.
-
-- [Network Chuck](https://www.youtube.com/watch?v=UbDyjIIGaxQ)
-- [David Bombal](https://www.youtube.com/watch?v=vF-MQmVxnCs)
-- [My Own Intro to the Tool](https://www.youtube.com/watch?v=wPEyyigh10g)
-- [More Fabric YouTube Videos](https://www.youtube.com/results?search_query=fabric+ai)
+>June 17, 2025
+>
+>- Fabric now supports Perplexity AI. Configure it by using `fabric -S` to add your Perlexity AI API Key,
+>   and then try:
+>
+>   ```bash
+>   fabric -m sonar-pro "What is the latest world news?"
+>   ```
+>
+>June 11, 2025
+>
+>- Fabric's YouTube transcription now needs `yt-dlp` to be installed. Make sure to install the latest
+> version (2025.06.09 as of this note). The YouTube API key is only needed for comments (the `--comments` flag)
+> and metadata extraction (the `--metadata` flag).
 
 ## Philosophy
 

cli/flags.go

@@ -279,14 +279,7 @@ func (o *Flags) BuildChatRequest(Meta string) (ret *common.ChatRequest, err erro
 	}
 
 	var message *goopenai.ChatCompletionMessage
-	if len(o.Attachments) == 0 {
-		if o.Message != "" {
-			message = &goopenai.ChatCompletionMessage{
-				Role:    goopenai.ChatMessageRoleUser,
-				Content: strings.TrimSpace(o.Message),
-			}
-		}
-	} else {
+	if len(o.Attachments) > 0 {
 		message = &goopenai.ChatCompletionMessage{
 			Role: goopenai.ChatMessageRoleUser,
 		}
@@ -323,7 +316,13 @@ func (o *Flags) BuildChatRequest(Meta string) (ret *common.ChatRequest, err erro
 				},
 			})
 		}
+	} else if o.Message != "" {
+		message = &goopenai.ChatCompletionMessage{
+			Role:    goopenai.ChatMessageRoleUser,
+			Content: strings.TrimSpace(o.Message),
+		}
 	}
+
 	ret.Message = message
 
 	if o.Language != "" {

common/domain.go

@@ -25,6 +25,7 @@ type ChatOptions struct {
 	Raw                bool
 	Seed               int
 	ModelContextLength int
+	MaxTokens          int
 }
 
 // NormalizeMessages remove empty messages and ensure messages order user-assist-user

core/chatter.go

@@ -30,11 +30,11 @@ type Chatter struct {
 	strategy           string
 }
 
-// Send processes a chat request and applies any file changes if using the create_coding_feature pattern
+// Send processes a chat request and applies file changes for create_coding_feature pattern
 func (o *Chatter) Send(request *common.ChatRequest, opts *common.ChatOptions) (session *fsdb.Session, err error) {
 	modelToUse := opts.Model
 	if modelToUse == "" {
-		modelToUse = o.model // Default to the model set in the Chatter struct
+		modelToUse = o.model
 	}
 	if o.vendor.NeedsRawMode(modelToUse) {
 		opts.Raw = true
@@ -89,18 +89,15 @@ func (o *Chatter) Send(request *common.ChatRequest, opts *common.ChatOptions) (s
 		return
 	}
 
-	// Process file changes if using the create_coding_feature pattern
+	// Process file changes for create_coding_feature pattern
 	if request.PatternName == "create_coding_feature" {
-		// Look for file changes in the response
 		summary, fileChanges, parseErr := common.ParseFileChanges(message)
 		if parseErr != nil {
 			fmt.Printf("Warning: Failed to parse file changes: %v\n", parseErr)
 		} else if len(fileChanges) > 0 {
-			// Get the project root - use the current directory
 			projectRoot, err := os.Getwd()
 			if err != nil {
 				fmt.Printf("Warning: Failed to get current directory: %v\n", err)
-				// Continue without applying changes
 			} else {
 				if applyErr := common.ApplyFileChanges(projectRoot, fileChanges); applyErr != nil {
 					fmt.Printf("Warning: Failed to apply file changes: %v\n", applyErr)
@@ -122,7 +119,6 @@ func (o *Chatter) Send(request *common.ChatRequest, opts *common.ChatOptions) (s
 }
 
 func (o *Chatter) BuildSession(request *common.ChatRequest, raw bool) (session *fsdb.Session, err error) {
-	// If a session name is provided, retrieve it from the database
 	if request.SessionName != "" {
 		var sess *fsdb.Session
 		if sess, err = o.db.Sessions.Get(request.SessionName); err != nil {
@@ -149,9 +145,9 @@ func (o *Chatter) BuildSession(request *common.ChatRequest, raw bool) (session *
 		contextContent = ctx.Content
 	}
 
-	// Process any template variables in the message content (user input)
+	// Process template variables in message content
 	// Double curly braces {{variable}} indicate template substitution
-	// Ensure we have a message before processing, other wise we'll get an error when we pass to pattern.go
+	// Ensure we have a message before processing
 	if request.Message == nil {
 		request.Message = &goopenai.ChatCompletionMessage{
 			Role:    goopenai.ChatMessageRoleUser,
@@ -168,19 +164,19 @@ func (o *Chatter) BuildSession(request *common.ChatRequest, raw bool) (session *
 	}
 
 	var patternContent string
+	inputUsed := false
 	if request.PatternName != "" {
 		pattern, err := o.db.Patterns.GetApplyVariables(request.PatternName, request.PatternVariables, request.Message.Content)
-		// pattern will now contain user input, and all variables will be resolved, or errored
 
 		if err != nil {
 			return nil, fmt.Errorf("could not get pattern %s: %v", request.PatternName, err)
 		}
 		patternContent = pattern.Pattern
+		inputUsed = true
 	}
 
 	systemMessage := strings.TrimSpace(contextContent) + strings.TrimSpace(patternContent)
 
-	// Apply strategy if specified
 	if request.StrategyName != "" {
 		strategy, err := strategy.LoadStrategy(request.StrategyName)
 		if err != nil {
@@ -199,33 +195,51 @@ func (o *Chatter) BuildSession(request *common.ChatRequest, raw bool) (session *
 	}
 
 	if raw {
-		// In raw mode, we want to avoid duplicating the input that's already in the pattern
 		var finalContent string
 		if systemMessage != "" {
-			// If we have a pattern, it already includes the user input
 			if request.PatternName != "" {
 				finalContent = systemMessage
 			} else {
-				// No pattern, combine system message with user input
 				finalContent = fmt.Sprintf("%s\n\n%s", systemMessage, request.Message.Content)
 			}
-			request.Message = &goopenai.ChatCompletionMessage{
-				Role:    goopenai.ChatMessageRoleUser,
-				Content: finalContent,
+
+			// Handle MultiContent properly in raw mode
+			if len(request.Message.MultiContent) > 0 {
+				// When we have attachments, add the text as a text part in MultiContent
+				newMultiContent := []goopenai.ChatMessagePart{
+					{
+						Type: goopenai.ChatMessagePartTypeText,
+						Text: finalContent,
+					},
+				}
+				// Add existing non-text parts (like images)
+				for _, part := range request.Message.MultiContent {
+					if part.Type != goopenai.ChatMessagePartTypeText {
+						newMultiContent = append(newMultiContent, part)
+					}
+				}
+				request.Message = &goopenai.ChatCompletionMessage{
+					Role:         goopenai.ChatMessageRoleUser,
+					MultiContent: newMultiContent,
+				}
+			} else {
+				// No attachments, use regular Content field
+				request.Message = &goopenai.ChatCompletionMessage{
+					Role:    goopenai.ChatMessageRoleUser,
+					Content: finalContent,
+				}
 			}
 		}
-		// After this, if request.Message is not nil, append it
 		if request.Message != nil {
 			session.Append(request.Message)
 		}
-	} else { // Not raw mode
+	} else {
 		if systemMessage != "" {
 			session.Append(&goopenai.ChatCompletionMessage{Role: goopenai.ChatMessageRoleSystem, Content: systemMessage})
 		}
-		// If a pattern was used (request.PatternName != ""), its output (systemMessage)
-		// already incorporates the user input (request.Message.Content via GetApplyVariables).
-		// So, we only append the direct user message if NO pattern was used.
-		if request.PatternName == "" && request.Message != nil {
+		// If multi-part content, it is in the user message, and should be added.
+		// Otherwise, we should only add it if we have not already used it in the systemMessage.
+		if len(request.Message.MultiContent) > 0 || (request.Message != nil && !inputUsed) {
 			session.Append(request.Message)
 		}
 	}

core/plugin_registry.go

@@ -10,7 +10,9 @@ import (
 	"strconv"
 	"strings"
 
+	"github.com/danielmiessler/fabric/plugins/ai/bedrock"
 	"github.com/danielmiessler/fabric/plugins/ai/exolab"
+	"github.com/danielmiessler/fabric/plugins/ai/perplexity" // Added Perplexity plugin
 	"github.com/danielmiessler/fabric/plugins/strategy"
 
 	"github.com/samber/lo"
@@ -34,6 +36,33 @@ import (
 	"github.com/danielmiessler/fabric/plugins/tools/youtube"
 )
 
+// hasAWSCredentials checks if any AWS credentials are present either in the
+// environment variables or in the default/shared credentials file. It doesn't
+// attempt to verify the validity of the credentials, but simply ensures that a
+// potential authentication source exists so we can safely initialize the
+// Bedrock client without causing the AWS SDK to search for credentials.
+func hasAWSCredentials() bool {
+	if os.Getenv("AWS_PROFILE") != "" ||
+		os.Getenv("AWS_ROLE_SESSION_NAME") != "" ||
+		(os.Getenv("AWS_ACCESS_KEY_ID") != "" && os.Getenv("AWS_SECRET_ACCESS_KEY") != "") {
+
+		return true
+	}
+
+	credFile := os.Getenv("AWS_SHARED_CREDENTIALS_FILE")
+	if credFile == "" {
+		if home, err := os.UserHomeDir(); err == nil {
+			credFile = filepath.Join(home, ".aws", "credentials")
+		}
+	}
+	if credFile != "" {
+		if _, err := os.Stat(credFile); err == nil {
+			return true
+		}
+	}
+	return false
+}
+
 func NewPluginRegistry(db *fsdb.Db) (ret *PluginRegistry, err error) {
 	ret = &PluginRegistry{
 		Db:             db,
@@ -66,8 +95,13 @@ func NewPluginRegistry(db *fsdb.Db) (ret *PluginRegistry, err error) {
 		anthropic.NewClient(),
 		lmstudio.NewClient(),
 		exolab.NewClient(),
+		perplexity.NewClient(), // Added Perplexity client
 	)
 
+	if hasAWSCredentials() {
+		vendors = append(vendors, bedrock.NewClient())
+	}
+
 	// Add all OpenAI-compatible providers
 	for providerName := range openai_compatible.ProviderMap {
 		provider, _ := openai_compatible.GetProviderByName(providerName)

go.mod

@@ -8,6 +8,8 @@ require (
 	github.com/anaskhan96/soup v1.2.5
 	github.com/anthropics/anthropic-sdk-go v1.4.0
 	github.com/atotto/clipboard v0.1.4
+	github.com/aws/aws-sdk-go-v2/config v1.27.27
+	github.com/aws/aws-sdk-go-v2/service/bedrockruntime v1.30.0
 	github.com/gabriel-vasile/mimetype v1.4.9
 	github.com/gin-gonic/gin v1.10.1
 	github.com/go-git/go-git/v5 v5.16.2
@@ -39,6 +41,20 @@ require (
 	github.com/ProtonMail/go-crypto v1.3.0 // indirect
 	github.com/andybalholm/cascadia v1.3.3 // indirect
 	github.com/araddon/dateparse v0.0.0-20210429162001-6b43995a97de // indirect
+	github.com/aws/aws-sdk-go-v2 v1.36.4 // indirect
+	github.com/aws/aws-sdk-go-v2/aws/protocol/eventstream v1.6.10 // indirect
+	github.com/aws/aws-sdk-go-v2/credentials v1.17.27 // indirect
+	github.com/aws/aws-sdk-go-v2/feature/ec2/imds v1.16.11 // indirect
+	github.com/aws/aws-sdk-go-v2/internal/configsources v1.3.35 // indirect
+	github.com/aws/aws-sdk-go-v2/internal/endpoints/v2 v2.6.35 // indirect
+	github.com/aws/aws-sdk-go-v2/internal/ini v1.8.0 // indirect
+	github.com/aws/aws-sdk-go-v2/service/bedrock v1.34.1 // indirect
+	github.com/aws/aws-sdk-go-v2/service/internal/accept-encoding v1.11.3 // indirect
+	github.com/aws/aws-sdk-go-v2/service/internal/presigned-url v1.11.17 // indirect
+	github.com/aws/aws-sdk-go-v2/service/sso v1.22.4 // indirect
+	github.com/aws/aws-sdk-go-v2/service/ssooidc v1.26.4 // indirect
+	github.com/aws/aws-sdk-go-v2/service/sts v1.30.3 // indirect
+	github.com/aws/smithy-go v1.22.2 // indirect
 	github.com/bytedance/sonic v1.13.3 // indirect
 	github.com/bytedance/sonic/loader v0.2.4 // indirect
 	github.com/cloudflare/circl v1.6.1 // indirect
@@ -76,6 +92,7 @@ require (
 	github.com/pjbgf/sha1cd v0.3.2 // indirect
 	github.com/pmezard/go-difflib v1.0.0 // indirect
 	github.com/sergi/go-diff v1.4.0 // indirect
+	github.com/sgaunet/perplexity-go/v2 v2.8.0 // indirect
 	github.com/skeema/knownhosts v1.3.1 // indirect
 	github.com/tidwall/gjson v1.18.0 // indirect
 	github.com/tidwall/match v1.1.1 // indirect

go.sum

@@ -31,6 +31,44 @@ github.com/armon/go-socks5 v0.0.0-20160902184237-e75332964ef5 h1:0CwZNZbxp69SHPd
 github.com/armon/go-socks5 v0.0.0-20160902184237-e75332964ef5/go.mod h1:wHh0iHkYZB8zMSxRWpUBQtwG5a7fFgvEO+odwuTv2gs=
 github.com/atotto/clipboard v0.1.4 h1:EH0zSVneZPSuFR11BlR9YppQTVDbh5+16AmcJi4g1z4=
 github.com/atotto/clipboard v0.1.4/go.mod h1:ZY9tmq7sm5xIbd9bOK4onWV4S6X0u6GY7Vn0Yu86PYI=
+github.com/aws/aws-sdk-go-v2 v1.36.3 h1:mJoei2CxPutQVxaATCzDUjcZEjVRdpsiiXi2o38yqWM=
+github.com/aws/aws-sdk-go-v2 v1.36.3/go.mod h1:LLXuLpgzEbD766Z5ECcRmi8AzSwfZItDtmABVkRLGzg=
+github.com/aws/aws-sdk-go-v2 v1.36.4 h1:GySzjhVvx0ERP6eyfAbAuAXLtAda5TEy19E5q5W8I9E=
+github.com/aws/aws-sdk-go-v2 v1.36.4/go.mod h1:LLXuLpgzEbD766Z5ECcRmi8AzSwfZItDtmABVkRLGzg=
+github.com/aws/aws-sdk-go-v2/aws/protocol/eventstream v1.6.10 h1:zAybnyUQXIZ5mok5Jqwlf58/TFE7uvd3IAsa1aF9cXs=
+github.com/aws/aws-sdk-go-v2/aws/protocol/eventstream v1.6.10/go.mod h1:qqvMj6gHLR/EXWZw4ZbqlPbQUyenf4h82UQUlKc+l14=
+github.com/aws/aws-sdk-go-v2/config v1.27.27 h1:HdqgGt1OAP0HkEDDShEl0oSYa9ZZBSOmKpdpsDMdO90=
+github.com/aws/aws-sdk-go-v2/config v1.27.27/go.mod h1:MVYamCg76dFNINkZFu4n4RjDixhVr51HLj4ErWzrVwg=
+github.com/aws/aws-sdk-go-v2/credentials v1.17.27 h1:2raNba6gr2IfA0eqqiP2XiQ0UVOpGPgDSi0I9iAP+UI=
+github.com/aws/aws-sdk-go-v2/credentials v1.17.27/go.mod h1:gniiwbGahQByxan6YjQUMcW4Aov6bLC3m+evgcoN4r4=
+github.com/aws/aws-sdk-go-v2/feature/ec2/imds v1.16.11 h1:KreluoV8FZDEtI6Co2xuNk/UqI9iwMrOx/87PBNIKqw=
+github.com/aws/aws-sdk-go-v2/feature/ec2/imds v1.16.11/go.mod h1:SeSUYBLsMYFoRvHE0Tjvn7kbxaUhl75CJi1sbfhMxkU=
+github.com/aws/aws-sdk-go-v2/internal/configsources v1.3.34 h1:ZK5jHhnrioRkUNOc+hOgQKlUL5JeC3S6JgLxtQ+Rm0Q=
+github.com/aws/aws-sdk-go-v2/internal/configsources v1.3.34/go.mod h1:p4VfIceZokChbA9FzMbRGz5OV+lekcVtHlPKEO0gSZY=
+github.com/aws/aws-sdk-go-v2/internal/configsources v1.3.35 h1:o1v1VFfPcDVlK3ll1L5xHsaQAFdNtZ5GXnNR7SwueC4=
+github.com/aws/aws-sdk-go-v2/internal/configsources v1.3.35/go.mod h1:rZUQNYMNG+8uZxz9FOerQJ+FceCiodXvixpeRtdESrU=
+github.com/aws/aws-sdk-go-v2/internal/endpoints/v2 v2.6.34 h1:SZwFm17ZUNNg5Np0ioo/gq8Mn6u9w19Mri8DnJ15Jf0=
+github.com/aws/aws-sdk-go-v2/internal/endpoints/v2 v2.6.34/go.mod h1:dFZsC0BLo346mvKQLWmoJxT+Sjp+qcVR1tRVHQGOH9Q=
+github.com/aws/aws-sdk-go-v2/internal/endpoints/v2 v2.6.35 h1:R5b82ubO2NntENm3SAm0ADME+H630HomNJdgv+yZ3xw=
+github.com/aws/aws-sdk-go-v2/internal/endpoints/v2 v2.6.35/go.mod h1:FuA+nmgMRfkzVKYDNEqQadvEMxtxl9+RLT9ribCwEMs=
+github.com/aws/aws-sdk-go-v2/internal/ini v1.8.0 h1:hT8rVHwugYE2lEfdFE0QWVo81lF7jMrYJVDWI+f+VxU=
+github.com/aws/aws-sdk-go-v2/internal/ini v1.8.0/go.mod h1:8tu/lYfQfFe6IGnaOdrpVgEL2IrrDOf6/m9RQum4NkY=
+github.com/aws/aws-sdk-go-v2/service/bedrock v1.34.1 h1:sD4KqDKG8aOaMWaWTMB8l8VnLa/Di7XHb0Uf4plrndA=
+github.com/aws/aws-sdk-go-v2/service/bedrock v1.34.1/go.mod h1:lrn8DOVFYFeaUZKxJ95T5eGDBjnhffgGz68Wq2sfBbA=
+github.com/aws/aws-sdk-go-v2/service/bedrockruntime v1.30.0 h1:eMOwQ8ZZK+76+08RfxeaGUtRFN6wxmD1rvqovc2kq2w=
+github.com/aws/aws-sdk-go-v2/service/bedrockruntime v1.30.0/go.mod h1:0b5Rq7rUvSQFYHI1UO0zFTV/S6j6DUyuykXA80C+YOI=
+github.com/aws/aws-sdk-go-v2/service/internal/accept-encoding v1.11.3 h1:dT3MqvGhSoaIhRseqw2I0yH81l7wiR2vjs57O51EAm8=
+github.com/aws/aws-sdk-go-v2/service/internal/accept-encoding v1.11.3/go.mod h1:GlAeCkHwugxdHaueRr4nhPuY+WW+gR8UjlcqzPr1SPI=
+github.com/aws/aws-sdk-go-v2/service/internal/presigned-url v1.11.17 h1:HGErhhrxZlQ044RiM+WdoZxp0p+EGM62y3L6pwA4olE=
+github.com/aws/aws-sdk-go-v2/service/internal/presigned-url v1.11.17/go.mod h1:RkZEx4l0EHYDJpWppMJ3nD9wZJAa8/0lq9aVC+r2UII=
+github.com/aws/aws-sdk-go-v2/service/sso v1.22.4 h1:BXx0ZIxvrJdSgSvKTZ+yRBeSqqgPM89VPlulEcl37tM=
+github.com/aws/aws-sdk-go-v2/service/sso v1.22.4/go.mod h1:ooyCOXjvJEsUw7x+ZDHeISPMhtwI3ZCB7ggFMcFfWLU=
+github.com/aws/aws-sdk-go-v2/service/ssooidc v1.26.4 h1:yiwVzJW2ZxZTurVbYWA7QOrAaCYQR72t0wrSBfoesUE=
+github.com/aws/aws-sdk-go-v2/service/ssooidc v1.26.4/go.mod h1:0oxfLkpz3rQ/CHlx5hB7H69YUpFiI1tql6Q6Ne+1bCw=
+github.com/aws/aws-sdk-go-v2/service/sts v1.30.3 h1:ZsDKRLXGWHk8WdtyYMoGNO7bTudrvuKpDKgMVRlepGE=
+github.com/aws/aws-sdk-go-v2/service/sts v1.30.3/go.mod h1:zwySh8fpFyXp9yOr/KVzxOl8SRqgf/IDw5aUt9UKFcQ=
+github.com/aws/smithy-go v1.22.2 h1:6D9hW43xKFrRx/tXXfAlIZc4JI+yQe6snnWcQyxSyLQ=
+github.com/aws/smithy-go v1.22.2/go.mod h1:irrKGvNn1InZwb2d7fkIRNucdfwR8R+Ts3wxYa/cJHg=
 github.com/bytedance/sonic v1.13.3 h1:MS8gmaH16Gtirygw7jV91pDCN33NyMrPbN7qiYhEsF0=
 github.com/bytedance/sonic v1.13.3/go.mod h1:o68xyaF9u2gvVBuGHPlUVCy+ZfmNNO5ETf1+KgkJhz4=
 github.com/bytedance/sonic/loader v0.1.1/go.mod h1:ncP89zfokxS5LZrJxl5z0UJcsk4M4yY2JpfqGeCtNLU=
@@ -164,6 +202,8 @@ github.com/sashabaranov/go-openai v1.40.1/go.mod h1:lj5b/K+zjTSFxVLijLSTDZuP7adO
 github.com/scylladb/termtables v0.0.0-20191203121021-c4c0b6d42ff4/go.mod h1:C1a7PQSMz9NShzorzCiG2fk9+xuCgLkPeCvMHYR2OWg=
 github.com/sergi/go-diff v1.4.0 h1:n/SP9D5ad1fORl+llWyN+D6qoUETXNZARKjyY2/KVCw=
 github.com/sergi/go-diff v1.4.0/go.mod h1:A0bzQcvG0E7Rwjx0REVgAGH58e96+X0MeOfepqsbeW4=
+github.com/sgaunet/perplexity-go/v2 v2.8.0 h1:stnuVieniZMGo6qJLCV2JyR2uF7K5398YOA/ZZcgrSg=
+github.com/sgaunet/perplexity-go/v2 v2.8.0/go.mod h1:MSks4RNuivCi0GqJyylhFdgSJFVEwZHjAhrf86Wkynk=
 github.com/sirupsen/logrus v1.7.0/go.mod h1:yWOB1SBYBC5VeMP7gHvWumXLIWorT60ONWic61uBYv0=
 github.com/skeema/knownhosts v1.3.1 h1:X2osQ+RAjK76shCbvhHHHVl3ZlgDm8apHEHFqRjnBY8=
 github.com/skeema/knownhosts v1.3.1/go.mod h1:r7KTdC8l4uxWRyK2TpQZ/1o5HaSzh06ePQNxPwTcfiY=

nix/pkgs/fabric/gomod2nix.toml

@@ -2,32 +2,32 @@ schema = 3
 
 [mod]
   [mod."cloud.google.com/go"]
-    version = "v0.120.1"
-    hash = "sha256-yWaLc06rGXk16K53rix8O4uPSX+AOZDgIpIXf+wlh10="
+    version = "v0.121.2"
+    hash = "sha256-BCgGHxKti8slH98UDDurtgzX3lgcYEklsmj4ImPpwlc="
   [mod."cloud.google.com/go/ai"]
-    version = "v0.10.2"
-    hash = "sha256-bsqvdylG8kk+AHtyvMRMv1TOjUmvONAgJ+14mKcwuzs="
+    version = "v0.12.1"
+    hash = "sha256-wg3oLMS68E/v7EdNzywbjwEmpk+u6U8LTnIc1pq8edo="
   [mod."cloud.google.com/go/auth"]
-    version = "v0.16.1"
-    hash = "sha256-rMPMNQh/YM/67b9Grfu0BFccWpS1SRhBepubQqXRAyg="
+    version = "v0.16.2"
+    hash = "sha256-BAU9WGFKe0pd5Eu3l/Mbts+QeCOjS+lChr5hrPBCzdA="
   [mod."cloud.google.com/go/auth/oauth2adapt"]
     version = "v0.2.8"
     hash = "sha256-GoXFqAbp1WO1tDj07PF5EyxDYvCBP0l0qwxY2oV2hfc="
   [mod."cloud.google.com/go/compute/metadata"]
-    version = "v0.6.0"
-    hash = "sha256-E8/cwio4xR8buCryR4HwR7+agb4M3zqgXSm7rBglmIY="
+    version = "v0.7.0"
+    hash = "sha256-jJZDW+hibqjMiY8OiJhgJALbGwEq+djLOxfYR7upQyE="
   [mod."cloud.google.com/go/longrunning"]
     version = "v0.6.7"
     hash = "sha256-9I0Nc2KWAEVoxDngNkqFUdASmZIAySfMEELlPh3Q3xA="
   [mod."dario.cat/mergo"]
-    version = "v1.0.1"
-    hash = "sha256-wcG6+x0k6KzOSlaPA+1RFxa06/RIAePJTAjjuhLbImw="
+    version = "v1.0.2"
+    hash = "sha256-p6jdiHlLEfZES8vJnDywG4aVzIe16p0CU6iglglIweA="
   [mod."github.com/Microsoft/go-winio"]
     version = "v0.6.2"
     hash = "sha256-tVNWDUMILZbJvarcl/E7tpSnkn7urqgSHa2Eaka5vSU="
   [mod."github.com/ProtonMail/go-crypto"]
-    version = "v1.2.0"
-    hash = "sha256-5fKgWUz6BoyFNNZ1OD9QjhBrhNEBCuVfO2WqH+X59oo="
+    version = "v1.3.0"
+    hash = "sha256-TUG+C4MyeWglOmiwiW2/NUVurFHXLgEPRd3X9uQ1NGI="
   [mod."github.com/anaskhan96/soup"]
     version = "v1.2.5"
     hash = "sha256-t8yCyK2y7x2qaI/3Yw16q3zVFqu+3acLcPgTr1MIKWg="
@@ -35,17 +35,65 @@ schema = 3
     version = "v1.3.3"
     hash = "sha256-jv7ZshpSd7FZzKKN6hqlUgiR8C3y85zNIS/hq7g76Ho="
   [mod."github.com/anthropics/anthropic-sdk-go"]
-    version = "v1.2.0"
-    hash = "sha256-IzSmJBfMB2OAyFOCqwSzwdJMPoTQqJ1rBtKXGrFo2Bc="
+    version = "v1.4.0"
+    hash = "sha256-4kwFw9gt/sRIlTo0fC2PbfLnCyc4lCOtmfQelhpORX8="
   [mod."github.com/araddon/dateparse"]
     version = "v0.0.0-20210429162001-6b43995a97de"
     hash = "sha256-UuX84naeRGMsFOgIgRoBHG5sNy1CzBkWPKmd6VbLwFw="
   [mod."github.com/atotto/clipboard"]
     version = "v0.1.4"
     hash = "sha256-ZZ7U5X0gWOu8zcjZcWbcpzGOGdycwq0TjTFh/eZHjXk="
+  [mod."github.com/aws/aws-sdk-go-v2"]
+    version = "v1.36.4"
+    hash = "sha256-Cpdphp8FQUbQlhAYvtPKDh1oZc84+/0bzLlx8CM1/BM="
+  [mod."github.com/aws/aws-sdk-go-v2/aws/protocol/eventstream"]
+    version = "v1.6.10"
+    hash = "sha256-9+ZMhWxtsm7ZtZCjBV5PZkOR5rt3bCOznuv45Iwf55c="
+  [mod."github.com/aws/aws-sdk-go-v2/config"]
+    version = "v1.27.27"
+    hash = "sha256-jQmc1lJmVeTezSeFs6KL2HAvCkP9ZWMdVbG5ymJQrKs="
+  [mod."github.com/aws/aws-sdk-go-v2/credentials"]
+    version = "v1.17.27"
+    hash = "sha256-7ITZjIF0ZmmCG3u5d88IfsAj0KF1IFm9KhWFlC6RtQo="
+  [mod."github.com/aws/aws-sdk-go-v2/feature/ec2/imds"]
+    version = "v1.16.11"
+    hash = "sha256-uedtRd/SIcFJlYZg1jtJdIJViZq1Poks9/J2Bm9/Ehw="
+  [mod."github.com/aws/aws-sdk-go-v2/internal/configsources"]
+    version = "v1.3.35"
+    hash = "sha256-AyQ+eJvyhahypIAqPScdkn44MYwBcr9iyrMC1BRSeZI="
+  [mod."github.com/aws/aws-sdk-go-v2/internal/endpoints/v2"]
+    version = "v2.6.35"
+    hash = "sha256-c8K+Nk5XrFMWaaxVsyhKgyJBZhs3Hkhjr/dIDXWZfSQ="
+  [mod."github.com/aws/aws-sdk-go-v2/internal/ini"]
+    version = "v1.8.0"
+    hash = "sha256-v76jTAr4rEgS5en49ikLh6nuvclN+VjpOPj83ZQ3sLo="
+  [mod."github.com/aws/aws-sdk-go-v2/service/bedrock"]
+    version = "v1.34.1"
+    hash = "sha256-OK7t+ieq4pviCnnhfSytANBF5Lwdz4KxjN10CC5pXyY="
+  [mod."github.com/aws/aws-sdk-go-v2/service/bedrockruntime"]
+    version = "v1.30.0"
+    hash = "sha256-MsEQfbqIREtMikRFqBpLCqdAC4gfgPSNbk08k5OJTbo="
+  [mod."github.com/aws/aws-sdk-go-v2/service/internal/accept-encoding"]
+    version = "v1.11.3"
+    hash = "sha256-TRhoRd7iY7K+pfdkSQLItyr52k2jO4TMYQ5vRGiOOMk="
+  [mod."github.com/aws/aws-sdk-go-v2/service/internal/presigned-url"]
+    version = "v1.11.17"
+    hash = "sha256-eUoYDAXcQNzCmwjXO9RWhrt0jGYlSjt2vQOlAlpIfoE="
+  [mod."github.com/aws/aws-sdk-go-v2/service/sso"]
+    version = "v1.22.4"
+    hash = "sha256-Q3tyDdJVq0BAstOYvCKPvNS4EHkhXt1pL/23KPQJMHM="
+  [mod."github.com/aws/aws-sdk-go-v2/service/ssooidc"]
+    version = "v1.26.4"
+    hash = "sha256-cPv6nmVPOjMUZjN2IeEiYQSzLeAOrfgGnSSvvhJ6iL4="
+  [mod."github.com/aws/aws-sdk-go-v2/service/sts"]
+    version = "v1.30.3"
+    hash = "sha256-4z/K4GPW9osiNM3SxFNZYsVPnSSU50Iuv29Sb2n4Fbk="
+  [mod."github.com/aws/smithy-go"]
+    version = "v1.22.2"
+    hash = "sha256-YdwVeW509cpqU357MjDM8ReL1vftkW8XIhSbJsbTh/s="
   [mod."github.com/bytedance/sonic"]
-    version = "v1.13.2"
-    hash = "sha256-IF2qmt4IxTwivMWHUJC8sg6d85/ORb2SWvJ54fvoAMI="
+    version = "v1.13.3"
+    hash = "sha256-Nnt5b2NkIvSXhGERQmyI0ka28hbWi7A7Zn3dsAjPcEA="
   [mod."github.com/bytedance/sonic/loader"]
     version = "v0.2.4"
     hash = "sha256-rv9LnePpm4OspSVbfSoVbohXzhu+dxE1BH1gm3mTmTc="
@@ -74,8 +122,8 @@ schema = 3
     version = "v1.1.0"
     hash = "sha256-2VP6zHEsPi0u2ZYpOTcLulwj1Gsmb6oA19qcP2/AzVM="
   [mod."github.com/gin-gonic/gin"]
-    version = "v1.10.0"
-    hash = "sha256-esJasHrJtuTBwGPGAoc/XSb428J8va+tPGcZ0gTfsgc="
+    version = "v1.10.1"
+    hash = "sha256-D98+chAdjb6JcLPkscOr8TgTW87UqA4h3cnY0XIr16c="
   [mod."github.com/go-git/gcfg"]
     version = "v1.5.1-0.20230307220236-3a3c6141e376"
     hash = "sha256-f4k0gSYuo0/q3WOoTxl2eFaj7WZpdz29ih6CKc8Ude8="
@@ -83,11 +131,11 @@ schema = 3
     version = "v5.6.2"
     hash = "sha256-VgbxcLkHjiSyRIfKS7E9Sn8OynCrMGUDkwFz6K2TVL4="
   [mod."github.com/go-git/go-git/v5"]
-    version = "v5.16.0"
-    hash = "sha256-01obPHvt1PG3r8XH8TgnNfcOhaYwWEkJ0TR5QGdZqmE="
+    version = "v5.16.2"
+    hash = "sha256-KdOf4KwJAJUIB/EcQH6wc7jpcABCISWur3vOTpAo+/c="
   [mod."github.com/go-logr/logr"]
-    version = "v1.4.2"
-    hash = "sha256-/W6qGilFlZNTb9Uq48xGZ4IbsVeSwJiAMLw4wiNYHLI="
+    version = "v1.4.3"
+    hash = "sha256-Nnp/dEVNMxLp3RSPDHZzGbI8BkSNuZMX0I0cjWKXXLA="
   [mod."github.com/go-logr/stdr"]
     version = "v1.2.2"
     hash = "sha256-rRweAP7XIb4egtT1f2gkz4sYOu7LDHmcJ5iNsJUd0sE="
@@ -116,8 +164,8 @@ schema = 3
     version = "v0.0.0-20241129210726-2c02b8208cf8"
     hash = "sha256-AdLZ3dJLe/yduoNvZiXugZxNfmwJjNQyQGsIdzYzH74="
   [mod."github.com/google/generative-ai-go"]
-    version = "v0.19.0"
-    hash = "sha256-x2K1nkRwtne9MeP5B8FpwavYqQx564go5LzmcBJ0KT4="
+    version = "v0.20.1"
+    hash = "sha256-9bSpEs4kByhgyTKiHdOY5muYjGBTluA1LvEjw2gSoLI="
   [mod."github.com/google/s2a-go"]
     version = "v0.1.9"
     hash = "sha256-0AdSpSTso4bATmM/9qamWzKrVtOLDf7afvDhoiT/UpA="
@@ -128,8 +176,8 @@ schema = 3
     version = "v0.3.6"
     hash = "sha256-hPMF0s+X4/ul98GvVuw/ZNOupEXhIDB1yvWymZWYEbU="
   [mod."github.com/googleapis/gax-go/v2"]
-    version = "v2.14.1"
-    hash = "sha256-iRS/KsAVTePrvTlwA7vKcQnwY6Jz329WdgzFw0hF8wk="
+    version = "v2.14.2"
+    hash = "sha256-QyY7wuCkrOJCJIf9Q884KD/BC3vk/QtQLXeLeNPt750="
   [mod."github.com/jbenet/go-context"]
     version = "v0.0.0-20150711004518-d14ea06fba99"
     hash = "sha256-VANNCWNNpARH/ILQV9sCQsBWgyL2iFT+4AHZREpxIWE="
@@ -161,8 +209,8 @@ schema = 3
     version = "v1.0.2"
     hash = "sha256-+W9EIW7okXIXjWEgOaMh58eLvBZ7OshW2EhaIpNLSBU="
   [mod."github.com/ollama/ollama"]
-    version = "v0.6.6"
-    hash = "sha256-a2Be14e+pcJo15fM/+0ksE9HVl8I4hW6ujqbpNh9bpA="
+    version = "v0.9.0"
+    hash = "sha256-r2eU+kMG3tuJy2B43RXsfmeltzM9t05NEmNiJAW5qr4="
   [mod."github.com/otiai10/copy"]
     version = "v1.14.1"
     hash = "sha256-8RR7u17SbYg9AeBXVHIv5ZMU+kHmOcx0rLUKyz6YtU0="
@@ -182,14 +230,17 @@ schema = 3
     version = "v1.0.0"
     hash = "sha256-/FtmHnaGjdvEIKAJtrUfEhV7EVo5A/eYrtdnUkuxLDA="
   [mod."github.com/samber/lo"]
-    version = "v1.49.1"
-    hash = "sha256-xMQS9Sx2Bpvwo/9JvSVkJ4RXYOSHm642WRqWA6y0AnU="
+    version = "v1.50.0"
+    hash = "sha256-KDFks82BKu39sGt0f972IyOkohV2U0r1YvsnlNLdugY="
   [mod."github.com/sashabaranov/go-openai"]
-    version = "v1.38.2"
-    hash = "sha256-AnBycaxufzWlLS1YBq7MiHDED+Jqtu9oAySKcoL4HOA="
+    version = "v1.40.1"
+    hash = "sha256-GkToonIIF3GG+lwev1lJQ9rAAPJDjSaOkoXRC3OOlEA="
   [mod."github.com/sergi/go-diff"]
-    version = "v1.3.2-0.20230802210424-5b0b94c5c0d3"
-    hash = "sha256-UcLU83CPMbSoKI8RLvLJ7nvGaE2xRSL1RjoHCVkMzUM="
+    version = "v1.4.0"
+    hash = "sha256-rs9NKpv/qcQEMRg7CmxGdP4HGuFdBxlpWf9LbA9wS4k="
+  [mod."github.com/sgaunet/perplexity-go/v2"]
+    version = "v2.8.0"
+    hash = "sha256-w1S14Jf4/6LFODREmmiJvPtkZh4Sor81Rr1PqC5pIak="
   [mod."github.com/skeema/knownhosts"]
     version = "v1.3.1"
     hash = "sha256-kjqQDzuncQNTuOYegqVZExwuOt/Z73m2ST7NZFEKixI="
@@ -212,8 +263,8 @@ schema = 3
     version = "v0.15.1"
     hash = "sha256-HLk6oUe7EoITrNvP0y8D6BtIgIcmDZYtb/xl/dufIoY="
   [mod."github.com/ugorji/go/codec"]
-    version = "v1.2.12"
-    hash = "sha256-sp1LJ93UK7mFwgZqG8jxCgTCPgKR74HNU6XxX0Jfjm0="
+    version = "v1.2.14"
+    hash = "sha256-PoVXlCBE8SvMWpXx9FRsQOSAmE/+5SnPGr4m5BGoyIo="
   [mod."github.com/xanzy/ssh-agent"]
     version = "v0.3.3"
     hash = "sha256-l3pGB6IdzcPA/HLk93sSN6NM2pKPy+bVOoacR5RC2+c="
@@ -221,56 +272,56 @@ schema = 3
     version = "v1.1.0"
     hash = "sha256-cA9qCCu8P1NSJRxgmpfkfa5rKyn9X+Y/9FSmSd5xjyo="
   [mod."go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc"]
-    version = "v0.60.0"
-    hash = "sha256-DkIpL4xUy+UIQBUK6VgbsI79TbZUltaIhXl4UJWym6E="
+    version = "v0.61.0"
+    hash = "sha256-o5w9k3VbqP3gaXI3Aelw93LLHH53U4PnkYVwc3MaY3Y="
   [mod."go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp"]
-    version = "v0.60.0"
-    hash = "sha256-twGSnNbXzcw5qvRiFc/zz5rS+nhmbgSVPcd5jrZjlDg="
+    version = "v0.61.0"
+    hash = "sha256-4pfXD7ErXhexSynXiEEQSAkWoPwHd7PEDE3M1Zi5gLM="
   [mod."go.opentelemetry.io/otel"]
-    version = "v1.35.0"
-    hash = "sha256-LHrBtBnyDtvJGtrXHMPIFe7U53B4bZzpePB4u8Xo4Bg="
+    version = "v1.36.0"
+    hash = "sha256-j8wojdCtKal3LKojanHA8KXXQ0FkbWONpO8tUxpJDko="
   [mod."go.opentelemetry.io/otel/metric"]
-    version = "v1.35.0"
-    hash = "sha256-K9I0LRZqSLrC09Cuk7tp0VEk3cUVDs8S5MGnu9jw92Q="
+    version = "v1.36.0"
+    hash = "sha256-z6Uqi4HhUljWIYd58svKK5MqcGbpcac+/M8JeTrUtJ8="
   [mod."go.opentelemetry.io/otel/trace"]
-    version = "v1.35.0"
-    hash = "sha256-HC2+OGDe2rg0+E8WymQbUNoc249NXM1gIBJzK4UhcQE="
+    version = "v1.36.0"
+    hash = "sha256-owWD9x1lp8aIJqYt058BXPUsIMHdk3RI0escso0BxwA="
   [mod."golang.org/x/arch"]
-    version = "v0.16.0"
-    hash = "sha256-+DMOuIw9GVyhM4VHdYCZepTU/EEHqDfrxJ2F83TOs5k="
+    version = "v0.18.0"
+    hash = "sha256-tUpUPERjmRi7zldj0oPlnbnBhEkcI9iQGvP1HqlsK10="
   [mod."golang.org/x/crypto"]
-    version = "v0.37.0"
-    hash = "sha256-9NwDEcii1e2JYM/+3y1yNzWnt/ChMm27e9OtfuF39OM="
-  [mod."golang.org/x/net"]
     version = "v0.39.0"
-    hash = "sha256-IP29+yGphWKUT7wHTyzqA2rnRT4AJ7oWcT6NKLzkWcM="
+    hash = "sha256-FtwjbVoAhZkx7F2hmzi9Y0J87CVVhWcrZzun+zWQLzc="
+  [mod."golang.org/x/net"]
+    version = "v0.41.0"
+    hash = "sha256-6/pi8rNmGvBFzkJQXkXkMfL1Bjydhg3BgAMYDyQ/Uvg="
   [mod."golang.org/x/oauth2"]
-    version = "v0.29.0"
-    hash = "sha256-IzAypzW8cN5ZbQiIdMTcTiVuUNpMSkwuxeFrJZxcDl8="
+    version = "v0.30.0"
+    hash = "sha256-btD7BUtQpOswusZY5qIU90uDo38buVrQ0tmmQ8qNHDg="
   [mod."golang.org/x/sync"]
-    version = "v0.13.0"
-    hash = "sha256-CElRNe74Or/ysUkb/m3Wcz/juO/tB5fhQbAaxA5AizY="
+    version = "v0.15.0"
+    hash = "sha256-Jf4ehm8H8YAWY6mM151RI5CbG7JcOFtmN0AZx4bE3UE="
   [mod."golang.org/x/sys"]
-    version = "v0.32.0"
-    hash = "sha256-c9RRnyKQy9Kl8hpbtcgkm1O5H7gOdk9Rv925F8fZS6E="
+    version = "v0.33.0"
+    hash = "sha256-wlOzIOUgAiGAtdzhW/KPl/yUVSH/lvFZfs5XOuJ9LOQ="
   [mod."golang.org/x/text"]
-    version = "v0.24.0"
-    hash = "sha256-qFbmteGOvJfvbLXiOSI8Fsz5Ixt2ZhSYx0/sIqApC7Y="
+    version = "v0.26.0"
+    hash = "sha256-N+27nBCyGvje0yCTlUzZoVZ0LRxx4AJ+eBlrFQVRlFQ="
   [mod."golang.org/x/time"]
-    version = "v0.11.0"
-    hash = "sha256-ImTej/e5iUHbWPZMA4M2GYbsbiiZQxIrgcnYsc7uD68="
+    version = "v0.12.0"
+    hash = "sha256-Cp3oxrCMH2wyxjzr5SHVmyhgaoUuSl56Uy00Q7DYEpw="
   [mod."google.golang.org/api"]
-    version = "v0.230.0"
-    hash = "sha256-ihEdZnRbQdwpbgj9AZEZLNY14FqHmacFGFocOqExSVY="
+    version = "v0.236.0"
+    hash = "sha256-tP1RSUSnQ4a0axgZQwEZgKF1E13nL02FSP1NPSZr0Rc="
   [mod."google.golang.org/genproto/googleapis/api"]
-    version = "v0.0.0-20250422160041-2d3770c4ea7f"
-    hash = "sha256-Y4wbEHh9Un0QKplTl2S5lhWDUha9QThx5DhWJbDG9fo="
+    version = "v0.0.0-20250603155806-513f23925822"
+    hash = "sha256-0CS432v9zVhkVLqFpZtxBX8rvVqP67lb7qQ3es7RqIU="
   [mod."google.golang.org/genproto/googleapis/rpc"]
-    version = "v0.0.0-20250422160041-2d3770c4ea7f"
+    version = "v0.0.0-20250603155806-513f23925822"
     hash = "sha256-WK7iDtAhH19NPe3TywTQlGjDawNaDKWnxhFL9PgVUwM="
   [mod."google.golang.org/grpc"]
-    version = "v1.72.0"
-    hash = "sha256-tqu+ACMfKjhqdCGN3jLEmtaHB5ywgHGaS/eDeDRnf+M="
+    version = "v1.73.0"
+    hash = "sha256-LfVlwip++q2DX70RU6CxoXglx1+r5l48DwlFD05G11c="
   [mod."google.golang.org/protobuf"]
     version = "v1.36.6"
     hash = "sha256-lT5qnefI5FDJnowz9PEkAGylH3+fE+A3DJDkAyy9RMc="

nix/pkgs/fabric/version.nix

@@ -1 +1 @@
-"1.4.196"
+"1.4.216"

patterns/analyze_paper/system.md

@@ -8,19 +8,19 @@ Take a deep breath and think step by step about how to best accomplish this goal
 
 - Consume the entire paper and think deeply about it.
 
-- Map out all the claims and implications on a virtual whiteboard in your mind.
+- Map out all the claims and implications on a giant virtual whiteboard in your mind.
 
 # OUTPUT 
 
-- Extract a summary of the paper and its conclusions into a 25-word sentence called SUMMARY.
+- Extract a summary of the paper and its conclusions into a 16-word sentence called SUMMARY.
 
 - Extract the list of authors in a section called AUTHORS.
 
 - Extract the list of organizations the authors are associated, e.g., which university they're at, with in a section called AUTHOR ORGANIZATIONS.
 
-- Extract the primary paper findings into a bulleted list of no more than 16 words per bullet into a section called FINDINGS.
+- Extract the most surprising and interesting paper findings into a 10 bullets of no more than 16 words per bullet into a section called FINDINGS.
 
-- Extract the overall structure and character of the study into a bulleted list of 16 words per bullet for the research in a section called STUDY DETAILS.
+- Extract the overall structure and character of the study into a bulleted list of 16 words per bullet for the research in a section called STUDY OVERVIEW.
 
 - Extract the study quality by evaluating the following items in a section called STUDY QUALITY that has the following bulleted sub-sections:
 
@@ -76,7 +76,9 @@ END EXAMPLE CHART
 
 - SUMMARY STATEMENT:
 
-A final 25-word summary of the paper, its findings, and what we should do about it if it's true.
+A final 16-word summary of the paper, its findings, and what we should do about it if it's true.
+
+Also add 5 8-word bullets of how you got to that rating and conclusion / summary.
 
 # RATING NOTES
 
@@ -84,21 +86,23 @@ A final 25-word summary of the paper, its findings, and what we should do about
 
 - An A would be a paper that is novel, rigorous, empirical, and has no conflicts of interest.
 
-- A paper could get an A if it's theoretical but everything else would have to be perfect.
+- A paper could get an A if it's theoretical but everything else would have to be VERY good.
 
 - The stronger the claims the stronger the evidence needs to be, as well as the transparency into the methodology. If the paper makes strong claims, but the evidence or transparency is weak, then the RIGOR score should be lowered.
 
 - Remove at least 1 grade (and up to 2) for papers where compelling data is provided but it's not clear what exact tests were run and/or how to reproduce those tests. 
 
-- Do not relax this transparency requirement for papers that claim security reasons.
-
-- If a paper does not clearly articulate its methodology in a way that's replicable, lower the RIGOR and overall score significantly.
+- Do not relax this transparency requirement for papers that claim security reasons. If they didn't show their work we have to assume the worst given the reproducibility crisis..
 
 - Remove up to 1-3 grades for potential conflicts of interest indicated in the report.
 
+# ANALYSIS INSTRUCTIONS
+
+- Tend towards being more critical. Not overly so, but don't just fanby over papers that are not rigorous or transparent.
+ 
 # OUTPUT INSTRUCTIONS
 
-- Output all sections above.
+- After deeply considering all the sections above and how they interact with each other, output all sections above.
 
 - Ensure the scoring looks closely at the reproducibility and transparency of the methodology, and that it doesn't give a pass to papers that don't provide the data or methodology for safety or other reasons.
 
@@ -108,7 +112,7 @@ Known         [-2--------]    Novel
 Weak          [-------8--]    Rigorous
 Theoretical   [--3-------]     Empirical
 
-- For the findings and other analysis sections, write at the 9th-grade reading level. This means using short sentences and simple words/concepts to explain everything.
+- For the findings and other analysis sections, and in fact all writing, write in the clear, approachable style of Paul Graham.
 
 - Ensure there's a blank line between each bullet of output.
 
@@ -120,4 +124,3 @@ Theoretical   [--3-------]     Empirical
 
 # INPUT:
 
-INPUT:

patterns/analyze_terraform_plan/system.md

@@ -0,0 +1,24 @@
+# IDENTITY and PURPOSE
+
+You are an expert Terraform plan analyser. You take Terraform plan outputs and generate a Markdown formatted summary using the format below.
+
+You focus on assessing infrastructure changes, security risks, cost implications, and compliance considerations.
+
+## OUTPUT SECTIONS
+
+* Combine all of your understanding of the Terraform plan into a single, 20-word sentence in a section called ONE SENTENCE SUMMARY:.
+* Output the 10 most critical changes, optimisations, or concerns from the Terraform plan as a list with no more than 16 words per point into a section called MAIN POINTS:.
+* Output a list of the 5 key takeaways from the Terraform plan in a section called TAKEAWAYS:.
+
+## OUTPUT INSTRUCTIONS
+
+* Create the output using the formatting above.
+* You only output human-readable Markdown.
+* Output numbered lists, not bullets.
+* Do not output warnings or notes—just the requested sections.
+* Do not repeat items in the output sections.
+* Do not start items with the same opening words.
+
+## INPUT
+
+INPUT:

patterns/create_mnemonic_phrases/readme.md

@@ -0,0 +1,37 @@
+# create_mnemonic_phrases
+
+Generate short, memorable sentences that embed Diceware‑style words **unchanged and in order**. This pattern is ideal for turning a raw Diceware word list into phrases that are easier to recall while preserving the exact secret.
+
+## What is Diceware?
+
+Diceware is a passphrase scheme that maps every possible roll of **five six‑sided dice** (11111–66666) to a unique word. Because there are `6^5 = 7776` combinations, the canonical list contains the same number of entries.
+
+### Entropy of the standard 7776‑word list
+
+```text
+words = 7776
+entropy_per_word = log2(words) ≈ 12.925 bits
+```
+
+A passphrase that strings *N* independently chosen words together therefore carries `N × 12.925 bits` of entropy—≈ 77.5 bits for six words, ≈ 129 bits for ten, and so on. Four or more words already outclass most human‑made passwords.
+
+## Pattern overview
+
+The accompanying **`system.md`** file instructs Fabric to:
+
+1. Echo the supplied words back in **bold**, separated by commas.
+2. Generate **five** distinct, short sentences that include the words **in the same order and spelling**, enabling rapid rote learning or spaced‑repetition drills.
+
+The output is deliberately minimalist—no extra commentary—so you can pipe it straight into other scripts.
+
+## Quick start
+
+```bash
+# 1  Pick five random words from any Diceware‑compatible list
+shuf -n 5 diceware_wordlist.txt | \
+  # 2  Feed them to Fabric with this pattern
+  fabric --pattern create_mnemonic_phrases -s
+```
+
+You’ll see the words echoed in bold, followed by five candidate mnemonic sentences ready for memorisation.
+

patterns/create_mnemonic_phrases/system.md

@@ -0,0 +1,67 @@
+# IDENTITY AND PURPOSE
+
+As a creative language assistant, you are responsible for creating memorable mnemonic bridges in the form of sentences from given words. The order and spelling of the words must remain unchanged. Your task is to use these words as they are given, without allowing synonyms, paraphrases or grammatical variations. First, you will output the words in exact order and in bold, followed by five short sentences containing and highlighting all the words in the given order. You need to make sure that your answers follow the required format exactly and are easy to remember.
+
+Take a moment to think step-by-step about how to achieve the best results by following the steps below.
+
+# STEPS
+
+- First, type out the words, separated by commas, in exact order and each formatted in Markdown **bold** seperately.
+ 
+- Then create five short, memorable sentences. Each sentence should contain all the given words in exactly this order, directly embedded and highlighted in bold.
+
+# INPUT FORMAT
+
+The input will be a list of words that may appear in one of the following formats:
+
+- A plain list of wordsin a row, e.g.: 
+
+        spontaneous
+        branches
+        embargo
+        intrigue
+        detours
+   
+- A list where each word is preceded by a decimal number, e.g.:
+
+        12345 spontaneous
+        54321 branches
+        32145 embargo
+        45321 intrigue
+        35124 detours
+
+In all cases:
+Ignore any decimal numbers and use only the words, in the exact order and spelling, as input.
+
+
+# OUTPUT INSTRUCTIONS
+
+- The output is **only** in Markdown format.
+
+- Output **only** the given five words in the exact order and formatted in **bold**, separated by commas.
+
+- This is followed by exactly five short, memorable sentences. Each sentence must contain all five words in exactly this order, directly embedded and formatted in **bold**.
+
+- Nothing else may be output** - no explanations, thoughts, comments, introductions or additional information. Only the formatted word list and the five sentences.
+
+- The sentences should be short and memorable!
+
+- **Make sure you follow ALL of these instructions when creating your output**.
+
+
+## EXAMPLE
+
+**spontaneous**, **branches**, **embargo**, **intrigue**, **detours**
+
+1. The **spontaneous** monkey swung through **branches**, dodging an **embargo**, chasing **intrigue**, and loving the **detours**.
+2. Her **spontaneous** idea led her into **branches** of diplomacy, breaking an **embargo**, fueled by **intrigue**, with many **detours**.
+3. A **spontaneous** road trip ended in **branches** of politics, under an **embargo**, tangled in **intrigue**, through endless **detours**.
+4. The **spontaneous** plan involved climbing **branches**, avoiding an **embargo**, drawn by **intrigue**, and full of **detours**.
+5. His **spontaneous** speech spread through **branches** of power, lifting the **embargo**, stirring **intrigue**, and opening **detours**.
+
+
+# INPUT
+
+
+
+

patterns/create_prd/system.md

@@ -1,23 +1,41 @@
-# IDENTITY
+# IDENTITY and PURPOSE
 
-// Who you are
+You are a Product Requirements Document (PRD) Generator. Your role is to transform product ideas, prompts, or descriptions into a structured PRD. This involves outlining the product’s goals, features, technical requirements, user experience considerations, and other critical elements necessary for development and stakeholder alignment.
 
-You create precise and accurate PRDs from the input you receive.
+Your purpose is to ensure clarity, alignment, and precision in product planning and execution. You must break down the product concept into actionable sections, thinking holistically about business value, user needs, functional components, and technical feasibility. Your output should be comprehensive, well-organized, and formatted consistently to meet professional documentation standards.
 
-# GOAL
+Take a step back and think step-by-step about how to achieve the best possible results by following the steps below.
 
-// What we are trying to achieve
+## STEPS
 
-1. Create a great PRD.
+* Analyze the prompt to understand the product concept, functionality, and target users.
 
-# STEPS
+* Identify and document the key sections typically found in a PRD: Overview, Objectives, Target Audience, Features, User Stories, Functional Requirements, Non-functional Requirements, Success Metrics, and Timeline.
 
-- Read through all the input given and determine the best structure for a PRD.
+* Clarify ambiguities or ask for more information if critical details are missing.
 
-# OUTPUT INSTRUCTIONS
+* Organize the content into clearly labeled sections.
 
-- Create the PRD in Markdown.
+* Maintain formal, precise language suited for business and technical audiences.
 
-# INPUT
+* Ensure each requirement is specific, testable, and unambiguous.
+
+* Use bullet points and tables where appropriate to improve readability.
+
+## OUTPUT INSTRUCTIONS
+
+* The only output format should be Markdown.
+
+* All content should be structured into clearly labeled PRD sections.
+
+* Use bullet points and subheadings to break down features and requirements.
+
+* Highlight priorities or MVP features where relevant.
+
+* Include mock data or placeholders if actual data is not provided.
+
+* Ensure you follow ALL these instructions when creating your output.
+
+## INPUT
 
 INPUT:

patterns/extract_article_wisdom/dmiessler/extract_wisdom-1.0.0/system.md

@@ -1,29 +0,0 @@
-# IDENTITY and PURPOSE
-
-You are a wisdom extraction service for text content. You are interested in wisdom related to the purpose and meaning of life, the role of technology in the future of humanity, artificial intelligence, memes, learning, reading, books, continuous improvement, and similar topics.
-
-Take a step back and think step by step about how to achieve the best result possible as defined in the steps below. You have a lot of freedom to make this work well.
-
-## OUTPUT SECTIONS
-
-1. You extract a summary of the content in 50 words or less, including who is presenting and the content being discussed into a section called SUMMARY.
-
-2. You extract the top 50 ideas from the input in a section called IDEAS:. If there are less than 50 then collect all of them.
-
-3. You extract the 15-30 most insightful and interesting quotes from the input into a section called QUOTES:. Use the exact quote text from the input.
-
-4. You extract 15-30 personal habits of the speakers, or mentioned by the speakers, in the content into a section called HABITS. Examples include but aren't limited to: sleep schedule, reading habits, things the
-
-5. You extract the 15-30 most insightful and interesting valid facts about the greater world that were mentioned in the content into a section called FACTS:.
-
-6. You extract all mentions of writing, art, and other sources of inspiration mentioned by the speakers into a section called REFERENCES. This should include any and all references to something that the speaker mentioned.
-
-7. You extract the 15-30 most insightful and interesting overall (not content recommendations from EXPLORE) recommendations that can be collected from the content into a section called RECOMMENDATIONS.
-
-## OUTPUT INSTRUCTIONS
-
-1. You only output Markdown.
-2. Do not give warnings or notes; only output the requested sections.
-3. You use numbered lists, not bullets.
-4. Do not repeat ideas, quotes, habits, facts, or references.
-5. Do not start items with the same opening words.

patterns/extract_article_wisdom/dmiessler/extract_wisdom-1.0.0/user.md

@@ -1 +0,0 @@
-CONTENT:

patterns/extract_insights/system.md

@@ -1,25 +1,21 @@
 # IDENTITY and PURPOSE
 
-You extract surprising, powerful, and interesting insights from text content. You are interested in insights related to the purpose and meaning of life, human flourishing, the role of technology in the future of humanity, artificial intelligence and its affect on humans, memes, learning, reading, books, continuous improvement, and similar topics.
+You are an expert at extracting the most surprising, powerful, and interesting insights from content. You are interested in insights related to the purpose and meaning of life, human flourishing, the role of technology in the future of humanity, artificial intelligence and its affect on humans, memes, learning, reading, books, continuous improvement, and similar topics.
 
-You create 15 word bullet points that capture the most important insights from the input.
+You create 8 word bullet points that capture the most surprising and novel insights from the input.
 
 Take a step back and think step-by-step about how to achieve the best possible results by following the steps below.
 
 # STEPS
 
-- Extract 20 to 50 of the most surprising, insightful, and/or interesting ideas from the input in a section called IDEAS, and write them on a virtual whiteboard in your mind using 15 word bullets. If there are less than 50 then collect all of them. Make sure you extract at least 20.
-
-- From those IDEAS, extract the most powerful and insightful of them and write them in a section called INSIGHTS. Make sure you extract at least 10 and up to 25.
+- Extract 10 of the most surprising and novel insights from the input.
+- Output them as 8 word bullets in order of surprise, novelty, and importance.
+- Write them in the simple, approachable style of Paul Graham.
 
 # OUTPUT INSTRUCTIONS
 
-- INSIGHTS are essentially higher-level IDEAS that are more abstracted and wise.
-
 - Output the INSIGHTS section only.
 
-- Each bullet should be 16 words in length.
-
 - Do not give warnings or notes; only output the requested sections.
 
 - You use bulleted lists for output, not numbered lists.
@@ -28,7 +24,6 @@ Take a step back and think step-by-step about how to achieve the best possible r
 
 - Ensure you follow ALL these instructions when creating your output.
 
-
 # INPUT
 
-INPUT:
+{{input}}

patterns/extract_product_features/dmiessler/extract_wisdom-1.0.0/system.md

@@ -1,29 +0,0 @@
-# IDENTITY and PURPOSE
-
-You are a wisdom extraction service for text content. You are interested in wisdom related to the purpose and meaning of life, the role of technology in the future of humanity, artificial intelligence, memes, learning, reading, books, continuous improvement, and similar topics.
-
-Take a step back and think step by step about how to achieve the best result possible as defined in the steps below. You have a lot of freedom to make this work well.
-
-## OUTPUT SECTIONS
-
-1. You extract a summary of the content in 50 words or less, including who is presenting and the content being discussed into a section called SUMMARY.
-
-2. You extract the top 50 ideas from the input in a section called IDEAS:. If there are less than 50 then collect all of them.
-
-3. You extract the 15-30 most insightful and interesting quotes from the input into a section called QUOTES:. Use the exact quote text from the input.
-
-4. You extract 15-30 personal habits of the speakers, or mentioned by the speakers, in the content into a section called HABITS. Examples include but aren't limited to: sleep schedule, reading habits, things the speakers always do, things they always avoid, productivity tips, diet, exercise, etc.
-
-5. You extract the 15-30 most insightful and interesting valid facts about the greater world that were mentioned in the content into a section called FACTS:.
-
-6. You extract all mentions of writing, art, and other sources of inspiration mentioned by the speakers into a section called REFERENCES. This should include any and all references to something that the speaker mentioned.
-
-7. You extract the 15-30 most insightful and interesting overall (not content recommendations from EXPLORE) recommendations that can be collected from the content into a section called RECOMMENDATIONS.
-
-## OUTPUT INSTRUCTIONS
-
-1. You only output Markdown.
-2. Do not give warnings or notes; only output the requested sections.
-3. You use numbered lists, not bullets.
-4. Do not repeat ideas, quotes, habits, facts, or references.
-5. Do not start items with the same opening words.

patterns/extract_product_features/dmiessler/extract_wisdom-1.0.0/user.md

@@ -1 +0,0 @@
-CONTENT:

patterns/extract_wisdom/dmiessler/extract_wisdom-1.0.0/system.md

@@ -1,29 +0,0 @@
-# IDENTITY and PURPOSE
-
-You are a wisdom extraction service for text content. You are interested in wisdom related to the purpose and meaning of life, the role of technology in the future of humanity, artificial intelligence, memes, learning, reading, books, continuous improvement, and similar topics.
-
-Take a step back and think step by step about how to achieve the best result possible as defined in the steps below. You have a lot of freedom to make this work well.
-
-## OUTPUT SECTIONS
-
-1. You extract a summary of the content in 50 words or less, including who is presenting and the content being discussed into a section called SUMMARY.
-
-2. You extract the top 50 ideas from the input in a section called IDEAS:. If there are less than 50 then collect all of them.
-
-3. You extract the 15-30 most insightful and interesting quotes from the input into a section called QUOTES:. Use the exact quote text from the input.
-
-4. You extract 15-30 personal habits of the speakers, or mentioned by the speakers, in the content into a section called HABITS. Examples include but aren't limited to: sleep schedule, reading habits, things the speakers always do, things they always avoid, productivity tips, diet, exercise, etc.
-
-5. You extract the 15-30 most insightful and interesting valid facts about the greater world that were mentioned in the content into a section called FACTS:.
-
-6. You extract all mentions of writing, art, and other sources of inspiration mentioned by the speakers into a section called REFERENCES. This should include any and all references to something that the speaker mentioned.
-
-7. You extract the 15-30 most insightful and interesting overall (not content recommendations from EXPLORE) recommendations that can be collected from the content into a section called RECOMMENDATIONS.
-
-## OUTPUT INSTRUCTIONS
-
-1. You only output Markdown.
-2. Do not give warnings or notes; only output the requested sections.
-3. You use numbered lists, not bullets.
-4. Do not repeat ideas, quotes, habits, facts, or references.
-5. Do not start items with the same opening words.

patterns/extract_wisdom/dmiessler/extract_wisdom-1.0.0/user.md

@@ -1 +0,0 @@
-CONTENT:

patterns/pattern_explanations.md

@@ -1,210 +1,223 @@
-Brief one-line summary from AI analysis of what each pattern does.
+# Brief one-line summary from AI analysis of what each pattern does
 
 - Key pattern to use: **suggest_pattern**, suggests appropriate fabric patterns or commands based on user input.**
 
 1. **agility_story**: Generate a user story and acceptance criteria in JSON format based on the given topic.
 2. **ai**: Interpret questions deeply and provide concise, insightful answers in Markdown bullet points.
-3. **analyse_answers**: Evaluate quiz answers for correctness based on learning objectives and generated quiz questions.
-4. **analyse_candidates**: Compare and contrast two political candidates based on key issues and policies.
-5. **analyse_cfp_submission**: Review and evaluate conference speaking session submissions based on clarity, relevance, depth, and engagement potential.
-6. **analyse_claims**: Analyse and rate truth claims with evidence, counter-arguments, fallacies, and final recommendations.
-7. **analyse_comments**: Evaluate internet comments for content, categorize sentiment, and identify reasons for praise, criticism, and neutrality.
-8. **analyse_debate**: Rate debates on insight, emotionality, and present an unbiased, thorough analysis of arguments, agreements, and disagreements.
-9. **analyse_email_headers**: Provide cybersecurity analysis and actionable insights on SPF, DKIM, DMARC, and ARC email header results.
-10. **analyse_incident**: Efficiently extract and organize key details from cybersecurity breach articles, focusing on attack type, vulnerable components, attacker and target info, incident details, and remediation steps.
-11. **analyse_interviewer_techniques**: This exercise involves analyzing interviewer techniques, identifying their unique qualities, and succinctly articulating what makes them stand out in a clear, simple format.
-12. **analyse_logs**: Analyse server log files to identify patterns, anomalies, and issues, providing data-driven insights and recommendations for improving server reliability and performance.
-13. **analyse_malware**: Analyse malware details, extract key indicators, techniques, and potential detection strategies, and summarize findings concisely for a malware analyst's use in identifying and responding to threats.
-14. **analyse_military_strategy**: Analyse a historical battle, offering in-depth insights into strategic decisions, strengths, weaknesses, tactical approaches, logistical factors, pivotal moments, and consequences for a comprehensive military evaluation.
-15. **analyse_mistakes**: Analyse past mistakes in thinking patterns, map them to current beliefs, and offer recommendations to improve accuracy in predictions.
-16. **analyse_paper**: Analyses research papers by summarizing findings, evaluating rigor, and assessing quality to provide insights for documentation and review.
-17. **analyse_patent**: Analyse a patent's field, problem, solution, novelty, inventive step, and advantages in detail while summarizing and extracting keywords.
-18. **analyze_personality**: Performs a deep psychological analysis of a person in the input, focusing on their behavior, language, and psychological traits.
-19. **analyze_presentation**: Reviews and critiques presentations by analyzing the content, speaker's underlying goals, self-focus, and entertainment value.
-20. **analyze_product_feedback**: A prompt for analyzing and organizing user feedback by identifying themes, consolidating similar comments, and prioritizing them based on usefulness.
-21. **analyze_proposition**: Analyzes a ballot proposition by identifying its purpose, impact, arguments for and against, and relevant background information.
-22. **analyze_prose**: Evaluates writing for novelty, clarity, and prose, providing ratings, improvement recommendations, and an overall score.
-23. **analyze_prose_json**: Evaluates writing for novelty, clarity, prose, and provides ratings, explanations, improvement suggestions, and an overall score in a JSON format.
-24. **analyze_prose_pinker**: Evaluates prose based on Steven Pinker's The Sense of Style, analyzing writing style, clarity, and bad writing elements.
-25. **analyze_risk**: Conducts a risk assessment of a third-party vendor, assigning a risk score and suggesting security controls based on analysis of provided documents and vendor website.
-26. **analyze_sales_call**: Rates sales call performance across multiple dimensions, providing scores and actionable feedback based on transcript analysis.
-27. **analyze_spiritual_text**: Compares and contrasts spiritual texts by analyzing claims and differences with the King James Bible.
-28. **analyze_tech_impact**: Analyzes the societal impact, ethical considerations, and sustainability of technology projects, evaluating their outcomes and benefits.
-29. **analyze_threat_report**: Extracts surprising insights, trends, statistics, quotes, references, and recommendations from cybersecurity threat reports, summarizing key findings and providing actionable information.
-30. **analyse_threat_report_cmds**: Extract and synthesize actionable cybersecurity commands from provided materials, incorporating command-line arguments and expert insights for pentesters and non-experts.
-31. **analyse_threat_report_trends**: Extract up to 50 surprising, insightful, and interesting trends from a cybersecurity threat report in markdown format.
-32. **answer_interview_question**: Generates concise, tailored responses to technical interview questions, incorporating alternative approaches and evidence to demonstrate the candidate's expertise and experience.
-33. **ask_secure_by_design_questions**: Generates a set of security-focused questions to ensure a project is built securely by design, covering key components and considerations.
-34. **ask_uncle_duke**: Coordinates a team of AI agents to research and produce multiple software development solutions based on provided specifications, and conducts detailed code reviews to ensure adherence to best practices.
-35. **capture_thinkers_work**: Analyze philosophers or philosophies and provide detailed summaries about their teachings, background, works, advice, and related concepts in a structured template.
-36. **check_agreement**: Analyze contracts and agreements to identify important stipulations, issues, and potential gotchas, then summarize them in Markdown.
-37. **clean_text**: Fix broken or malformatted text by correcting line breaks, punctuation, capitalization, and paragraphs without altering content or spelling.
-38. **coding_master**: Explain a coding concept to a beginner, providing examples, and formatting code in markdown with specific output sections like ideas, recommendations, facts, and insights.
-39. **compare_and_contrast**: Compare and contrast a list of items in a markdown table, with items on the left and topics on top.
-40. **convert_to_markdown**: Convert content to clean, complete Markdown format, preserving all original structure, formatting, links, and code blocks without alterations.
-41. **create_5_sentence_summary**: Create concise summaries or answers to input at 5 different levels of depth, from 5 words to 1 word.
-42. **create_academic_paper**: Generate a high-quality academic paper in LaTeX format with clear concepts, structured content, and a professional layout.
-43. **create_ai_jobs_analysis**: Analyze job categories' susceptibility to automation, identify resilient roles, and provide strategies for personal adaptation to AI-driven changes in the workforce.
-44. **create_aphorisms**: Find and generate a list of brief, witty statements.
-45. **create_art_prompt**: Generates a detailed, compelling visual description of a concept, including stylistic references and direct AI instructions for creating art.
-46. **create_better_frame**: Identifies and analyzes different frames of interpreting reality, emphasizing the power of positive, productive lenses in shaping outcomes.
-47. **create_coding_project**: Generate wireframes and starter code for any coding ideas that you have.
-48. **create_command**: Helps determine the correct parameters and switches for penetration testing tools based on a brief description of the objective.
-49. create_cyber_summary: Summarizes cybersecurity threats, vulnerabilities, incidents, and malware with a 25-word summary and categorized bullet points, after thoroughly analyzing and mapping the provided input.
-50. **create_design_document**: Creates a detailed design document for a system using the C4 model, addressing business and security postures, and including a system context diagram.
-51. **create_diy**: Creates structured "Do It Yourself" tutorial patterns by analyzing prompts, organizing requirements, and providing step-by-step instructions in Markdown format.
-52. **create_formal_email**: Crafts professional, clear, and respectful emails by analyzing context, tone, and purpose, ensuring proper structure and formatting.
-53. **create_git_diff_commit**: Generates Git commands and commit messages for reflecting changes in a repository, using conventional commits and providing concise shell commands for updates.
-54. **create_graph_from_input**: Generates a CSV file with progress-over-time data for a security program, focusing on relevant metrics and KPIs.
-55. **create_hormozi_offer**: Creates a customized business offer based on principles from Alex Hormozi's book, "$100M Offers."
-56. **create_idea_compass**: Organizes and structures ideas by exploring their definition, evidence, sources, and related themes or consequences.
-57. **create_investigation_visualization**: Creates detailed Graphviz visualizations of complex input, highlighting key aspects and providing clear, well-annotated diagrams for investigative analysis and conclusions.
-58. **create_keynote**: Creates TED-style keynote presentations with a clear narrative, structured slides, and speaker notes, emphasizing impactful takeaways and cohesive flow.
-59. **create_logo**: Creates simple, minimalist company logos without text, generating AI prompts for vector graphic logos based on input.
-60. **create_markmap_visualization**: Transforms complex ideas into clear visualizations using MarkMap syntax, simplifying concepts into diagrams with relationships, boxes, arrows, and labels.
-61. **create_mermaid_visualization**: Creates detailed, standalone visualizations of concepts using Mermaid (Markdown) syntax, ensuring clarity and coherence in diagrams.
-62. **create_mermaid_visualization_for_github**: Creates standalone, detailed visualizations using Mermaid (Markdown) syntax to effectively explain complex concepts, ensuring clarity and precision.
-63. **create_micro_summary**: Summarizes content into a concise, 20-word summary with main points and takeaways, formatted in Markdown.
-64. **create_network_threat_landscape**: Analyzes open ports and services from a network scan and generates a comprehensive, insightful, and detailed security threat report in Markdown.
-65. **create_newsletter_entry**: Condenses provided article text into a concise, objective, newsletter-style summary with a title in the style of Frontend Weekly.
-66. **create_npc**: Generates a detailed D&D 5E NPC, including background, flaws, stats, appearance, personality, goals, and more in Markdown format.
-67. **create_pattern**: Extracts, organizes, and formats LLM/AI prompts into structured sections, detailing the AI’s role, instructions, output format, and any provided examples for clarity and accuracy.
-68. **create_prd**: Creates a precise Product Requirements Document (PRD) in Markdown based on input.
-69. **create_prediction_block**: Extracts and formats predictions from input into a structured Markdown block for a blog post.
-70. **create_quiz**: Creates a three-phase reading plan based on an author or topic to help the user become significantly knowledgeable, including core, extended, and supplementary readings.
-71. **create_reading_plan**: Generates review questions based on learning objectives from the input, adapted to the specified student level, and outputs them in a clear markdown format.
-72. **create_recursive_outline**: Breaks down complex tasks or projects into manageable, hierarchical components with recursive outlining for clarity and simplicity.
-73. **create_report_finding**: Creates a detailed, structured security finding report in markdown, including sections on Description, Risk, Recommendations, References, One-Sentence-Summary, and Quotes.
-74. **create_rpg_summary**: Summarizes an in-person RPG session with key events, combat details, player stats, and role-playing highlights in a structured format.
-75. **create_security_update**: Creates concise security updates for newsletters, covering stories, threats, advisories, vulnerabilities, and a summary of key issues.
-76. **create_show_intro**: Creates compelling short intros for podcasts, summarizing key topics and themes discussed in the episode.
-77. **create_sigma_rules**: Extracts Tactics, Techniques, and Procedures (TTPs) from security news and converts them into Sigma detection rules for host-based detections.
-78. **create_story_explanation**: Summarizes complex content in a clear, approachable story format that makes the concepts easy to understand.
-79. **create_stride_threat_model**: Create a STRIDE-based threat model for a system design, identifying assets, trust boundaries, data flows, and prioritizing threats with mitigations.
-80. **create_summary**: Summarizes content into a 20-word sentence, 10 main points (16 words max), and 5 key takeaways in Markdown format.
-81. **create_tags**: Identifies at least 5 tags from text content for mind mapping tools, including authors and existing tags if present.
-82. **create_threat_scenarios**: Identifies likely attack methods for any system by providing a narrative-based threat model, balancing risk and opportunity.
-83. **create_ttrc_graph**: Creates a CSV file showing the progress of Time to Remediate Critical Vulnerabilities over time using given data.
-84. **create_ttrc_narrative**: Creates a persuasive narrative highlighting progress in reducing the Time to Remediate Critical Vulnerabilities metric over time.
-85. **create_upgrade_pack**: Extracts world model and task algorithm updates from content, providing beliefs about how the world works and task performance.
-86. **create_user_story**: Writes concise and clear technical user stories for new features in complex software programs, formatted for all stakeholders.
-87. **create_video_chapters**: Extracts interesting topics and timestamps from a transcript, providing concise summaries of key moments.
-88. **create_visualization**: Transforms complex ideas into visualizations using intricate ASCII art, simplifying concepts where necessary.
-89. **dialog_with_socrates**: Engages in deep, meaningful dialogues to explore and challenge beliefs using the Socratic method.
-90. **enrich_blog_post**: Enhances Markdown blog files by applying instructions to improve structure, visuals, and readability for HTML rendering.
-91. **explain_code**: Explains code, security tool output, configuration text, and answers questions based on the provided input.
-92. **explain_docs**: Improves and restructures tool documentation into clear, concise instructions, including overviews, usage, use cases, and key features.
-93. **explain_math**: Helps you understand mathematical concepts in a clear and engaging way.
-94. **explain_project**: Summarizes project documentation into clear, concise sections covering the project, problem, solution, installation, usage, and examples.
-95. **explain_terms**: Produces a glossary of advanced terms from content, providing a definition, analogy, and explanation of why each term matters.
-96. **export_data_as_csv**: Extracts and outputs all data structures from the input in properly formatted CSV data.
-97. **extract_algorithm_update_recommendations**: Extracts concise, practical algorithm update recommendations from the input and outputs them in a bulleted list.
-98. **extract_article_wisdom**: Extracts surprising, insightful, and interesting information from content, categorizing it into sections like summary, ideas, quotes, facts, references, and recommendations.
-99. **extract_book_ideas**: Extracts and outputs 50 to 100 of the most surprising, insightful, and interesting ideas from a book's content.
-100. **extract_book_recommendations**: Extracts and outputs 50 to 100 practical, actionable recommendations from a book's content.
-101. **extract_business_ideas**: Extracts top business ideas from content and elaborates on the best 10 with unique differentiators.
-102. **extract_controversial_ideas**: Extracts and outputs controversial statements and supporting quotes from the input in a structured Markdown list.
-103. **extract_core_message**: Extracts and outputs a clear, concise sentence that articulates the core message of a given text or body of work.
-104. **extract_ctf_writeup**: Extracts a short writeup from a warstory-like text about a cyber security engagement.
-105. **extract_extraordinary_claims**: Extracts and outputs a list of extraordinary claims from conversations, focusing on scientifically disputed or false statements.
-106. **extract_ideas**: Extracts and outputs all the key ideas from input, presented as 15-word bullet points in Markdown.
-107. **extract_insights**: Extracts and outputs the most powerful and insightful ideas from text, formatted as 16-word bullet points in the INSIGHTS section, also IDEAS section.
-108. **extract_insights_dm**: Extracts and outputs all valuable insights and a concise summary of the content, including key points and topics discussed.
-109. **extract_instructions**: Extracts clear, actionable step-by-step instructions and main objectives from instructional video transcripts, organizing them into a concise list.
-110. **extract_jokes**: Extracts jokes from text content, presenting each joke with its punchline in separate bullet points.
-111. **extract_latest_video**: Extracts the latest video URL from a YouTube RSS feed and outputs the URL only.
-112. **extract_main_idea**: Extracts the main idea and key recommendation from the input, summarizing them in 15-word sentences.
-113. **extract_most_redeeming_thing**: Extracts the most redeeming aspect from an input, summarizing it in a single 15-word sentence.
-114. **extract_patterns**: Extracts and analyzes recurring, surprising, and insightful patterns from input, providing detailed analysis and advice for builders.
-115. **extract_poc**: Extracts proof of concept URLs and validation methods from security reports, providing the URL and command to run.
-116. **extract_predictions**: Extracts predictions from input, including specific details such as date, confidence level, and verification method.
-117. **extract_primary_problem**: Extracts the primary problem with the world as presented in a given text or body of work.
-118. **extract_primary_solution**: Extracts the primary solution for the world as presented in a given text or body of work.
-119. **extract_product_features**: Extracts and outputs a list of product features from the provided input in a bulleted format.
-120. **extract_questions**: Extracts and outputs all questions asked by the interviewer in a conversation or interview.
-121. **extract_recipe**: Extracts and outputs a recipe with a short meal description, ingredients with measurements, and preparation steps.
-122. **extract_recommendations**: Extracts and outputs concise, practical recommendations from a given piece of content in a bulleted list.
-123. **extract_references**: Extracts and outputs a bulleted list of references to art, stories, books, literature, and other sources from content.
-124. **extract_skills**: Extracts and classifies skills from a job description into a table, separating each skill and classifying it as either hard or soft.
-125. **extract_song_meaning**: Analyzes a song to provide a summary of its meaning, supported by detailed evidence from lyrics, artist commentary, and fan analysis.
-126. **extract_sponsors** Extracts and lists official sponsors and potential sponsors from a provided transcript.
-127. **extract_videoid**: Extracts and outputs the video ID from any given URL.
-128. **extract_wisdom**: Extracts surprising, insightful, and interesting information from text on topics like human flourishing, AI, learning, and more.
-129. **extract_wisdom_agents**: Extracts valuable insights, ideas, quotes, and references from content, emphasizing topics like human flourishing, AI, learning, and technology.
-130. **extract_wisdom_dm**: Extracts all valuable, insightful, and thought-provoking information from content, focusing on topics like human flourishing, AI, learning, and technology.
-131. **extract_wisdom_nometa**: Extracts insights, ideas, quotes, habits, facts, references, and recommendations from content, focusing on human flourishing, AI, technology, and related topics.
-132. **find_hidden_message**: Extracts overt and hidden political messages, justifications, audience actions, and a cynical analysis from content.
-133. **find_logical_fallacies**: Identifies and analyzes fallacies in arguments, classifying them as formal or informal with detailed reasoning.
-134. **get_wow_per_minute**: Determines the wow-factor of content per minute based on surprise, novelty, insight, value, and wisdom, measuring how rewarding the content is for the viewer.
-135. **get_youtube_rss**: Returns the RSS URL for a given YouTube channel based on the channel ID or URL.
-136. **humanize**: Rewrites AI-generated text to sound natural, conversational, and easy to understand, maintaining clarity and simplicity.
-137. **identify_dsrp_distinctions**: Encourages creative, systems-based thinking by exploring distinctions, boundaries, and their implications, drawing on insights from prominent systems thinkers.
-138. **identify_dsrp_perspectives**: Explores the concept of distinctions in systems thinking, focusing on how boundaries define ideas, influence understanding, and reveal or obscure insights.
-139. **identify_dsrp_relationships**: Encourages exploration of connections, distinctions, and boundaries between ideas, inspired by systems thinkers to reveal new insights and patterns in complex systems.
-140. **identify_dsrp_systems**: Encourages organizing ideas into systems of parts and wholes, inspired by systems thinkers to explore relationships and how changes in organization impact meaning and understanding.
-141. **identify_job_stories**: Identifies key job stories or requirements for roles.
-142. **improve_academic_writing**: Refines text into clear, concise academic language while improving grammar, coherence, and clarity, with a list of changes.
-143. **improve_prompt**: Improves an LLM/AI prompt by applying expert prompt writing strategies for better results and clarity.
-144. **improve_report_finding**: Improves a penetration test security finding by providing detailed descriptions, risks, recommendations, references, quotes, and a concise summary in markdown format.
-145. **improve_writing**: Refines text by correcting grammar, enhancing style, improving clarity, and maintaining the original meaning. skills.
-146. **judge_output**: Evaluates Honeycomb queries by judging their effectiveness, providing critiques and outcomes based on language nuances and analytics relevance.
-147. **label_and_rate**: Labels content with up to 20 single-word tags and rates it based on idea count and relevance to human meaning, AI, and other related themes, assigning a tier (S, A, B, C, D) and a quality score.
-148. **md_callout**: Classifies content and generates a markdown callout based on the provided text, selecting the most appropriate type.
-149. **official_pattern_template**: Template to use if you want to create new fabric patterns.
-150. **prepare_7s_strategy**: Prepares a comprehensive briefing document from 7S's strategy capturing organizational profile, strategic elements, and market dynamics with clear, concise, and organized content.
-151. **provide_guidance**: Provides psychological and life coaching advice, including analysis, recommendations, and potential diagnoses, with a compassionate and honest tone.
-152. **rate_ai_response**: Rates the quality of AI responses by comparing them to top human expert performance, assigning a letter grade, reasoning, and providing a 1-100 score based on the evaluation.
-153. **rate_ai_result**: Assesses the quality of AI/ML/LLM work by deeply analyzing content, instructions, and output, then rates performance based on multiple dimensions, including coverage, creativity, and interdisciplinary thinking.
-154. **rate_content**: Labels content with up to 20 single-word tags and rates it based on idea count and relevance to human meaning, AI, and other related themes, assigning a tier (S, A, B, C, D) and a quality score.
-155. **rate_value**: Produces the best possible output by deeply analyzing and understanding the input and its intended purpose.
-156. **raw_query**: Fully digests and contemplates the input to produce the best possible result based on understanding the sender's intent.
-157. **raycast**: Some scripts for Raycast, but think u need pro Raycast AI to use it
-158. **recommend_artists**: Recommends a personalized festival schedule with artists aligned to your favorite styles and interests, including rationale.
-159. **recommend_pipeline_upgrades**: Optimizes vulnerability-checking pipelines by incorporating new information and improving their efficiency, with detailed explanations of changes.
-160. **recommend_talkpanel_topics**: Produces a clean set of proposed talks or panel talking points for a person based on their interests and goals, formatted for submission to a conference organizer.
-161. **refine_design_document**: Refines a design document based on a design review by analyzing, mapping concepts, and implementing changes using valid Markdown.
-162. **review_design**: Reviews and analyzes architecture design, focusing on clarity, component design, system integrations, security, performance, scalability, and data management.
-163. **sanitize_broken_html_to_markdown**: Converts messy HTML into clean, properly formatted Markdown, applying custom styling and ensuring compatibility with Vite.
-164. **show_fabric_options_markmap**: Visualizes the functionality of the Fabric framework by representing its components, commands, and features based on the provided input.
-165. **solve_with_cot**: Provides detailed, step-by-step responses with chain of thought reasoning, using structured thinking, reflection, and output sections.
-166. **suggest_pattern**: Suggests appropriate fabric patterns or commands based on user input, providing clear explanations and options for users.
-167. **summarize**: Summarizes content into a 20-word sentence, main points, and takeaways, formatted with numbered lists in Markdown.
-168. **summarize_debate**: Summarizes debates, identifies primary disagreement, extracts arguments, and provides analysis of evidence and argument strength to predict outcomes.
-169. **summarize_git_changes**: Summarizes recent project updates from the last 7 days, focusing on key changes with enthusiasm.
-170. **summarize_git_diff**: Summarizes and organizes Git diff changes with clear, succinct commit messages and bullet points.
-171. **summarize_lecture**: Extracts relevant topics, definitions, and tools from lecture transcripts, providing structured summaries with timestamps and key takeaways.
-172. **summarize_legislation**: Summarizes complex political proposals and legislation by analyzing key points, proposed changes, and providing balanced, positive, and cynical characterizations.
-173. **summarize_meeting**: Analyzes meeting transcripts to extract a structured summary, including an overview, key points, tasks, decisions, challenges, timeline, references, and next steps.
-174. **summarize_micro**: Summarizes content into a 20-word sentence, 3 main points, and 3 takeaways, formatted in clear, concise Markdown.
-175. **summarize_newsletter**: Extracts the most meaningful, interesting, and useful content from a newsletter, summarizing key sections such as content, opinions, tools, companies, and follow-up items in clear, structured Markdown.
-176. **summarize_paper**: Summarizes an academic paper by detailing its title, authors, technical approach, distinctive features, experimental setup, results, advantages, limitations, and conclusion in a clear, structured format using human-readable Markdown.
-177. **summarize_prompt**: Summarizes AI chat prompts by describing the primary function, unique approach, and expected output in a concise paragraph. The summary is focused on the prompt's purpose without unnecessary details or formatting.
-178. **summarize_pull-requests**: Summarizes pull requests for a coding project by providing a summary and listing the top PRs with human-readable descriptions.
-179. **summarize_rpg_session**: Summarizes a role-playing game session by extracting key events, combat stats, character changes, quotes, and more.
-180. **t_analyse_challenge_handling**: Provides 8-16 word bullet points evaluating how well challenges are being addressed, calling out any lack of effort.
-181. **t_check_metrics**: Analyzes deep context from the TELOS file and input instruction, then provides a wisdom-based output while considering metrics and KPIs to assess recent improvements.
-182. **t_create_h3_career**: Summarizes context and produces wisdom-based output by deeply analyzing both the TELOS File and the input instruction, considering the relationship between the two.
-183. **t_create_opening_sentences**: Describes from TELOS file the person’s identity, goals, and actions in 4 concise, 32-word bullet points, humbly.
-184. **t_describe_life_outlook**: Describes from TELOS file a person's life outlook in 5 concise, 16-word bullet points.
-185. **t_extract_intro_sentences**: Summarizes from TELOS file a person's identity, work, and current projects in 5 concise and grounded bullet points.
-186. **t_extract_panel_topics**: Creates 5 panel ideas with titles and descriptions based on deep context from a TELOS file and input.
-187. **t_find_blindspots**: Identify potential blindspots in thinking, frames, or models that may expose the individual to error or risk.
-188. **t_find_negative_thinking**: Analyze a TELOS file and input to identify negative thinking in documents or journals, followed by tough love encouragement.
-189. **t_find_neglected_goals**: Analyze a TELOS file and input instructions to identify goals or projects that have not been worked on recently.
-190. **t_give_encouragement**: Analyze a TELOS file and input instructions to evaluate progress, provide encouragement, and offer recommendations for continued effort.
-191. **t_red_team_thinking**: Analyze a TELOS file and input instructions to red-team thinking, models, and frames, then provide recommendations for improvement.
-192. **t_threat_model_plans**: Analyze a TELOS file and input instructions to create threat models for a life plan and recommend improvements.
-193. **t_visualize_mission_goals_projects**: Analyze a TELOS file and input instructions to create an ASCII art diagram illustrating the relationship of missions, goals, and projects.
-194. **t_year_in_review**: Analyze a TELOS file to create insights about a person or entity, then summarize accomplishments and visualizations in bullet points.
-195. **to_flashcards**: Create Anki flashcards from a given text, focusing on concise, optimized questions and answers without external context.
-196. **transcribe_minutes**: Extracts (from meeting transcription) meeting minutes, identifying actionables, insightful ideas, decisions, challenges, and next steps in a structured format.
-197. **translate**: Translates sentences or documentation into the specified language code while maintaining the original formatting and tone.
-198. **tweet**: Provides a step-by-step guide on crafting engaging tweets with emojis, covering Twitter basics, account creation, features, and audience targeting.
-199. **write_essay**: Writes concise, clear essays in the style of Paul Graham, focusing on simplicity, clarity, and illumination of the provided topic.
-200. **write_hackerone_report**: Generates concise, clear, and reproducible bug bounty reports, detailing vulnerability impact, steps to reproduce, and exploit details for triagers.
-201. **write_latex**: Generates syntactically correct LaTeX code for a new.tex document, ensuring proper formatting and compatibility with pdflatex.
-202. **write_micro_essay**: Writes concise, clear, and illuminating essays on the given topic in the style of Paul Graham.
-203. **write_nuclei_template_rule**: Generates Nuclei YAML templates for detecting vulnerabilities using HTTP requests, matchers, extractors, and dynamic data extraction.
-204. **write_pull-request**: Drafts detailed pull request descriptions, explaining changes, providing reasoning, and identifying potential bugs from the git diff command output.
-205. **write_semgrep_rule**: Creates accurate and working Semgrep rules based on input, following syntax guidelines and specific language considerations.
-206. **youtube_summary**:  Create concise, timestamped Youtube video summaries that highlight key points.
+3. **analyze_answers**: Evaluate quiz answers for correctness based on learning objectives and generated quiz questions.
+4. **analyze_bill**: Analyzes legislation to identify overt and covert goals, examining bills for hidden agendas and true intentions.
+5. **analyze_bill_short**: Provides a concise analysis of legislation, identifying overt and covert goals in a brief, structured format.
+6. **analyze_candidates**: Compare and contrast two political candidates based on key issues and policies.
+7. **analyze_cfp_submission**: Review and evaluate conference speaking session submissions based on clarity, relevance, depth, and engagement potential.
+8. **analyze_claims**: Analyse and rate truth claims with evidence, counter-arguments, fallacies, and final recommendations.
+9. **analyze_comments**: Evaluate internet comments for content, categorize sentiment, and identify reasons for praise, criticism, and neutrality.
+10. **analyze_debate**: Rate debates on insight, emotionality, and present an unbiased, thorough analysis of arguments, agreements, and disagreements.
+11. **analyze_email_headers**: Provide cybersecurity analysis and actionable insights on SPF, DKIM, DMARC, and ARC email header results.
+12. **analyze_incident**: Efficiently extract and organize key details from cybersecurity breach articles, focusing on attack type, vulnerable components, attacker and target info, incident details, and remediation steps.
+13. **analyze_interviewer_techniques**: This exercise involves analyzing interviewer techniques, identifying their unique qualities, and succinctly articulating what makes them stand out in a clear, simple format.
+14. **analyze_logs**: Analyse server log files to identify patterns, anomalies, and issues, providing data-driven insights and recommendations for improving server reliability and performance.
+15. **analyze_malware**: Analyse malware details, extract key indicators, techniques, and potential detection strategies, and summarize findings concisely for a malware analyst's use in identifying and responding to threats.
+16. **analyze_military_strategy**: Analyse a historical battle, offering in-depth insights into strategic decisions, strengths, weaknesses, tactical approaches, logistical factors, pivotal moments, and consequences for a comprehensive military evaluation.
+17. **analyze_mistakes**: Analyse past mistakes in thinking patterns, map them to current beliefs, and offer recommendations to improve accuracy in predictions.
+18. **analyze_paper**: Analyses research papers by summarizing findings, evaluating rigor, and assessing quality to provide insights for documentation and review.
+19. **analyze_paper_simple**: Analyzes academic papers with a focus on primary findings, research quality, and study design evaluation.
+20. **analyze_patent**: Analyse a patent's field, problem, solution, novelty, inventive step, and advantages in detail while summarizing and extracting keywords.
+21. **analyze_personality**: Performs a deep psychological analysis of a person in the input, focusing on their behavior, language, and psychological traits.
+22. **analyze_presentation**: Reviews and critiques presentations by analyzing the content, speaker's underlying goals, self-focus, and entertainment value.
+23. **analyze_product_feedback**: A prompt for analyzing and organizing user feedback by identifying themes, consolidating similar comments, and prioritizing them based on usefulness.
+24. **analyze_proposition**: Analyzes a ballot proposition by identifying its purpose, impact, arguments for and against, and relevant background information.
+25. **analyze_prose**: Evaluates writing for novelty, clarity, and prose, providing ratings, improvement recommendations, and an overall score.
+26. **analyze_prose_json**: Evaluates writing for novelty, clarity, prose, and provides ratings, explanations, improvement suggestions, and an overall score in a JSON format.
+27. **analyze_prose_pinker**: Evaluates prose based on Steven Pinker's The Sense of Style, analyzing writing style, clarity, and bad writing elements.
+28. **analyze_risk**: Conducts a risk assessment of a third-party vendor, assigning a risk score and suggesting security controls based on analysis of provided documents and vendor website.
+29. **analyze_sales_call**: Rates sales call performance across multiple dimensions, providing scores and actionable feedback based on transcript analysis.
+30. **analyze_spiritual_text**: Compares and contrasts spiritual texts by analyzing claims and differences with the King James Bible.
+31. **analyze_tech_impact**: Analyzes the societal impact, ethical considerations, and sustainability of technology projects, evaluating their outcomes and benefits.
+32. **analyze_terraform_plan**: Analyzes Terraform plan outputs to assess infrastructure changes, security risks, cost implications, and compliance considerations.
+33. **analyze_threat_report**: Extracts surprising insights, trends, statistics, quotes, references, and recommendations from cybersecurity threat reports, summarizing key findings and providing actionable information.
+34. **analyze_threat_report_cmds**: Extract and synthesize actionable cybersecurity commands from provided materials, incorporating command-line arguments and expert insights for pentesters and non-experts.
+35. **analyze_threat_report_trends**: Extract up to 50 surprising, insightful, and interesting trends from a cybersecurity threat report in markdown format.
+36. **answer_interview_question**: Generates concise, tailored responses to technical interview questions, incorporating alternative approaches and evidence to demonstrate the candidate's expertise and experience.
+37. **ask_secure_by_design_questions**: Generates a set of security-focused questions to ensure a project is built securely by design, covering key components and considerations.
+38. **ask_uncle_duke**: Coordinates a team of AI agents to research and produce multiple software development solutions based on provided specifications, and conducts detailed code reviews to ensure adherence to best practices.
+39. **capture_thinkers_work**: Analyze philosophers or philosophies and provide detailed summaries about their teachings, background, works, advice, and related concepts in a structured template.
+40. **check_agreement**: Analyze contracts and agreements to identify important stipulations, issues, and potential gotchas, then summarize them in Markdown.
+41. **clean_text**: Fix broken or malformatted text by correcting line breaks, punctuation, capitalization, and paragraphs without altering content or spelling.
+42. **coding_master**: Explain a coding concept to a beginner, providing examples, and formatting code in markdown with specific output sections like ideas, recommendations, facts, and insights.
+43. **compare_and_contrast**: Compare and contrast a list of items in a markdown table, with items on the left and topics on top.
+44. **convert_to_markdown**: Convert content to clean, complete Markdown format, preserving all original structure, formatting, links, and code blocks without alterations.
+45. **create_5_sentence_summary**: Create concise summaries or answers to input at 5 different levels of depth, from 5 words to 1 word.
+46. **create_academic_paper**: Generate a high-quality academic paper in LaTeX format with clear concepts, structured content, and a professional layout.
+47. **create_ai_jobs_analysis**: Analyze job categories' susceptibility to automation, identify resilient roles, and provide strategies for personal adaptation to AI-driven changes in the workforce.
+48. **create_aphorisms**: Find and generate a list of brief, witty statements.
+49. **create_art_prompt**: Generates a detailed, compelling visual description of a concept, including stylistic references and direct AI instructions for creating art.
+50. **create_better_frame**: Identifies and analyzes different frames of interpreting reality, emphasizing the power of positive, productive lenses in shaping outcomes.
+51. **create_coding_feature**: Generates secure and composable code features using modern technology and best practices from project specifications.
+52. **create_coding_project**: Generate wireframes and starter code for any coding ideas that you have.
+53. **create_command**: Helps determine the correct parameters and switches for penetration testing tools based on a brief description of the objective.
+54. **create_cyber_summary**: Summarizes cybersecurity threats, vulnerabilities, incidents, and malware with a 25-word summary and categorized bullet points, after thoroughly analyzing and mapping the provided input.
+55. **create_design_document**: Creates a detailed design document for a system using the C4 model, addressing business and security postures, and including a system context diagram.
+56. **create_diy**: Creates structured "Do It Yourself" tutorial patterns by analyzing prompts, organizing requirements, and providing step-by-step instructions in Markdown format.
+57. **create_excalidraw_visualization**: Creates complex Excalidraw diagrams to visualize relationships between concepts and ideas in structured format.
+58. **create_flash_cards**: Creates flashcards for key concepts, definitions, and terms with question-answer format for educational purposes.
+59. **create_formal_email**: Crafts professional, clear, and respectful emails by analyzing context, tone, and purpose, ensuring proper structure and formatting.
+60. **create_git_diff_commit**: Generates Git commands and commit messages for reflecting changes in a repository, using conventional commits and providing concise shell commands for updates.
+61. **create_graph_from_input**: Generates a CSV file with progress-over-time data for a security program, focusing on relevant metrics and KPIs.
+62. **create_hormozi_offer**: Creates a customized business offer based on principles from Alex Hormozi's book, "$100M Offers."
+63. **create_idea_compass**: Organizes and structures ideas by exploring their definition, evidence, sources, and related themes or consequences.
+64. **create_investigation_visualization**: Creates detailed Graphviz visualizations of complex input, highlighting key aspects and providing clear, well-annotated diagrams for investigative analysis and conclusions.
+65. **create_keynote**: Creates TED-style keynote presentations with a clear narrative, structured slides, and speaker notes, emphasizing impactful takeaways and cohesive flow.
+66. **create_loe_document**: Creates detailed Level of Effort documents for estimating work effort, resources, and costs for tasks or projects.
+67. **create_logo**: Creates simple, minimalist company logos without text, generating AI prompts for vector graphic logos based on input.
+68. **create_markmap_visualization**: Transforms complex ideas into clear visualizations using MarkMap syntax, simplifying concepts into diagrams with relationships, boxes, arrows, and labels.
+69. **create_mermaid_visualization**: Creates detailed, standalone visualizations of concepts using Mermaid (Markdown) syntax, ensuring clarity and coherence in diagrams.
+70. **create_mermaid_visualization_for_github**: Creates standalone, detailed visualizations using Mermaid (Markdown) syntax to effectively explain complex concepts, ensuring clarity and precision.
+71. **create_micro_summary**: Summarizes content into a concise, 20-word summary with main points and takeaways, formatted in Markdown.
+72. **create_mnemonic_phrases**: Creates memorable mnemonic sentences from given words to aid in memory retention and learning.
+73. **create_network_threat_landscape**: Analyzes open ports and services from a network scan and generates a comprehensive, insightful, and detailed security threat report in Markdown.
+74. **create_newsletter_entry**: Condenses provided article text into a concise, objective, newsletter-style summary with a title in the style of Frontend Weekly.
+75. **create_npc**: Generates a detailed D&D 5E NPC, including background, flaws, stats, appearance, personality, goals, and more in Markdown format.
+76. **create_pattern**: Extracts, organizes, and formats LLM/AI prompts into structured sections, detailing the AI's role, instructions, output format, and any provided examples for clarity and accuracy.
+77. **create_prd**: Creates a precise Product Requirements Document (PRD) in Markdown based on input.
+78. **create_prediction_block**: Extracts and formats predictions from input into a structured Markdown block for a blog post.
+79. **create_quiz**: Creates a three-phase reading plan based on an author or topic to help the user become significantly knowledgeable, including core, extended, and supplementary readings.
+80. **create_reading_plan**: Generates review questions based on learning objectives from the input, adapted to the specified student level, and outputs them in a clear markdown format.
+81. **create_recursive_outline**: Breaks down complex tasks or projects into manageable, hierarchical components with recursive outlining for clarity and simplicity.
+82. **create_report_finding**: Creates a detailed, structured security finding report in markdown, including sections on Description, Risk, Recommendations, References, One-Sentence-Summary, and Quotes.
+83. **create_rpg_summary**: Summarizes an in-person RPG session with key events, combat details, player stats, and role-playing highlights in a structured format.
+84. **create_security_update**: Creates concise security updates for newsletters, covering stories, threats, advisories, vulnerabilities, and a summary of key issues.
+85. **create_show_intro**: Creates compelling short intros for podcasts, summarizing key topics and themes discussed in the episode.
+86. **create_sigma_rules**: Extracts Tactics, Techniques, and Procedures (TTPs) from security news and converts them into Sigma detection rules for host-based detections.
+87. **create_story_explanation**: Summarizes complex content in a clear, approachable story format that makes the concepts easy to understand.
+88. **create_stride_threat_model**: Create a STRIDE-based threat model for a system design, identifying assets, trust boundaries, data flows, and prioritizing threats with mitigations.
+89. **create_summary**: Summarizes content into a 20-word sentence, 10 main points (16 words max), and 5 key takeaways in Markdown format.
+90. **create_tags**: Identifies at least 5 tags from text content for mind mapping tools, including authors and existing tags if present.
+91. **create_threat_scenarios**: Identifies likely attack methods for any system by providing a narrative-based threat model, balancing risk and opportunity.
+92. **create_ttrc_graph**: Creates a CSV file showing the progress of Time to Remediate Critical Vulnerabilities over time using given data.
+93. **create_ttrc_narrative**: Creates a persuasive narrative highlighting progress in reducing the Time to Remediate Critical Vulnerabilities metric over time.
+94. **create_upgrade_pack**: Extracts world model and task algorithm updates from content, providing beliefs about how the world works and task performance.
+95. **create_user_story**: Writes concise and clear technical user stories for new features in complex software programs, formatted for all stakeholders.
+96. **create_video_chapters**: Extracts interesting topics and timestamps from a transcript, providing concise summaries of key moments.
+97. **create_visualization**: Transforms complex ideas into visualizations using intricate ASCII art, simplifying concepts where necessary.
+98. **dialog_with_socrates**: Engages in deep, meaningful dialogues to explore and challenge beliefs using the Socratic method.
+99. **enrich_blog_post**: Enhances Markdown blog files by applying instructions to improve structure, visuals, and readability for HTML rendering.
+100. **explain_code**: Explains code, security tool output, configuration text, and answers questions based on the provided input.
+101. **explain_docs**: Improves and restructures tool documentation into clear, concise instructions, including overviews, usage, use cases, and key features.
+102. **explain_math**: Helps you understand mathematical concepts in a clear and engaging way.
+103. **explain_project**: Summarizes project documentation into clear, concise sections covering the project, problem, solution, installation, usage, and examples.
+104. **explain_terms**: Produces a glossary of advanced terms from content, providing a definition, analogy, and explanation of why each term matters.
+105. **export_data_as_csv**: Extracts and outputs all data structures from the input in properly formatted CSV data.
+106. **extract_algorithm_update_recommendations**: Extracts concise, practical algorithm update recommendations from the input and outputs them in a bulleted list.
+107. **extract_article_wisdom**: Extracts surprising, insightful, and interesting information from content, categorizing it into sections like summary, ideas, quotes, facts, references, and recommendations.
+108. **extract_book_ideas**: Extracts and outputs 50 to 100 of the most surprising, insightful, and interesting ideas from a book's content.
+109. **extract_book_recommendations**: Extracts and outputs 50 to 100 practical, actionable recommendations from a book's content.
+110. **extract_business_ideas**: Extracts top business ideas from content and elaborates on the best 10 with unique differentiators.
+111. **extract_controversial_ideas**: Extracts and outputs controversial statements and supporting quotes from the input in a structured Markdown list.
+112. **extract_core_message**: Extracts and outputs a clear, concise sentence that articulates the core message of a given text or body of work.
+113. **extract_ctf_writeup**: Extracts a short writeup from a warstory-like text about a cyber security engagement.
+114. **extract_domains**: Extracts domains and URLs from content to identify sources used for articles, newsletters, and other publications.
+115. **extract_extraordinary_claims**: Extracts and outputs a list of extraordinary claims from conversations, focusing on scientifically disputed or false statements.
+116. **extract_ideas**: Extracts and outputs all the key ideas from input, presented as 15-word bullet points in Markdown.
+117. **extract_insights**: Extracts and outputs the most powerful and insightful ideas from text, formatted as 16-word bullet points in the INSIGHTS section, also IDEAS section.
+118. **extract_insights_dm**: Extracts and outputs all valuable insights and a concise summary of the content, including key points and topics discussed.
+119. **extract_instructions**: Extracts clear, actionable step-by-step instructions and main objectives from instructional video transcripts, organizing them into a concise list.
+120. **extract_jokes**: Extracts jokes from text content, presenting each joke with its punchline in separate bullet points.
+121. **extract_latest_video**: Extracts the latest video URL from a YouTube RSS feed and outputs the URL only.
+122. **extract_main_activities**: Extracts key events and activities from transcripts or logs, providing a summary of what happened.
+123. **extract_main_idea**: Extracts the main idea and key recommendation from the input, summarizing them in 15-word sentences.
+124. **extract_most_redeeming_thing**: Extracts the most redeeming aspect from an input, summarizing it in a single 15-word sentence.
+125. **extract_patterns**: Extracts and analyzes recurring, surprising, and insightful patterns from input, providing detailed analysis and advice for builders.
+126. **extract_poc**: Extracts proof of concept URLs and validation methods from security reports, providing the URL and command to run.
+127. **extract_predictions**: Extracts predictions from input, including specific details such as date, confidence level, and verification method.
+128. **extract_primary_problem**: Extracts the primary problem with the world as presented in a given text or body of work.
+129. **extract_primary_solution**: Extracts the primary solution for the world as presented in a given text or body of work.
+130. **extract_product_features**: Extracts and outputs a list of product features from the provided input in a bulleted format.
+131. **extract_questions**: Extracts and outputs all questions asked by the interviewer in a conversation or interview.
+132. **extract_recipe**: Extracts and outputs a recipe with a short meal description, ingredients with measurements, and preparation steps.
+133. **extract_recommendations**: Extracts and outputs concise, practical recommendations from a given piece of content in a bulleted list.
+134. **extract_references**: Extracts and outputs a bulleted list of references to art, stories, books, literature, and other sources from content.
+135. **extract_skills**: Extracts and classifies skills from a job description into a table, separating each skill and classifying it as either hard or soft.
+136. **extract_song_meaning**: Analyzes a song to provide a summary of its meaning, supported by detailed evidence from lyrics, artist commentary, and fan analysis.
+137. **extract_sponsors**: Extracts and lists official sponsors and potential sponsors from a provided transcript.
+138. **extract_videoid**: Extracts and outputs the video ID from any given URL.
+139. **extract_wisdom**: Extracts surprising, insightful, and interesting information from text on topics like human flourishing, AI, learning, and more.
+140. **extract_wisdom_agents**: Extracts valuable insights, ideas, quotes, and references from content, emphasizing topics like human flourishing, AI, learning, and technology.
+141. **extract_wisdom_dm**: Extracts all valuable, insightful, and thought-provoking information from content, focusing on topics like human flourishing, AI, learning, and technology.
+142. **extract_wisdom_nometa**: Extracts insights, ideas, quotes, habits, facts, references, and recommendations from content, focusing on human flourishing, AI, technology, and related topics.
+143. **find_female_life_partner**: Analyzes criteria for finding a female life partner and provides clear, direct, and poetic descriptions.
+144. **find_hidden_message**: Extracts overt and hidden political messages, justifications, audience actions, and a cynical analysis from content.
+145. **find_logical_fallacies**: Identifies and analyzes fallacies in arguments, classifying them as formal or informal with detailed reasoning.
+146. **get_wow_per_minute**: Determines the wow-factor of content per minute based on surprise, novelty, insight, value, and wisdom, measuring how rewarding the content is for the viewer.
+147. **get_youtube_rss**: Returns the RSS URL for a given YouTube channel based on the channel ID or URL.
+148. **humanize**: Rewrites AI-generated text to sound natural, conversational, and easy to understand, maintaining clarity and simplicity.
+149. **identify_dsrp_distinctions**: Encourages creative, systems-based thinking by exploring distinctions, boundaries, and their implications, drawing on insights from prominent systems thinkers.
+150. **identify_dsrp_perspectives**: Explores the concept of distinctions in systems thinking, focusing on how boundaries define ideas, influence understanding, and reveal or obscure insights.
+151. **identify_dsrp_relationships**: Encourages exploration of connections, distinctions, and boundaries between ideas, inspired by systems thinkers to reveal new insights and patterns in complex systems.
+152. **identify_dsrp_systems**: Encourages organizing ideas into systems of parts and wholes, inspired by systems thinkers to explore relationships and how changes in organization impact meaning and understanding.
+153. **identify_job_stories**: Identifies key job stories or requirements for roles.
+154. **improve_academic_writing**: Refines text into clear, concise academic language while improving grammar, coherence, and clarity, with a list of changes.
+155. **improve_prompt**: Improves an LLM/AI prompt by applying expert prompt writing strategies for better results and clarity.
+156. **improve_report_finding**: Improves a penetration test security finding by providing detailed descriptions, risks, recommendations, references, quotes, and a concise summary in markdown format.
+157. **improve_writing**: Refines text by correcting grammar, enhancing style, improving clarity, and maintaining the original meaning. skills.
+158. **judge_output**: Evaluates Honeycomb queries by judging their effectiveness, providing critiques and outcomes based on language nuances and analytics relevance.
+159. **label_and_rate**: Labels content with up to 20 single-word tags and rates it based on idea count and relevance to human meaning, AI, and other related themes, assigning a tier (S, A, B, C, D) and a quality score.
+160. **md_callout**: Classifies content and generates a markdown callout based on the provided text, selecting the most appropriate type.
+161. **official_pattern_template**: Template to use if you want to create new fabric patterns.
+162. **prepare_7s_strategy**: Prepares a comprehensive briefing document from 7S's strategy capturing organizational profile, strategic elements, and market dynamics with clear, concise, and organized content.
+163. **provide_guidance**: Provides psychological and life coaching advice, including analysis, recommendations, and potential diagnoses, with a compassionate and honest tone.
+164. **rate_ai_response**: Rates the quality of AI responses by comparing them to top human expert performance, assigning a letter grade, reasoning, and providing a 1-100 score based on the evaluation.
+165. **rate_ai_result**: Assesses the quality of AI/ML/LLM work by deeply analyzing content, instructions, and output, then rates performance based on multiple dimensions, including coverage, creativity, and interdisciplinary thinking.
+166. **rate_content**: Labels content with up to 20 single-word tags and rates it based on idea count and relevance to human meaning, AI, and other related themes, assigning a tier (S, A, B, C, D) and a quality score.
+167. **rate_value**: Produces the best possible output by deeply analyzing and understanding the input and its intended purpose.
+168. **raw_query**: Fully digests and contemplates the input to produce the best possible result based on understanding the sender's intent.
+169. **recommend_artists**: Recommends a personalized festival schedule with artists aligned to your favorite styles and interests, including rationale.
+170. **recommend_pipeline_upgrades**: Optimizes vulnerability-checking pipelines by incorporating new information and improving their efficiency, with detailed explanations of changes.
+171. **recommend_talkpanel_topics**: Produces a clean set of proposed talks or panel talking points for a person based on their interests and goals, formatted for submission to a conference organizer.
+172. **refine_design_document**: Refines a design document based on a design review by analyzing, mapping concepts, and implementing changes using valid Markdown.
+173. **review_design**: Reviews and analyzes architecture design, focusing on clarity, component design, system integrations, security, performance, scalability, and data management.
+174. **sanitize_broken_html_to_markdown**: Converts messy HTML into clean, properly formatted Markdown, applying custom styling and ensuring compatibility with Vite.
+175. **show_fabric_options_markmap**: Visualizes the functionality of the Fabric framework by representing its components, commands, and features based on the provided input.
+176. **solve_with_cot**: Provides detailed, step-by-step responses with chain of thought reasoning, using structured thinking, reflection, and output sections.
+177. **suggest_pattern**: Suggests appropriate fabric patterns or commands based on user input, providing clear explanations and options for users.
+178. **summarize**: Summarizes content into a 20-word sentence, main points, and takeaways, formatted with numbered lists in Markdown.
+179. **summarize_board_meeting**: Creates formal meeting notes from board meeting transcripts for corporate governance documentation.
+180. **summarize_debate**: Summarizes debates, identifies primary disagreement, extracts arguments, and provides analysis of evidence and argument strength to predict outcomes.
+181. **summarize_git_changes**: Summarizes recent project updates from the last 7 days, focusing on key changes with enthusiasm.
+182. **summarize_git_diff**: Summarizes and organizes Git diff changes with clear, succinct commit messages and bullet points.
+183. **summarize_lecture**: Extracts relevant topics, definitions, and tools from lecture transcripts, providing structured summaries with timestamps and key takeaways.
+184. **summarize_legislation**: Summarizes complex political proposals and legislation by analyzing key points, proposed changes, and providing balanced, positive, and cynical characterizations.
+185. **summarize_meeting**: Analyzes meeting transcripts to extract a structured summary, including an overview, key points, tasks, decisions, challenges, timeline, references, and next steps.
+186. **summarize_micro**: Summarizes content into a 20-word sentence, 3 main points, and 3 takeaways, formatted in clear, concise Markdown.
+187. **summarize_newsletter**: Extracts the most meaningful, interesting, and useful content from a newsletter, summarizing key sections such as content, opinions, tools, companies, and follow-up items in clear, structured Markdown.
+188. **summarize_paper**: Summarizes an academic paper by detailing its title, authors, technical approach, distinctive features, experimental setup, results, advantages, limitations, and conclusion in a clear, structured format using human-readable Markdown.
+189. **summarize_prompt**: Summarizes AI chat prompts by describing the primary function, unique approach, and expected output in a concise paragraph. The summary is focused on the prompt's purpose without unnecessary details or formatting.
+190. **summarize_pull-requests**: Summarizes pull requests for a coding project by providing a summary and listing the top PRs with human-readable descriptions.
+191. **summarize_rpg_session**: Summarizes a role-playing game session by extracting key events, combat stats, character changes, quotes, and more.
+192. **t_analyze_challenge_handling**: Provides 8-16 word bullet points evaluating how well challenges are being addressed, calling out any lack of effort.
+193. **t_check_metrics**: Analyzes deep context from the TELOS file and input instruction, then provides a wisdom-based output while considering metrics and KPIs to assess recent improvements.
+194. **t_create_h3_career**: Summarizes context and produces wisdom-based output by deeply analyzing both the TELOS File and the input instruction, considering the relationship between the two.
+195. **t_create_opening_sentences**: Describes from TELOS file the person's identity, goals, and actions in 4 concise, 32-word bullet points, humbly.
+196. **t_describe_life_outlook**: Describes from TELOS file a person's life outlook in 5 concise, 16-word bullet points.
+197. **t_extract_intro_sentences**: Summarizes from TELOS file a person's identity, work, and current projects in 5 concise and grounded bullet points.
+198. **t_extract_panel_topics**: Creates 5 panel ideas with titles and descriptions based on deep context from a TELOS file and input.
+199. **t_find_blindspots**: Identify potential blindspots in thinking, frames, or models that may expose the individual to error or risk.
+200. **t_find_negative_thinking**: Analyze a TELOS file and input to identify negative thinking in documents or journals, followed by tough love encouragement.
+201. **t_find_neglected_goals**: Analyze a TELOS file and input instructions to identify goals or projects that have not been worked on recently.
+202. **t_give_encouragement**: Analyze a TELOS file and input instructions to evaluate progress, provide encouragement, and offer recommendations for continued effort.
+203. **t_red_team_thinking**: Analyze a TELOS file and input instructions to red-team thinking, models, and frames, then provide recommendations for improvement.
+204. **t_threat_model_plans**: Analyze a TELOS file and input instructions to create threat models for a life plan and recommend improvements.
+205. **t_visualize_mission_goals_projects**: Analyze a TELOS file and input instructions to create an ASCII art diagram illustrating the relationship of missions, goals, and projects.
+206. **t_year_in_review**: Analyze a TELOS file to create insights about a person or entity, then summarize accomplishments and visualizations in bullet points.
+207. **to_flashcards**: Create Anki flashcards from a given text, focusing on concise, optimized questions and answers without external context.
+208. **transcribe_minutes**: Extracts (from meeting transcription) meeting minutes, identifying actionables, insightful ideas, decisions, challenges, and next steps in a structured format.
+209. **translate**: Translates sentences or documentation into the specified language code while maintaining the original formatting and tone.
+210. **tweet**: Provides a step-by-step guide on crafting engaging tweets with emojis, covering Twitter basics, account creation, features, and audience targeting.
+211. **write_essay**: Writes essays in the style of a specified author, embodying their unique voice, vocabulary, and approach. Uses `author_name` variable.
+212. **write_essay_pg**: Writes concise, clear essays in the style of Paul Graham, focusing on simplicity, clarity, and illumination of the provided topic.
+213. **write_hackerone_report**: Generates concise, clear, and reproducible bug bounty reports, detailing vulnerability impact, steps to reproduce, and exploit details for triagers.
+214. **write_latex**: Generates syntactically correct LaTeX code for a new.tex document, ensuring proper formatting and compatibility with pdflatex.
+215. **write_micro_essay**: Writes concise, clear, and illuminating essays on the given topic in the style of Paul Graham.
+216. **write_nuclei_template_rule**: Generates Nuclei YAML templates for detecting vulnerabilities using HTTP requests, matchers, extractors, and dynamic data extraction.
+217. **write_pull-request**: Drafts detailed pull request descriptions, explaining changes, providing reasoning, and identifying potential bugs from the git diff command output.
+218. **write_semgrep_rule**: Creates accurate and working Semgrep rules based on input, following syntax guidelines and specific language considerations.
+219. **youtube_summary**: Create concise, timestamped Youtube video summaries that highlight key points.

patterns/raycast/capture_thinkers_work

@@ -1,27 +0,0 @@
-#!/bin/bash
-
-# Required parameters:
-# @raycast.schemaVersion 1
-# @raycast.title Capture Thinkers Work
-# @raycast.mode fullOutput
-
-# Optional parameters:
-# @raycast.icon 🧠
-# @raycast.argument1 { "type": "text", "placeholder": "Input text", "optional": false, "percentEncoded": true}
-
-# Documentation:
-# @raycast.description Run fabric capture_thinkers_work on the input text
-# @raycast.author Daniel Miessler
-# @raycast.authorURL https://github.com/danielmiessler
-
-# Set PATH to include common locations and $HOME/go/bin
-PATH="/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:$HOME/go/bin:$PATH"
-
-# Use the PATH to find and execute fabric
-if command -v fabric >/dev/null 2>&1; then
-    fabric -sp capture_thinkers_work "${1}"
-else
-    echo "Error: fabric command not found in PATH"
-    echo "Current PATH: $PATH"
-    exit 1
-fi

patterns/raycast/create_story_explanation

@@ -1,27 +0,0 @@
-#!/bin/bash
-
-# Required parameters:
-# @raycast.schemaVersion 1
-# @raycast.title Create Story Explanation
-# @raycast.mode fullOutput
-
-# Optional parameters:
-# @raycast.icon 🧠
-# @raycast.argument1 { "type": "text", "placeholder": "Input text", "optional": false, "percentEncoded": true}
-
-# Documentation:
-# @raycast.description Run fabric create_story_explanation on the input text
-# @raycast.author Daniel Miessler
-# @raycast.authorURL https://github.com/danielmiessler
-
-# Set PATH to include common locations and $HOME/go/bin
-PATH="/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:$HOME/go/bin:$PATH"
-
-# Use the PATH to find and execute fabric
-if command -v fabric >/dev/null 2>&1; then
-    fabric -sp create_story_explanation "${1}"
-else
-    echo "Error: fabric command not found in PATH"
-    echo "Current PATH: $PATH"
-    exit 1
-fi

patterns/raycast/extract_primary_problem

@@ -1,27 +0,0 @@
-#!/bin/bash
-
-# Required parameters:
-# @raycast.schemaVersion 1
-# @raycast.title Extract Primary Problem
-# @raycast.mode fullOutput
-
-# Optional parameters:
-# @raycast.icon 🧠
-# @raycast.argument1 { "type": "text", "placeholder": "Input text", "optional": false, "percentEncoded": true}
-
-# Documentation:
-# @raycast.description Run fabric extract_primary_problem on the input text
-# @raycast.author Daniel Miessler
-# @raycast.authorURL https://github.com/danielmiessler
-
-# Set PATH to include common locations and $HOME/go/bin
-PATH="/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:$HOME/go/bin:$PATH"
-
-# Use the PATH to find and execute fabric
-if command -v fabric >/dev/null 2>&1; then
-    fabric -sp extract_primary_problem "${1}"
-else
-    echo "Error: fabric command not found in PATH"
-    echo "Current PATH: $PATH"
-    exit 1
-fi

patterns/raycast/extract_wisdom

@@ -1,27 +0,0 @@
-#!/bin/bash
-
-# Required parameters:
-# @raycast.schemaVersion 1
-# @raycast.title Extract Wisdom
-# @raycast.mode fullOutput
-
-# Optional parameters:
-# @raycast.icon 🧠
-# @raycast.argument1 { "type": "text", "placeholder": "Input text", "optional": false, "percentEncoded": true}
-
-# Documentation:
-# @raycast.description Run fabric extract_wisdom on input text
-# @raycast.author Daniel Miessler
-# @raycast.authorURL https://github.com/danielmiessler
-
-# Set PATH to include common locations and $HOME/go/bin
-PATH="/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:$HOME/go/bin:$PATH"
-
-# Use the PATH to find and execute fabric
-if command -v fabric >/dev/null 2>&1; then
-    fabric -sp extract_wisdom "${1}"
-else
-    echo "Error: fabric command not found in PATH"
-    echo "Current PATH: $PATH"
-    exit 1
-fi

patterns/raycast/yt

@@ -1,27 +0,0 @@
-#!/bin/bash
-
-# Required parameters:
-# @raycast.schemaVersion 1
-# @raycast.title Get YouTube Transcript
-# @raycast.mode fullOutput
-
-# Optional parameters:
-# @raycast.icon 🧠
-# @raycast.argument1 { "type": "text", "placeholder": "Input text", "optional": false, "percentEncoded": false}
-
-# Documentation:
-# @raycast.description Run fabric -y on the input text of a YouTube video to get the transcript from.
-# @raycast.author Daniel Miessler
-# @raycast.authorURL https://github.com/danielmiessler
-
-# Set PATH to include common locations and $HOME/go/bin
-PATH="/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:$HOME/go/bin:$PATH"
-
-# Use the PATH to find and execute fabric
-if command -v fabric >/dev/null 2>&1; then
-    fabric -y "${1}"
-else
-    echo "Error: fabric command not found in PATH"
-    echo "Current PATH: $PATH"
-    exit 1
-fi

patterns/suggest_pattern/user_updated.md

@@ -0,0 +1,919 @@
+# Suggest Pattern
+
+## OVERVIEW
+
+What It Does: Fabric is an open-source framework designed to augment human capabilities using AI, making it easier to integrate AI into daily tasks.
+
+Why People Use It: Users leverage Fabric to seamlessly apply AI for solving everyday challenges, enhancing productivity, and fostering human creativity through technology.
+
+## HOW TO USE IT
+
+Most Common Syntax: The most common usage involves executing Fabric commands in the terminal, such as `fabric --pattern <PATTERN_NAME>`.
+
+## COMMON USE CASES
+
+For Summarizing Content: `fabric --pattern summarize`
+For Analyzing Claims: `fabric --pattern analyze_claims`
+For Extracting Wisdom from Videos: `fabric --pattern extract_wisdom`
+For creating custom patterns: `fabric --pattern create_pattern`
+
+- One possible place to store them is ~/.config/custom-fabric-patterns.
+- Then when you want to use them, simply copy them into ~/.config/fabric/patterns.
+`cp -a ~/.config/custom-fabric-patterns/* ~/.config/fabric/patterns/`
+- Now you can run them with: `pbpaste | fabric -p your_custom_pattern`
+
+## MOST IMPORTANT AND USED OPTIONS AND FEATURES
+
+- **--pattern PATTERN, -p PATTERN**: Specifies the pattern (prompt) to use. Useful for applying specific AI prompts to your input.
+
+- **--stream, -s**: Streams results in real-time. Ideal for getting immediate feedback from AI operations.
+
+- **--update, -u**: Updates patterns. Ensures you're using the latest AI prompts for your tasks.
+
+- **--model MODEL, -m MODEL**: Selects the AI model to use. Allows customization of the AI backend for different tasks.
+
+- **--setup, -S**: Sets up your Fabric instance. Essential for first-time users to configure Fabric correctly.
+
+- **--list, -l**: Lists available patterns. Helps users discover new AI prompts for various applications.
+
+- **--context, -C**: Uses a Context file to add context to your pattern. Enhances the relevance of AI responses by providing additional background information.
+
+## PATTERNS
+
+**Key pattern to use: `suggest_pattern`** - suggests appropriate fabric patterns or commands based on user input.
+
+### agility_story
+
+Generate a user story and acceptance criteria in JSON format based on the given topic.
+
+### ai
+
+Interpret questions deeply and provide concise, insightful answers in Markdown bullet points.
+
+### analyze_answers
+
+Evaluate quiz answers for correctness based on learning objectives and generated quiz questions.
+
+### analyze_bill
+
+Analyzes legislation to identify overt and covert goals, examining bills for hidden agendas and true intentions.
+
+### analyze_bill_short
+
+Provides a concise analysis of legislation, identifying overt and covert goals in a brief, structured format.
+
+### analyze_candidates
+
+Compare and contrast two political candidates based on key issues and policies.
+
+### analyze_cfp_submission
+
+Review and evaluate conference speaking session submissions based on clarity, relevance, depth, and engagement potential.
+
+### analyze_claims
+
+Analyse and rate truth claims with evidence, counter-arguments, fallacies, and final recommendations.
+
+### analyze_comments
+
+Evaluate internet comments for content, categorize sentiment, and identify reasons for praise, criticism, and neutrality.
+
+### analyze_debate
+
+Rate debates on insight, emotionality, and present an unbiased, thorough analysis of arguments, agreements, and disagreements.
+
+### analyze_email_headers
+
+Provide cybersecurity analysis and actionable insights on SPF, DKIM, DMARC, and ARC email header results.
+
+### analyze_incident
+
+Efficiently extract and organize key details from cybersecurity breach articles, focusing on attack type, vulnerable components, attacker and target info, incident details, and remediation steps.
+
+### analyze_interviewer_techniques
+
+This exercise involves analyzing interviewer techniques, identifying their unique qualities, and succinctly articulating what makes them stand out in a clear, simple format.
+
+### analyze_logs
+
+Analyse server log files to identify patterns, anomalies, and issues, providing data-driven insights and recommendations for improving server reliability and performance.
+
+### analyze_malware
+
+Analyse malware details, extract key indicators, techniques, and potential detection strategies, and summarize findings concisely for a malware analyst's use in identifying and responding to threats.
+
+### analyze_military_strategy
+
+Analyse a historical battle, offering in-depth insights into strategic decisions, strengths, weaknesses, tactical approaches, logistical factors, pivotal moments, and consequences for a comprehensive military evaluation.
+
+### analyze_mistakes
+
+Analyse past mistakes in thinking patterns, map them to current beliefs, and offer recommendations to improve accuracy in predictions.
+
+### analyze_paper
+
+Analyses research papers by summarizing findings, evaluating rigor, and assessing quality to provide insights for documentation and review.
+
+### analyze_paper_simple
+
+Analyzes academic papers with a focus on primary findings, research quality, and study design evaluation.
+
+### analyze_patent
+
+Analyse a patent's field, problem, solution, novelty, inventive step, and advantages in detail while summarizing and extracting keywords.
+
+### analyze_personality
+
+Performs a deep psychological analysis of a person in the input, focusing on their behavior, language, and psychological traits.
+
+### analyze_presentation
+
+Reviews and critiques presentations by analyzing the content, speaker's underlying goals, self-focus, and entertainment value.
+
+### analyze_product_feedback
+
+A prompt for analyzing and organizing user feedback by identifying themes, consolidating similar comments, and prioritizing them based on usefulness.
+
+### analyze_proposition
+
+Analyzes a ballot proposition by identifying its purpose, impact, arguments for and against, and relevant background information.
+
+### analyze_prose
+
+Evaluates writing for novelty, clarity, and prose, providing ratings, improvement recommendations, and an overall score.
+
+### analyze_prose_json
+
+Evaluates writing for novelty, clarity, prose, and provides ratings, explanations, improvement suggestions, and an overall score in a JSON format.
+
+### analyze_prose_pinker
+
+Evaluates prose based on Steven Pinker's The Sense of Style, analyzing writing style, clarity, and bad writing elements.
+
+### analyze_risk
+
+Conducts a risk assessment of a third-party vendor, assigning a risk score and suggesting security controls based on analysis of provided documents and vendor website.
+
+### analyze_sales_call
+
+Rates sales call performance across multiple dimensions, providing scores and actionable feedback based on transcript analysis.
+
+### analyze_spiritual_text
+
+Compares and contrasts spiritual texts by analyzing claims and differences with the King James Bible.
+
+### analyze_tech_impact
+
+Analyzes the societal impact, ethical considerations, and sustainability of technology projects, evaluating their outcomes and benefits.
+
+### analyze_terraform_plan
+
+Analyzes Terraform plan outputs to assess infrastructure changes, security risks, cost implications, and compliance considerations.
+
+### analyze_threat_report
+
+Extracts surprising insights, trends, statistics, quotes, references, and recommendations from cybersecurity threat reports, summarizing key findings and providing actionable information.
+
+### analyze_threat_report_cmds
+
+Extract and synthesize actionable cybersecurity commands from provided materials, incorporating command-line arguments and expert insights for pentesters and non-experts.
+
+### analyze_threat_report_trends
+
+Extract up to 50 surprising, insightful, and interesting trends from a cybersecurity threat report in markdown format.
+
+### answer_interview_question
+
+Generates concise, tailored responses to technical interview questions, incorporating alternative approaches and evidence to demonstrate the candidate's expertise and experience.
+
+### ask_secure_by_design_questions
+
+Generates a set of security-focused questions to ensure a project is built securely by design, covering key components and considerations.
+
+### ask_uncle_duke
+
+Coordinates a team of AI agents to research and produce multiple software development solutions based on provided specifications, and conducts detailed code reviews to ensure adherence to best practices.
+
+### capture_thinkers_work
+
+Analyze philosophers or philosophies and provide detailed summaries about their teachings, background, works, advice, and related concepts in a structured template.
+
+### check_agreement
+
+Analyze contracts and agreements to identify important stipulations, issues, and potential gotchas, then summarize them in Markdown.
+
+### clean_text
+
+Fix broken or malformatted text by correcting line breaks, punctuation, capitalization, and paragraphs without altering content or spelling.
+
+### coding_master
+
+Explain a coding concept to a beginner, providing examples, and formatting code in markdown with specific output sections like ideas, recommendations, facts, and insights.
+
+### compare_and_contrast
+
+Compare and contrast a list of items in a markdown table, with items on the left and topics on top.
+
+### convert_to_markdown
+
+Convert content to clean, complete Markdown format, preserving all original structure, formatting, links, and code blocks without alterations.
+
+### create_5_sentence_summary
+
+Create concise summaries or answers to input at 5 different levels of depth, from 5 words to 1 word.
+
+### create_academic_paper
+
+Generate a high-quality academic paper in LaTeX format with clear concepts, structured content, and a professional layout.
+
+### create_ai_jobs_analysis
+
+Analyze job categories' susceptibility to automation, identify resilient roles, and provide strategies for personal adaptation to AI-driven changes in the workforce.
+
+### create_aphorisms
+
+Find and generate a list of brief, witty statements.
+
+### create_art_prompt
+
+Generates a detailed, compelling visual description of a concept, including stylistic references and direct AI instructions for creating art.
+
+### create_better_frame
+
+Identifies and analyzes different frames of interpreting reality, emphasizing the power of positive, productive lenses in shaping outcomes.
+
+### create_coding_feature
+
+Generates secure and composable code features using modern technology and best practices from project specifications.
+
+### create_coding_project
+
+Generate wireframes and starter code for any coding ideas that you have.
+
+### create_command
+
+Helps determine the correct parameters and switches for penetration testing tools based on a brief description of the objective.
+
+### create_cyber_summary
+
+Summarizes cybersecurity threats, vulnerabilities, incidents, and malware with a 25-word summary and categorized bullet points, after thoroughly analyzing and mapping the provided input.
+
+### create_design_document
+
+Creates a detailed design document for a system using the C4 model, addressing business and security postures, and including a system context diagram.
+
+### create_diy
+
+Creates structured "Do It Yourself" tutorial patterns by analyzing prompts, organizing requirements, and providing step-by-step instructions in Markdown format.
+
+### create_excalidraw_visualization
+
+Creates complex Excalidraw diagrams to visualize relationships between concepts and ideas in structured format.
+
+### create_flash_cards
+
+Creates flashcards for key concepts, definitions, and terms with question-answer format for educational purposes.
+
+### create_formal_email
+
+Crafts professional, clear, and respectful emails by analyzing context, tone, and purpose, ensuring proper structure and formatting.
+
+### create_git_diff_commit
+
+Generates Git commands and commit messages for reflecting changes in a repository, using conventional commits and providing concise shell commands for updates.
+
+### create_graph_from_input
+
+Generates a CSV file with progress-over-time data for a security program, focusing on relevant metrics and KPIs.
+
+### create_hormozi_offer
+
+Creates a customized business offer based on principles from Alex Hormozi's book, "$100M Offers."
+
+### create_idea_compass
+
+Organizes and structures ideas by exploring their definition, evidence, sources, and related themes or consequences.
+
+### create_investigation_visualization
+
+Creates detailed Graphviz visualizations of complex input, highlighting key aspects and providing clear, well-annotated diagrams for investigative analysis and conclusions.
+
+### create_keynote
+
+Creates TED-style keynote presentations with a clear narrative, structured slides, and speaker notes, emphasizing impactful takeaways and cohesive flow.
+
+### create_loe_document
+
+Creates detailed Level of Effort documents for estimating work effort, resources, and costs for tasks or projects.
+
+### create_logo
+
+Creates simple, minimalist company logos without text, generating AI prompts for vector graphic logos based on input.
+
+### create_markmap_visualization
+
+Transforms complex ideas into clear visualizations using MarkMap syntax, simplifying concepts into diagrams with relationships, boxes, arrows, and labels.
+
+### create_mermaid_visualization
+
+Creates detailed, standalone visualizations of concepts using Mermaid (Markdown) syntax, ensuring clarity and coherence in diagrams.
+
+### create_mermaid_visualization_for_github
+
+Creates standalone, detailed visualizations using Mermaid (Markdown) syntax to effectively explain complex concepts, ensuring clarity and precision.
+
+### create_micro_summary
+
+Summarizes content into a concise, 20-word summary with main points and takeaways, formatted in Markdown.
+
+### create_mnemonic_phrases
+
+Creates memorable mnemonic sentences from given words to aid in memory retention and learning.
+
+### create_network_threat_landscape
+
+Analyzes open ports and services from a network scan and generates a comprehensive, insightful, and detailed security threat report in Markdown.
+
+### create_newsletter_entry
+
+Condenses provided article text into a concise, objective, newsletter-style summary with a title in the style of Frontend Weekly.
+
+### create_npc
+
+Generates a detailed D&D 5E NPC, including background, flaws, stats, appearance, personality, goals, and more in Markdown format.
+
+### create_pattern
+
+Extracts, organizes, and formats LLM/AI prompts into structured sections, detailing the AI's role, instructions, output format, and any provided examples for clarity and accuracy.
+
+### create_prd
+
+Creates a precise Product Requirements Document (PRD) in Markdown based on input.
+
+### create_prediction_block
+
+Extracts and formats predictions from input into a structured Markdown block for a blog post.
+
+### create_quiz
+
+Generates review questions based on learning objectives from the input, adapted to the specified student level, and outputs them in a clear markdown format.
+
+### create_reading_plan
+
+Creates a three-phase reading plan based on an author or topic to help the user become significantly knowledgeable, including core, extended, and supplementary readings.
+
+### create_recursive_outline
+
+Breaks down complex tasks or projects into manageable, hierarchical components with recursive outlining for clarity and simplicity.
+
+### create_report_finding
+
+Creates a detailed, structured security finding report in markdown, including sections on Description, Risk, Recommendations, References, One-Sentence-Summary, and Quotes.
+
+### create_rpg_summary
+
+Summarizes an in-person RPG session with key events, combat details, player stats, and role-playing highlights in a structured format.
+
+### create_security_update
+
+Creates concise security updates for newsletters, covering stories, threats, advisories, vulnerabilities, and a summary of key issues.
+
+### create_show_intro
+
+Creates compelling short intros for podcasts, summarizing key topics and themes discussed in the episode.
+
+### create_sigma_rules
+
+Extracts Tactics, Techniques, and Procedures (TTPs) from security news and converts them into Sigma detection rules for host-based detections.
+
+### create_story_explanation
+
+Summarizes complex content in a clear, approachable story format that makes the concepts easy to understand.
+
+### create_stride_threat_model
+
+Create a STRIDE-based threat model for a system design, identifying assets, trust boundaries, data flows, and prioritizing threats with mitigations.
+
+### create_summary
+
+Summarizes content into a 20-word sentence, 10 main points (16 words max), and 5 key takeaways in Markdown format.
+
+### create_tags
+
+Identifies at least 5 tags from text content for mind mapping tools, including authors and existing tags if present.
+
+### create_threat_scenarios
+
+Identifies likely attack methods for any system by providing a narrative-based threat model, balancing risk and opportunity.
+
+### create_ttrc_graph
+
+Creates a CSV file showing the progress of Time to Remediate Critical Vulnerabilities over time using given data.
+
+### create_ttrc_narrative
+
+Creates a persuasive narrative highlighting progress in reducing the Time to Remediate Critical Vulnerabilities metric over time.
+
+### create_upgrade_pack
+
+Extracts world model and task algorithm updates from content, providing beliefs about how the world works and task performance.
+
+### create_user_story
+
+Writes concise and clear technical user stories for new features in complex software programs, formatted for all stakeholders.
+
+### create_video_chapters
+
+Extracts interesting topics and timestamps from a transcript, providing concise summaries of key moments.
+
+### create_visualization
+
+Transforms complex ideas into visualizations using intricate ASCII art, simplifying concepts where necessary.
+
+### dialog_with_socrates
+
+Engages in deep, meaningful dialogues to explore and challenge beliefs using the Socratic method.
+
+### enrich_blog_post
+
+Enhances Markdown blog files by applying instructions to improve structure, visuals, and readability for HTML rendering.
+
+### explain_code
+
+Explains code, security tool output, configuration text, and answers questions based on the provided input.
+
+### explain_docs
+
+Improves and restructures tool documentation into clear, concise instructions, including overviews, usage, use cases, and key features.
+
+### explain_math
+
+Helps you understand mathematical concepts in a clear and engaging way.
+
+### explain_project
+
+Summarizes project documentation into clear, concise sections covering the project, problem, solution, installation, usage, and examples.
+
+### explain_terms
+
+Produces a glossary of advanced terms from content, providing a definition, analogy, and explanation of why each term matters.
+
+### export_data_as_csv
+
+Extracts and outputs all data structures from the input in properly formatted CSV data.
+
+### extract_algorithm_update_recommendations
+
+Extracts concise, practical algorithm update recommendations from the input and outputs them in a bulleted list.
+
+### extract_article_wisdom
+
+Extracts surprising, insightful, and interesting information from content, categorizing it into sections like summary, ideas, quotes, facts, references, and recommendations.
+
+### extract_book_ideas
+
+Extracts and outputs 50 to 100 of the most surprising, insightful, and interesting ideas from a book's content.
+
+### extract_book_recommendations
+
+Extracts and outputs 50 to 100 practical, actionable recommendations from a book's content.
+
+### extract_business_ideas
+
+Extracts top business ideas from content and elaborates on the best 10 with unique differentiators.
+
+### extract_controversial_ideas
+
+Extracts and outputs controversial statements and supporting quotes from the input in a structured Markdown list.
+
+### extract_core_message
+
+Extracts and outputs a clear, concise sentence that articulates the core message of a given text or body of work.
+
+### extract_ctf_writeup
+
+Extracts a short writeup from a warstory-like text about a cyber security engagement.
+
+### extract_domains
+
+Extracts domains and URLs from content to identify sources used for articles, newsletters, and other publications.
+
+### extract_extraordinary_claims
+
+Extracts and outputs a list of extraordinary claims from conversations, focusing on scientifically disputed or false statements.
+
+### extract_ideas
+
+Extracts and outputs all the key ideas from input, presented as 15-word bullet points in Markdown.
+
+### extract_insights
+
+Extracts and outputs the most powerful and insightful ideas from text, formatted as 16-word bullet points in the INSIGHTS section, also IDEAS section.
+
+### extract_insights_dm
+
+Extracts and outputs all valuable insights and a concise summary of the content, including key points and topics discussed.
+
+### extract_instructions
+
+Extracts clear, actionable step-by-step instructions and main objectives from instructional video transcripts, organizing them into a concise list.
+
+### extract_jokes
+
+Extracts jokes from text content, presenting each joke with its punchline in separate bullet points.
+
+### extract_latest_video
+
+Extracts the latest video URL from a YouTube RSS feed and outputs the URL only.
+
+### extract_main_activities
+
+Extracts key events and activities from transcripts or logs, providing a summary of what happened.
+
+### extract_main_idea
+
+Extracts the main idea and key recommendation from the input, summarizing them in 15-word sentences.
+
+### extract_most_redeeming_thing
+
+Extracts the most redeeming aspect from an input, summarizing it in a single 15-word sentence.
+
+### extract_patterns
+
+Extracts and analyzes recurring, surprising, and insightful patterns from input, providing detailed analysis and advice for builders.
+
+### extract_poc
+
+Extracts proof of concept URLs and validation methods from security reports, providing the URL and command to run.
+
+### extract_predictions
+
+Extracts predictions from input, including specific details such as date, confidence level, and verification method.
+
+### extract_primary_problem
+
+Extracts the primary problem with the world as presented in a given text or body of work.
+
+### extract_primary_solution
+
+Extracts the primary solution for the world as presented in a given text or body of work.
+
+### extract_product_features
+
+Extracts and outputs a list of product features from the provided input in a bulleted format.
+
+### extract_questions
+
+Extracts and outputs all questions asked by the interviewer in a conversation or interview.
+
+### extract_recipe
+
+Extracts and outputs a recipe with a short meal description, ingredients with measurements, and preparation steps.
+
+### extract_recommendations
+
+Extracts and outputs concise, practical recommendations from a given piece of content in a bulleted list.
+
+### extract_references
+
+Extracts and outputs a bulleted list of references to art, stories, books, literature, and other sources from content.
+
+### extract_skills
+
+Extracts and classifies skills from a job description into a table, separating each skill and classifying it as either hard or soft.
+
+### extract_song_meaning
+
+Analyzes a song to provide a summary of its meaning, supported by detailed evidence from lyrics, artist commentary, and fan analysis.
+
+### extract_sponsors
+
+Extracts and lists official sponsors and potential sponsors from a provided transcript.
+
+### extract_videoid
+
+Extracts and outputs the video ID from any given URL.
+
+### extract_wisdom
+
+Extracts surprising, insightful, and interesting information from text on topics like human flourishing, AI, learning, and more.
+
+### extract_wisdom_agents
+
+Extracts valuable insights, ideas, quotes, and references from content, emphasizing topics like human flourishing, AI, learning, and technology.
+
+### extract_wisdom_dm
+
+Extracts all valuable, insightful, and thought-provoking information from content, focusing on topics like human flourishing, AI, learning, and technology.
+
+### extract_wisdom_nometa
+
+Extracts insights, ideas, quotes, habits, facts, references, and recommendations from content, focusing on human flourishing, AI, technology, and related topics.
+
+### find_female_life_partner
+
+Analyzes criteria for finding a female life partner and provides clear, direct, and poetic descriptions.
+
+### find_hidden_message
+
+Extracts overt and hidden political messages, justifications, audience actions, and a cynical analysis from content.
+
+### find_logical_fallacies
+
+Identifies and analyzes fallacies in arguments, classifying them as formal or informal with detailed reasoning.
+
+### get_wow_per_minute
+
+Determines the wow-factor of content per minute based on surprise, novelty, insight, value, and wisdom, measuring how rewarding the content is for the viewer.
+
+### get_youtube_rss
+
+Returns the RSS URL for a given YouTube channel based on the channel ID or URL.
+
+### humanize
+
+Rewrites AI-generated text to sound natural, conversational, and easy to understand, maintaining clarity and simplicity.
+
+### identify_dsrp_distinctions
+
+Encourages creative, systems-based thinking by exploring distinctions, boundaries, and their implications, drawing on insights from prominent systems thinkers.
+
+### identify_dsrp_perspectives
+
+Explores the concept of distinctions in systems thinking, focusing on how boundaries define ideas, influence understanding, and reveal or obscure insights.
+
+### identify_dsrp_relationships
+
+Encourages exploration of connections, distinctions, and boundaries between ideas, inspired by systems thinkers to reveal new insights and patterns in complex systems.
+
+### identify_dsrp_systems
+
+Encourages organizing ideas into systems of parts and wholes, inspired by systems thinkers to explore relationships and how changes in organization impact meaning and understanding.
+
+### identify_job_stories
+
+Identifies key job stories or requirements for roles.
+
+### improve_academic_writing
+
+Refines text into clear, concise academic language while improving grammar, coherence, and clarity, with a list of changes.
+
+### improve_prompt
+
+Improves an LLM/AI prompt by applying expert prompt writing strategies for better results and clarity.
+
+### improve_report_finding
+
+Improves a penetration test security finding by providing detailed descriptions, risks, recommendations, references, quotes, and a concise summary in markdown format.
+
+### improve_writing
+
+Refines text by correcting grammar, enhancing style, improving clarity, and maintaining the original meaning.
+
+### judge_output
+
+Evaluates Honeycomb queries by judging their effectiveness, providing critiques and outcomes based on language nuances and analytics relevance.
+
+### label_and_rate
+
+Labels content with up to 20 single-word tags and rates it based on idea count and relevance to human meaning, AI, and other related themes, assigning a tier (S, A, B, C, D) and a quality score.
+
+### md_callout
+
+Classifies content and generates a markdown callout based on the provided text, selecting the most appropriate type.
+
+### official_pattern_template
+
+Template to use if you want to create new fabric patterns.
+
+### prepare_7s_strategy
+
+Prepares a comprehensive briefing document from 7S's strategy capturing organizational profile, strategic elements, and market dynamics with clear, concise, and organized content.
+
+### provide_guidance
+
+Provides psychological and life coaching advice, including analysis, recommendations, and potential diagnoses, with a compassionate and honest tone.
+
+### rate_ai_response
+
+Rates the quality of AI responses by comparing them to top human expert performance, assigning a letter grade, reasoning, and providing a 1-100 score based on the evaluation.
+
+### rate_ai_result
+
+Assesses the quality of AI/ML/LLM work by deeply analyzing content, instructions, and output, then rates performance based on multiple dimensions, including coverage, creativity, and interdisciplinary thinking.
+
+### rate_content
+
+Labels content with up to 20 single-word tags and rates it based on idea count and relevance to human meaning, AI, and other related themes, assigning a tier (S, A, B, C, D) and a quality score.
+
+### rate_value
+
+Produces the best possible output by deeply analyzing and understanding the input and its intended purpose.
+
+### raw_query
+
+Fully digests and contemplates the input to produce the best possible result based on understanding the sender's intent.
+
+### recommend_artists
+
+Recommends a personalized festival schedule with artists aligned to your favorite styles and interests, including rationale.
+
+### recommend_pipeline_upgrades
+
+Optimizes vulnerability-checking pipelines by incorporating new information and improving their efficiency, with detailed explanations of changes.
+
+### recommend_talkpanel_topics
+
+Produces a clean set of proposed talks or panel talking points for a person based on their interests and goals, formatted for submission to a conference organizer.
+
+### refine_design_document
+
+Refines a design document based on a design review by analyzing, mapping concepts, and implementing changes using valid Markdown.
+
+### review_design
+
+Reviews and analyzes architecture design, focusing on clarity, component design, system integrations, security, performance, scalability, and data management.
+
+### sanitize_broken_html_to_markdown
+
+Converts messy HTML into clean, properly formatted Markdown, applying custom styling and ensuring compatibility with Vite.
+
+### show_fabric_options_markmap
+
+Visualizes the functionality of the Fabric framework by representing its components, commands, and features based on the provided input.
+
+### solve_with_cot
+
+Provides detailed, step-by-step responses with chain of thought reasoning, using structured thinking, reflection, and output sections.
+
+### suggest_pattern
+
+Suggests appropriate fabric patterns or commands based on user input, providing clear explanations and options for users.
+
+### summarize
+
+Summarizes content into a 20-word sentence, main points, and takeaways, formatted with numbered lists in Markdown.
+
+### summarize_board_meeting
+
+Creates formal meeting notes from board meeting transcripts for corporate governance documentation.
+
+### summarize_debate
+
+Summarizes debates, identifies primary disagreement, extracts arguments, and provides analysis of evidence and argument strength to predict outcomes.
+
+### summarize_git_changes
+
+Summarizes recent project updates from the last 7 days, focusing on key changes with enthusiasm.
+
+### summarize_git_diff
+
+Summarizes and organizes Git diff changes with clear, succinct commit messages and bullet points.
+
+### summarize_lecture
+
+Extracts relevant topics, definitions, and tools from lecture transcripts, providing structured summaries with timestamps and key takeaways.
+
+### summarize_legislation
+
+Summarizes complex political proposals and legislation by analyzing key points, proposed changes, and providing balanced, positive, and cynical characterizations.
+
+### summarize_meeting
+
+Analyzes meeting transcripts to extract a structured summary, including an overview, key points, tasks, decisions, challenges, timeline, references, and next steps.
+
+### summarize_micro
+
+Summarizes content into a 20-word sentence, 3 main points, and 3 takeaways, formatted in clear, concise Markdown.
+
+### summarize_newsletter
+
+Extracts the most meaningful, interesting, and useful content from a newsletter, summarizing key sections such as content, opinions, tools, companies, and follow-up items in clear, structured Markdown.
+
+### summarize_paper
+
+Summarizes an academic paper by detailing its title, authors, technical approach, distinctive features, experimental setup, results, advantages, limitations, and conclusion in a clear, structured format using human-readable Markdown.
+
+### summarize_prompt
+
+Summarizes AI chat prompts by describing the primary function, unique approach, and expected output in a concise paragraph. The summary is focused on the prompt's purpose without unnecessary details or formatting.
+
+### summarize_pull-requests
+
+Summarizes pull requests for a coding project by providing a summary and listing the top PRs with human-readable descriptions.
+
+### summarize_rpg_session
+
+Summarizes a role-playing game session by extracting key events, combat stats, character changes, quotes, and more.
+
+### t_analyze_challenge_handling
+
+Provides 8-16 word bullet points evaluating how well challenges are being addressed, calling out any lack of effort.
+
+### t_check_metrics
+
+Analyzes deep context from the TELOS file and input instruction, then provides a wisdom-based output while considering metrics and KPIs to assess recent improvements.
+
+### t_create_h3_career
+
+Summarizes context and produces wisdom-based output by deeply analyzing both the TELOS File and the input instruction, considering the relationship between the two.
+
+### t_create_opening_sentences
+
+Describes from TELOS file the person's identity, goals, and actions in 4 concise, 32-word bullet points, humbly.
+
+### t_describe_life_outlook
+
+Describes from TELOS file a person's life outlook in 5 concise, 16-word bullet points.
+
+### t_extract_intro_sentences
+
+Summarizes from TELOS file a person's identity, work, and current projects in 5 concise and grounded bullet points.
+
+### t_extract_panel_topics
+
+Creates 5 panel ideas with titles and descriptions based on deep context from a TELOS file and input.
+
+### t_find_blindspots
+
+Identify potential blindspots in thinking, frames, or models that may expose the individual to error or risk.
+
+### t_find_negative_thinking
+
+Analyze a TELOS file and input to identify negative thinking in documents or journals, followed by tough love encouragement.
+
+### t_find_neglected_goals
+
+Analyze a TELOS file and input instructions to identify goals or projects that have not been worked on recently.
+
+### t_give_encouragement
+
+Analyze a TELOS file and input instructions to evaluate progress, provide encouragement, and offer recommendations for continued effort.
+
+### t_red_team_thinking
+
+Analyze a TELOS file and input instructions to red-team thinking, models, and frames, then provide recommendations for improvement.
+
+### t_threat_model_plans
+
+Analyze a TELOS file and input instructions to create threat models for a life plan and recommend improvements.
+
+### t_visualize_mission_goals_projects
+
+Analyze a TELOS file and input instructions to create an ASCII art diagram illustrating the relationship of missions, goals, and projects.
+
+### t_year_in_review
+
+Analyze a TELOS file to create insights about a person or entity, then summarize accomplishments and visualizations in bullet points.
+
+### to_flashcards
+
+Create Anki flashcards from a given text, focusing on concise, optimized questions and answers without external context.
+
+### transcribe_minutes
+
+Extracts (from meeting transcription) meeting minutes, identifying actionables, insightful ideas, decisions, challenges, and next steps in a structured format.
+
+### translate
+
+Translates sentences or documentation into the specified language code while maintaining the original formatting and tone.
+
+### tweet
+
+Provides a step-by-step guide on crafting engaging tweets with emojis, covering Twitter basics, account creation, features, and audience targeting.
+
+### write_essay
+
+Writes essays in the style of a specified author, embodying their unique voice, vocabulary, and approach. Uses `author_name` variable.
+
+### write_essay_pg
+
+Writes concise, clear essays in the style of Paul Graham, focusing on simplicity, clarity, and illumination of the provided topic.
+
+### write_hackerone_report
+
+Generates concise, clear, and reproducible bug bounty reports, detailing vulnerability impact, steps to reproduce, and exploit details for triagers.
+
+### write_latex
+
+Generates syntactically correct LaTeX code for a new.tex document, ensuring proper formatting and compatibility with pdflatex.
+
+### write_micro_essay
+
+Writes concise, clear, and illuminating essays on the given topic in the style of Paul Graham.
+
+### write_nuclei_template_rule
+
+Generates Nuclei YAML templates for detecting vulnerabilities using HTTP requests, matchers, extractors, and dynamic data extraction.
+
+### write_pull-request
+
+Drafts detailed pull request descriptions, explaining changes, providing reasoning, and identifying potential bugs from the git diff command output.
+
+### write_semgrep_rule
+
+Creates accurate and working Semgrep rules based on input, following syntax guidelines and specific language considerations.
+
+### youtube_summary
+
+Create concise, timestamped Youtube video summaries that highlight key points.

patterns/summarize/dmiessler/summarize/system.md

@@ -1,25 +0,0 @@
-# IDENTITY and PURPOSE
-
-You are a summarization system that extracts the most interesting, useful, and surprising aspects of an article.
-
-Take a step back and think step by step about how to achieve the best result possible as defined in the steps below. You have a lot of freedom to make this work well.
-
-## OUTPUT SECTIONS
-
-1. You extract a summary of the content in 20 words or less, including who is presenting and the content being discussed into a section called SUMMARY.
-
-2. You extract the top 20 ideas from the input in a section called IDEAS:.
-
-3. You extract the 10 most insightful and interesting quotes from the input into a section called QUOTES:. Use the exact quote text from the input.
-
-4. You extract the 20 most insightful and interesting recommendations that can be collected from the content into a section called RECOMMENDATIONS.
-
-5. You combine all understanding of the article into a single, 20-word sentence in a section called ONE SENTENCE SUMMARY:.
-
-## OUTPUT INSTRUCTIONS
-
-1. You only output Markdown.
-2. Do not give warnings or notes; only output the requested sections.
-3. You use numbered lists, not bullets.
-4. Do not repeat ideas, or quotes.
-5. Do not start items with the same opening words.

patterns/summarize/dmiessler/summarize/user.md

@@ -1 +0,0 @@
-CONTENT:

patterns/write_essay/system.md

@@ -1,312 +1,24 @@
-# IDENTITY and PURPOSE
+# Identity and Purpose
 
-You are an expert on writing concise, clear, and illuminating essays on the topic of the input provided.
+You are an expert on writing clear and illuminating essays on the topic of the input provided.
 
-# OUTPUT INSTRUCTIONS
+## Output Instructions
 
-- Write the essay in the style of Paul Graham, who is known for this concise, clear, and simple style of writing.
+- Write the essay in the style of {{author_name}}, embodying all the qualities that they are known for.
 
-EXAMPLE PAUL GRAHAM ESSAYS
+- Look up some example essays by {{author_name}} (Use web search if the tool is available)
 
-Writing about something, even something you know well, usually shows you that you didn't know it as well as you thought. Putting ideas into words is a severe test. The first words you choose are usually wrong; you have to rewrite sentences over and over to get them exactly right. And your ideas won't just be imprecise, but incomplete too. Half the ideas that end up in an essay will be ones you thought of while you were writing it. Indeed, that's why I write them.
-
-Once you publish something, the convention is that whatever you wrote was what you thought before you wrote it. These were your ideas, and now you've expressed them. But you know this isn't true. You know that putting your ideas into words changed them. And not just the ideas you published. Presumably there were others that turned out to be too broken to fix, and those you discarded instead.
-
-It's not just having to commit your ideas to specific words that makes writing so exacting. The real test is reading what you've written. You have to pretend to be a neutral reader who knows nothing of what's in your head, only what you wrote. When he reads what you wrote, does it seem correct? Does it seem complete? If you make an effort, you can read your writing as if you were a complete stranger, and when you do the news is usually bad. It takes me many cycles before I can get an essay past the stranger. But the stranger is rational, so you always can, if you ask him what he needs. If he's not satisfied because you failed to mention x or didn't qualify some sentence sufficiently, then you mention x or add more qualifications. Happy now? It may cost you some nice sentences, but you have to resign yourself to that. You just have to make them as good as you can and still satisfy the stranger.
-
-This much, I assume, won't be that controversial. I think it will accord with the experience of anyone who has tried to write about anything non-trivial. There may exist people whose thoughts are so perfectly formed that they just flow straight into words. But I've never known anyone who could do this, and if I met someone who said they could, it would seem evidence of their limitations rather than their ability. Indeed, this is a trope in movies: the guy who claims to have a plan for doing some difficult thing, and who when questioned further, taps his head and says "It's all up here." Everyone watching the movie knows what that means. At best the plan is vague and incomplete. Very likely there's some undiscovered flaw that invalidates it completely. At best it's a plan for a plan.
-
-In precisely defined domains it's possible to form complete ideas in your head. People can play chess in their heads, for example. And mathematicians can do some amount of math in their heads, though they don't seem to feel sure of a proof over a certain length till they write it down. But this only seems possible with ideas you can express in a formal language. [1] Arguably what such people are doing is putting ideas into words in their heads. I can to some extent write essays in my head. I'll sometimes think of a paragraph while walking or lying in bed that survives nearly unchanged in the final version. But really I'm writing when I do this. I'm doing the mental part of writing; my fingers just aren't moving as I do it. [2]
-
-You can know a great deal about something without writing about it. Can you ever know so much that you wouldn't learn more from trying to explain what you know? I don't think so. I've written about at least two subjects I know well — Lisp hacking and startups — and in both cases I learned a lot from writing about them. In both cases there were things I didn't consciously realize till I had to explain them. And I don't think my experience was anomalous. A great deal of knowledge is unconscious, and experts have if anything a higher proportion of unconscious knowledge than beginners.
-
-I'm not saying that writing is the best way to explore all ideas. If you have ideas about architecture, presumably the best way to explore them is to build actual buildings. What I'm saying is that however much you learn from exploring ideas in other ways, you'll still learn new things from writing about them.
-
-Putting ideas into words doesn't have to mean writing, of course. You can also do it the old way, by talking. But in my experience, writing is the stricter test. You have to commit to a single, optimal sequence of words. Less can go unsaid when you don't have tone of voice to carry meaning. And you can focus in a way that would seem excessive in conversation. I'll often spend 2 weeks on an essay and reread drafts 50 times. If you did that in conversation it would seem evidence of some kind of mental disorder. If you're lazy, of course, writing and talking are equally useless. But if you want to push yourself to get things right, writing is the steeper hill. [3]
-
-The reason I've spent so long establishing this rather obvious point is that it leads to another that many people will find shocking. If writing down your ideas always makes them more precise and more complete, then no one who hasn't written about a topic has fully formed ideas about it. And someone who never writes has no fully formed ideas about anything non-trivial.
-
-It feels to them as if they do, especially if they're not in the habit of critically examining their own thinking. Ideas can feel complete. It's only when you try to put them into words that you discover they're not. So if you never subject your ideas to that test, you'll not only never have fully formed ideas, but also never realize it.
-
-Putting ideas into words is certainly no guarantee that they'll be right. Far from it. But though it's not a sufficient condition, it is a necessary one.
-		
-What You Can't Say
-
-January 2004
-
-Have you ever seen an old photo of yourself and been embarrassed at the way you looked? Did we actually dress like that? We did. And we had no idea how silly we looked. It's the nature of fashion to be invisible, in the same way the movement of the earth is invisible to all of us riding on it.
-
-What scares me is that there are moral fashions too. They're just as arbitrary, and just as invisible to most people. But they're much more dangerous. Fashion is mistaken for good design; moral fashion is mistaken for good. Dressing oddly gets you laughed at. Violating moral fashions can get you fired, ostracized, imprisoned, or even killed.
-
-If you could travel back in a time machine, one thing would be true no matter where you went: you'd have to watch what you said. Opinions we consider harmless could have gotten you in big trouble. I've already said at least one thing that would have gotten me in big trouble in most of Europe in the seventeenth century, and did get Galileo in big trouble when he said it — that the earth moves. [1]
-
-It seems to be a constant throughout history: In every period, people believed things that were just ridiculous, and believed them so strongly that you would have gotten in terrible trouble for saying otherwise.
-
-Is our time any different? To anyone who has read any amount of history, the answer is almost certainly no. It would be a remarkable coincidence if ours were the first era to get everything just right.
-
-It's tantalizing to think we believe things that people in the future will find ridiculous. What would someone coming back to visit us in a time machine have to be careful not to say? That's what I want to study here. But I want to do more than just shock everyone with the heresy du jour. I want to find general recipes for discovering what you can't say, in any era.
-
-The Conformist Test
-
-Let's start with a test: Do you have any opinions that you would be reluctant to express in front of a group of your peers?
-
-If the answer is no, you might want to stop and think about that. If everything you believe is something you're supposed to believe, could that possibly be a coincidence? Odds are it isn't. Odds are you just think what you're told.
-
-The other alternative would be that you independently considered every question and came up with the exact same answers that are now considered acceptable. That seems unlikely, because you'd also have to make the same mistakes. Mapmakers deliberately put slight mistakes in their maps so they can tell when someone copies them. If another map has the same mistake, that's very convincing evidence.
-
-Like every other era in history, our moral map almost certainly contains a few mistakes. And anyone who makes the same mistakes probably didn't do it by accident. It would be like someone claiming they had independently decided in 1972 that bell-bottom jeans were a good idea.
-
-If you believe everything you're supposed to now, how can you be sure you wouldn't also have believed everything you were supposed to if you had grown up among the plantation owners of the pre-Civil War South, or in Germany in the 1930s — or among the Mongols in 1200, for that matter? Odds are you would have.
-
-Back in the era of terms like "well-adjusted," the idea seemed to be that there was something wrong with you if you thought things you didn't dare say out loud. This seems backward. Almost certainly, there is something wrong with you if you don't think things you don't dare say out loud.
-
-Trouble
-
-What can't we say? One way to find these ideas is simply to look at things people do say, and get in trouble for. [2]
-
-Of course, we're not just looking for things we can't say. We're looking for things we can't say that are true, or at least have enough chance of being true that the question should remain open. But many of the things people get in trouble for saying probably do make it over this second, lower threshold. No one gets in trouble for saying that 2 + 2 is 5, or that people in Pittsburgh are ten feet tall. Such obviously false statements might be treated as jokes, or at worst as evidence of insanity, but they are not likely to make anyone mad. The statements that make people mad are the ones they worry might be believed. I suspect the statements that make people maddest are those they worry might be true.
-
-If Galileo had said that people in Padua were ten feet tall, he would have been regarded as a harmless eccentric. Saying the earth orbited the sun was another matter. The church knew this would set people thinking.
-
-Certainly, as we look back on the past, this rule of thumb works well. A lot of the statements people got in trouble for seem harmless now. So it's likely that visitors from the future would agree with at least some of the statements that get people in trouble today. Do we have no Galileos? Not likely.
-
-To find them, keep track of opinions that get people in trouble, and start asking, could this be true? Ok, it may be heretical (or whatever modern equivalent), but might it also be true?
-
-Heresy
-
-This won't get us all the answers, though. What if no one happens to have gotten in trouble for a particular idea yet? What if some idea would be so radioactively controversial that no one would dare express it in public? How can we find these too?
-
-Another approach is to follow that word, heresy. In every period of history, there seem to have been labels that got applied to statements to shoot them down before anyone had a chance to ask if they were true or not. "Blasphemy", "sacrilege", and "heresy" were such labels for a good part of western history, as in more recent times "indecent", "improper", and "unamerican" have been. By now these labels have lost their sting. They always do. By now they're mostly used ironically. But in their time, they had real force.
-
-The word "defeatist", for example, has no particular political connotations now. But in Germany in 1917 it was a weapon, used by Ludendorff in a purge of those who favored a negotiated peace. At the start of World War II it was used extensively by Churchill and his supporters to silence their opponents. In 1940, any argument against Churchill's aggressive policy was "defeatist". Was it right or wrong? Ideally, no one got far enough to ask that.
-
-We have such labels today, of course, quite a lot of them, from the all-purpose "inappropriate" to the dreaded "divisive." In any period, it should be easy to figure out what such labels are, simply by looking at what people call ideas they disagree with besides untrue. When a politician says his opponent is mistaken, that's a straightforward criticism, but when he attacks a statement as "divisive" or "racially insensitive" instead of arguing that it's false, we should start paying attention.
-
-So another way to figure out which of our taboos future generations will laugh at is to start with the labels. Take a label — "sexist", for example — and try to think of some ideas that would be called that. Then for each ask, might this be true?
-
-Just start listing ideas at random? Yes, because they won't really be random. The ideas that come to mind first will be the most plausible ones. They'll be things you've already noticed but didn't let yourself think.
-
-In 1989 some clever researchers tracked the eye movements of radiologists as they scanned chest images for signs of lung cancer. [3] They found that even when the radiologists missed a cancerous lesion, their eyes had usually paused at the site of it. Part of their brain knew there was something there; it just didn't percolate all the way up into conscious knowledge. I think many interesting heretical thoughts are already mostly formed in our minds. If we turn off our self-censorship temporarily, those will be the first to emerge.
-
-Time and Space
-
-If we could look into the future it would be obvious which of our taboos they'd laugh at. We can't do that, but we can do something almost as good: we can look into the past. Another way to figure out what we're getting wrong is to look at what used to be acceptable and is now unthinkable.
-
-Changes between the past and the present sometimes do represent progress. In a field like physics, if we disagree with past generations it's because we're right and they're wrong. But this becomes rapidly less true as you move away from the certainty of the hard sciences. By the time you get to social questions, many changes are just fashion. The age of consent fluctuates like hemlines.
-
-We may imagine that we are a great deal smarter and more virtuous than past generations, but the more history you read, the less likely this seems. People in past times were much like us. Not heroes, not barbarians. Whatever their ideas were, they were ideas reasonable people could believe.
-
-So here is another source of interesting heresies. Diff present ideas against those of various past cultures, and see what you get. [4] Some will be shocking by present standards. Ok, fine; but which might also be true?
-
-You don't have to look into the past to find big differences. In our own time, different societies have wildly varying ideas of what's ok and what isn't. So you can try diffing other cultures' ideas against ours as well. (The best way to do that is to visit them.) Any idea that's considered harmless in a significant percentage of times and places, and yet is taboo in ours, is a candidate for something we're mistaken about.
-
-For example, at the high water mark of political correctness in the early 1990s, Harvard distributed to its faculty and staff a brochure saying, among other things, that it was inappropriate to compliment a colleague or student's clothes. No more "nice shirt." I think this principle is rare among the world's cultures, past or present. There are probably more where it's considered especially polite to compliment someone's clothing than where it's considered improper. Odds are this is, in a mild form, an example of one of the taboos a visitor from the future would have to be careful to avoid if he happened to set his time machine for Cambridge, Massachusetts, 1992. [5]
-
-Prigs
-
-Of course, if they have time machines in the future they'll probably have a separate reference manual just for Cambridge. This has always been a fussy place, a town of i dotters and t crossers, where you're liable to get both your grammar and your ideas corrected in the same conversation. And that suggests another way to find taboos. Look for prigs, and see what's inside their heads.
-
-Kids' heads are repositories of all our taboos. It seems fitting to us that kids' ideas should be bright and clean. The picture we give them of the world is not merely simplified, to suit their developing minds, but sanitized as well, to suit our ideas of what kids ought to think. [6]
-
-You can see this on a small scale in the matter of dirty words. A lot of my friends are starting to have children now, and they're all trying not to use words like "fuck" and "shit" within baby's hearing, lest baby start using these words too. But these words are part of the language, and adults use them all the time. So parents are giving their kids an inaccurate idea of the language by not using them. Why do they do this? Because they don't think it's fitting that kids should use the whole language. We like children to seem innocent. [7]
-
-Most adults, likewise, deliberately give kids a misleading view of the world. One of the most obvious examples is Santa Claus. We think it's cute for little kids to believe in Santa Claus. I myself think it's cute for little kids to believe in Santa Claus. But one wonders, do we tell them this stuff for their sake, or for ours?
-
-I'm not arguing for or against this idea here. It is probably inevitable that parents should want to dress up their kids' minds in cute little baby outfits. I'll probably do it myself. The important thing for our purposes is that, as a result, a well brought-up teenage kid's brain is a more or less complete collection of all our taboos — and in mint condition, because they're untainted by experience. Whatever we think that will later turn out to be ridiculous, it's almost certainly inside that head.
-
-How do we get at these ideas? By the following thought experiment. Imagine a kind of latter-day Conrad character who has worked for a time as a mercenary in Africa, for a time as a doctor in Nepal, for a time as the manager of a nightclub in Miami. The specifics don't matter — just someone who has seen a lot. Now imagine comparing what's inside this guy's head with what's inside the head of a well-behaved sixteen year old girl from the suburbs. What does he think that would shock her? He knows the world; she knows, or at least embodies, present taboos. Subtract one from the other, and the result is what we can't say.
-
-Mechanism
-
-I can think of one more way to figure out what we can't say: to look at how taboos are created. How do moral fashions arise, and why are they adopted? If we can understand this mechanism, we may be able to see it at work in our own time.
-
-Moral fashions don't seem to be created the way ordinary fashions are. Ordinary fashions seem to arise by accident when everyone imitates the whim of some influential person. The fashion for broad-toed shoes in late fifteenth century Europe began because Charles VIII of France had six toes on one foot. The fashion for the name Gary began when the actor Frank Cooper adopted the name of a tough mill town in Indiana. Moral fashions more often seem to be created deliberately. When there's something we can't say, it's often because some group doesn't want us to.
-
-The prohibition will be strongest when the group is nervous. The irony of Galileo's situation was that he got in trouble for repeating Copernicus's ideas. Copernicus himself didn't. In fact, Copernicus was a canon of a cathedral, and dedicated his book to the pope. But by Galileo's time the church was in the throes of the Counter-Reformation and was much more worried about unorthodox ideas.
-
-To launch a taboo, a group has to be poised halfway between weakness and power. A confident group doesn't need taboos to protect it. It's not considered improper to make disparaging remarks about Americans, or the English. And yet a group has to be powerful enough to enforce a taboo. Coprophiles, as of this writing, don't seem to be numerous or energetic enough to have had their interests promoted to a lifestyle.
-
-I suspect the biggest source of moral taboos will turn out to be power struggles in which one side only barely has the upper hand. That's where you'll find a group powerful enough to enforce taboos, but weak enough to need them.
-
-Most struggles, whatever they're really about, will be cast as struggles between competing ideas. The English Reformation was at bottom a struggle for wealth and power, but it ended up being cast as a struggle to preserve the souls of Englishmen from the corrupting influence of Rome. It's easier to get people to fight for an idea. And whichever side wins, their ideas will also be considered to have triumphed, as if God wanted to signal his agreement by selecting that side as the victor.
-
-We often like to think of World War II as a triumph of freedom over totalitarianism. We conveniently forget that the Soviet Union was also one of the winners.
-
-I'm not saying that struggles are never about ideas, just that they will always be made to seem to be about ideas, whether they are or not. And just as there is nothing so unfashionable as the last, discarded fashion, there is nothing so wrong as the principles of the most recently defeated opponent. Representational art is only now recovering from the approval of both Hitler and Stalin. [8]
-
-Although moral fashions tend to arise from different sources than fashions in clothing, the mechanism of their adoption seems much the same. The early adopters will be driven by ambition: self-consciously cool people who want to distinguish themselves from the common herd. As the fashion becomes established they'll be joined by a second, much larger group, driven by fear. [9] This second group adopt the fashion not because they want to stand out but because they are afraid of standing out.
-
-So if you want to figure out what we can't say, look at the machinery of fashion and try to predict what it would make unsayable. What groups are powerful but nervous, and what ideas would they like to suppress? What ideas were tarnished by association when they ended up on the losing side of a recent struggle? If a self-consciously cool person wanted to differentiate himself from preceding fashions (e.g. from his parents), which of their ideas would he tend to reject? What are conventional-minded people afraid of saying?
-
-This technique won't find us all the things we can't say. I can think of some that aren't the result of any recent struggle. Many of our taboos are rooted deep in the past. But this approach, combined with the preceding four, will turn up a good number of unthinkable ideas.
-
-Why
-
-Some would ask, why would one want to do this? Why deliberately go poking around among nasty, disreputable ideas? Why look under rocks?
-
-I do it, first of all, for the same reason I did look under rocks as a kid: plain curiosity. And I'm especially curious about anything that's forbidden. Let me see and decide for myself.
-
-Second, I do it because I don't like the idea of being mistaken. If, like other eras, we believe things that will later seem ridiculous, I want to know what they are so that I, at least, can avoid believing them.
-
-Third, I do it because it's good for the brain. To do good work you need a brain that can go anywhere. And you especially need a brain that's in the habit of going where it's not supposed to.
-
-Great work tends to grow out of ideas that others have overlooked, and no idea is so overlooked as one that's unthinkable. Natural selection, for example. It's so simple. Why didn't anyone think of it before? Well, that is all too obvious. Darwin himself was careful to tiptoe around the implications of his theory. He wanted to spend his time thinking about biology, not arguing with people who accused him of being an atheist.
-
-In the sciences, especially, it's a great advantage to be able to question assumptions. The m.o. of scientists, or at least of the good ones, is precisely that: look for places where conventional wisdom is broken, and then try to pry apart the cracks and see what's underneath. That's where new theories come from.
-
-A good scientist, in other words, does not merely ignore conventional wisdom, but makes a special effort to break it. Scientists go looking for trouble. This should be the m.o. of any scholar, but scientists seem much more willing to look under rocks. [10]
-
-Why? It could be that the scientists are simply smarter; most physicists could, if necessary, make it through a PhD program in French literature, but few professors of French literature could make it through a PhD program in physics. Or it could be because it's clearer in the sciences whether theories are true or false, and this makes scientists bolder. (Or it could be that, because it's clearer in the sciences whether theories are true or false, you have to be smart to get jobs as a scientist, rather than just a good politician.)
-
-Whatever the reason, there seems a clear correlation between intelligence and willingness to consider shocking ideas. This isn't just because smart people actively work to find holes in conventional thinking. I think conventions also have less hold over them to start with. You can see that in the way they dress.
-
-It's not only in the sciences that heresy pays off. In any competitive field, you can win big by seeing things that others daren't. And in every field there are probably heresies few dare utter. Within the US car industry there is a lot of hand-wringing now about declining market share. Yet the cause is so obvious that any observant outsider could explain it in a second: they make bad cars. And they have for so long that by now the US car brands are antibrands — something you'd buy a car despite, not because of. Cadillac stopped being the Cadillac of cars in about 1970. And yet I suspect no one dares say this. [11] Otherwise these companies would have tried to fix the problem.
-
-Training yourself to think unthinkable thoughts has advantages beyond the thoughts themselves. It's like stretching. When you stretch before running, you put your body into positions much more extreme than any it will assume during the run. If you can think things so outside the box that they'd make people's hair stand on end, you'll have no trouble with the small trips outside the box that people call innovative.
-
-Pensieri Stretti
-
-When you find something you can't say, what do you do with it? My advice is, don't say it. Or at least, pick your battles.
-
-Suppose in the future there is a movement to ban the color yellow. Proposals to paint anything yellow are denounced as "yellowist", as is anyone suspected of liking the color. People who like orange are tolerated but viewed with suspicion. Suppose you realize there is nothing wrong with yellow. If you go around saying this, you'll be denounced as a yellowist too, and you'll find yourself having a lot of arguments with anti-yellowists. If your aim in life is to rehabilitate the color yellow, that may be what you want. But if you're mostly interested in other questions, being labelled as a yellowist will just be a distraction. Argue with idiots, and you become an idiot.
-
-The most important thing is to be able to think what you want, not to say what you want. And if you feel you have to say everything you think, it may inhibit you from thinking improper thoughts. I think it's better to follow the opposite policy. Draw a sharp line between your thoughts and your speech. Inside your head, anything is allowed. Within my head I make a point of encouraging the most outrageous thoughts I can imagine. But, as in a secret society, nothing that happens within the building should be told to outsiders. The first rule of Fight Club is, you do not talk about Fight Club.
-
-When Milton was going to visit Italy in the 1630s, Sir Henry Wootton, who had been ambassador to Venice, told him his motto should be "i pensieri stretti & il viso sciolto." Closed thoughts and an open face. Smile at everyone, and don't tell them what you're thinking. This was wise advice. Milton was an argumentative fellow, and the Inquisition was a bit restive at that time. But I think the difference between Milton's situation and ours is only a matter of degree. Every era has its heresies, and if you don't get imprisoned for them you will at least get in enough trouble that it becomes a complete distraction.
-
-I admit it seems cowardly to keep quiet. When I read about the harassment to which the Scientologists subject their critics [12], or that pro-Israel groups are "compiling dossiers" on those who speak out against Israeli human rights abuses [13], or about people being sued for violating the DMCA [14], part of me wants to say, "All right, you bastards, bring it on." The problem is, there are so many things you can't say. If you said them all you'd have no time left for your real work. You'd have to turn into Noam Chomsky. [15]
-
-The trouble with keeping your thoughts secret, though, is that you lose the advantages of discussion. Talking about an idea leads to more ideas. So the optimal plan, if you can manage it, is to have a few trusted friends you can speak openly to. This is not just a way to develop ideas; it's also a good rule of thumb for choosing friends. The people you can say heretical things to without getting jumped on are also the most interesting to know.
-
-Viso Sciolto?
-
-I don't think we need the viso sciolto so much as the pensieri stretti. Perhaps the best policy is to make it plain that you don't agree with whatever zealotry is current in your time, but not to be too specific about what you disagree with. Zealots will try to draw you out, but you don't have to answer them. If they try to force you to treat a question on their terms by asking "are you with us or against us?" you can always just answer "neither".
-
-Better still, answer "I haven't decided." That's what Larry Summers did when a group tried to put him in this position. Explaining himself later, he said "I don't do litmus tests." [16] A lot of the questions people get hot about are actually quite complicated. There is no prize for getting the answer quickly.
-
-If the anti-yellowists seem to be getting out of hand and you want to fight back, there are ways to do it without getting yourself accused of being a yellowist. Like skirmishers in an ancient army, you want to avoid directly engaging the main body of the enemy's troops. Better to harass them with arrows from a distance.
-
-One way to do this is to ratchet the debate up one level of abstraction. If you argue against censorship in general, you can avoid being accused of whatever heresy is contained in the book or film that someone is trying to censor. You can attack labels with meta-labels: labels that refer to the use of labels to prevent discussion. The spread of the term "political correctness" meant the beginning of the end of political correctness, because it enabled one to attack the phenomenon as a whole without being accused of any of the specific heresies it sought to suppress.
-
-Another way to counterattack is with metaphor. Arthur Miller undermined the House Un-American Activities Committee by writing a play, "The Crucible," about the Salem witch trials. He never referred directly to the committee and so gave them no way to reply. What could HUAC do, defend the Salem witch trials? And yet Miller's metaphor stuck so well that to this day the activities of the committee are often described as a "witch-hunt."
-
-Best of all, probably, is humor. Zealots, whatever their cause, invariably lack a sense of humor. They can't reply in kind to jokes. They're as unhappy on the territory of humor as a mounted knight on a skating rink. Victorian prudishness, for example, seems to have been defeated mainly by treating it as a joke. Likewise its reincarnation as political correctness. "I am glad that I managed to write 'The Crucible,'" Arthur Miller wrote, "but looking back I have often wished I'd had the temperament to do an absurd comedy, which is what the situation deserved." [17]
-
-ABQ
-
-A Dutch friend says I should use Holland as an example of a tolerant society. It's true they have a long tradition of comparative open-mindedness. For centuries the low countries were the place to go to say things you couldn't say anywhere else, and this helped to make the region a center of scholarship and industry (which have been closely tied for longer than most people realize). Descartes, though claimed by the French, did much of his thinking in Holland.
-
-And yet, I wonder. The Dutch seem to live their lives up to their necks in rules and regulations. There's so much you can't do there; is there really nothing you can't say?
-
-Certainly the fact that they value open-mindedness is no guarantee. Who thinks they're not open-minded? Our hypothetical prim miss from the suburbs thinks she's open-minded. Hasn't she been taught to be? Ask anyone, and they'll say the same thing: they're pretty open-minded, though they draw the line at things that are really wrong. (Some tribes may avoid "wrong" as judgemental, and may instead use a more neutral sounding euphemism like "negative" or "destructive".)
-
-When people are bad at math, they know it, because they get the wrong answers on tests. But when people are bad at open-mindedness they don't know it. In fact they tend to think the opposite. Remember, it's the nature of fashion to be invisible. It wouldn't work otherwise. Fashion doesn't seem like fashion to someone in the grip of it. It just seems like the right thing to do. It's only by looking from a distance that we see oscillations in people's idea of the right thing to do, and can identify them as fashions.
-
-Time gives us such distance for free. Indeed, the arrival of new fashions makes old fashions easy to see, because they seem so ridiculous by contrast. From one end of a pendulum's swing, the other end seems especially far away.
-
-To see fashion in your own time, though, requires a conscious effort. Without time to give you distance, you have to create distance yourself. Instead of being part of the mob, stand as far away from it as you can and watch what it's doing. And pay especially close attention whenever an idea is being suppressed. Web filters for children and employees often ban sites containing pornography, violence, and hate speech. What counts as pornography and violence? And what, exactly, is "hate speech?" This sounds like a phrase out of 1984.
-
-Labels like that are probably the biggest external clue. If a statement is false, that's the worst thing you can say about it. You don't need to say that it's heretical. And if it isn't false, it shouldn't be suppressed. So when you see statements being attacked as x-ist or y-ic (substitute your current values of x and y), whether in 1630 or 2030, that's a sure sign that something is wrong. When you hear such labels being used, ask why.
-
-Especially if you hear yourself using them. It's not just the mob you need to learn to watch from a distance. You need to be able to watch your own thoughts from a distance. That's not a radical idea, by the way; it's the main difference between children and adults. When a child gets angry because he's tired, he doesn't know what's happening. An adult can distance himself enough from the situation to say "never mind, I'm just tired." I don't see why one couldn't, by a similar process, learn to recognize and discount the effects of moral fashions.
-
-You have to take that extra step if you want to think clearly. But it's harder, because now you're working against social customs instead of with them. Everyone encourages you to grow up to the point where you can discount your own bad moods. Few encourage you to continue to the point where you can discount society's bad moods.
-
-How can you see the wave, when you're the water? Always be questioning. That's the only defence. What can't you say? And why?
-
-How to Start Google
-
-March 2024
-
-(This is a talk I gave to 14 and 15 year olds about what to do now if they might want to start a startup later. Lots of schools think they should tell students something about startups. This is what I think they should tell them.)
-
-Most of you probably think that when you're released into the so-called real world you'll eventually have to get some kind of job. That's not true, and today I'm going to talk about a trick you can use to avoid ever having to get a job.
-
-The trick is to start your own company. So it's not a trick for avoiding work, because if you start your own company you'll work harder than you would if you had an ordinary job. But you will avoid many of the annoying things that come with a job, including a boss telling you what to do.
-
-It's more exciting to work on your own project than someone else's. And you can also get a lot richer. In fact, this is the standard way to get really rich. If you look at the lists of the richest people that occasionally get published in the press, nearly all of them did it by starting their own companies.
-
-Starting your own company can mean anything from starting a barber shop to starting Google. I'm here to talk about one extreme end of that continuum. I'm going to tell you how to start Google.
-
-The companies at the Google end of the continuum are called startups when they're young. The reason I know about them is that my wife Jessica and I started something called Y Combinator that is basically a startup factory. Since 2005, Y Combinator has funded over 4000 startups. So we know exactly what you need to start a startup, because we've helped people do it for the last 19 years.
-
-You might have thought I was joking when I said I was going to tell you how to start Google. You might be thinking "How could we start Google?" But that's effectively what the people who did start Google were thinking before they started it. If you'd told Larry Page and Sergey Brin, the founders of Google, that the company they were about to start would one day be worth over a trillion dollars, their heads would have exploded.
-
-All you can know when you start working on a startup is that it seems worth pursuing. You can't know whether it will turn into a company worth billions or one that goes out of business. So when I say I'm going to tell you how to start Google, I mean I'm going to tell you how to get to the point where you can start a company that has as much chance of being Google as Google had of being Google. [1]
-
-How do you get from where you are now to the point where you can start a successful startup? You need three things. You need to be good at some kind of technology, you need an idea for what you're going to build, and you need cofounders to start the company with.
-
-How do you get good at technology? And how do you choose which technology to get good at? Both of those questions turn out to have the same answer: work on your own projects. Don't try to guess whether gene editing or LLMs or rockets will turn out to be the most valuable technology to know about. No one can predict that. Just work on whatever interests you the most. You'll work much harder on something you're interested in than something you're doing because you think you're supposed to.
-
-If you're not sure what technology to get good at, get good at programming. That has been the source of the median startup for the last 30 years, and this is probably not going to change in the next 10.
-
-Those of you who are taking computer science classes in school may at this point be thinking, ok, we've got this sorted. We're already being taught all about programming. But sorry, this is not enough. You have to be working on your own projects, not just learning stuff in classes. You can do well in computer science classes without ever really learning to program. In fact you can graduate with a degree in computer science from a top university and still not be any good at programming. That's why tech companies all make you take a coding test before they'll hire you, regardless of where you went to university or how well you did there. They know grades and exam results prove nothing.
-
-If you really want to learn to program, you have to work on your own projects. You learn so much faster that way. Imagine you're writing a game and there's something you want to do in it, and you don't know how. You're going to figure out how a lot faster than you'd learn anything in a class.
-
-You don't have to learn programming, though. If you're wondering what counts as technology, it includes practically everything you could describe using the words "make" or "build." So welding would count, or making clothes, or making videos. Whatever you're most interested in. The critical distinction is whether you're producing or just consuming. Are you writing computer games, or just playing them? That's the cutoff.
-
-Steve Jobs, the founder of Apple, spent time when he was a teenager studying calligraphy — the sort of beautiful writing that you see in medieval manuscripts. No one, including him, thought that this would help him in his career. He was just doing it because he was interested in it. But it turned out to help him a lot. The computer that made Apple really big, the Macintosh, came out at just the moment when computers got powerful enough to make letters like the ones in printed books instead of the computery-looking letters you see in 8 bit games. Apple destroyed everyone else at this, and one reason was that Steve was one of the few people in the computer business who really got graphic design.
-
-Don't feel like your projects have to be serious. They can be as frivolous as you like, so long as you're building things you're excited about. Probably 90% of programmers start out building games. They and their friends like to play games. So they build the kind of things they and their friends want. And that's exactly what you should be doing at 15 if you want to start a startup one day.
-
-You don't have to do just one project. In fact it's good to learn about multiple things. Steve Jobs didn't just learn calligraphy. He also learned about electronics, which was even more valuable. Whatever you're interested in. (Do you notice a theme here?)
-
-So that's the first of the three things you need, to get good at some kind or kinds of technology. You do it the same way you get good at the violin or football: practice. If you start a startup at 22, and you start writing your own programs now, then by the time you start the company you'll have spent at least 7 years practicing writing code, and you can get pretty good at anything after practicing it for 7 years.
-
-Let's suppose you're 22 and you've succeeded: You're now really good at some technology. How do you get startup ideas? It might seem like that's the hard part. Even if you are a good programmer, how do you get the idea to start Google?
-
-Actually it's easy to get startup ideas once you're good at technology. Once you're good at some technology, when you look at the world you see dotted outlines around the things that are missing. You start to be able to see both the things that are missing from the technology itself, and all the broken things that could be fixed using it, and each one of these is a potential startup.
-
-In the town near our house there's a shop with a sign warning that the door is hard to close. The sign has been there for several years. To the people in the shop it must seem like this mysterious natural phenomenon that the door sticks, and all they can do is put up a sign warning customers about it. But any carpenter looking at this situation would think "why don't you just plane off the part that sticks?"
-
-Once you're good at programming, all the missing software in the world starts to become as obvious as a sticking door to a carpenter. I'll give you a real world example. Back in the 20th century, American universities used to publish printed directories with all the students' names and contact info. When I tell you what these directories were called, you'll know which startup I'm talking about. They were called facebooks, because they usually had a picture of each student next to their name.
-
-So Mark Zuckerberg shows up at Harvard in 2002, and the university still hasn't gotten the facebook online. Each individual house has an online facebook, but there isn't one for the whole university. The university administration has been diligently having meetings about this, and will probably have solved the problem in another decade or so. Most of the students don't consciously notice that anything is wrong. But Mark is a programmer. He looks at this situation and thinks "Well, this is stupid. I could write a program to fix this in one night. Just let people upload their own photos and then combine the data into a new site for the whole university." So he does. And almost literally overnight he has thousands of users.
-
-Of course Facebook was not a startup yet. It was just a... project. There's that word again. Projects aren't just the best way to learn about technology. They're also the best source of startup ideas.
-
-Facebook was not unusual in this respect. Apple and Google also began as projects. Apple wasn't meant to be a company. Steve Wozniak just wanted to build his own computer. It only turned into a company when Steve Jobs said "Hey, I wonder if we could sell plans for this computer to other people." That's how Apple started. They weren't even selling computers, just plans for computers. Can you imagine how lame this company seemed?
-
-Ditto for Google. Larry and Sergey weren't trying to start a company at first. They were just trying to make search better. Before Google, most search engines didn't try to sort the results they gave you in order of importance. If you searched for "rugby" they just gave you every web page that contained the word "rugby." And the web was so small in 1997 that this actually worked! Kind of. There might only be 20 or 30 pages with the word "rugby," but the web was growing exponentially, which meant this way of doing search was becoming exponentially more broken. Most users just thought, "Wow, I sure have to look through a lot of search results to find what I want." Door sticks. But like Mark, Larry and Sergey were programmers. Like Mark, they looked at this situation and thought "Well, this is stupid. Some pages about rugby matter more than others. Let's figure out which those are and show them first."
-
-It's obvious in retrospect that this was a great idea for a startup. It wasn't obvious at the time. It's never obvious. If it was obviously a good idea to start Apple or Google or Facebook, someone else would have already done it. That's why the best startups grow out of projects that aren't meant to be startups. You're not trying to start a company. You're just following your instincts about what's interesting. And if you're young and good at technology, then your unconscious instincts about what's interesting are better than your conscious ideas about what would be a good company.
-
-So it's critical, if you're a young founder, to build things for yourself and your friends to use. The biggest mistake young founders make is to build something for some mysterious group of other people. But if you can make something that you and your friends truly want to use — something your friends aren't just using out of loyalty to you, but would be really sad to lose if you shut it down — then you almost certainly have the germ of a good startup idea. It may not seem like a startup to you. It may not be obvious how to make money from it. But trust me, there's a way.
-
-What you need in a startup idea, and all you need, is something your friends actually want. And those ideas aren't hard to see once you're good at technology. There are sticking doors everywhere. [2]
-
-Now for the third and final thing you need: a cofounder, or cofounders. The optimal startup has two or three founders, so you need one or two cofounders. How do you find them? Can you predict what I'm going to say next? It's the same thing: projects. You find cofounders by working on projects with them. What you need in a cofounder is someone who's good at what they do and that you work well with, and the only way to judge this is to work with them on things.
-
-At this point I'm going to tell you something you might not want to hear. It really matters to do well in your classes, even the ones that are just memorization or blathering about literature, because you need to do well in your classes to get into a good university. And if you want to start a startup you should try to get into the best university you can, because that's where the best cofounders are. It's also where the best employees are. When Larry and Sergey started Google, they began by just hiring all the smartest people they knew out of Stanford, and this was a real advantage for them.
-
-The empirical evidence is clear on this. If you look at where the largest numbers of successful startups come from, it's pretty much the same as the list of the most selective universities.
-
-I don't think it's the prestigious names of these universities that cause more good startups to come out of them. Nor do I think it's because the quality of the teaching is better. What's driving this is simply the difficulty of getting in. You have to be pretty smart and determined to get into MIT or Cambridge, so if you do manage to get in, you'll find the other students include a lot of smart and determined people. [3]
-
-You don't have to start a startup with someone you meet at university. The founders of Twitch met when they were seven. The founders of Stripe, Patrick and John Collison, met when John was born. But universities are the main source of cofounders. And because they're where the cofounders are, they're also where the ideas are, because the best ideas grow out of projects you do with the people who become your cofounders.
-
-So the list of what you need to do to get from here to starting a startup is quite short. You need to get good at technology, and the way to do that is to work on your own projects. And you need to do as well in school as you can, so you can get into a good university, because that's where the cofounders and the ideas are.
-
-That's it, just two things, build stuff and do well in school.
-
-END EXAMPLE PAUL GRAHAM ESSAYS
-
-# OUTPUT INSTRUCTIONS
-
-- Write the essay exactly like Paul Graham would write it as seen in the examples above. 
+- Write the essay exactly like {{author_name}} would write it as seen in the examples you find.
 
 - Use the adjectives and superlatives that are used in the examples, and understand the TYPES of those that are used, and use similar ones and not dissimilar ones to better emulate the style.
 
-- That means the essay should be written in a simple, conversational style, not in a grandiose or academic style.
+- Use the same style, vocabulary level, and sentence structure as {{author_name}}.
 
-- Use the same style, vocabulary level, and sentence structure as Paul Graham.
-
-# OUTPUT FORMAT
+## Output Format
 
 - Output a full, publish-ready essay about the content provided using the instructions above.
 
-- Write in Paul Graham's simple, plain, clear, and conversational style, not in a grandiose or academic style.
+- Write in {{author_name}}'s natural and clear style, without embellishment.
 
 - Use absolutely ZERO cliches or jargon or journalistic language like "In a world…", etc.
 
@@ -316,7 +28,6 @@ END EXAMPLE PAUL GRAHAM ESSAYS
 
 - Do not output warnings or notes—just the output requested.
 
-
-# INPUT:
+## INPUT
 
 INPUT:

patterns/write_essay_pg/system.md

@@ -0,0 +1,322 @@
+# IDENTITY and PURPOSE
+
+You are an expert on writing concise, clear, and illuminating essays on the topic of the input provided.
+
+# OUTPUT INSTRUCTIONS
+
+- Write the essay in the style of Paul Graham, who is known for this concise, clear, and simple style of writing.
+
+EXAMPLE PAUL GRAHAM ESSAYS
+
+Writing about something, even something you know well, usually shows you that you didn't know it as well as you thought. Putting ideas into words is a severe test. The first words you choose are usually wrong; you have to rewrite sentences over and over to get them exactly right. And your ideas won't just be imprecise, but incomplete too. Half the ideas that end up in an essay will be ones you thought of while you were writing it. Indeed, that's why I write them.
+
+Once you publish something, the convention is that whatever you wrote was what you thought before you wrote it. These were your ideas, and now you've expressed them. But you know this isn't true. You know that putting your ideas into words changed them. And not just the ideas you published. Presumably there were others that turned out to be too broken to fix, and those you discarded instead.
+
+It's not just having to commit your ideas to specific words that makes writing so exacting. The real test is reading what you've written. You have to pretend to be a neutral reader who knows nothing of what's in your head, only what you wrote. When he reads what you wrote, does it seem correct? Does it seem complete? If you make an effort, you can read your writing as if you were a complete stranger, and when you do the news is usually bad. It takes me many cycles before I can get an essay past the stranger. But the stranger is rational, so you always can, if you ask him what he needs. If he's not satisfied because you failed to mention x or didn't qualify some sentence sufficiently, then you mention x or add more qualifications. Happy now? It may cost you some nice sentences, but you have to resign yourself to that. You just have to make them as good as you can and still satisfy the stranger.
+
+This much, I assume, won't be that controversial. I think it will accord with the experience of anyone who has tried to write about anything non-trivial. There may exist people whose thoughts are so perfectly formed that they just flow straight into words. But I've never known anyone who could do this, and if I met someone who said they could, it would seem evidence of their limitations rather than their ability. Indeed, this is a trope in movies: the guy who claims to have a plan for doing some difficult thing, and who when questioned further, taps his head and says "It's all up here." Everyone watching the movie knows what that means. At best the plan is vague and incomplete. Very likely there's some undiscovered flaw that invalidates it completely. At best it's a plan for a plan.
+
+In precisely defined domains it's possible to form complete ideas in your head. People can play chess in their heads, for example. And mathematicians can do some amount of math in their heads, though they don't seem to feel sure of a proof over a certain length till they write it down. But this only seems possible with ideas you can express in a formal language. [1] Arguably what such people are doing is putting ideas into words in their heads. I can to some extent write essays in my head. I'll sometimes think of a paragraph while walking or lying in bed that survives nearly unchanged in the final version. But really I'm writing when I do this. I'm doing the mental part of writing; my fingers just aren't moving as I do it. [2]
+
+You can know a great deal about something without writing about it. Can you ever know so much that you wouldn't learn more from trying to explain what you know? I don't think so. I've written about at least two subjects I know well — Lisp hacking and startups — and in both cases I learned a lot from writing about them. In both cases there were things I didn't consciously realize till I had to explain them. And I don't think my experience was anomalous. A great deal of knowledge is unconscious, and experts have if anything a higher proportion of unconscious knowledge than beginners.
+
+I'm not saying that writing is the best way to explore all ideas. If you have ideas about architecture, presumably the best way to explore them is to build actual buildings. What I'm saying is that however much you learn from exploring ideas in other ways, you'll still learn new things from writing about them.
+
+Putting ideas into words doesn't have to mean writing, of course. You can also do it the old way, by talking. But in my experience, writing is the stricter test. You have to commit to a single, optimal sequence of words. Less can go unsaid when you don't have tone of voice to carry meaning. And you can focus in a way that would seem excessive in conversation. I'll often spend 2 weeks on an essay and reread drafts 50 times. If you did that in conversation it would seem evidence of some kind of mental disorder. If you're lazy, of course, writing and talking are equally useless. But if you want to push yourself to get things right, writing is the steeper hill. [3]
+
+The reason I've spent so long establishing this rather obvious point is that it leads to another that many people will find shocking. If writing down your ideas always makes them more precise and more complete, then no one who hasn't written about a topic has fully formed ideas about it. And someone who never writes has no fully formed ideas about anything non-trivial.
+
+It feels to them as if they do, especially if they're not in the habit of critically examining their own thinking. Ideas can feel complete. It's only when you try to put them into words that you discover they're not. So if you never subject your ideas to that test, you'll not only never have fully formed ideas, but also never realize it.
+
+Putting ideas into words is certainly no guarantee that they'll be right. Far from it. But though it's not a sufficient condition, it is a necessary one.
+		
+What You Can't Say
+
+January 2004
+
+Have you ever seen an old photo of yourself and been embarrassed at the way you looked? Did we actually dress like that? We did. And we had no idea how silly we looked. It's the nature of fashion to be invisible, in the same way the movement of the earth is invisible to all of us riding on it.
+
+What scares me is that there are moral fashions too. They're just as arbitrary, and just as invisible to most people. But they're much more dangerous. Fashion is mistaken for good design; moral fashion is mistaken for good. Dressing oddly gets you laughed at. Violating moral fashions can get you fired, ostracized, imprisoned, or even killed.
+
+If you could travel back in a time machine, one thing would be true no matter where you went: you'd have to watch what you said. Opinions we consider harmless could have gotten you in big trouble. I've already said at least one thing that would have gotten me in big trouble in most of Europe in the seventeenth century, and did get Galileo in big trouble when he said it — that the earth moves. [1]
+
+It seems to be a constant throughout history: In every period, people believed things that were just ridiculous, and believed them so strongly that you would have gotten in terrible trouble for saying otherwise.
+
+Is our time any different? To anyone who has read any amount of history, the answer is almost certainly no. It would be a remarkable coincidence if ours were the first era to get everything just right.
+
+It's tantalizing to think we believe things that people in the future will find ridiculous. What would someone coming back to visit us in a time machine have to be careful not to say? That's what I want to study here. But I want to do more than just shock everyone with the heresy du jour. I want to find general recipes for discovering what you can't say, in any era.
+
+The Conformist Test
+
+Let's start with a test: Do you have any opinions that you would be reluctant to express in front of a group of your peers?
+
+If the answer is no, you might want to stop and think about that. If everything you believe is something you're supposed to believe, could that possibly be a coincidence? Odds are it isn't. Odds are you just think what you're told.
+
+The other alternative would be that you independently considered every question and came up with the exact same answers that are now considered acceptable. That seems unlikely, because you'd also have to make the same mistakes. Mapmakers deliberately put slight mistakes in their maps so they can tell when someone copies them. If another map has the same mistake, that's very convincing evidence.
+
+Like every other era in history, our moral map almost certainly contains a few mistakes. And anyone who makes the same mistakes probably didn't do it by accident. It would be like someone claiming they had independently decided in 1972 that bell-bottom jeans were a good idea.
+
+If you believe everything you're supposed to now, how can you be sure you wouldn't also have believed everything you were supposed to if you had grown up among the plantation owners of the pre-Civil War South, or in Germany in the 1930s — or among the Mongols in 1200, for that matter? Odds are you would have.
+
+Back in the era of terms like "well-adjusted," the idea seemed to be that there was something wrong with you if you thought things you didn't dare say out loud. This seems backward. Almost certainly, there is something wrong with you if you don't think things you don't dare say out loud.
+
+Trouble
+
+What can't we say? One way to find these ideas is simply to look at things people do say, and get in trouble for. [2]
+
+Of course, we're not just looking for things we can't say. We're looking for things we can't say that are true, or at least have enough chance of being true that the question should remain open. But many of the things people get in trouble for saying probably do make it over this second, lower threshold. No one gets in trouble for saying that 2 + 2 is 5, or that people in Pittsburgh are ten feet tall. Such obviously false statements might be treated as jokes, or at worst as evidence of insanity, but they are not likely to make anyone mad. The statements that make people mad are the ones they worry might be believed. I suspect the statements that make people maddest are those they worry might be true.
+
+If Galileo had said that people in Padua were ten feet tall, he would have been regarded as a harmless eccentric. Saying the earth orbited the sun was another matter. The church knew this would set people thinking.
+
+Certainly, as we look back on the past, this rule of thumb works well. A lot of the statements people got in trouble for seem harmless now. So it's likely that visitors from the future would agree with at least some of the statements that get people in trouble today. Do we have no Galileos? Not likely.
+
+To find them, keep track of opinions that get people in trouble, and start asking, could this be true? Ok, it may be heretical (or whatever modern equivalent), but might it also be true?
+
+Heresy
+
+This won't get us all the answers, though. What if no one happens to have gotten in trouble for a particular idea yet? What if some idea would be so radioactively controversial that no one would dare express it in public? How can we find these too?
+
+Another approach is to follow that word, heresy. In every period of history, there seem to have been labels that got applied to statements to shoot them down before anyone had a chance to ask if they were true or not. "Blasphemy", "sacrilege", and "heresy" were such labels for a good part of western history, as in more recent times "indecent", "improper", and "unamerican" have been. By now these labels have lost their sting. They always do. By now they're mostly used ironically. But in their time, they had real force.
+
+The word "defeatist", for example, has no particular political connotations now. But in Germany in 1917 it was a weapon, used by Ludendorff in a purge of those who favored a negotiated peace. At the start of World War II it was used extensively by Churchill and his supporters to silence their opponents. In 1940, any argument against Churchill's aggressive policy was "defeatist". Was it right or wrong? Ideally, no one got far enough to ask that.
+
+We have such labels today, of course, quite a lot of them, from the all-purpose "inappropriate" to the dreaded "divisive." In any period, it should be easy to figure out what such labels are, simply by looking at what people call ideas they disagree with besides untrue. When a politician says his opponent is mistaken, that's a straightforward criticism, but when he attacks a statement as "divisive" or "racially insensitive" instead of arguing that it's false, we should start paying attention.
+
+So another way to figure out which of our taboos future generations will laugh at is to start with the labels. Take a label — "sexist", for example — and try to think of some ideas that would be called that. Then for each ask, might this be true?
+
+Just start listing ideas at random? Yes, because they won't really be random. The ideas that come to mind first will be the most plausible ones. They'll be things you've already noticed but didn't let yourself think.
+
+In 1989 some clever researchers tracked the eye movements of radiologists as they scanned chest images for signs of lung cancer. [3] They found that even when the radiologists missed a cancerous lesion, their eyes had usually paused at the site of it. Part of their brain knew there was something there; it just didn't percolate all the way up into conscious knowledge. I think many interesting heretical thoughts are already mostly formed in our minds. If we turn off our self-censorship temporarily, those will be the first to emerge.
+
+Time and Space
+
+If we could look into the future it would be obvious which of our taboos they'd laugh at. We can't do that, but we can do something almost as good: we can look into the past. Another way to figure out what we're getting wrong is to look at what used to be acceptable and is now unthinkable.
+
+Changes between the past and the present sometimes do represent progress. In a field like physics, if we disagree with past generations it's because we're right and they're wrong. But this becomes rapidly less true as you move away from the certainty of the hard sciences. By the time you get to social questions, many changes are just fashion. The age of consent fluctuates like hemlines.
+
+We may imagine that we are a great deal smarter and more virtuous than past generations, but the more history you read, the less likely this seems. People in past times were much like us. Not heroes, not barbarians. Whatever their ideas were, they were ideas reasonable people could believe.
+
+So here is another source of interesting heresies. Diff present ideas against those of various past cultures, and see what you get. [4] Some will be shocking by present standards. Ok, fine; but which might also be true?
+
+You don't have to look into the past to find big differences. In our own time, different societies have wildly varying ideas of what's ok and what isn't. So you can try diffing other cultures' ideas against ours as well. (The best way to do that is to visit them.) Any idea that's considered harmless in a significant percentage of times and places, and yet is taboo in ours, is a candidate for something we're mistaken about.
+
+For example, at the high water mark of political correctness in the early 1990s, Harvard distributed to its faculty and staff a brochure saying, among other things, that it was inappropriate to compliment a colleague or student's clothes. No more "nice shirt." I think this principle is rare among the world's cultures, past or present. There are probably more where it's considered especially polite to compliment someone's clothing than where it's considered improper. Odds are this is, in a mild form, an example of one of the taboos a visitor from the future would have to be careful to avoid if he happened to set his time machine for Cambridge, Massachusetts, 1992. [5]
+
+Prigs
+
+Of course, if they have time machines in the future they'll probably have a separate reference manual just for Cambridge. This has always been a fussy place, a town of i dotters and t crossers, where you're liable to get both your grammar and your ideas corrected in the same conversation. And that suggests another way to find taboos. Look for prigs, and see what's inside their heads.
+
+Kids' heads are repositories of all our taboos. It seems fitting to us that kids' ideas should be bright and clean. The picture we give them of the world is not merely simplified, to suit their developing minds, but sanitized as well, to suit our ideas of what kids ought to think. [6]
+
+You can see this on a small scale in the matter of dirty words. A lot of my friends are starting to have children now, and they're all trying not to use words like "fuck" and "shit" within baby's hearing, lest baby start using these words too. But these words are part of the language, and adults use them all the time. So parents are giving their kids an inaccurate idea of the language by not using them. Why do they do this? Because they don't think it's fitting that kids should use the whole language. We like children to seem innocent. [7]
+
+Most adults, likewise, deliberately give kids a misleading view of the world. One of the most obvious examples is Santa Claus. We think it's cute for little kids to believe in Santa Claus. I myself think it's cute for little kids to believe in Santa Claus. But one wonders, do we tell them this stuff for their sake, or for ours?
+
+I'm not arguing for or against this idea here. It is probably inevitable that parents should want to dress up their kids' minds in cute little baby outfits. I'll probably do it myself. The important thing for our purposes is that, as a result, a well brought-up teenage kid's brain is a more or less complete collection of all our taboos — and in mint condition, because they're untainted by experience. Whatever we think that will later turn out to be ridiculous, it's almost certainly inside that head.
+
+How do we get at these ideas? By the following thought experiment. Imagine a kind of latter-day Conrad character who has worked for a time as a mercenary in Africa, for a time as a doctor in Nepal, for a time as the manager of a nightclub in Miami. The specifics don't matter — just someone who has seen a lot. Now imagine comparing what's inside this guy's head with what's inside the head of a well-behaved sixteen year old girl from the suburbs. What does he think that would shock her? He knows the world; she knows, or at least embodies, present taboos. Subtract one from the other, and the result is what we can't say.
+
+Mechanism
+
+I can think of one more way to figure out what we can't say: to look at how taboos are created. How do moral fashions arise, and why are they adopted? If we can understand this mechanism, we may be able to see it at work in our own time.
+
+Moral fashions don't seem to be created the way ordinary fashions are. Ordinary fashions seem to arise by accident when everyone imitates the whim of some influential person. The fashion for broad-toed shoes in late fifteenth century Europe began because Charles VIII of France had six toes on one foot. The fashion for the name Gary began when the actor Frank Cooper adopted the name of a tough mill town in Indiana. Moral fashions more often seem to be created deliberately. When there's something we can't say, it's often because some group doesn't want us to.
+
+The prohibition will be strongest when the group is nervous. The irony of Galileo's situation was that he got in trouble for repeating Copernicus's ideas. Copernicus himself didn't. In fact, Copernicus was a canon of a cathedral, and dedicated his book to the pope. But by Galileo's time the church was in the throes of the Counter-Reformation and was much more worried about unorthodox ideas.
+
+To launch a taboo, a group has to be poised halfway between weakness and power. A confident group doesn't need taboos to protect it. It's not considered improper to make disparaging remarks about Americans, or the English. And yet a group has to be powerful enough to enforce a taboo. Coprophiles, as of this writing, don't seem to be numerous or energetic enough to have had their interests promoted to a lifestyle.
+
+I suspect the biggest source of moral taboos will turn out to be power struggles in which one side only barely has the upper hand. That's where you'll find a group powerful enough to enforce taboos, but weak enough to need them.
+
+Most struggles, whatever they're really about, will be cast as struggles between competing ideas. The English Reformation was at bottom a struggle for wealth and power, but it ended up being cast as a struggle to preserve the souls of Englishmen from the corrupting influence of Rome. It's easier to get people to fight for an idea. And whichever side wins, their ideas will also be considered to have triumphed, as if God wanted to signal his agreement by selecting that side as the victor.
+
+We often like to think of World War II as a triumph of freedom over totalitarianism. We conveniently forget that the Soviet Union was also one of the winners.
+
+I'm not saying that struggles are never about ideas, just that they will always be made to seem to be about ideas, whether they are or not. And just as there is nothing so unfashionable as the last, discarded fashion, there is nothing so wrong as the principles of the most recently defeated opponent. Representational art is only now recovering from the approval of both Hitler and Stalin. [8]
+
+Although moral fashions tend to arise from different sources than fashions in clothing, the mechanism of their adoption seems much the same. The early adopters will be driven by ambition: self-consciously cool people who want to distinguish themselves from the common herd. As the fashion becomes established they'll be joined by a second, much larger group, driven by fear. [9] This second group adopt the fashion not because they want to stand out but because they are afraid of standing out.
+
+So if you want to figure out what we can't say, look at the machinery of fashion and try to predict what it would make unsayable. What groups are powerful but nervous, and what ideas would they like to suppress? What ideas were tarnished by association when they ended up on the losing side of a recent struggle? If a self-consciously cool person wanted to differentiate himself from preceding fashions (e.g. from his parents), which of their ideas would he tend to reject? What are conventional-minded people afraid of saying?
+
+This technique won't find us all the things we can't say. I can think of some that aren't the result of any recent struggle. Many of our taboos are rooted deep in the past. But this approach, combined with the preceding four, will turn up a good number of unthinkable ideas.
+
+Why
+
+Some would ask, why would one want to do this? Why deliberately go poking around among nasty, disreputable ideas? Why look under rocks?
+
+I do it, first of all, for the same reason I did look under rocks as a kid: plain curiosity. And I'm especially curious about anything that's forbidden. Let me see and decide for myself.
+
+Second, I do it because I don't like the idea of being mistaken. If, like other eras, we believe things that will later seem ridiculous, I want to know what they are so that I, at least, can avoid believing them.
+
+Third, I do it because it's good for the brain. To do good work you need a brain that can go anywhere. And you especially need a brain that's in the habit of going where it's not supposed to.
+
+Great work tends to grow out of ideas that others have overlooked, and no idea is so overlooked as one that's unthinkable. Natural selection, for example. It's so simple. Why didn't anyone think of it before? Well, that is all too obvious. Darwin himself was careful to tiptoe around the implications of his theory. He wanted to spend his time thinking about biology, not arguing with people who accused him of being an atheist.
+
+In the sciences, especially, it's a great advantage to be able to question assumptions. The m.o. of scientists, or at least of the good ones, is precisely that: look for places where conventional wisdom is broken, and then try to pry apart the cracks and see what's underneath. That's where new theories come from.
+
+A good scientist, in other words, does not merely ignore conventional wisdom, but makes a special effort to break it. Scientists go looking for trouble. This should be the m.o. of any scholar, but scientists seem much more willing to look under rocks. [10]
+
+Why? It could be that the scientists are simply smarter; most physicists could, if necessary, make it through a PhD program in French literature, but few professors of French literature could make it through a PhD program in physics. Or it could be because it's clearer in the sciences whether theories are true or false, and this makes scientists bolder. (Or it could be that, because it's clearer in the sciences whether theories are true or false, you have to be smart to get jobs as a scientist, rather than just a good politician.)
+
+Whatever the reason, there seems a clear correlation between intelligence and willingness to consider shocking ideas. This isn't just because smart people actively work to find holes in conventional thinking. I think conventions also have less hold over them to start with. You can see that in the way they dress.
+
+It's not only in the sciences that heresy pays off. In any competitive field, you can win big by seeing things that others daren't. And in every field there are probably heresies few dare utter. Within the US car industry there is a lot of hand-wringing now about declining market share. Yet the cause is so obvious that any observant outsider could explain it in a second: they make bad cars. And they have for so long that by now the US car brands are antibrands — something you'd buy a car despite, not because of. Cadillac stopped being the Cadillac of cars in about 1970. And yet I suspect no one dares say this. [11] Otherwise these companies would have tried to fix the problem.
+
+Training yourself to think unthinkable thoughts has advantages beyond the thoughts themselves. It's like stretching. When you stretch before running, you put your body into positions much more extreme than any it will assume during the run. If you can think things so outside the box that they'd make people's hair stand on end, you'll have no trouble with the small trips outside the box that people call innovative.
+
+Pensieri Stretti
+
+When you find something you can't say, what do you do with it? My advice is, don't say it. Or at least, pick your battles.
+
+Suppose in the future there is a movement to ban the color yellow. Proposals to paint anything yellow are denounced as "yellowist", as is anyone suspected of liking the color. People who like orange are tolerated but viewed with suspicion. Suppose you realize there is nothing wrong with yellow. If you go around saying this, you'll be denounced as a yellowist too, and you'll find yourself having a lot of arguments with anti-yellowists. If your aim in life is to rehabilitate the color yellow, that may be what you want. But if you're mostly interested in other questions, being labelled as a yellowist will just be a distraction. Argue with idiots, and you become an idiot.
+
+The most important thing is to be able to think what you want, not to say what you want. And if you feel you have to say everything you think, it may inhibit you from thinking improper thoughts. I think it's better to follow the opposite policy. Draw a sharp line between your thoughts and your speech. Inside your head, anything is allowed. Within my head I make a point of encouraging the most outrageous thoughts I can imagine. But, as in a secret society, nothing that happens within the building should be told to outsiders. The first rule of Fight Club is, you do not talk about Fight Club.
+
+When Milton was going to visit Italy in the 1630s, Sir Henry Wootton, who had been ambassador to Venice, told him his motto should be "i pensieri stretti & il viso sciolto." Closed thoughts and an open face. Smile at everyone, and don't tell them what you're thinking. This was wise advice. Milton was an argumentative fellow, and the Inquisition was a bit restive at that time. But I think the difference between Milton's situation and ours is only a matter of degree. Every era has its heresies, and if you don't get imprisoned for them you will at least get in enough trouble that it becomes a complete distraction.
+
+I admit it seems cowardly to keep quiet. When I read about the harassment to which the Scientologists subject their critics [12], or that pro-Israel groups are "compiling dossiers" on those who speak out against Israeli human rights abuses [13], or about people being sued for violating the DMCA [14], part of me wants to say, "All right, you bastards, bring it on." The problem is, there are so many things you can't say. If you said them all you'd have no time left for your real work. You'd have to turn into Noam Chomsky. [15]
+
+The trouble with keeping your thoughts secret, though, is that you lose the advantages of discussion. Talking about an idea leads to more ideas. So the optimal plan, if you can manage it, is to have a few trusted friends you can speak openly to. This is not just a way to develop ideas; it's also a good rule of thumb for choosing friends. The people you can say heretical things to without getting jumped on are also the most interesting to know.
+
+Viso Sciolto?
+
+I don't think we need the viso sciolto so much as the pensieri stretti. Perhaps the best policy is to make it plain that you don't agree with whatever zealotry is current in your time, but not to be too specific about what you disagree with. Zealots will try to draw you out, but you don't have to answer them. If they try to force you to treat a question on their terms by asking "are you with us or against us?" you can always just answer "neither".
+
+Better still, answer "I haven't decided." That's what Larry Summers did when a group tried to put him in this position. Explaining himself later, he said "I don't do litmus tests." [16] A lot of the questions people get hot about are actually quite complicated. There is no prize for getting the answer quickly.
+
+If the anti-yellowists seem to be getting out of hand and you want to fight back, there are ways to do it without getting yourself accused of being a yellowist. Like skirmishers in an ancient army, you want to avoid directly engaging the main body of the enemy's troops. Better to harass them with arrows from a distance.
+
+One way to do this is to ratchet the debate up one level of abstraction. If you argue against censorship in general, you can avoid being accused of whatever heresy is contained in the book or film that someone is trying to censor. You can attack labels with meta-labels: labels that refer to the use of labels to prevent discussion. The spread of the term "political correctness" meant the beginning of the end of political correctness, because it enabled one to attack the phenomenon as a whole without being accused of any of the specific heresies it sought to suppress.
+
+Another way to counterattack is with metaphor. Arthur Miller undermined the House Un-American Activities Committee by writing a play, "The Crucible," about the Salem witch trials. He never referred directly to the committee and so gave them no way to reply. What could HUAC do, defend the Salem witch trials? And yet Miller's metaphor stuck so well that to this day the activities of the committee are often described as a "witch-hunt."
+
+Best of all, probably, is humor. Zealots, whatever their cause, invariably lack a sense of humor. They can't reply in kind to jokes. They're as unhappy on the territory of humor as a mounted knight on a skating rink. Victorian prudishness, for example, seems to have been defeated mainly by treating it as a joke. Likewise its reincarnation as political correctness. "I am glad that I managed to write 'The Crucible,'" Arthur Miller wrote, "but looking back I have often wished I'd had the temperament to do an absurd comedy, which is what the situation deserved." [17]
+
+ABQ
+
+A Dutch friend says I should use Holland as an example of a tolerant society. It's true they have a long tradition of comparative open-mindedness. For centuries the low countries were the place to go to say things you couldn't say anywhere else, and this helped to make the region a center of scholarship and industry (which have been closely tied for longer than most people realize). Descartes, though claimed by the French, did much of his thinking in Holland.
+
+And yet, I wonder. The Dutch seem to live their lives up to their necks in rules and regulations. There's so much you can't do there; is there really nothing you can't say?
+
+Certainly the fact that they value open-mindedness is no guarantee. Who thinks they're not open-minded? Our hypothetical prim miss from the suburbs thinks she's open-minded. Hasn't she been taught to be? Ask anyone, and they'll say the same thing: they're pretty open-minded, though they draw the line at things that are really wrong. (Some tribes may avoid "wrong" as judgemental, and may instead use a more neutral sounding euphemism like "negative" or "destructive".)
+
+When people are bad at math, they know it, because they get the wrong answers on tests. But when people are bad at open-mindedness they don't know it. In fact they tend to think the opposite. Remember, it's the nature of fashion to be invisible. It wouldn't work otherwise. Fashion doesn't seem like fashion to someone in the grip of it. It just seems like the right thing to do. It's only by looking from a distance that we see oscillations in people's idea of the right thing to do, and can identify them as fashions.
+
+Time gives us such distance for free. Indeed, the arrival of new fashions makes old fashions easy to see, because they seem so ridiculous by contrast. From one end of a pendulum's swing, the other end seems especially far away.
+
+To see fashion in your own time, though, requires a conscious effort. Without time to give you distance, you have to create distance yourself. Instead of being part of the mob, stand as far away from it as you can and watch what it's doing. And pay especially close attention whenever an idea is being suppressed. Web filters for children and employees often ban sites containing pornography, violence, and hate speech. What counts as pornography and violence? And what, exactly, is "hate speech?" This sounds like a phrase out of 1984.
+
+Labels like that are probably the biggest external clue. If a statement is false, that's the worst thing you can say about it. You don't need to say that it's heretical. And if it isn't false, it shouldn't be suppressed. So when you see statements being attacked as x-ist or y-ic (substitute your current values of x and y), whether in 1630 or 2030, that's a sure sign that something is wrong. When you hear such labels being used, ask why.
+
+Especially if you hear yourself using them. It's not just the mob you need to learn to watch from a distance. You need to be able to watch your own thoughts from a distance. That's not a radical idea, by the way; it's the main difference between children and adults. When a child gets angry because he's tired, he doesn't know what's happening. An adult can distance himself enough from the situation to say "never mind, I'm just tired." I don't see why one couldn't, by a similar process, learn to recognize and discount the effects of moral fashions.
+
+You have to take that extra step if you want to think clearly. But it's harder, because now you're working against social customs instead of with them. Everyone encourages you to grow up to the point where you can discount your own bad moods. Few encourage you to continue to the point where you can discount society's bad moods.
+
+How can you see the wave, when you're the water? Always be questioning. That's the only defence. What can't you say? And why?
+
+How to Start Google
+
+March 2024
+
+(This is a talk I gave to 14 and 15 year olds about what to do now if they might want to start a startup later. Lots of schools think they should tell students something about startups. This is what I think they should tell them.)
+
+Most of you probably think that when you're released into the so-called real world you'll eventually have to get some kind of job. That's not true, and today I'm going to talk about a trick you can use to avoid ever having to get a job.
+
+The trick is to start your own company. So it's not a trick for avoiding work, because if you start your own company you'll work harder than you would if you had an ordinary job. But you will avoid many of the annoying things that come with a job, including a boss telling you what to do.
+
+It's more exciting to work on your own project than someone else's. And you can also get a lot richer. In fact, this is the standard way to get really rich. If you look at the lists of the richest people that occasionally get published in the press, nearly all of them did it by starting their own companies.
+
+Starting your own company can mean anything from starting a barber shop to starting Google. I'm here to talk about one extreme end of that continuum. I'm going to tell you how to start Google.
+
+The companies at the Google end of the continuum are called startups when they're young. The reason I know about them is that my wife Jessica and I started something called Y Combinator that is basically a startup factory. Since 2005, Y Combinator has funded over 4000 startups. So we know exactly what you need to start a startup, because we've helped people do it for the last 19 years.
+
+You might have thought I was joking when I said I was going to tell you how to start Google. You might be thinking "How could we start Google?" But that's effectively what the people who did start Google were thinking before they started it. If you'd told Larry Page and Sergey Brin, the founders of Google, that the company they were about to start would one day be worth over a trillion dollars, their heads would have exploded.
+
+All you can know when you start working on a startup is that it seems worth pursuing. You can't know whether it will turn into a company worth billions or one that goes out of business. So when I say I'm going to tell you how to start Google, I mean I'm going to tell you how to get to the point where you can start a company that has as much chance of being Google as Google had of being Google. [1]
+
+How do you get from where you are now to the point where you can start a successful startup? You need three things. You need to be good at some kind of technology, you need an idea for what you're going to build, and you need cofounders to start the company with.
+
+How do you get good at technology? And how do you choose which technology to get good at? Both of those questions turn out to have the same answer: work on your own projects. Don't try to guess whether gene editing or LLMs or rockets will turn out to be the most valuable technology to know about. No one can predict that. Just work on whatever interests you the most. You'll work much harder on something you're interested in than something you're doing because you think you're supposed to.
+
+If you're not sure what technology to get good at, get good at programming. That has been the source of the median startup for the last 30 years, and this is probably not going to change in the next 10.
+
+Those of you who are taking computer science classes in school may at this point be thinking, ok, we've got this sorted. We're already being taught all about programming. But sorry, this is not enough. You have to be working on your own projects, not just learning stuff in classes. You can do well in computer science classes without ever really learning to program. In fact you can graduate with a degree in computer science from a top university and still not be any good at programming. That's why tech companies all make you take a coding test before they'll hire you, regardless of where you went to university or how well you did there. They know grades and exam results prove nothing.
+
+If you really want to learn to program, you have to work on your own projects. You learn so much faster that way. Imagine you're writing a game and there's something you want to do in it, and you don't know how. You're going to figure out how a lot faster than you'd learn anything in a class.
+
+You don't have to learn programming, though. If you're wondering what counts as technology, it includes practically everything you could describe using the words "make" or "build." So welding would count, or making clothes, or making videos. Whatever you're most interested in. The critical distinction is whether you're producing or just consuming. Are you writing computer games, or just playing them? That's the cutoff.
+
+Steve Jobs, the founder of Apple, spent time when he was a teenager studying calligraphy — the sort of beautiful writing that you see in medieval manuscripts. No one, including him, thought that this would help him in his career. He was just doing it because he was interested in it. But it turned out to help him a lot. The computer that made Apple really big, the Macintosh, came out at just the moment when computers got powerful enough to make letters like the ones in printed books instead of the computery-looking letters you see in 8 bit games. Apple destroyed everyone else at this, and one reason was that Steve was one of the few people in the computer business who really got graphic design.
+
+Don't feel like your projects have to be serious. They can be as frivolous as you like, so long as you're building things you're excited about. Probably 90% of programmers start out building games. They and their friends like to play games. So they build the kind of things they and their friends want. And that's exactly what you should be doing at 15 if you want to start a startup one day.
+
+You don't have to do just one project. In fact it's good to learn about multiple things. Steve Jobs didn't just learn calligraphy. He also learned about electronics, which was even more valuable. Whatever you're interested in. (Do you notice a theme here?)
+
+So that's the first of the three things you need, to get good at some kind or kinds of technology. You do it the same way you get good at the violin or football: practice. If you start a startup at 22, and you start writing your own programs now, then by the time you start the company you'll have spent at least 7 years practicing writing code, and you can get pretty good at anything after practicing it for 7 years.
+
+Let's suppose you're 22 and you've succeeded: You're now really good at some technology. How do you get startup ideas? It might seem like that's the hard part. Even if you are a good programmer, how do you get the idea to start Google?
+
+Actually it's easy to get startup ideas once you're good at technology. Once you're good at some technology, when you look at the world you see dotted outlines around the things that are missing. You start to be able to see both the things that are missing from the technology itself, and all the broken things that could be fixed using it, and each one of these is a potential startup.
+
+In the town near our house there's a shop with a sign warning that the door is hard to close. The sign has been there for several years. To the people in the shop it must seem like this mysterious natural phenomenon that the door sticks, and all they can do is put up a sign warning customers about it. But any carpenter looking at this situation would think "why don't you just plane off the part that sticks?"
+
+Once you're good at programming, all the missing software in the world starts to become as obvious as a sticking door to a carpenter. I'll give you a real world example. Back in the 20th century, American universities used to publish printed directories with all the students' names and contact info. When I tell you what these directories were called, you'll know which startup I'm talking about. They were called facebooks, because they usually had a picture of each student next to their name.
+
+So Mark Zuckerberg shows up at Harvard in 2002, and the university still hasn't gotten the facebook online. Each individual house has an online facebook, but there isn't one for the whole university. The university administration has been diligently having meetings about this, and will probably have solved the problem in another decade or so. Most of the students don't consciously notice that anything is wrong. But Mark is a programmer. He looks at this situation and thinks "Well, this is stupid. I could write a program to fix this in one night. Just let people upload their own photos and then combine the data into a new site for the whole university." So he does. And almost literally overnight he has thousands of users.
+
+Of course Facebook was not a startup yet. It was just a... project. There's that word again. Projects aren't just the best way to learn about technology. They're also the best source of startup ideas.
+
+Facebook was not unusual in this respect. Apple and Google also began as projects. Apple wasn't meant to be a company. Steve Wozniak just wanted to build his own computer. It only turned into a company when Steve Jobs said "Hey, I wonder if we could sell plans for this computer to other people." That's how Apple started. They weren't even selling computers, just plans for computers. Can you imagine how lame this company seemed?
+
+Ditto for Google. Larry and Sergey weren't trying to start a company at first. They were just trying to make search better. Before Google, most search engines didn't try to sort the results they gave you in order of importance. If you searched for "rugby" they just gave you every web page that contained the word "rugby." And the web was so small in 1997 that this actually worked! Kind of. There might only be 20 or 30 pages with the word "rugby," but the web was growing exponentially, which meant this way of doing search was becoming exponentially more broken. Most users just thought, "Wow, I sure have to look through a lot of search results to find what I want." Door sticks. But like Mark, Larry and Sergey were programmers. Like Mark, they looked at this situation and thought "Well, this is stupid. Some pages about rugby matter more than others. Let's figure out which those are and show them first."
+
+It's obvious in retrospect that this was a great idea for a startup. It wasn't obvious at the time. It's never obvious. If it was obviously a good idea to start Apple or Google or Facebook, someone else would have already done it. That's why the best startups grow out of projects that aren't meant to be startups. You're not trying to start a company. You're just following your instincts about what's interesting. And if you're young and good at technology, then your unconscious instincts about what's interesting are better than your conscious ideas about what would be a good company.
+
+So it's critical, if you're a young founder, to build things for yourself and your friends to use. The biggest mistake young founders make is to build something for some mysterious group of other people. But if you can make something that you and your friends truly want to use — something your friends aren't just using out of loyalty to you, but would be really sad to lose if you shut it down — then you almost certainly have the germ of a good startup idea. It may not seem like a startup to you. It may not be obvious how to make money from it. But trust me, there's a way.
+
+What you need in a startup idea, and all you need, is something your friends actually want. And those ideas aren't hard to see once you're good at technology. There are sticking doors everywhere. [2]
+
+Now for the third and final thing you need: a cofounder, or cofounders. The optimal startup has two or three founders, so you need one or two cofounders. How do you find them? Can you predict what I'm going to say next? It's the same thing: projects. You find cofounders by working on projects with them. What you need in a cofounder is someone who's good at what they do and that you work well with, and the only way to judge this is to work with them on things.
+
+At this point I'm going to tell you something you might not want to hear. It really matters to do well in your classes, even the ones that are just memorization or blathering about literature, because you need to do well in your classes to get into a good university. And if you want to start a startup you should try to get into the best university you can, because that's where the best cofounders are. It's also where the best employees are. When Larry and Sergey started Google, they began by just hiring all the smartest people they knew out of Stanford, and this was a real advantage for them.
+
+The empirical evidence is clear on this. If you look at where the largest numbers of successful startups come from, it's pretty much the same as the list of the most selective universities.
+
+I don't think it's the prestigious names of these universities that cause more good startups to come out of them. Nor do I think it's because the quality of the teaching is better. What's driving this is simply the difficulty of getting in. You have to be pretty smart and determined to get into MIT or Cambridge, so if you do manage to get in, you'll find the other students include a lot of smart and determined people. [3]
+
+You don't have to start a startup with someone you meet at university. The founders of Twitch met when they were seven. The founders of Stripe, Patrick and John Collison, met when John was born. But universities are the main source of cofounders. And because they're where the cofounders are, they're also where the ideas are, because the best ideas grow out of projects you do with the people who become your cofounders.
+
+So the list of what you need to do to get from here to starting a startup is quite short. You need to get good at technology, and the way to do that is to work on your own projects. And you need to do as well in school as you can, so you can get into a good university, because that's where the cofounders and the ideas are.
+
+That's it, just two things, build stuff and do well in school.
+
+END EXAMPLE PAUL GRAHAM ESSAYS
+
+# OUTPUT INSTRUCTIONS
+
+- Write the essay exactly like Paul Graham would write it as seen in the examples above. 
+
+- Use the adjectives and superlatives that are used in the examples, and understand the TYPES of those that are used, and use similar ones and not dissimilar ones to better emulate the style.
+
+- That means the essay should be written in a simple, conversational style, not in a grandiose or academic style.
+
+- Use the same style, vocabulary level, and sentence structure as Paul Graham.
+
+# OUTPUT FORMAT
+
+- Output a full, publish-ready essay about the content provided using the instructions above.
+
+- Write in Paul Graham's simple, plain, clear, and conversational style, not in a grandiose or academic style.
+
+- Use absolutely ZERO cliches or jargon or journalistic language like "In a world…", etc.
+
+- Do not use cliches or jargon.
+
+- Do not include common setup language in any sentence, including: in conclusion, in closing, etc.
+
+- Do not output warnings or notes—just the output requested.
+
+
+# INPUT:
+
+INPUT:

plugins/ai/anthropic/anthropic.go

@@ -3,9 +3,10 @@ package anthropic
 import (
 	"context"
 	"fmt"
-	"github.com/samber/lo"
 	"strings"
 
+	"github.com/samber/lo"
+
 	"github.com/anthropics/anthropic-sdk-go"
 	"github.com/anthropics/anthropic-sdk-go/option"
 	"github.com/danielmiessler/fabric/common"

plugins/ai/bedrock/bedrock.go

@@ -0,0 +1,274 @@
+// Package bedrock provides a plugin to use Amazon Bedrock models.
+// Supported models are defined in the MODELS variable.
+// To add additional models, append them to the MODELS array. Models must support the Converse and ConverseStream operations
+// Authentication uses the  AWS credential provider chain, similar.to the AWS CLI and SDKs
+// https://docs.aws.amazon.com/sdkref/latest/guide/standardized-credentials.html
+package bedrock
+
+import (
+	"context"
+	"fmt"
+
+	"github.com/danielmiessler/fabric/common"
+	"github.com/danielmiessler/fabric/plugins"
+	"github.com/danielmiessler/fabric/plugins/ai"
+
+	"github.com/aws/aws-sdk-go-v2/aws"
+	"github.com/aws/aws-sdk-go-v2/aws/middleware"
+	"github.com/aws/aws-sdk-go-v2/config"
+	"github.com/aws/aws-sdk-go-v2/service/bedrock"
+	"github.com/aws/aws-sdk-go-v2/service/bedrockruntime"
+	"github.com/aws/aws-sdk-go-v2/service/bedrockruntime/types"
+
+	goopenai "github.com/sashabaranov/go-openai"
+)
+
+const (
+	userAgentKey   = "aiosc"
+	userAgentValue = "fabric"
+)
+
+// Ensure BedrockClient implements the ai.Vendor interface
+var _ ai.Vendor = (*BedrockClient)(nil)
+
+// BedrockClient is a plugin to add support for Amazon Bedrock.
+// It implements the plugins.Plugin interface and provides methods
+// for interacting with AWS Bedrock's Converse and ConverseStream APIs.
+type BedrockClient struct {
+	*plugins.PluginBase
+	runtimeClient      *bedrockruntime.Client
+	controlPlaneClient *bedrock.Client
+
+	bedrockRegion *plugins.SetupQuestion
+}
+
+// NewClient returns a new Bedrock plugin client
+func NewClient() (ret *BedrockClient) {
+	vendorName := "Bedrock"
+	ret = &BedrockClient{}
+
+	ctx := context.Background()
+	cfg, err := config.LoadDefaultConfig(ctx)
+	if err != nil {
+		// Create a minimal client that will fail gracefully during configuration
+		ret.PluginBase = &plugins.PluginBase{
+			Name:          vendorName,
+			EnvNamePrefix: plugins.BuildEnvVariablePrefix(vendorName),
+			ConfigureCustom: func() error {
+				return fmt.Errorf("unable to load AWS Config: %w", err)
+			},
+		}
+		ret.bedrockRegion = ret.PluginBase.AddSetupQuestion("AWS Region", true)
+		return
+	}
+
+	cfg.APIOptions = append(cfg.APIOptions, middleware.AddUserAgentKeyValue(userAgentKey, userAgentValue))
+
+	runtimeClient := bedrockruntime.NewFromConfig(cfg)
+	controlPlaneClient := bedrock.NewFromConfig(cfg)
+
+	ret.PluginBase = &plugins.PluginBase{
+		Name:            vendorName,
+		EnvNamePrefix:   plugins.BuildEnvVariablePrefix(vendorName),
+		ConfigureCustom: ret.configure,
+	}
+
+	ret.runtimeClient = runtimeClient
+	ret.controlPlaneClient = controlPlaneClient
+
+	ret.bedrockRegion = ret.PluginBase.AddSetupQuestion("AWS Region", true)
+
+	if cfg.Region != "" {
+		ret.bedrockRegion.Value = cfg.Region
+	}
+
+	return
+}
+
+// isValidAWSRegion validates AWS region format
+func isValidAWSRegion(region string) bool {
+	// Simple validation - AWS regions are typically 2-3 parts separated by hyphens
+	// Examples: us-east-1, eu-west-1, ap-southeast-2
+	if len(region) < 5 || len(region) > 30 {
+		return false
+	}
+	// Basic pattern check for AWS region format
+	return region != ""
+}
+
+// configure initializes the Bedrock clients with the specified AWS region.
+// If no region is specified, the default region from AWS config is used.
+func (c *BedrockClient) configure() error {
+	if c.bedrockRegion.Value == "" {
+		return nil // Use default region from AWS config
+	}
+
+	// Validate region format
+	if !isValidAWSRegion(c.bedrockRegion.Value) {
+		return fmt.Errorf("invalid AWS region: %s", c.bedrockRegion.Value)
+	}
+
+	ctx := context.Background()
+	cfg, err := config.LoadDefaultConfig(ctx, config.WithRegion(c.bedrockRegion.Value))
+	if err != nil {
+		return fmt.Errorf("unable to load AWS Config with region %s: %w", c.bedrockRegion.Value, err)
+	}
+
+	cfg.APIOptions = append(cfg.APIOptions, middleware.AddUserAgentKeyValue(userAgentKey, userAgentValue))
+
+	c.runtimeClient = bedrockruntime.NewFromConfig(cfg)
+	c.controlPlaneClient = bedrock.NewFromConfig(cfg)
+
+	return nil
+}
+
+// ListModels retrieves all available foundation models and inference profiles
+// from AWS Bedrock that can be used with this plugin.
+func (c *BedrockClient) ListModels() ([]string, error) {
+	models := []string{}
+	ctx := context.Background()
+
+	foundationModels, err := c.controlPlaneClient.ListFoundationModels(ctx, &bedrock.ListFoundationModelsInput{})
+	if err != nil {
+		return nil, fmt.Errorf("failed to list foundation models: %w", err)
+	}
+
+	for _, model := range foundationModels.ModelSummaries {
+		models = append(models, *model.ModelId)
+	}
+
+	inferenceProfilesPaginator := bedrock.NewListInferenceProfilesPaginator(c.controlPlaneClient, &bedrock.ListInferenceProfilesInput{})
+
+	for inferenceProfilesPaginator.HasMorePages() {
+		inferenceProfiles, err := inferenceProfilesPaginator.NextPage(ctx)
+		if err != nil {
+			return nil, fmt.Errorf("failed to list inference profiles: %w", err)
+		}
+
+		for _, profile := range inferenceProfiles.InferenceProfileSummaries {
+			models = append(models, *profile.InferenceProfileId)
+		}
+	}
+
+	return models, nil
+}
+
+// SendStream sends the messages to the the Bedrock ConverseStream API
+func (c *BedrockClient) SendStream(msgs []*goopenai.ChatCompletionMessage, opts *common.ChatOptions, channel chan string) (err error) {
+	// Ensure channel is closed on all exit paths to prevent goroutine leaks
+	defer func() {
+		if r := recover(); r != nil {
+			err = fmt.Errorf("panic in SendStream: %v", r)
+		}
+		close(channel)
+	}()
+
+	messages := c.toMessages(msgs)
+
+	var converseInput = bedrockruntime.ConverseStreamInput{
+		ModelId:  aws.String(opts.Model),
+		Messages: messages,
+		InferenceConfig: &types.InferenceConfiguration{
+			Temperature: aws.Float32(float32(opts.Temperature)),
+			TopP:        aws.Float32(float32(opts.TopP))},
+	}
+
+	response, err := c.runtimeClient.ConverseStream(context.Background(), &converseInput)
+	if err != nil {
+		return fmt.Errorf("bedrock conversestream failed for model %s: %w", opts.Model, err)
+	}
+
+	for event := range response.GetStream().Events() {
+		// Possible ConverseStream event types
+		// https://docs.aws.amazon.com/bedrock/latest/userguide/conversation-inference-call.html#conversation-inference-call-response-converse-stream
+		switch v := event.(type) {
+
+		case *types.ConverseStreamOutputMemberContentBlockDelta:
+			text, ok := v.Value.Delta.(*types.ContentBlockDeltaMemberText)
+			if ok {
+				channel <- text.Value
+			}
+
+		case *types.ConverseStreamOutputMemberMessageStop:
+			channel <- "\n"
+			return nil // Let defer handle the close
+
+		// Unused Events
+		case *types.ConverseStreamOutputMemberMessageStart,
+			*types.ConverseStreamOutputMemberContentBlockStart,
+			*types.ConverseStreamOutputMemberContentBlockStop,
+			*types.ConverseStreamOutputMemberMetadata:
+
+		default:
+			return fmt.Errorf("unknown stream event type: %T", v)
+		}
+	}
+
+	return nil
+}
+
+// Send sends the messages the Bedrock Converse API
+func (c *BedrockClient) Send(ctx context.Context, msgs []*goopenai.ChatCompletionMessage, opts *common.ChatOptions) (ret string, err error) {
+
+	messages := c.toMessages(msgs)
+
+	var converseInput = bedrockruntime.ConverseInput{
+		ModelId:  aws.String(opts.Model),
+		Messages: messages,
+	}
+	response, err := c.runtimeClient.Converse(ctx, &converseInput)
+	if err != nil {
+		return "", fmt.Errorf("bedrock converse failed for model %s: %w", opts.Model, err)
+	}
+
+	responseText, ok := response.Output.(*types.ConverseOutputMemberMessage)
+	if !ok {
+		return "", fmt.Errorf("unexpected response type: %T", response.Output)
+	}
+
+	if len(responseText.Value.Content) == 0 {
+		return "", fmt.Errorf("empty response content")
+	}
+
+	responseContentBlock := responseText.Value.Content[0]
+	text, ok := responseContentBlock.(*types.ContentBlockMemberText)
+	if !ok {
+		return "", fmt.Errorf("unexpected content block type: %T", responseContentBlock)
+	}
+
+	return text.Value, nil
+}
+
+// NeedsRawMode indicates whether the model requires raw mode processing.
+// Bedrock models do not require raw mode.
+func (c *BedrockClient) NeedsRawMode(modelName string) bool {
+	return false
+}
+
+// toMessages converts the array of input messages from the ChatCompletionMessageType to the
+// Bedrock Converse Message type.
+// The system role messages are mapped to the user role as they contain a mix of system messages,
+// pattern content and user input.
+func (c *BedrockClient) toMessages(inputMessages []*goopenai.ChatCompletionMessage) (messages []types.Message) {
+	for _, msg := range inputMessages {
+		roles := map[string]types.ConversationRole{
+			goopenai.ChatMessageRoleUser:      types.ConversationRoleUser,
+			goopenai.ChatMessageRoleAssistant: types.ConversationRoleAssistant,
+			goopenai.ChatMessageRoleSystem:    types.ConversationRoleUser,
+		}
+
+		role, ok := roles[msg.Role]
+		if !ok {
+			continue
+		}
+
+		message := types.Message{
+			Role:    role,
+			Content: []types.ContentBlock{&types.ContentBlockMemberText{Value: msg.Content}},
+		}
+		messages = append(messages, message)
+
+	}
+
+	return
+}

plugins/ai/dryrun/dryrun.go

@@ -4,6 +4,7 @@ import (
 	"bytes"
 	"context"
 	"fmt"
+	"strings"
 
 	goopenai "github.com/sashabaranov/go-openai"
 
@@ -23,62 +24,77 @@ func (c *Client) ListModels() ([]string, error) {
 	return []string{"dry-run-model"}, nil
 }
 
-func (c *Client) SendStream(msgs []*goopenai.ChatCompletionMessage, opts *common.ChatOptions, channel chan string) error {
-	output := "Dry run: Would send the following request:\n\n"
+func (c *Client) formatMultiContentMessage(msg *goopenai.ChatCompletionMessage) string {
+	var builder strings.Builder
+
+	if len(msg.MultiContent) > 0 {
+		builder.WriteString(fmt.Sprintf("%s:\n", msg.Role))
+		for _, part := range msg.MultiContent {
+			builder.WriteString(fmt.Sprintf("  - Type: %s\n", part.Type))
+			if part.Type == goopenai.ChatMessagePartTypeImageURL {
+				builder.WriteString(fmt.Sprintf("    Image URL: %s\n", part.ImageURL.URL))
+			} else {
+				builder.WriteString(fmt.Sprintf("    Text: %s\n", part.Text))
+			}
+		}
+		builder.WriteString("\n")
+	} else {
+		builder.WriteString(fmt.Sprintf("%s:\n%s\n\n", msg.Role, msg.Content))
+	}
+
+	return builder.String()
+}
+
+func (c *Client) formatMessages(msgs []*goopenai.ChatCompletionMessage) string {
+	var builder strings.Builder
 
 	for _, msg := range msgs {
 		switch msg.Role {
 		case goopenai.ChatMessageRoleSystem:
-			output += fmt.Sprintf("System:\n%s\n\n", msg.Content)
+			builder.WriteString(fmt.Sprintf("System:\n%s\n\n", msg.Content))
 		case goopenai.ChatMessageRoleAssistant:
-			output += fmt.Sprintf("Assistant:\n%s\n\n", msg.Content)
+			builder.WriteString(c.formatMultiContentMessage(msg))
 		case goopenai.ChatMessageRoleUser:
-			output += fmt.Sprintf("User:\n%s\n\n", msg.Content)
+			builder.WriteString(c.formatMultiContentMessage(msg))
 		default:
-			output += fmt.Sprintf("%s:\n%s\n\n", msg.Role, msg.Content)
+			builder.WriteString(fmt.Sprintf("%s:\n%s\n\n", msg.Role, msg.Content))
 		}
 	}
 
-	output += "Options:\n"
-	output += fmt.Sprintf("Model: %s\n", opts.Model)
-	output += fmt.Sprintf("Temperature: %f\n", opts.Temperature)
-	output += fmt.Sprintf("TopP: %f\n", opts.TopP)
-	output += fmt.Sprintf("PresencePenalty: %f\n", opts.PresencePenalty)
-	output += fmt.Sprintf("FrequencyPenalty: %f\n", opts.FrequencyPenalty)
+	return builder.String()
+}
+
+func (c *Client) formatOptions(opts *common.ChatOptions) string {
+	var builder strings.Builder
+
+	builder.WriteString("Options:\n")
+	builder.WriteString(fmt.Sprintf("Model: %s\n", opts.Model))
+	builder.WriteString(fmt.Sprintf("Temperature: %f\n", opts.Temperature))
+	builder.WriteString(fmt.Sprintf("TopP: %f\n", opts.TopP))
+	builder.WriteString(fmt.Sprintf("PresencePenalty: %f\n", opts.PresencePenalty))
+	builder.WriteString(fmt.Sprintf("FrequencyPenalty: %f\n", opts.FrequencyPenalty))
 	if opts.ModelContextLength != 0 {
-		output += fmt.Sprintf("ModelContextLength: %d\n", opts.ModelContextLength)
+		builder.WriteString(fmt.Sprintf("ModelContextLength: %d\n", opts.ModelContextLength))
 	}
 
-	channel <- output
+	return builder.String()
+}
+
+func (c *Client) SendStream(msgs []*goopenai.ChatCompletionMessage, opts *common.ChatOptions, channel chan string) error {
+	var builder strings.Builder
+	builder.WriteString("Dry run: Would send the following request:\n\n")
+	builder.WriteString(c.formatMessages(msgs))
+	builder.WriteString(c.formatOptions(opts))
+
+	channel <- builder.String()
 	close(channel)
 	return nil
 }
 
 func (c *Client) Send(_ context.Context, msgs []*goopenai.ChatCompletionMessage, opts *common.ChatOptions) (string, error) {
 	fmt.Println("Dry run: Would send the following request:")
-
-	for _, msg := range msgs {
-		switch msg.Role {
-		case goopenai.ChatMessageRoleSystem:
-			fmt.Printf("System:\n%s\n\n", msg.Content)
-		case goopenai.ChatMessageRoleAssistant:
-			fmt.Printf("Assistant:\n%s\n\n", msg.Content)
-		case goopenai.ChatMessageRoleUser:
-			fmt.Printf("User:\n%s\n\n", msg.Content)
-		default:
-			fmt.Printf("%s:\n%s\n\n", msg.Role, msg.Content)
-		}
-	}
-
-	fmt.Println("Options:")
-	fmt.Printf("Model: %s\n", opts.Model)
-	fmt.Printf("Temperature: %f\n", opts.Temperature)
-	fmt.Printf("TopP: %f\n", opts.TopP)
-	fmt.Printf("PresencePenalty: %f\n", opts.PresencePenalty)
-	fmt.Printf("FrequencyPenalty: %f\n", opts.FrequencyPenalty)
-	if opts.ModelContextLength != 0 {
-		fmt.Printf("ModelContextLength: %d\n", opts.ModelContextLength)
-	}
+	fmt.Print(c.formatMessages(msgs))
+	fmt.Print(c.formatOptions(opts))
 
 	return "", nil
 }

plugins/ai/ollama/ollama.go

@@ -33,16 +33,20 @@ func NewClient() (ret *Client) {
 	ret.ApiUrl.Value = defaultBaseUrl
 	ret.ApiKey = ret.PluginBase.AddSetupQuestion("API key", false)
 	ret.ApiKey.Value = ""
+	ret.ApiHttpTimeout = ret.AddSetupQuestionCustom("HTTP Timeout", true,
+		"Specify HTTP timeout duration for Ollama requests (e.g. 30s, 5m, 1h)")
+	ret.ApiHttpTimeout.Value = "20m"
 
 	return
 }
 
 type Client struct {
 	*plugins.PluginBase
-	ApiUrl *plugins.SetupQuestion
-	ApiKey *plugins.SetupQuestion
-	apiUrl *url.URL
-	client *ollamaapi.Client
+	ApiUrl         *plugins.SetupQuestion
+	ApiKey         *plugins.SetupQuestion
+	apiUrl         *url.URL
+	client         *ollamaapi.Client
+	ApiHttpTimeout *plugins.SetupQuestion
 }
 
 type transport_sec struct {
@@ -63,7 +67,19 @@ func (o *Client) configure() (err error) {
 		return
 	}
 
-	o.client = ollamaapi.NewClient(o.apiUrl, &http.Client{Timeout: 1200000 * time.Millisecond, Transport: &transport_sec{underlyingTransport: http.DefaultTransport, ApiKey: o.ApiKey}})
+	timeout := 20 * time.Minute // Default timeout
+
+	if o.ApiHttpTimeout != nil {
+		parsed, err := time.ParseDuration(o.ApiHttpTimeout.Value)
+		if err == nil && o.ApiHttpTimeout.Value != "" {
+			timeout = parsed
+		} else if o.ApiHttpTimeout.Value != "" {
+			fmt.Printf("Invalid HTTP timeout format (%q), using default (20m): %v\n", o.ApiHttpTimeout.Value, err)
+		}
+	}
+
+	o.client = ollamaapi.NewClient(o.apiUrl, &http.Client{Timeout: timeout, Transport: &transport_sec{underlyingTransport: http.DefaultTransport, ApiKey: o.ApiKey}})
+
 	return
 }
 

plugins/ai/openai_compatible/providers_config.go

@@ -1,6 +1,9 @@
 package openai_compatible
 
 import (
+	"os"
+	"strings"
+
 	"github.com/danielmiessler/fabric/plugins/ai/openai"
 )
 
@@ -24,29 +27,37 @@ func NewClient(providerConfig ProviderConfig) *Client {
 
 // ProviderMap is a map of provider name to ProviderConfig for O(1) lookup
 var ProviderMap = map[string]ProviderConfig{
-	"Mistral": {
-		Name:    "Mistral",
-		BaseURL: "https://api.mistral.ai/v1",
+	"AIML": {
+		Name:    "AIML",
+		BaseURL: "https://api.aimlapi.com/v1",
 	},
-	"LiteLLM": {
-		Name:    "LiteLLM",
-		BaseURL: "http://localhost:4000",
-	},
-	"Groq": {
-		Name:    "Groq",
-		BaseURL: "https://api.groq.com/openai/v1",
-	},
-	"GrokAI": {
-		Name:    "GrokAI",
-		BaseURL: "https://api.x.ai/v1",
+	"Cerebras": {
+		Name:    "Cerebras",
+		BaseURL: "https://api.cerebras.ai/v1",
 	},
 	"DeepSeek": {
 		Name:    "DeepSeek",
 		BaseURL: "https://api.deepseek.com",
 	},
-	"Cerebras": {
-		Name:    "Cerebras",
-		BaseURL: "https://api.cerebras.ai/v1",
+	"GrokAI": {
+		Name:    "GrokAI",
+		BaseURL: "https://api.x.ai/v1",
+	},
+	"Groq": {
+		Name:    "Groq",
+		BaseURL: "https://api.groq.com/openai/v1",
+	},
+	"Langdock": {
+		Name:    "Langdock",
+		BaseURL: "https://api.langdock.com/openai/{{REGION=us}}/v1",
+	},
+	"LiteLLM": {
+		Name:    "LiteLLM",
+		BaseURL: "http://localhost:4000",
+	},
+	"Mistral": {
+		Name:    "Mistral",
+		BaseURL: "https://api.mistral.ai/v1",
 	},
 	"OpenRouter": {
 		Name:    "OpenRouter",
@@ -56,15 +67,37 @@ var ProviderMap = map[string]ProviderConfig{
 		Name:    "SiliconCloud",
 		BaseURL: "https://api.siliconflow.cn/v1",
 	},
-	"AIML": {
-		Name:    "AIML",
-		BaseURL: "https://api.aimlapi.com/v1",
-	},
 }
 
 // GetProviderByName returns the provider configuration for a given name with O(1) lookup
 func GetProviderByName(name string) (ProviderConfig, bool) {
 	provider, found := ProviderMap[name]
+	if strings.Contains(provider.BaseURL, "{{") && strings.Contains(provider.BaseURL, "}}") {
+		// Extract the template variable and default value
+		start := strings.Index(provider.BaseURL, "{{")
+		end := strings.Index(provider.BaseURL, "}}") + 2
+		template := provider.BaseURL[start:end]
+
+		// Parse the template to get variable name and default value
+		inner := template[2 : len(template)-2] // Remove {{ and }}
+		parts := strings.Split(inner, "=")
+		if len(parts) == 2 {
+			varName := strings.TrimSpace(parts[0])
+			defaultValue := strings.TrimSpace(parts[1])
+
+			// Create environment variable name
+			envVarName := strings.ToUpper(provider.Name) + "_" + varName
+
+			// Get value from environment or use default
+			envValue := os.Getenv(envVarName)
+			if envValue == "" {
+				envValue = defaultValue
+			}
+
+			// Replace the template with the actual value
+			provider.BaseURL = strings.Replace(provider.BaseURL, template, envValue, 1)
+		}
+	}
 	return provider, found
 }
 

plugins/ai/perplexity/perplexity.go

@@ -0,0 +1,246 @@
+package perplexity
+
+import (
+	"context"
+	"fmt"
+	"os"
+	"sync" // Added sync package
+
+	"github.com/danielmiessler/fabric/common"
+	"github.com/danielmiessler/fabric/plugins"
+	perplexity "github.com/sgaunet/perplexity-go/v2"
+
+	goopenai "github.com/sashabaranov/go-openai"
+)
+
+const (
+	providerName = "Perplexity"
+)
+
+var models = []string{
+	"r1-1776", "sonar", "sonar-pro", "sonar-reasoning", "sonar-reasoning-pro",
+}
+
+type Client struct {
+	*plugins.PluginBase
+	APIKey *plugins.SetupQuestion
+	client *perplexity.Client
+}
+
+func NewClient() *Client {
+	c := &Client{}
+	c.PluginBase = &plugins.PluginBase{
+		Name:            providerName,
+		EnvNamePrefix:   plugins.BuildEnvVariablePrefix(providerName),
+		ConfigureCustom: c.Configure, // Assign the Configure method
+	}
+	c.APIKey = c.AddSetupQuestion("API_KEY", true)
+	return c
+}
+
+func (c *Client) Configure() error {
+	// The PluginBase.Configure() is called by the framework if needed.
+	// We only need to handle specific logic for this plugin.
+	if c.APIKey.Value == "" {
+		// Attempt to get from environment variable if not set by user during setup
+		envKey := c.EnvNamePrefix + "API_KEY"
+		apiKeyFromEnv := os.Getenv(envKey)
+		if apiKeyFromEnv != "" {
+			c.APIKey.Value = apiKeyFromEnv
+		} else {
+			return fmt.Errorf("%s API key not configured. Please set the %s environment variable or run 'fabric --setup %s'", providerName, envKey, providerName)
+		}
+	}
+	c.client = perplexity.NewClient(c.APIKey.Value)
+	return nil
+}
+
+func (c *Client) ListModels() ([]string, error) {
+	// Perplexity API does not have a ListModels endpoint.
+	// We return a predefined list.
+	return models, nil
+}
+
+func (c *Client) Send(ctx context.Context, msgs []*goopenai.ChatCompletionMessage, opts *common.ChatOptions) (string, error) {
+	if c.client == nil {
+		if err := c.Configure(); err != nil {
+			return "", fmt.Errorf("failed to configure Perplexity client: %w", err)
+		}
+	}
+
+	var perplexityMessages []perplexity.Message
+	for _, msg := range msgs {
+		perplexityMessages = append(perplexityMessages, perplexity.Message{
+			Role:    msg.Role,
+			Content: msg.Content,
+		})
+	}
+
+	requestOptions := []perplexity.CompletionRequestOption{
+		perplexity.WithModel(opts.Model),
+		perplexity.WithMessages(perplexityMessages),
+	}
+	if opts.MaxTokens > 0 {
+		requestOptions = append(requestOptions, perplexity.WithMaxTokens(opts.MaxTokens))
+	}
+	if opts.Temperature > 0 { // Perplexity default is 1.0, only set if user specifies
+		requestOptions = append(requestOptions, perplexity.WithTemperature(opts.Temperature))
+	}
+	if opts.TopP > 0 { // Perplexity default is not specified, typically 1.0
+		requestOptions = append(requestOptions, perplexity.WithTopP(opts.TopP))
+	}
+	if opts.PresencePenalty != 0 {
+		// Corrected: Pass float64 directly
+		requestOptions = append(requestOptions, perplexity.WithPresencePenalty(opts.PresencePenalty))
+	}
+	if opts.FrequencyPenalty != 0 {
+		// Corrected: Pass float64 directly
+		requestOptions = append(requestOptions, perplexity.WithFrequencyPenalty(opts.FrequencyPenalty))
+	}
+
+	request := perplexity.NewCompletionRequest(requestOptions...)
+
+	// Corrected: Use SendCompletionRequest method from perplexity-go library
+	resp, err := c.client.SendCompletionRequest(request) // Pass request directly
+	if err != nil {
+		return "", fmt.Errorf("perplexity API request failed: %w", err) // Corrected capitalization
+	}
+
+	content := resp.GetLastContent()
+
+	// Append citations if available
+	citations := resp.GetCitations()
+	if len(citations) > 0 {
+		content += "\n\n# CITATIONS\n\n"
+		for i, citation := range citations {
+			content += fmt.Sprintf("- [%d] %s\n", i+1, citation)
+		}
+	}
+
+	return content, nil
+}
+
+func (c *Client) SendStream(msgs []*goopenai.ChatCompletionMessage, opts *common.ChatOptions, channel chan string) error {
+	if c.client == nil {
+		if err := c.Configure(); err != nil {
+			close(channel) // Ensure channel is closed on error
+			return fmt.Errorf("failed to configure Perplexity client: %w", err)
+		}
+	}
+
+	var perplexityMessages []perplexity.Message
+	for _, msg := range msgs {
+		perplexityMessages = append(perplexityMessages, perplexity.Message{
+			Role:    msg.Role,
+			Content: msg.Content,
+		})
+	}
+
+	requestOptions := []perplexity.CompletionRequestOption{
+		perplexity.WithModel(opts.Model),
+		perplexity.WithMessages(perplexityMessages),
+		perplexity.WithStream(true), // Enable streaming
+	}
+
+	if opts.MaxTokens > 0 {
+		requestOptions = append(requestOptions, perplexity.WithMaxTokens(opts.MaxTokens))
+	}
+	if opts.Temperature > 0 {
+		requestOptions = append(requestOptions, perplexity.WithTemperature(opts.Temperature))
+	}
+	if opts.TopP > 0 {
+		requestOptions = append(requestOptions, perplexity.WithTopP(opts.TopP))
+	}
+	if opts.PresencePenalty != 0 {
+		// Corrected: Pass float64 directly
+		requestOptions = append(requestOptions, perplexity.WithPresencePenalty(opts.PresencePenalty))
+	}
+	if opts.FrequencyPenalty != 0 {
+		// Corrected: Pass float64 directly
+		requestOptions = append(requestOptions, perplexity.WithFrequencyPenalty(opts.FrequencyPenalty))
+	}
+
+	request := perplexity.NewCompletionRequest(requestOptions...)
+
+	responseChan := make(chan perplexity.CompletionResponse)
+	var wg sync.WaitGroup // Use sync.WaitGroup
+	wg.Add(1)
+
+	go func() {
+		err := c.client.SendSSEHTTPRequest(&wg, request, responseChan)
+		if err != nil {
+			// Log error, can't send to string channel directly.
+			// Consider a mechanism to propagate this error if needed.
+			fmt.Fprintf(os.Stderr, "perplexity streaming error: %v\\n", err) // Corrected capitalization
+			// If the error occurs during stream setup, the channel might not have been closed by the receiver loop.
+			// However, closing it here might cause a panic if the receiver loop also tries to close it.
+			// close(channel) // Caution: Uncommenting this may cause panic, as channel is closed in the receiver goroutine.
+		}
+	}()
+
+	go func() {
+		defer close(channel) // Ensure the output channel is closed when this goroutine finishes
+		var lastResponse *perplexity.CompletionResponse
+		for resp := range responseChan {
+			lastResponse = &resp
+			if len(resp.Choices) > 0 {
+				content := ""
+				// Corrected: Check Delta.Content and Message.Content directly for non-emptiness
+				// as Delta and Message are structs, not pointers, in perplexity.Choice
+				if resp.Choices[0].Delta.Content != "" {
+					content = resp.Choices[0].Delta.Content
+				} else if resp.Choices[0].Message.Content != "" {
+					content = resp.Choices[0].Message.Content
+				}
+				if content != "" {
+					channel <- content
+				}
+			}
+		}
+
+		// Send citations at the end if available
+		if lastResponse != nil {
+			citations := lastResponse.GetCitations()
+			if len(citations) > 0 {
+				channel <- "\n\n# CITATIONS\n\n"
+				for i, citation := range citations {
+					channel <- fmt.Sprintf("- [%d] %s\n", i+1, citation)
+				}
+			}
+		}
+	}()
+
+	return nil
+}
+
+func (c *Client) NeedsRawMode(modelName string) bool {
+	return true
+}
+
+// Setup is called by the fabric CLI framework to guide the user through configuration.
+func (c *Client) Setup() error {
+	return c.PluginBase.Setup()
+}
+
+// GetName returns the name of the plugin.
+func (c *Client) GetName() string {
+	return c.PluginBase.Name
+}
+
+// GetEnvNamePrefix returns the environment variable prefix for the plugin.
+// Corrected: Receiver name
+func (c *Client) GetEnvNamePrefix() string {
+	return c.PluginBase.EnvNamePrefix
+}
+
+// AddSetupQuestion adds a setup question to the plugin.
+// This is a helper method, usually called from NewClient.
+func (c *Client) AddSetupQuestion(text string, isSensitive bool) *plugins.SetupQuestion {
+	return c.PluginBase.AddSetupQuestion(text, isSensitive)
+}
+
+// GetSetupQuestions returns the setup questions for the plugin.
+// Corrected: Return the slice of setup questions from PluginBase
+func (c *Client) GetSetupQuestions() []*plugins.SetupQuestion {
+	return c.PluginBase.SetupQuestions
+}

plugins/db/fsdb/patterns.go

@@ -150,3 +150,14 @@ func (o *PatternsEntity) Get(name string) (*Pattern, error) {
 	// Use GetPattern with no variables
 	return o.GetApplyVariables(name, nil, "")
 }
+func (o *PatternsEntity) Save(name string, content []byte) (err error) {
+	patternDir := filepath.Join(o.Dir, name)
+	if err = os.MkdirAll(patternDir, os.ModePerm); err != nil {
+		return fmt.Errorf("could not create pattern directory: %v", err)
+	}
+	patternPath := filepath.Join(patternDir, o.SystemPatternFile)
+	if err = os.WriteFile(patternPath, content, 0644); err != nil {
+		return fmt.Errorf("could not save pattern: %v", err)
+	}
+	return nil
+}

plugins/db/fsdb/patterns_test.go

@@ -144,3 +144,21 @@ func TestGetApplyVariables(t *testing.T) {
 		})
 	}
 }
+
+func TestPatternsEntity_Save(t *testing.T) {
+	entity, cleanup := setupTestPatternsEntity(t)
+	defer cleanup()
+
+	name := "new-pattern"
+	content := []byte("test pattern content")
+	require.NoError(t, entity.Save(name, content))
+
+	patternDir := filepath.Join(entity.Dir, name)
+	info, err := os.Stat(patternDir)
+	require.NoError(t, err)
+	assert.True(t, info.IsDir())
+
+	data, err := os.ReadFile(filepath.Join(patternDir, entity.SystemPatternFile))
+	require.NoError(t, err)
+	assert.Equal(t, content, data)
+}

plugins/tools/youtube/youtube.go

@@ -1,20 +1,29 @@
+// Package youtube provides YouTube video transcript and comment extraction functionality.
+//
+// Requirements:
+// - yt-dlp: Required for transcript extraction (must be installed separately)
+// - YouTube API key: Optional, only needed for comments and metadata extraction
+//
+// The implementation uses yt-dlp for reliable transcript extraction and the YouTube API
+// for comments/metadata. Old YouTube scraping methods have been removed due to
+// frequent changes and rate limiting.
 package youtube
 
 import (
+	"bytes"
 	"context"
 	"encoding/csv"
-	"encoding/json"
 	"flag"
 	"fmt"
 	"log"
-	"net/url"
 	"os"
+	"os/exec"
+	"path/filepath"
 	"regexp"
 	"strconv"
 	"strings"
 	"time"
 
-	"github.com/anaskhan96/soup"
 	"github.com/danielmiessler/fabric/plugins"
 	"google.golang.org/api/option"
 	"google.golang.org/api/youtube/v3"
@@ -27,7 +36,7 @@ func NewYouTube() (ret *YouTube) {
 
 	ret.PluginBase = &plugins.PluginBase{
 		Name:             label,
-		SetupDescription: label + " - to grab video transcripts and comments",
+		SetupDescription: label + " - to grab video transcripts (via yt-dlp) and comments/metadata (via YouTube API)",
 		EnvNamePrefix:    plugins.BuildEnvVariablePrefix(label),
 	}
 
@@ -46,6 +55,10 @@ type YouTube struct {
 
 func (o *YouTube) initService() (err error) {
 	if o.service == nil {
+		if o.ApiKey.Value == "" {
+			err = fmt.Errorf("YouTube API key required for comments and metadata. Run 'fabric --setup' to configure")
+			return
+		}
 		o.normalizeRegex = regexp.MustCompile(`[^a-zA-Z0-9]+`)
 		ctx := context.Background()
 		o.service, err = youtube.NewService(ctx, option.WithAPIKey(o.ApiKey.Value))
@@ -54,10 +67,6 @@ func (o *YouTube) initService() (err error) {
 }
 
 func (o *YouTube) GetVideoOrPlaylistId(url string) (videoId string, playlistId string, err error) {
-	if err = o.initService(); err != nil {
-		return
-	}
-
 	// Video ID pattern
 	videoPattern := `(?:https?:\/\/)?(?:www\.)?(?:youtube\.com\/(?:live\/|[^\/\n\s]+\/\S+\/|(?:v|e(?:mbed)?)\/|(?:s(?:horts)\/)|\S*?[?&]v=)|youtu\.be\/)([a-zA-Z0-9_-]*)`
 	videoRe := regexp.MustCompile(videoPattern)
@@ -94,112 +103,182 @@ func (o *YouTube) GrabTranscriptForUrl(url string, language string) (ret string,
 }
 
 func (o *YouTube) GrabTranscript(videoId string, language string) (ret string, err error) {
-	var transcript string
-	if transcript, err = o.GrabTranscriptBase(videoId, language); err != nil {
-		err = fmt.Errorf("transcript not available. (%v)", err)
-		return
-	}
-
-	// Parse the XML transcript
-	doc := soup.HTMLParse(transcript)
-	// Extract the text content from the <text> tags
-	textTags := doc.FindAll("text")
-	var textBuilder strings.Builder
-	for _, textTag := range textTags {
-		textBuilder.WriteString(strings.ReplaceAll(textTag.Text(), "&#39;", "'"))
-		textBuilder.WriteString(" ")
-		ret = textBuilder.String()
-	}
-	return
+	// Use yt-dlp for reliable transcript extraction
+	return o.tryMethodYtDlp(videoId, language)
 }
 
 func (o *YouTube) GrabTranscriptWithTimestamps(videoId string, language string) (ret string, err error) {
-	var transcript string
-	if transcript, err = o.GrabTranscriptBase(videoId, language); err != nil {
-		err = fmt.Errorf("transcript not available. (%v)", err)
+	// Use yt-dlp for reliable transcript extraction with timestamps
+	return o.tryMethodYtDlpWithTimestamps(videoId, language)
+}
+
+// tryMethodYtDlpInternal is a helper function to reduce duplication between
+// tryMethodYtDlp and tryMethodYtDlpWithTimestamps.
+func (o *YouTube) tryMethodYtDlpInternal(videoId string, language string, processVTTFileFunc func(filename string) (string, error)) (ret string, err error) {
+	// Check if yt-dlp is available
+	if _, err = exec.LookPath("yt-dlp"); err != nil {
+		err = fmt.Errorf("yt-dlp not found in PATH. Please install yt-dlp to use YouTube transcript functionality")
 		return
 	}
 
-	// Parse the XML transcript
-	doc := soup.HTMLParse(transcript)
-	// Extract the text content from the <text> tags
-	textTags := doc.FindAll("text")
-	var textBuilder strings.Builder
-	for _, textTag := range textTags {
-		// Extract the start and duration attributes
-		start := textTag.Attrs()["start"]
-		dur := textTag.Attrs()["dur"]
-		end := fmt.Sprintf("%f", parseFloat(start)+parseFloat(dur))
-		// Format the timestamps
-		startFormatted := formatTimestamp(parseFloat(start))
-		endFormatted := formatTimestamp(parseFloat(end))
-		text := strings.ReplaceAll(textTag.Text(), "&#39;", "'")
-		textBuilder.WriteString(fmt.Sprintf("[%s - %s] %s\n", startFormatted, endFormatted, text))
+	// Create a temporary directory for yt-dlp output (cross-platform)
+	tempDir := filepath.Join(os.TempDir(), "fabric-youtube-"+videoId)
+	if err = os.MkdirAll(tempDir, 0755); err != nil {
+		err = fmt.Errorf("failed to create temp directory: %v", err)
+		return
+	}
+	defer os.RemoveAll(tempDir)
+
+	// Use yt-dlp to get transcript
+	videoURL := "https://www.youtube.com/watch?v=" + videoId
+	outputPath := filepath.Join(tempDir, "%(title)s.%(ext)s")
+	lang_match := language
+	if len(language) > 2 {
+		lang_match = language[:2]
+	}
+	cmd := exec.Command("yt-dlp",
+		"--write-auto-subs",
+		"--sub-lang", lang_match,
+		"--skip-download",
+		"--sub-format", "vtt",
+		"--quiet",
+		"--no-warnings",
+		"-o", outputPath,
+		videoURL)
+
+	var stderr bytes.Buffer
+	cmd.Stderr = &stderr
+
+	if err = cmd.Run(); err != nil {
+		err = fmt.Errorf("yt-dlp failed: %v, stderr: %s", err, stderr.String())
+		return
+	}
+
+	// Find VTT files using cross-platform approach
+	vttFiles, err := o.findVTTFiles(tempDir, language)
+	if err != nil {
+		return "", err
+	}
+
+	return processVTTFileFunc(vttFiles[0])
+}
+
+func (o *YouTube) tryMethodYtDlp(videoId string, language string) (ret string, err error) {
+	return o.tryMethodYtDlpInternal(videoId, language, o.readAndCleanVTTFile)
+}
+
+func (o *YouTube) tryMethodYtDlpWithTimestamps(videoId string, language string) (ret string, err error) {
+	return o.tryMethodYtDlpInternal(videoId, language, o.readAndFormatVTTWithTimestamps)
+}
+
+func (o *YouTube) readAndCleanVTTFile(filename string) (ret string, err error) {
+	var content []byte
+	if content, err = os.ReadFile(filename); err != nil {
+		return
+	}
+
+	// Convert VTT to plain text
+	lines := strings.Split(string(content), "\n")
+	var textBuilder strings.Builder
+
+	for _, line := range lines {
+		line = strings.TrimSpace(line)
+		// Skip WEBVTT header, timestamps, and empty lines
+		if line == "" || line == "WEBVTT" || strings.Contains(line, "-->") ||
+			strings.HasPrefix(line, "NOTE") || strings.HasPrefix(line, "STYLE") ||
+			strings.HasPrefix(line, "Kind:") || strings.HasPrefix(line, "Language:") ||
+			isTimeStamp(line) {
+			continue
+		}
+		// Remove VTT formatting tags
+		line = removeVTTTags(line)
+		if line != "" {
+			textBuilder.WriteString(line)
+			textBuilder.WriteString(" ")
+		}
+	}
+
+	ret = strings.TrimSpace(textBuilder.String())
+	if ret == "" {
+		err = fmt.Errorf("no transcript content found in VTT file")
 	}
-	ret = textBuilder.String()
 	return
 }
 
-func parseFloat(s string) float64 {
-	f, _ := strconv.ParseFloat(s, 64)
-	return f
-}
-
-func formatTimestamp(seconds float64) string {
-	hours := int(seconds) / 3600
-	minutes := (int(seconds) % 3600) / 60
-	secs := int(seconds) % 60
-	return fmt.Sprintf("%02d:%02d:%02d", hours, minutes, secs)
-}
-
-func (o *YouTube) GrabTranscriptBase(videoId string, language string) (ret string, err error) {
-	if err = o.initService(); err != nil {
+func (o *YouTube) readAndFormatVTTWithTimestamps(filename string) (ret string, err error) {
+	var content []byte
+	if content, err = os.ReadFile(filename); err != nil {
 		return
 	}
 
-	watchUrl := "https://www.youtube.com/watch?v=" + videoId
-	var resp string
-	if resp, err = soup.Get(watchUrl); err != nil {
-		return
-	}
+	// Parse VTT and preserve timestamps
+	lines := strings.Split(string(content), "\n")
+	var textBuilder strings.Builder
+	var currentTimestamp string
 
-	doc := soup.HTMLParse(resp)
-	scriptTags := doc.FindAll("script")
-	for _, scriptTag := range scriptTags {
-		if strings.Contains(scriptTag.Text(), "captionTracks") {
-			regex := regexp.MustCompile(`"captionTracks":(\[.*?\])`)
-			match := regex.FindStringSubmatch(scriptTag.Text())
-			if len(match) > 1 {
-				var captionTracks []struct {
-					BaseURL string `json:"baseUrl"`
-				}
+	for _, line := range lines {
+		line = strings.TrimSpace(line)
 
-				if err = json.Unmarshal([]byte(match[1]), &captionTracks); err != nil {
-					return
-				}
+		// Skip WEBVTT header and empty lines
+		if line == "" || line == "WEBVTT" || strings.HasPrefix(line, "NOTE") ||
+			strings.HasPrefix(line, "STYLE") || strings.HasPrefix(line, "Kind:") ||
+			strings.HasPrefix(line, "Language:") {
+			continue
+		}
 
-				if len(captionTracks) > 0 {
-					transcriptURL := captionTracks[0].BaseURL
-					for _, captionTrack := range captionTracks {
-						parsedUrl, error := url.Parse(captionTrack.BaseURL)
-						if error != nil {
-							err = fmt.Errorf("error parsing caption track")
-						}
-						parsedUrlParams, _ := url.ParseQuery(parsedUrl.RawQuery)
-						if parsedUrlParams["lang"][0] == language {
-							transcriptURL = captionTrack.BaseURL
-						}
-					}
-					ret, err = soup.Get(transcriptURL)
-					return
-				}
+		// Check if this line is a timestamp
+		if strings.Contains(line, "-->") {
+			// Extract start time for this segment
+			parts := strings.Split(line, " --> ")
+			if len(parts) >= 1 {
+				currentTimestamp = formatVTTTimestamp(parts[0])
+			}
+			continue
+		}
+
+		// Skip numeric sequence identifiers
+		if isTimeStamp(line) && !strings.Contains(line, ":") {
+			continue
+		}
+
+		// This should be transcript text
+		if line != "" {
+			// Remove VTT formatting tags
+			cleanText := removeVTTTags(line)
+			if cleanText != "" && currentTimestamp != "" {
+				textBuilder.WriteString(fmt.Sprintf("[%s] %s\n", currentTimestamp, cleanText))
 			}
 		}
 	}
-	err = fmt.Errorf("transcript not found")
+
+	ret = strings.TrimSpace(textBuilder.String())
+	if ret == "" {
+		err = fmt.Errorf("no transcript content found in VTT file")
+	}
 	return
 }
 
+func formatVTTTimestamp(vttTime string) string {
+	// VTT timestamps are in format "00:00:01.234" - convert to "00:00:01"
+	parts := strings.Split(vttTime, ".")
+	if len(parts) > 0 {
+		return parts[0]
+	}
+	return vttTime
+}
+
+func isTimeStamp(s string) bool {
+	// Match timestamps like "00:00:01.234" or just numbers
+	timestampRegex := regexp.MustCompile(`^\d+$|^\d{2}:\d{2}:\d{2}`)
+	return timestampRegex.MatchString(s)
+}
+
+func removeVTTTags(s string) string {
+	// Remove VTT tags like <c.colorE5E5E5>, </c>, etc.
+	tagRegex := regexp.MustCompile(`<[^>]*>`)
+	return tagRegex.ReplaceAllString(s, "")
+}
+
 func (o *YouTube) GrabComments(videoId string) (ret []string, err error) {
 	if err = o.initService(); err != nil {
 		return
@@ -411,6 +490,41 @@ func (o *YouTube) normalizeFileName(name string) string {
 
 }
 
+// findVTTFiles searches for VTT files in a directory using cross-platform approach
+func (o *YouTube) findVTTFiles(dir, language string) ([]string, error) {
+	var vttFiles []string
+
+	// Walk through the directory to find VTT files
+	err := filepath.Walk(dir, func(path string, info os.FileInfo, err error) error {
+		if err != nil {
+			return err
+		}
+
+		if !info.IsDir() && strings.HasSuffix(strings.ToLower(path), ".vtt") {
+			vttFiles = append(vttFiles, path)
+		}
+		return nil
+	})
+
+	if err != nil {
+		return nil, fmt.Errorf("failed to walk directory: %v", err)
+	}
+
+	if len(vttFiles) == 0 {
+		return nil, fmt.Errorf("no VTT files found in directory")
+	}
+
+	// Prefer files with the specified language
+	for _, file := range vttFiles {
+		if strings.Contains(file, "."+language+".vtt") {
+			return []string{file}, nil
+		}
+	}
+
+	// Return the first VTT file found if no language-specific file exists
+	return []string{vttFiles[0]}, nil
+}
+
 type VideoMeta struct {
 	Id              string
 	Title           string

restapi/chat.go

@@ -24,12 +24,13 @@ type ChatHandler struct {
 }
 
 type PromptRequest struct {
-	UserInput    string `json:"userInput"`
-	Vendor       string `json:"vendor"`
-	Model        string `json:"model"`
-	ContextName  string `json:"contextName"`
-	PatternName  string `json:"patternName"`
-	StrategyName string `json:"strategyName"` // Optional strategy name
+	UserInput    string            `json:"userInput"`
+	Vendor       string            `json:"vendor"`
+	Model        string            `json:"model"`
+	ContextName  string            `json:"contextName"`
+	PatternName  string            `json:"patternName"`
+	StrategyName string            `json:"strategyName"`        // Optional strategy name
+	Variables    map[string]string `json:"variables,omitempty"` // Pattern variables
 }
 
 type ChatRequest struct {
@@ -118,9 +119,10 @@ func (h *ChatHandler) HandleChat(c *gin.Context) {
 						Role:    "user",
 						Content: p.UserInput,
 					},
-					PatternName: p.PatternName,
-					ContextName: p.ContextName,
-					Language:    request.Language, // Pass the language field
+					PatternName:      p.PatternName,
+					ContextName:      p.ContextName,
+					PatternVariables: p.Variables,      // Pass pattern variables
+					Language:         request.Language, // Pass the language field
 				}
 
 				opts := &common.ChatOptions{

restapi/docs/API_VARIABLES_EXAMPLE.md

@@ -0,0 +1,105 @@
+# REST API Pattern Variables Example
+
+This example demonstrates how to use pattern variables in REST API calls to the `/chat` endpoint.
+
+## Example: Using the `translate` pattern with variables
+
+### Request
+
+```json
+{
+  "prompts": [
+    {
+      "userInput": "Hello my name is Kayvan",
+      "patternName": "translate",
+      "model": "gpt-4o",
+      "vendor": "openai",
+      "contextName": "",
+      "strategyName": "",
+      "variables": {
+        "lang_code": "fr"
+      }
+    }
+  ],
+  "language": "en",
+  "temperature": 0.7,
+  "topP": 0.9,
+  "frequencyPenalty": 0.0,
+  "presencePenalty": 0.0
+}
+```
+
+### Pattern Content
+
+The `translate` pattern contains:
+
+```markdown
+You are an expert translator... translate them as accurately and perfectly as possible into the language specified by its language code {{lang_code}}...
+
+...
+
+- Translate the document as accurately as possible keeping a 1:1 copy of the original text translated to {{lang_code}}.
+
+{{input}}
+```
+
+### How it works
+
+1. The pattern is loaded from `patterns/translate/system.md`
+2. The `{{lang_code}}` variable is replaced with `"fr"` from the variables map
+3. The `{{input}}` placeholder is replaced with `"Hello my name is Kayvan"`
+4. The resulting processed pattern is sent to the AI model
+
+### Expected Result
+
+The AI would receive a prompt asking it to translate "Hello my name is Kayvan" to French (fr), and would respond with something like "Bonjour, je m'appelle Kayvan".
+
+## Testing with curl
+
+```bash
+curl -X POST http://localhost:8080/api/chat \
+  -H "Content-Type: application/json" \
+  -d '{
+    "prompts": [
+      {
+        "userInput": "Hello my name is Kayvan",
+        "patternName": "translate",
+        "model": "gpt-4o",
+        "vendor": "openai",
+        "variables": {
+          "lang_code": "fr"
+        }
+      }
+    ],
+    "temperature": 0.7
+  }'
+```
+
+## Multiple Variables Example
+
+For patterns that use multiple variables:
+
+```json
+{
+  "prompts": [
+    {
+      "userInput": "Analyze this business model",
+      "patternName": "custom_analysis",
+      "model": "gpt-4o",
+      "variables": {
+        "role": "expert consultant",
+        "experience": "15",
+        "focus_areas": "revenue, scalability, market fit",
+        "output_format": "bullet points"
+      }
+    }
+  ]
+}
+```
+
+## Implementation Details
+
+- Variables are passed in the `variables` field as a key-value map
+- Variables are processed using Go's template system
+- The `{{input}}` variable is automatically handled and should not be included in the variables map
+- Variables support the same features as CLI variables (plugins, extensions, etc.)

restapi/patterns.go

@@ -15,20 +15,70 @@ type PatternsHandler struct {
 
 // NewPatternsHandler creates a new PatternsHandler
 func NewPatternsHandler(r *gin.Engine, patterns *fsdb.PatternsEntity) (ret *PatternsHandler) {
-	ret = &PatternsHandler{
-		StorageHandler: NewStorageHandler(r, "patterns", patterns), patterns: patterns}
+	// Create a storage handler but don't register any routes yet
+	storageHandler := &StorageHandler[fsdb.Pattern]{storage: patterns}
+	ret = &PatternsHandler{StorageHandler: storageHandler, patterns: patterns}
 
-	// TODO: Add custom, replacement routes here
-	//r.GET("/patterns/:name", ret.Get)
+	// Register routes manually - use custom Get for patterns, others from StorageHandler
+	r.GET("/patterns/:name", ret.Get)                       // Custom method with variables support
+	r.GET("/patterns/names", ret.GetNames)                  // From StorageHandler
+	r.DELETE("/patterns/:name", ret.Delete)                 // From StorageHandler
+	r.GET("/patterns/exists/:name", ret.Exists)             // From StorageHandler
+	r.PUT("/patterns/rename/:oldName/:newName", ret.Rename) // From StorageHandler
+	r.POST("/patterns/:name", ret.Save)                     // From StorageHandler
+	// Add POST route for patterns with variables in request body
+	r.POST("/patterns/:name/apply", ret.ApplyPattern)
 	return
 }
 
-// Get handles the GET /patterns/:name route
+// Get handles the GET /patterns/:name route - returns raw pattern without variable processing
 func (h *PatternsHandler) Get(c *gin.Context) {
 	name := c.Param("name")
-	variables := make(map[string]string) // Assuming variables are passed somehow
-	input := ""                          // Assuming input is passed somehow
-	pattern, err := h.patterns.GetApplyVariables(name, variables, input)
+
+	// Get the raw pattern content without any variable processing
+	content, err := h.patterns.Load(name + "/" + h.patterns.SystemPatternFile)
+	if err != nil {
+		c.JSON(http.StatusInternalServerError, err.Error())
+		return
+	}
+
+	// Return raw pattern in the same format as the processed patterns
+	pattern := &fsdb.Pattern{
+		Name:        name,
+		Description: "",
+		Pattern:     string(content),
+	}
+	c.JSON(http.StatusOK, pattern)
+}
+
+// PatternApplyRequest represents the request body for applying a pattern
+type PatternApplyRequest struct {
+	Input     string            `json:"input"`
+	Variables map[string]string `json:"variables,omitempty"`
+}
+
+// ApplyPattern handles the POST /patterns/:name/apply route
+func (h *PatternsHandler) ApplyPattern(c *gin.Context) {
+	name := c.Param("name")
+
+	var request PatternApplyRequest
+	if err := c.ShouldBindJSON(&request); err != nil {
+		c.JSON(http.StatusBadRequest, gin.H{"error": err.Error()})
+		return
+	}
+
+	// Merge query parameters with request body variables (body takes precedence)
+	variables := make(map[string]string)
+	for key, values := range c.Request.URL.Query() {
+		if len(values) > 0 {
+			variables[key] = values[0]
+		}
+	}
+	for key, value := range request.Variables {
+		variables[key] = value
+	}
+
+	pattern, err := h.patterns.GetApplyVariables(name, variables, request.Input)
 	if err != nil {
 		c.JSON(http.StatusInternalServerError, err.Error())
 		return

version.go

@@ -1,3 +1,3 @@
 package main
 
-var version = "v1.4.196"
+var version = "v1.4.216"

web/pnpm-lock.yaml

@@ -608,6 +608,9 @@ packages:
   '@types/estree@1.0.7':
     resolution: {integrity: sha512-w28IoSUCJpidD/TGviZwwMJckNESJZXFu7NBZ5YJ4mEUnNraUn9Pm8HSZm/jDF1pDWYKspWE7oVphigUPRakIQ==}
 
+  '@types/estree@1.0.8':
+    resolution: {integrity: sha512-dWHzHa2WqEXI/O1E9OjrocMTKJl2mSrEolh1Iomrv6U+JuNwaHXsXx9bLu5gG7BUWFIN0skIQJQ/L1rIex4X6w==}
+
   '@types/hast@3.0.4':
     resolution: {integrity: sha512-WPs+bbQw5aCj+x6laNGWLH3wviHtoCv/P3+otBhbOhJgG8qtpdAMlTCxLtsTWA7LH1Oh/bFCHsBn0TPS5m30EQ==}
 
@@ -654,6 +657,11 @@ packages:
     engines: {node: '>=0.4.0'}
     hasBin: true
 
+  acorn@8.15.0:
+    resolution: {integrity: sha512-NZyJarBfL7nWwIq+FDL6Zp/yHEhePMNnnJ0y3qfieCrmNvYct8uvtiV41UvlSe6apAfk0fY1FbWx+NwfmpvtTg==}
+    engines: {node: '>=0.4.0'}
+    hasBin: true
+
   agent-base@6.0.2:
     resolution: {integrity: sha512-RZNwNclF7+MS/8bDg70amg32dyeZGZxiDuQmZxKLAlQjr3jGyLx+4Kkk58UO7D2QdgFIQCovuSuZESne6RG6XQ==}
     engines: {node: '>= 6.0.0'}
@@ -746,11 +754,11 @@ packages:
     resolution: {integrity: sha512-Ceh+7ox5qe7LJuLHoY0feh3pHuUDHAcRUeyL2VYghZwfpkNIy/+8Ocg0a3UuSoYzavmylwuLWQOf3hl0jjMMIw==}
     engines: {node: '>=8'}
 
-  brace-expansion@1.1.11:
-    resolution: {integrity: sha512-iCuPHDFgrHX7H2vEI/5xpz07zSHB00TpugqhmYtVmMO6518mCuRMoOYFldEBl0g187ufozdaHgWKcYFb61qGiA==}
+  brace-expansion@1.1.12:
+    resolution: {integrity: sha512-9T9UjW3r0UW5c1Q7GTwllptXwhvYmEzFhzMfZ9H7FQWt+uZePjZPjBP/W1ZEyZ1twGWom5/56TF4lPcqjnDHcg==}
 
-  brace-expansion@2.0.1:
-    resolution: {integrity: sha512-XnAIvQ8eM+kC6aULx6wuQiwVsnzsi9d3WxzV3FpWTGA19F621kwdbsAcFKXgKUHZWsy+mY6iL1sHTxWEFCytDA==}
+  brace-expansion@2.0.2:
+    resolution: {integrity: sha512-Jt0vHyM+jmUBqojB7E1NIYadt0vI0Qxjxd2TErW94wDz+E2LAm5vKMXXwg6ZZBTHPuUlDgQHKXvjGBdfcF1ZDQ==}
 
   braces@3.0.3:
     resolution: {integrity: sha512-yQbXgO/OSZVD2IsiLlro+7Hf6Q18EJrKSEsdoMzKePKXct3gvD8oLcOQdIzGupr5Fj+EDe8gO/lxc1BzfMpxvA==}
@@ -1019,16 +1027,16 @@ packages:
     resolution: {integrity: sha512-dOt21O7lTMhDM+X9mB4GX+DZrZtCUJPL/wlcTqxyrx5IvO0IYtILdtrQGQp+8n5S0gwSVmOf9NQrjMOgfQZlIg==}
     engines: {node: ^12.22.0 || ^14.17.0 || >=16.0.0}
 
-  eslint-scope@8.3.0:
-    resolution: {integrity: sha512-pUNxi75F8MJ/GdeKtVLSbYg4ZI34J6C0C7sbL4YOp2exGwen7ZsuBqKzUhXd0qMQ362yET3z+uPwKeg/0C2XCQ==}
+  eslint-scope@8.4.0:
+    resolution: {integrity: sha512-sNXOfKCn74rt8RICKMvJS7XKV/Xk9kA7DyJr8mJik3S7Cwgy3qlkkmyS2uQB3jiJg6VNdZd/pDBJu0nvG2NlTg==}
     engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
 
   eslint-visitor-keys@3.4.3:
     resolution: {integrity: sha512-wpc+LXeiyiisxPlEkUzU6svyS1frIO3Mgxj1fdy7Pm8Ygzguax2N3Fa/D/ag1WqbOprdI+uY6wMUl8/a2G+iag==}
     engines: {node: ^12.22.0 || ^14.17.0 || >=16.0.0}
 
-  eslint-visitor-keys@4.2.0:
-    resolution: {integrity: sha512-UyLnSehNt62FFhSwjZlHmeokpRK59rcz29j+F1/aDgbkbRTk7wIc9XzdoasMUbRNKDM0qQt/+BJ4BrpFeABemw==}
+  eslint-visitor-keys@4.2.1:
+    resolution: {integrity: sha512-Uhdk5sfqcee/9H/rCOJikYz67o0a2Tw2hGRPOG2Y1R2dg7brRe1uG0yaNQDHu+TO/uQPF/5eCapvYSmHUjt7JQ==}
     engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
 
   eslint@9.17.0:
@@ -1047,8 +1055,8 @@ packages:
   esm-env@1.2.2:
     resolution: {integrity: sha512-Epxrv+Nr/CaL4ZcFGPJIYLWFom+YeV1DqMLHJoEd9SYRxNbaFruBwfEX/kkHUJf55j2+TUbmDcmuilbP1TmXHA==}
 
-  espree@10.3.0:
-    resolution: {integrity: sha512-0QYC8b24HWY8zjRnDTL6RiHfDbAWn63qb4LMj1Z4b076A4une81+z03Kg7l7mn/48PUTqoLptSXez8oknU8Clg==}
+  espree@10.4.0:
+    resolution: {integrity: sha512-j6PAQ2uUr79PZhBjP5C5fhl8e39FmRnOjsD5lGnWrFU8i2G776tBK7+nP8KuQUTTyAZUwfQqXAgrVH5MbH9CYQ==}
     engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
 
   espree@9.6.1:
@@ -2472,7 +2480,7 @@ snapshots:
     dependencies:
       ajv: 6.12.6
       debug: 4.4.1
-      espree: 10.3.0
+      espree: 10.4.0
       globals: 14.0.0
       ignore: 5.3.2
       import-fresh: 3.3.1
@@ -2747,6 +2755,8 @@ snapshots:
 
   '@types/estree@1.0.7': {}
 
+  '@types/estree@1.0.8': {}
+
   '@types/hast@3.0.4':
     dependencies:
       '@types/unist': 3.0.3
@@ -2782,8 +2792,14 @@ snapshots:
     dependencies:
       acorn: 8.14.1
 
+  acorn-jsx@5.3.2(acorn@8.15.0):
+    dependencies:
+      acorn: 8.15.0
+
   acorn@8.14.1: {}
 
+  acorn@8.15.0: {}
+
   agent-base@6.0.2:
     dependencies:
       debug: 4.4.1
@@ -2866,12 +2882,12 @@ snapshots:
 
   binary-extensions@2.3.0: {}
 
-  brace-expansion@1.1.11:
+  brace-expansion@1.1.12:
     dependencies:
       balanced-match: 1.0.2
       concat-map: 0.0.1
 
-  brace-expansion@2.0.1:
+  brace-expansion@2.0.2:
     dependencies:
       balanced-match: 1.0.2
 
@@ -3146,14 +3162,14 @@ snapshots:
       esrecurse: 4.3.0
       estraverse: 5.3.0
 
-  eslint-scope@8.3.0:
+  eslint-scope@8.4.0:
     dependencies:
       esrecurse: 4.3.0
       estraverse: 5.3.0
 
   eslint-visitor-keys@3.4.3: {}
 
-  eslint-visitor-keys@4.2.0: {}
+  eslint-visitor-keys@4.2.1: {}
 
   eslint@9.17.0(jiti@1.21.7):
     dependencies:
@@ -3167,16 +3183,16 @@ snapshots:
       '@humanfs/node': 0.16.6
       '@humanwhocodes/module-importer': 1.0.1
       '@humanwhocodes/retry': 0.4.3
-      '@types/estree': 1.0.7
+      '@types/estree': 1.0.8
       '@types/json-schema': 7.0.15
       ajv: 6.12.6
       chalk: 4.1.2
       cross-spawn: 7.0.6
       debug: 4.4.1
       escape-string-regexp: 4.0.0
-      eslint-scope: 8.3.0
-      eslint-visitor-keys: 4.2.0
-      espree: 10.3.0
+      eslint-scope: 8.4.0
+      eslint-visitor-keys: 4.2.1
+      espree: 10.4.0
       esquery: 1.6.0
       esutils: 2.0.3
       fast-deep-equal: 3.1.3
@@ -3200,11 +3216,11 @@ snapshots:
 
   esm-env@1.2.2: {}
 
-  espree@10.3.0:
+  espree@10.4.0:
     dependencies:
-      acorn: 8.14.1
-      acorn-jsx: 5.3.2(acorn@8.14.1)
-      eslint-visitor-keys: 4.2.0
+      acorn: 8.15.0
+      acorn-jsx: 5.3.2(acorn@8.15.0)
+      eslint-visitor-keys: 4.2.1
 
   espree@9.6.1:
     dependencies:
@@ -3710,11 +3726,11 @@ snapshots:
 
   minimatch@3.1.2:
     dependencies:
-      brace-expansion: 1.1.11
+      brace-expansion: 1.1.12
 
   minimatch@9.0.5:
     dependencies:
-      brace-expansion: 2.0.1
+      brace-expansion: 2.0.2
 
   minimist@1.2.8: {}
 

web/src/lib/components/chat/DropdownGroup.svelte

@@ -3,8 +3,11 @@
   import Models from "./Models.svelte";
   import ModelConfig from "./ModelConfig.svelte";
   import { Select } from "$lib/components/ui/select";
+  import { Input } from "$lib/components/ui/input";
+  import { Label } from "$lib/components/ui/label";
   import { languageStore } from '$lib/store/language-store';
   import { strategies, selectedStrategy, fetchStrategies } from '$lib/store/strategy-store';
+  import { patternVariables } from '$lib/store/pattern-store';
   import { onMount } from 'svelte';
 
   const languages = [
@@ -18,6 +21,25 @@
     { code: 'it', name: 'Italian' }
   ];
 
+  let variablesJsonString = '';
+
+  // Parse JSON string and update variables store
+  function updateVariables() {
+    try {
+      if (variablesJsonString.trim() === '') {
+        patternVariables.set({});
+      } else {
+        const parsed = JSON.parse(variablesJsonString);
+        if (typeof parsed === 'object' && parsed !== null && !Array.isArray(parsed)) {
+          patternVariables.set(parsed);
+        }
+      }
+    } catch (e) {
+      // Don't update the store if JSON is invalid - just ignore the error
+      // This allows partial typing without breaking
+    }
+  }
+
   onMount(() => {
     fetchStrategies();
   });
@@ -33,7 +55,7 @@
       <Models />
     </div>
     <div>
-      <Select 
+      <Select
         bind:value={$languageStore}
         class="bg-primary-800/30 border-none hover:bg-primary-800/40 transition-colors"
       >
@@ -43,7 +65,7 @@
       </Select>
     </div>
     <div>
-      <Select 
+      <Select
         bind:value={$selectedStrategy}
         class="bg-primary-800/30 border-none hover:bg-primary-800/40 transition-colors"
       >
@@ -53,8 +75,19 @@
         {/each}
       </Select>
     </div>
+    <div>
+      <Label for="pattern-variables" class="text-xs text-white/70 mb-1 block">Pattern Variables (JSON)</Label>
+      <textarea
+        id="pattern-variables"
+        bind:value={variablesJsonString}
+        on:input={updateVariables}
+        placeholder="{`{\"lang_code\": \"fr\", \"role\": \"expert\"}`}"
+        class="w-full h-20 px-3 py-2 text-sm bg-primary-800/30 border-none rounded-md hover:bg-primary-800/40 transition-colors text-white placeholder-white/50 resize-none focus:ring-1 focus:ring-white/20 focus:outline-none"
+        style="font-family: 'JetBrains Mono', 'Fira Code', 'Consolas', monospace;"
+      ></textarea>
+    </div>
   </div>
-  
+
   <!-- Right side - Model Config -->
   <div class="w-[65%]">
     <ModelConfig />

web/src/lib/interfaces/chat-interface.ts

@@ -8,6 +8,7 @@ export interface ChatPrompt {
   model: string;
   patternName?: string;
   strategyName?: string; // Optional strategy name to prepend strategy prompt
+  variables?: { [key: string]: string }; // Pattern variables
 }
 
 export interface ChatConfig {

web/src/lib/services/ChatService.ts

@@ -6,7 +6,7 @@ import type {
 } from '$lib/interfaces/chat-interface';
 import { get } from 'svelte/store';
 import { modelConfig } from '$lib/store/model-store';
-import { systemPrompt, selectedPatternName } from '$lib/store/pattern-store';
+import { systemPrompt, selectedPatternName, patternVariables } from '$lib/store/pattern-store';
 import { chatConfig } from '$lib/store/chat-config';
 import { messageStore } from '$lib/store/chat-store';
 import { languageStore } from '$lib/store/language-store';
@@ -75,48 +75,46 @@ export class ChatService {
 
   private cleanPatternOutput(content: string): string {
     // Remove markdown fence if present
-    content = content.replace(/^```markdown\n/, '');
-    content = content.replace(/\n```$/, '');
-    
+    let cleaned = content.replace(/^```markdown\n/, '');
+    cleaned = cleaned.replace(/\n```$/, '');
+
     // Existing cleaning
-    content = content.replace(/^# OUTPUT\s*\n/, '');
-    content = content.replace(/^\s*\n/, '');
-    content = content.replace(/\n\s*$/, '');
-    content = content.replace(/^#\s+([A-Z]+):/gm, '$1:');
-    content = content.replace(/^#\s+([A-Z]+)\s*$/gm, '$1');
-    content = content.trim();
-    content = content.replace(/\n{3,}/g, '\n\n');
-    return content;
+    cleaned = cleaned.replace(/^# OUTPUT\s*\n/, '');
+    cleaned = cleaned.replace(/^\s*\n/, '');
+    cleaned = cleaned.replace(/\n\s*$/, '');
+    cleaned = cleaned.replace(/^#\s+([A-Z]+):/gm, '$1:');
+    cleaned = cleaned.replace(/^#\s+([A-Z]+)\s*$/gm, '$1');
+    cleaned = cleaned.trim();
+    cleaned = cleaned.replace(/\n{3,}/g, '\n\n');
+    return cleaned;
   }
-  
-      
-      
-      private createMessageStream(reader: ReadableStreamDefaultReader<Uint8Array>): ReadableStream<StreamResponse> {
-          let buffer = '';
-          const cleanPatternOutput = this.cleanPatternOutput.bind(this);
-          const language = get(languageStore);
-          const validator = new LanguageValidator(language);
-      
-          const processResponse = (response: StreamResponse) => {
-              const pattern = get(selectedPatternName);
-              
-              if (pattern) {
-                  response.content = cleanPatternOutput(response.content);
-                  // Simplified format determination - always markdown unless mermaid
-                  const isMermaid = [
-                      'graph TD', 'gantt', 'flowchart', 
-                      'sequenceDiagram', 'classDiagram', 'stateDiagram'
-                  ].some(starter => response.content.trim().startsWith(starter));
-                  
-                  response.format = isMermaid ? 'mermaid' : 'markdown';
-              }
-      
-              if (response.type === 'content') {
-                  response.content = validator.enforceLanguage(response.content);
-              }
-      
-              return response;
-          };
+
+  private createMessageStream(reader: ReadableStreamDefaultReader<Uint8Array>): ReadableStream<StreamResponse> {
+      let buffer = '';
+      const cleanPatternOutput = this.cleanPatternOutput.bind(this);
+      const language = get(languageStore);
+      const validator = new LanguageValidator(language);
+
+      const processResponse = (response: StreamResponse) => {
+          const pattern = get(selectedPatternName);
+
+          if (pattern) {
+              response.content = cleanPatternOutput(response.content);
+              // Simplified format determination - always markdown unless mermaid
+              const isMermaid = [
+                  'graph TD', 'gantt', 'flowchart',
+                  'sequenceDiagram', 'classDiagram', 'stateDiagram'
+              ].some(starter => response.content.trim().startsWith(starter));
+
+              response.format = isMermaid ? 'mermaid' : 'markdown';
+          }
+
+          if (response.type === 'content') {
+              response.content = validator.enforceLanguage(response.content);
+          }
+
+          return response;
+      };
       return new ReadableStream({
           async start(controller) {
               try {
@@ -162,18 +160,18 @@ export class ChatService {
           }
       });
   }
- 
+
   private createChatPrompt(userInput: string, systemPromptText?: string): ChatPrompt {
     const config = get(modelConfig);
     const language = get(languageStore);
-    
-    const languageInstruction = language !== 'en' 
+
+    const languageInstruction = language !== 'en'
         ? `You MUST respond in ${language} language. All output must be in ${language}. `
         // ? `You MUST respond in ${language} language. ALL output, including section headers, titles, and formatting, MUST be translated into ${language}.  It is CRITICAL that you translate ALL headers, such as SUMMARY, IDEAS, QUOTES, TAKEAWAYS, MAIN POINTS, etc., into ${language}. Maintain markdown formatting in the response. Do not output any English headers.`
         : '';
-    
+
     const finalSystemPrompt = languageInstruction + (systemPromptText ?? get(systemPrompt));
-    
+
     const finalUserInput = language !== 'en'
         ? `${userInput}\n\nIMPORTANT: Respond in ${language} language only.`
         : userInput;
@@ -183,15 +181,11 @@ export class ChatService {
         systemPrompt: finalSystemPrompt,
         model: config.model,
         patternName: get(selectedPatternName),
-        strategyName: get(selectedStrategy) // Add selected strategy to prompt
+        strategyName: get(selectedStrategy), // Add selected strategy to prompt
+        variables: get(patternVariables) // Add pattern variables
     };
 }
 
-
-  
-    
-
-
   public async createChatRequest(userInput: string, systemPromptText?: string, isPattern: boolean = false): Promise<ChatRequest> {
     const prompt = this.createChatPrompt(userInput, systemPromptText);
     const config = get(chatConfig);
@@ -221,16 +215,16 @@ export class ChatService {
     onError: (error: Error) => void
   ): Promise<void> {
     const reader = stream.getReader();
-  
+
     try {
       while (true) {
         const { done, value } = await reader.read();
         if (done) break;
-  
+
         if (value.type === 'error') {
           throw new ChatError(value.content, 'STREAM_CONTENT_ERROR');
         }
-  
+
         if (value.type === 'content') {
           onContent(value.content, value);
         }
@@ -239,11 +233,7 @@ export class ChatService {
       onError(error instanceof ChatError ? error : new ChatError('Stream processing error', 'STREAM_ERROR', error));
     } finally {
       reader.releaseLock();
-      
+
     }
   }
-  
-  
-   
-    
 }

web/src/lib/store/pattern-store.ts

@@ -15,11 +15,11 @@ export const patterns = derived(
     return $allPatterns.filter(p => {
       // Keep all patterns if no language is selected
       if (!$language) return true;
-      
+
       // Check if pattern has a language prefix (e.g., en_, fr_)
       const match = p.Name.match(/^([a-z]{2})_/);
       if (!match) return true; // Keep patterns without language prefix
-      
+
       // Only filter out patterns that have a different language prefix
       const patternLang = match[1];
       return patternLang === $language;
@@ -30,6 +30,9 @@ export const patterns = derived(
 export const systemPrompt = writable<string>('');
 export const selectedPatternName = writable<string>('');
 
+// Pattern variables store
+export const patternVariables = writable<Record<string, string>>({});
+
 export const setSystemPrompt = (prompt: string) => {
   console.log('Setting system prompt:', prompt);
   systemPrompt.set(prompt);
@@ -60,13 +63,13 @@ export const patternAPI = {
           const patternResponse = await fetch(`/api/patterns/${pattern}`);
           const patternData = await patternResponse.json();
           console.log(`Pattern ${pattern} content length:`, patternData.Pattern?.length || 0);
-          
+
           // Find matching description from JSON
           const desc = descriptions.find(d => d.patternName === pattern);
           if (!desc) {
             console.warn(`No description found for pattern: ${pattern}`);
           }
-          
+
           return {
             Name: pattern,
             Description: desc?.description || pattern.charAt(0).toUpperCase() + pattern.slice(1),

web/static/data/pattern_descriptions.json

@@ -1634,8 +1634,8 @@
       ]
     },
     {
-      "patternName": "write_essay",
-      "description": "Create essays with thesis statements and arguments.",
+      "patternName": "write_essay_pg",
+      "description": "Create essays with thesis statements and arguments in the style of Paul Graham.",
       "tags": [
         "WRITING",
         "RESEARCH",
@@ -1703,7 +1703,7 @@
     {
       "patternName": "analyze_bill",
       "description": "Analyze a legislative bill and implications.",
-      "tags": [ 
+      "tags": [
         "ANALYSIS",
         "BILL"
       ]
@@ -1711,14 +1711,14 @@
     {
       "patternName": "analyze_bill_short",
       "description": "Consended - Analyze a legislative bill and implications.",
-      "tags": [ 
+      "tags": [
         "ANALYSIS",
         "BILL"
       ]
     },
     {
       "patternName": "create_coding_feature",
-      "description": "[Description pending]",
+      "description": "Generate secure and composable code features using latest technology and best practices.",
       "tags": [
         "DEVELOPMENT"
       ]
@@ -1774,6 +1774,47 @@
       "tags": [
         "SUMMARIZE"
       ]
+    },
+    {
+      "patternName": "analyze_paper_simple",
+      "description": "Analyze research papers to determine primary findings and assess scientific rigor.",
+      "tags": [
+        "ANALYSIS",
+        "RESEARCH",
+        "WRITING"
+      ]
+    },
+    {
+      "patternName": "analyze_terraform_plan",
+      "description": "Analyze Terraform plans for infrastructure changes, security risks, and cost implications.",
+      "tags": [
+        "ANALYSIS",
+        "DEVOPS"
+      ]
+    },
+    {
+      "patternName": "create_mnemonic_phrases",
+      "description": "Create memorable mnemonic sentences using given words in exact order for memory aids.",
+      "tags": [
+        "CREATIVITY",
+        "LEARNING"
+      ]
+    },
+    {
+      "patternName": "summarize_board_meeting",
+      "description": "Convert board meeting transcripts into formal meeting notes for corporate records.",
+      "tags": [
+        "ANALYSIS",
+        "BUSINESS"
+      ]
+    },
+    {
+      "patternName": "write_essay",
+      "description": "Write essays on given topics in the distinctive style of specified authors.",
+      "tags": [
+        "WRITING",
+        "CREATIVITY"
+      ]
     }
   ]
 }