@compilr-dev/sdk 0.9.24 → 0.9.26

package/dist/project-types/configs.js

@@ -106,6 +106,15 @@ Specialized agents may be available:
 - **Architect** — system design, technical decisions
 - **PM** — requirements, backlog management, priorities
 Suggest delegation when a task would benefit from focused expertise.`,
+    tagline: 'Build a web app, API, CLI, or library — from idea to running code.',
+    bestFor: 'you have an idea and want compilr.dev to help you ship it.',
+    produces: [
+        'Application model + entities',
+        'PRD + architecture',
+        'Working code (scaffolded)',
+        'Backlog of features',
+        'Session notes',
+    ],
 };
 // =============================================================================
 // General (blank slate)
@@ -134,6 +143,9 @@ You are assisting with a general-purpose project. Adapt your approach to whateve
 - Use work items to track tasks and progress
 - Use documents to store important artifacts
 - Suggest team agents if the project would benefit from specialization`,
+    tagline: 'An empty workspace — define your own workflow as you go.',
+    bestFor: "you don't see a fit above and want a blank slate.",
+    produces: ['Notes & documents', 'Conversations with agents', 'Whatever you build'],
 };
 // =============================================================================
 // Research Paper / Academic
@@ -288,6 +300,15 @@ Suggest delegation when a task would benefit from focused expertise. For example
 - \`/draft-section\` — write a section using outline + claims + sources (when available)
 - \`/peer-review\` — validate argument structure and consistency (when available)
 - \`/session-notes\` — summarize work done in this session`,
+    tagline: 'Write an academic paper, thesis, or research report — outline to bibliography.',
+    bestFor: "you're writing something with a literature review and citations.",
+    produces: [
+        'Outline + abstract',
+        'Literature review',
+        'Drafted sections',
+        'Bibliography (BibTeX-ready)',
+        'Session notes',
+    ],
 };
 // =============================================================================
 // Business Plan / Startup
@@ -401,6 +422,15 @@ You are assisting with a business plan or startup project. Your role is to help
 - **Analyst** — market research, competitive intelligence, data analysis
 - **Strategist** — business model, go-to-market, positioning
 - **Writer** — pitch narrative, executive summary, investor communication`,
+    tagline: 'Build a business plan, market analysis, and pitch deck — from idea to investor-ready.',
+    bestFor: "you're planning a venture, raising money, or entering a new market.",
+    produces: [
+        'Executive summary',
+        'Market & competitor analysis',
+        'Financial model',
+        'Positioning matrix',
+        'Pitch outline',
+    ],
 };
 // =============================================================================
 // Content / Blog / Marketing
@@ -528,6 +558,15 @@ This project uses a Brand Model that captures visual identity (logos, colors, fo
 - **Visual Director** — visual briefs from Brand Model guidelines
 - **Editor** — voice consistency, brand alignment, quality review
 Suggest delegation when a task benefits from focused expertise.`,
+    tagline: 'Plan and write articles, blog posts, and social content — at the pace of a publication.',
+    bestFor: "you're producing content on a calendar and want help shipping it.",
+    produces: [
+        'Editorial calendar',
+        'Article drafts',
+        'Headlines & social variants',
+        'SEO outlines',
+        'Style guide',
+    ],
 };
 // =============================================================================
 // Technical Documentation
@@ -613,6 +652,15 @@ You are assisting with a technical documentation project. Your role is to help t
 - **Writer** — drafting documentation, tutorials, guides
 - **Editor** — clarity, consistency, grammar, readability
 - **Reviewer** — technical accuracy, completeness, correctness`,
+    tagline: 'Write API docs, user guides, and tutorials that read like a real product.',
+    bestFor: 'your project needs docs, or docs ARE the project.',
+    produces: [
+        'Getting started guide',
+        'API reference',
+        'Tutorials',
+        'Concept explanations',
+        'Changelog drafts',
+    ],
 };
 // =============================================================================
 // Course / Training Material
@@ -725,6 +773,15 @@ This project uses a Curriculum Model that tracks the course structure: modules (
 - **Instructor** — curriculum design, sequencing, pedagogy
 - **Content Designer** — lesson planning, exercises, assessments
 - **Reviewer** — pedagogical quality, balance, difficulty calibration`,
+    tagline: 'Design a course, training program, or curriculum — from outcomes to assessments.',
+    bestFor: "you're teaching something and need to structure modules + lessons.",
+    produces: [
+        'Curriculum outline',
+        'Module + lesson plans',
+        'Exercises & worked examples',
+        'Assessments / quizzes',
+        'Instructor notes',
+    ],
 };
 // =============================================================================
 // Book
@@ -838,4 +895,13 @@ This project uses a Book Model that tracks: chapters (with scenes), characters (
 - **Plotter** — story architecture, beats, pacing, plot threads
 - **Character Dev** — characters, arcs, relationships, dialogue voice
 - **Scene Writer** — scene construction, setting, POV, transitions`,
+    tagline: 'Plan and write a book — fiction or non-fiction, outline to manuscript.',
+    bestFor: "you're writing a book and want help with structure, characters, or chapters.",
+    produces: [
+        'Outline + chapter map',
+        'Character profiles (fiction)',
+        'Drafted chapters',
+        'Beat-by-beat structure',
+        'Revision notes',
+    ],
 };

package/dist/project-types/types.d.ts

@@ -100,4 +100,15 @@ export interface ProjectTypeConfig {
     systemPromptContext: string;
     /** Rich multi-line system prompt section for the default agent. Takes precedence over systemPromptContext. */
     systemPromptSection?: string;
+    /** One-sentence value prop for the project-type picker. Punchier than
+     *  `description`, written for someone who doesn't know the term yet.
+     *  Used in the New Project / Import Project wizards. */
+    tagline?: string;
+    /** "Best when…" trigger phrase a user can self-recognize.
+     *  Example: "you're starting from a literature review and need a paper". */
+    bestFor?: string;
+    /** Concrete outputs the user will produce in this project type. 3-5 short
+     *  items shown as bullets in the picker's detail panel. Mined from
+     *  documentTemplates / projectActions / domain models. */
+    produces?: string[];
 }

package/dist/system-prompt/modules.js

@@ -168,10 +168,11 @@ export const TOOL_USAGE_HINTS_MODULE = {
 export const PLATFORM_TOOL_HINTS_MODULE = {
     id: 'platform-tool-hints',
     name: 'Platform Tool Hints',
-    estimatedTokens: 120,
+    estimatedTokens: 200,
     conditions: { enableMetaTools: true },
     content: `## Platform Tool Hints
 
+- **CRITICAL — Filesystem vs Database**: Project documents (PRD, design, outline, analysis, plan, session-notes) and backlog items live in the **database**, not the filesystem. Use \`project_document_*\` and \`workitem_*\` tools — NEVER \`write_file\` / \`bash mkdir\` / \`edit\` for project artifacts. Source code uses filesystem tools as normal. See the "Filesystem vs Database (Hard Rule)" section below for the wrong-vs-right table.
 - **workitem_* vs todo_***: workitem_* tools manage PERSISTENT backlog items (database). todo_* tools manage ephemeral session tasks (footer display). Use workitem_claim/workitem_handoff for persistent ownership, todo_claim/todo_handoff for session tasks.
 - **project_id**: All project/workitem/document/plan tools default to the active project. Only pass project_id to target a different project.
 - **Plan status flow**: draft → approved → in_progress → completed. Any → abandoned. abandoned → draft.
@@ -206,7 +207,7 @@ Common operations:
 export const TOOL_USAGE_META_MODULE = {
     id: 'tool-usage-meta',
     name: 'Tool Usage (Meta)',
-    estimatedTokens: 250,
+    estimatedTokens: 450,
     conditions: { enableMetaTools: true },
     content: `### Specialized Tools
 
@@ -221,20 +222,44 @@ Key categories:
 - **Runners**: run_tests, run_lint
 - **Anchors**: anchor_add, anchor_list, anchor_remove
 
-### Document Storage (CRITICAL)
-
-Project documents (drafts, outlines, analyses, plans) are stored in the **database**, not the filesystem.
-- **Read**: \`project_document_get({ doc_type: "outline" })\` or \`project_document_list()\`
-- **Write (new)**: \`project_document_add({ doc_type: "outline", title: "...", content: "..." })\`
-- **Patch (update without reading)**: \`project_document_patch({ doc_type: "draft", operation: "append", content: "## New Section\\n..." })\`
-  - Operations: \`append\`, \`prepend\`, \`replace_section\` (with \`section_heading\`)
-  - Prefer patch over add when updating large documents — avoids reading the full content into context
-- Do NOT use write_file or edit for project documents — always use these database tools
-- **Software doc_types**: prd, architecture, design, notes, plan
-- **Research doc_types**: outline, literature-review, abstract, methodology, bibliography
-- **Business doc_types**: executive-summary, market-analysis, financial-model, pitch
-- **Content doc_types**: editorial-calendar, article
-- **General doc_types**: draft, review, session-notes, chapter, notes`,
+### CRITICAL: Filesystem vs Database (Hard Rule)
+
+**Project documents and project data live in the DATABASE. Source code lives in the FILESYSTEM. Never mix these.**
+
+This is a non-negotiable project standard. Using filesystem tools (\`write_file\`, \`edit\`, \`bash mkdir\`) for project artifacts is a violation that breaks the integration with the rest of the workspace (no Documents panel visibility, no agent shared context, no exports, no version tracking).
+
+**Decision heuristic — ask before writing:**
+
+1. *"Is this source code or a config file (e.g., \`src/main.ts\`, \`package.json\`, \`.env\`)?"*
+   → If YES, use filesystem tools (\`write_file\`, \`edit\`, \`bash\`).
+2. *"Is this a project artifact (PRD, design doc, draft, outline, analysis, plan, backlog item, session notes)?"*
+   → If YES, you **MUST** use the corresponding database tool (\`project_document_*\`, \`workitem_*\`). Filesystem ops for these are forbidden.
+
+**Wrong vs Right:**
+
+| Task | ❌ WRONG | ✅ RIGHT |
+|------|----------|---------|
+| Create PRD | \`bash mkdir -p .compilr/requirements\` + \`write_file ".compilr/PRD.md"\` | \`project_document_add({ doc_type: "prd", title: "...", content: "..." })\` |
+| Read design doc | \`read_file "docs/design.md"\` | \`project_document_get({ doc_type: "design" })\` |
+| Update outline | \`edit "outline.md" ...\` | \`project_document_patch({ doc_type: "outline", operation: "append", content: "..." })\` |
+| Save session notes | \`write_file "notes.md" ...\` | \`project_document_add({ doc_type: "session-notes", ... })\` |
+| List backlog | \`read_file "backlog.csv"\` | \`workitem_query()\` |
+| Add backlog item | \`edit "backlog.md" ...\` | \`workitem_add({ ... })\` |
+
+**Operations:**
+- **Read**: \`project_document_get({ doc_type: "..." })\` or \`project_document_list()\`
+- **Write (new)**: \`project_document_add({ doc_type: "...", title: "...", content: "..." })\`
+- **Patch (update without reading)**: \`project_document_patch({ doc_type: "...", operation: "append" | "prepend" | "replace_section", content: "...", section_heading?: "..." })\`
+  - Prefer patch over add when updating large documents — avoids loading full content into context
+
+**Always query before writing.** Before adding a document or work item, run \`project_document_list()\` or \`workitem_query()\` first to check for existing entries — avoids duplicates.
+
+**doc_types by project type:**
+- **Software**: prd, architecture, design, notes, plan
+- **Research**: outline, literature-review, abstract, methodology, bibliography
+- **Business**: executive-summary, market-analysis, financial-model, pitch
+- **Content**: editorial-calendar, article
+- **General**: draft, review, session-notes, chapter, notes`,
 };
 /**
  * Token delegation module - always included

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@compilr-dev/sdk",
-  "version": "0.9.24",
+  "version": "0.9.26",
   "description": "Universal agent runtime for building AI-powered applications",
   "type": "module",
   "main": "dist/index.js",