@esoteric-logic/praxis-harness 3.1.2 → 3.2.0

package/base/skills/px-prompt/SKILL.md

@@ -39,13 +39,17 @@ Do NOT show "Work on praxis" or "Work on maximus" or any project name — the en
 
 Platform outputs use suffixed filenames so users can distinguish them at a glance:
 
-| Platform | Output Filename | Budget |
-|----------|----------------|--------|
-| Source (Claude Projects) | `system-prompt.md` | 5,000 chars |
-| Claude Desktop / Projects | `project-instructions-claude-desktop.md` | 2,500 chars |
-| Perplexity Spaces | `space-instructions-perplexity.md` | 4,000 chars |
+| Platform | Output Filename | Budget | When |
+|----------|----------------|--------|------|
+| Claude Projects | `system-prompt.md` | 5,000 chars | Standalone projects |
+| Claude Projects | `project-instructions-claude-desktop.md` | 2,500 chars | Compiled projects (compiler output) |
+| Perplexity Spaces | `space-instructions-perplexity.md` | 4,000 chars | All projects |
 
-Claude Code `CLAUDE.md` is NOT generated by this skill — use `px-scaffold` for repo-level CLAUDE.md files.
+Each project has exactly **2 output files** — one for Claude Projects, one for Perplexity Spaces.
+- Standalone: `system-prompt.md` + `space-instructions-perplexity.md`
+- Compiled: `project-instructions-claude-desktop.md` + `space-instructions-perplexity.md`
+
+Claude Code `CLAUDE.md` is NOT generated by this skill — use `px-scaffold`.
 
 All output files live in the project's folder under `prompts/work/` or `prompts/personal/`.
 Reference/knowledge files live in `<project>/references/`.
@@ -361,7 +365,7 @@ For each research domain:
 
 ## Step 3 — CONDENSE: Generate platform outputs from system-prompt.md
 
-**Triggered when:** standalone project has `system-prompt.md` but missing `space-instructions-perplexity.md` or `project-instructions-claude-desktop.md`.
+**Triggered when:** standalone project has `system-prompt.md` but missing `space-instructions-perplexity.md`.
 
 Read the full `system-prompt.md` as source.
 
@@ -408,18 +412,11 @@ Think step-by-step: Understand the question → search sources → analyze findi
 - Replace absolute language with conditional ("if available", "when sources confirm")
 - Search-friendly domain terms
 
-### 3b. Generate Claude Desktop project instructions (if Claude Projects is a target platform)
-
-**Target:** `project-instructions-claude-desktop.md` | **Budget:** under 2,500 chars
-
-**Include:** role, behavioral constraints, domain expertise (condensed), output format, quality controls, when uncertain
-**Exclude:** full domain details (those go in knowledge files), reference content, deployment details
-
-### 3c. Validate budgets
+### 3b. Validate budgets
 
 After generating, check:
+- `system-prompt.md` under 5,000 chars
 - `space-instructions-perplexity.md` under 4,000 chars
-- `project-instructions-claude-desktop.md` under 2,500 chars
 
 If over budget: flag and suggest sections to trim.
 
@@ -442,7 +439,6 @@ node bin/prompt-compile.js <project-name>
 | Output                                   | Chars  | Budget | Status |
 |------------------------------------------|--------|--------|--------|
 | system-prompt.md                         | X      | 5,000  | Source |
-| project-instructions-claude-desktop.md   | X      | 2,500  | OK     |
 | space-instructions-perplexity.md         | X      | 4,000  | OK     |
 | references/                              | N files| —      | Upload |
 ```
@@ -451,7 +447,7 @@ node bin/prompt-compile.js <project-name>
 
 **Claude Desktop / Projects (claude.ai):**
 1. Open project at claude.ai/projects → "Set project instructions"
-2. Standalone: paste `system-prompt.md` | Compiled: paste `project-instructions-claude-desktop.md`
+2. Paste `system-prompt.md` (standalone) or `project-instructions-claude-desktop.md` (compiled)
 3. If `references/` exists: upload each `.md` file as project knowledge
 4. Save
 
@@ -497,7 +493,7 @@ Print deployment reminders for any project with changes.
 ### 6a. Read all project files
 1. Read `prompt-config.yaml` for project metadata
 2. Read `system-prompt.md` (source of truth)
-3. Read all platform outputs (`space-instructions-perplexity.md`, `project-instructions-claude-desktop.md`)
+3. Read platform outputs (`system-prompt.md` or `project-instructions-claude-desktop.md`, `space-instructions-perplexity.md`)
 4. Read all files in `references/` directory
 5. List any other files in the project folder
 
@@ -513,8 +509,9 @@ Check each file against these criteria:
 - Are all referenced knowledge files present in references/?
 
 **Budget checks:**
+- `system-prompt.md` under 5,000 chars? (standalone)
+- `project-instructions-claude-desktop.md` under 2,500 chars? (compiled)
 - `space-instructions-perplexity.md` under 4,000 chars?
-- `project-instructions-claude-desktop.md` under 2,500 chars?
 
 **Currency checks (via Perplexity):**
 - Are domain-specific terms, standards, and versions still current?
@@ -740,7 +737,7 @@ Maximus PP:  2 contracts at IRS (from USASpending)
 Gaps:        Key personnel [RESEARCH NEEDED]
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 Files created:
-  ✓ project-instructions-claude-desktop.md (2,480 chars)
+  ✓ project-instructions-claude-desktop.md (2,480 chars) — compiled from profile
   ✓ space-instructions-perplexity.md (3,976 chars) — deal-specific research domains
   ✓ references/irs-masterfile-intel.md
   ✓ knowledge/deal-context.md
@@ -827,7 +824,7 @@ EDIT APPLIED
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 Changed: <file(s) modified>
 Regenerated: <platform outputs updated>
-Budget: perplexity ✓ | claude-desktop ✓
+Budget: claude-projects ✓ | perplexity ✓
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 ```
 
@@ -933,11 +930,10 @@ Determine which platforms are targets from `prompt-config.yaml`.
 ### 11b. Deploy sequence (per platform)
 
 **For Claude Projects / Desktop:**
-1. Read `system-prompt.md` (standalone) or `project-instructions-claude-desktop.md` (compiled)
-2. Copy content to clipboard: `cat <file> | pbcopy`
+1. Determine file: `system-prompt.md` (standalone) or `project-instructions-claude-desktop.md` (compiled)
+2. Copy to clipboard: `cat <file> | pbcopy`
 3. Print: "Copied to clipboard. Paste at: claude.ai/projects → Set project instructions"
 4. List knowledge files to upload: all `.md` files from `references/` AND `knowledge/`
-5. Print upload instructions: "Upload these as project knowledge files (drag & drop):"
 
 **For Perplexity Spaces:**
 1. Read `space-instructions-perplexity.md`
@@ -1106,8 +1102,9 @@ NEXT GATE CHECKLIST: Pre-Proposal
 - **Claude Code CLAUDE.md**: NOT generated by px-prompt — use px-scaffold
 
 ### File naming
-- **Always** use platform-suffixed filenames: `space-instructions-perplexity.md`, `project-instructions-claude-desktop.md`
-- `system-prompt.md` keeps its name (it's the source of truth, not platform-specific)
+- Standalone Claude Projects output: `system-prompt.md`
+- Compiled Claude Projects output: `project-instructions-claude-desktop.md`
+- Perplexity output: `space-instructions-perplexity.md`
 
 ### Quality defaults (mandatory in all generated prompts)
 - Anti-Hallucination Protocol: never fabricate, cite sources, flag confidence, distinguish fact from inference

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@esoteric-logic/praxis-harness",
-  "version": "3.1.2",
+  "version": "3.2.0",
   "description": "Layered Claude Code harness — workflow discipline, AI-Kits, persistent vault integration",
   "bin": {
     "praxis-harness": "./bin/praxis.js",

package/prompts/work/ecs-limited/projects/soc2-zero-trust/project-instructions-claude-desktop.md

@@ -1,32 +0,0 @@
-## Role
-Solutions architect supporting ECS Limited's Azure Zero Trust security engagement. Brownfield Azure environment (50-100+ apps, 50-100 VMs) targeting SOC 2 Type 2 and ISO 27001:2022 readiness.
-
-## Engagement Context
-3-phase contractor engagement: Discovery → Zero Trust Implementation → Future Architecture. 93 checklist items (84 contractor, 9 internal). No hard compliance deadline.
-
-## Behavioral Constraints
-- Lead with recommendations and rationale, not options lists
-- Verify claims against the engagement SOW and knowledge files before presenting as fact
-- When uncertain, ask one clarifying question. Flag confidence: HIGH / MEDIUM / LOW
-
-## Domain Expertise
-- Tiered network: User → Web → App/API → Data (deny-all default, no direct backend access)
-- Uncontrolled device model: all devices untrusted, no compliance gates. PAW for admin only.
-- Environment parity: dev = staging = prod for all security controls
-- Azure stack: Entra ID, Conditional Access, PIM, Firewall, NSGs, Private Link, Sentinel, Defender, Key Vault
-- SOC 2 TSC (2017/2022), ISO 27001:2022
-- 6 critical risks: R-01 (segmentation outages), R-05 (trusted client apps), R-07 (env parity), R-22 (dev adaptation), R-26 (client disruption), R-28 (no detection during transition)
-
-## Output Format
-- Tables for control mappings, gap analyses, risk assessments
-- Map to 93-item engagement checklist where applicable
-- BLUF structure: bottom line, evidence, next steps
-
-## Quality Controls
-- Cross-reference SOW and knowledge files. Flag contradictions.
-- Never fabricate version numbers, dates, statistics, or citations
-- Cite specific TSC criteria and ISO controls by reference
-- Flag information older than 12 months
-
-## When Uncertain
-State uncertainty explicitly. Flag confidence: HIGH (verified), MEDIUM (corroborated), LOW (inferred).