@withmata/blueprints 0.5.0 → 3.0.0

package/blueprints/thinking/thinking-partner/templates/reflection-template.md

@@ -0,0 +1,131 @@
+# Reflection: [Topic in the user's own words]
+
+**Date:** [YYYY-MM-DD]
+**Session length:** [approximate, e.g. "~90 min"]
+**Frameworks applied:** [Named list, e.g. "5 Whys, Steelmanning, Letter from Future Self"]
+
+---
+
+## Where I Started
+
+[The original framing, in the user's own words. What they said the question was when the session opened. What they thought the goal was. What they thought they wanted to figure out.]
+
+> "[Direct quote from how the user opened the session, if it was vivid]"
+
+---
+
+## What the Question Actually Was
+
+[The real question, as it surfaced through Phase 1. How it differs from where they started. What shifted in the framing.]
+
+[Be honest about whether the surface question was already pretty close, or whether it was masking something else entirely. Don't manufacture a dramatic shift if there wasn't one.]
+
+---
+
+## The Facts We Worked From
+
+[Concrete events, behaviors, numbers, conversations — the things we treated as ground truth. Separate this from interpretations. This is the "what is actually happening" layer.]
+
+- [Fact 1]
+- [Fact 2]
+- [Fact 3]
+
+### What we checked
+
+[Anything that was researched during the session, and what we found. Be specific — link sources where applicable. Note where evidence supported the user's framing and where it pushed back.]
+
+- **Claim:** [What was claimed] -> **Found:** [What the evidence actually said]
+- **Claim:** [...] -> **Found:** [...]
+
+### Assumptions we surfaced
+
+[Things the user was treating as fact that turned out to be assumption. Things the user hadn't realized they believed. Inherited framings.]
+
+- [Assumption 1 — and what we did with it]
+- [Assumption 2]
+
+---
+
+## The Walkthrough
+
+[The narrative middle. This is the heart of the document. Tell the story of how the thinking moved.]
+
+### [Framework 1, e.g. "5 Whys on the goal"]
+
+[What this framework is and why it fit. What it surfaced. The actual chain or output. What changed because of it.]
+
+### [Framework 2, e.g. "Steelmanning the path I was rejecting"]
+
+[Same structure. What was the strongest case for the rejected path? What did it expose?]
+
+### [Framework 3, if used]
+
+[...]
+
+### Moments that shifted things
+
+[The "huh" moments. When something clicked, when a framing fell apart, when an emotion surfaced that changed the analysis. Quote yourself if a specific phrase from the user captured it.]
+
+> "[A direct user quote from the session that captures a turning point]"
+
+---
+
+## Where I Landed
+
+### The direction
+
+[One paragraph, in the user's voice, describing the chosen direction. Not a bullet list — a sentence or two that the user can read in a month and understand what they decided.]
+
+### The why, in one sentence
+
+> [The user's articulation, edited for clarity but kept in their voice.]
+
+### What I'm choosing against
+
+[The path not taken, and the strongest version of why someone might take it anyway. This is here so future-self knows it was considered, not ignored.]
+
+[If/when this comes up again, here's what I'd want to remember about why I didn't go this way: ...]
+
+---
+
+## What I'm Sitting With
+
+[Things that aren't fully resolved. Honest uncertainty. Tradeoffs the user accepted rather than solved. This section matters — pretending everything is settled is a failure mode.]
+
+- [Uncertainty 1]
+- [Uncertainty 2]
+- [Tradeoff I'm accepting]
+
+---
+
+## What I'll Revisit, and When
+
+[Concrete checkpoints. Not vague "I'll see how it goes" — actual triggers or dates.]
+
+| What | When | What would change my mind |
+|------|------|---------------------------|
+| [Decision/assumption to revisit] | [Date or trigger] | [What evidence would push me to reconsider] |
+
+---
+
+## The Recommendation, As Input
+
+[If the agent made a recommendation during the session, capture it here verbatim — even if the user chose differently. The point is to have the alternative viewpoint preserved, not to override the user's choice.]
+
+> Agent recommendation: [What was recommended and the reasoning, in 2-3 sentences]
+>
+> What I'm doing with it: [Took it / partially / set it aside because of X]
+
+---
+
+## Frameworks I Want to Remember
+
+[A short list of the techniques used in this session, with one-sentence reminders of when they apply. The point: next time the user is thinking through something on their own, they have these tools named.]
+
+- **[Framework 1]** — [When to reach for it, in one sentence]
+- **[Framework 2]** — [When to reach for it]
+- **[Framework 3]** — [When to reach for it]
+
+---
+
+*Generated through a `/reflect` session. The walkthrough above is the journey, not a verdict. If conditions change or the situation looks different in a few weeks, run another session.*

package/dist/index.js

@@ -6,7 +6,7 @@ import pc4 from "picocolors";
 
 // src/constants.ts
 var API_URL = process.env["WITHMATA_API_URL"] || "https://blueprints.withmata.dev";
-var VERSION = "0.5.0";
+var VERSION = "3.0.0";
 
 // src/lib/install-state.ts
 import { existsSync, readdirSync, lstatSync, readlinkSync } from "fs";
@@ -269,7 +269,7 @@ function isBlueprintsRepo(dir) {
 function discoverBlueprints(blueprintsDir) {
   const ids = [];
   if (!existsSync3(blueprintsDir)) return ids;
-  const tiers = ["discovery", "foundation", "features"];
+  const tiers = ["discovery", "foundation", "features", "thinking"];
   for (const tier of tiers) {
     const tierDir = join3(blueprintsDir, tier);
     if (!existsSync3(tierDir)) continue;
@@ -483,6 +483,15 @@ var SKILL_GROUPS = [
         description: "Check project health and find available upgrades"
       }
     ]
+  },
+  {
+    title: "Think",
+    skills: [
+      {
+        command: "/reflect",
+        description: "Run a structured thinking-partner session on any personal topic"
+      }
+    ]
   }
 ];
 function showSummary({

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@withmata/blueprints",
-  "version": "0.5.0",
+  "version": "3.0.0",
   "description": "Set up AI-powered project blueprints for Claude Code, OpenCode, and Cursor",
   "type": "module",
   "bin": {

package/blueprints/features/env-t3/files/nextjs/.env.example

@@ -1,17 +0,0 @@
-# =============================================================================
-# {{APP_NAME}} — Environment Variables
-# =============================================================================
-# Copy this file to .env.local and fill in the values.
-# Feature blueprints will add their own variables — check their BLUEPRINT.md.
-
-# -----------------------------------------------------------------------------
-# App
-# -----------------------------------------------------------------------------
-
-# Frontend URL (used for redirects, CORS, and metadata)
-# Local: http://localhost:3000 | Production: https://yourdomain.com
-NEXT_PUBLIC_FRONTEND_URL=http://localhost:3000
-
-# CONFIGURE: Feature blueprints add variables here:
-# - /scaffold-auth adds: BETTER_AUTH_URL, BETTER_AUTH_SECRET, GOOGLE_CLIENT_ID, etc.
-# - /scaffold-db adds: DATABASE_URL (in packages/db/.env for monorepos)

package/blueprints/features/env-t3/files/server/.env.example

@@ -1,14 +0,0 @@
-# =============================================================================
-# {{APP_NAME}} Server — Environment Variables
-# =============================================================================
-# Copy this file to .env.local and fill in the values.
-
-# -----------------------------------------------------------------------------
-# Server Configuration
-# -----------------------------------------------------------------------------
-
-# Port the server listens on
-# Local: 4000 | Production: Set by hosting platform
-PORT=4000
-
-# CONFIGURE: Add server-specific variables below