prjct-cli 0.10.11 → 0.10.13

package/core/utils/branding.js

@@ -0,0 +1,47 @@
+/**
+ * Branding Configuration for prjct-cli
+ * Single source of truth for all branding across CLI and Claude Code
+ */
+
+const chalk = require('chalk')
+
+const SPINNER_FRAMES = ['⠋', '⠙', '⠹', '⠸', '⠼', '⠴', '⠦', '⠧', '⠇', '⠏']
+const SPINNER_SPEED = 80
+
+const branding = {
+  // Core identity
+  name: 'prjct',
+  icon: '⚡',
+  signature: '⚡ prjct',
+
+  // Spinner config
+  spinner: {
+    frames: SPINNER_FRAMES,
+    speed: SPINNER_SPEED
+  },
+
+  // CLI output (with chalk colors)
+  cli: {
+    header: () => chalk.cyan.bold('⚡') + ' ' + chalk.cyan('prjct'),
+    footer: () => chalk.dim('⚡ prjct'),
+    spin: (frame, msg) => chalk.cyan('⚡') + ' ' + chalk.cyan('prjct') + ' ' + chalk.cyan(SPINNER_FRAMES[frame % 10]) + ' ' + chalk.dim(msg || '')
+  },
+
+  // Template/Claude (plain text)
+  template: {
+    header: '⚡ prjct',
+    footer: '⚡ prjct'
+  },
+
+  // Git commit footer
+  commitFooter: `🤖 Generated with [p/](https://www.prjct.app/)
+Designed for [Claude](https://www.anthropic.com/claude)`,
+
+  // URLs
+  urls: {
+    website: 'https://prjct.app',
+    docs: 'https://prjct.app/docs'
+  }
+}
+
+module.exports = branding

package/core/utils/output.js

@@ -1,24 +1,39 @@
 /**
  * Minimal Output System for prjct-cli
  * Spinner while working → Single line result
+ * With ⚡ prjct branding
  */
 
 const chalk = require('chalk')
+const branding = require('./branding')
 
-const FRAMES = ['⠋', '⠙', '⠹', '⠸', '⠼', '⠴', '⠦', '⠧', '⠇', '⠏']
-const SPEED = 80
+const FRAMES = branding.spinner.frames
+const SPEED = branding.spinner.speed
 
 let interval = null
 let frame = 0
 
 const truncate = (s, max = 50) => (s && s.length > max ? s.slice(0, max - 1) + '…' : s || '')
-const clear = () => process.stdout.write('\r' + ' '.repeat(70) + '\r')
+const clear = () => process.stdout.write('\r' + ' '.repeat(80) + '\r')
 
 const out = {
+  // Branding: Show header at start
+  start() {
+    console.log(branding.cli.header())
+    return this
+  },
+
+  // Branding: Show footer at end
+  end() {
+    console.log(branding.cli.footer())
+    return this
+  },
+
+  // Branded spinner: ⚡ prjct ⠋ message...
   spin(msg) {
     this.stop()
     interval = setInterval(() => {
-      process.stdout.write(`\r${chalk.cyan(FRAMES[frame++ % 10])} ${truncate(msg, 55)}`)
+      process.stdout.write(`\r${branding.cli.spin(frame++, truncate(msg, 45))}`)
     }, SPEED)
     return this
   },

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "prjct-cli",
-  "version": "0.10.11",
+  "version": "0.10.13",
   "description": "Built for Claude - Ship fast, track progress, stay focused. Developer momentum tool for indie hackers.",
   "main": "core/index.js",
   "bin": {

package/templates/agent-assignment.md

@@ -0,0 +1,72 @@
+---
+name: agent-assignment
+description: Assign the best agent for a task
+allowed-tools: [Read]
+---
+
+# Agent Assignment
+
+Select the best agent for the given task based on semantic understanding.
+
+## Input
+
+- **Task**: {{task}}
+- **Available Agents**: {{agents}}
+- **Project Context**: {{context}}
+
+## Instructions
+
+1. **Understand the Task**
+   - What domain does this task belong to?
+   - What skills are required?
+   - What is the complexity level?
+
+2. **Analyze Available Agents**
+   - Read each agent's expertise and domain
+   - Consider their skills and past success
+   - Match capabilities to task requirements
+
+3. **Select Best Agent**
+   - Choose the agent with highest relevance
+   - If multiple agents fit, prefer the specialist over generalist
+   - If no good match, use 'generalist' or 'full-stack'
+
+## Decision Criteria
+
+- **Domain Match**: Does the agent's domain align with the task?
+- **Skills Match**: Does the agent have the required skills?
+- **Complexity Fit**: Is the agent appropriate for this complexity level?
+
+## Output Format
+
+Return JSON with your decision:
+
+```json
+{
+  "agent": "agent-name",
+  "confidence": 0.85,
+  "reason": "Brief explanation of why this agent was selected",
+  "domain": "detected domain of the task"
+}
+```
+
+## Examples
+
+**Task**: "Implement React login component with form validation"
+**Decision**: `{ "agent": "frontend-specialist", "confidence": 0.95, "reason": "React component work requires frontend expertise", "domain": "frontend" }`
+
+**Task**: "Fix database connection timeout issue"
+**Decision**: `{ "agent": "backend-specialist", "confidence": 0.90, "reason": "Database issues require backend/infrastructure knowledge", "domain": "backend" }`
+
+**Task**: "Write unit tests for user service"
+**Decision**: `{ "agent": "qa-specialist", "confidence": 0.85, "reason": "Testing tasks benefit from QA expertise", "domain": "qa" }`
+
+**Task**: "Update README documentation"
+**Decision**: `{ "agent": "generalist", "confidence": 0.70, "reason": "Documentation is general task, no specialist needed", "domain": "docs" }`
+
+## Guidelines
+
+- Prefer specialists when task clearly fits their domain
+- Use generalist only when no specialist matches
+- Higher confidence = stronger match
+- Always provide a reason for transparency