@compilr-dev/sdk 0.6.1 → 0.7.0

package/dist/agent.js

@@ -96,8 +96,11 @@ class CompilrAgentImpl {
             model: config?.model,
             apiKey: config?.apiKey,
         });
-        // Resolve preset
-        const preset = resolvePreset(config?.preset ?? 'coding');
+        // Resolve preset — non-software projects get 'general' by default
+        const defaultPreset = config?.projectCategory && config.projectCategory !== 'software'
+            ? 'general'
+            : 'coding';
+        const preset = resolvePreset(config?.preset ?? defaultPreset);
         // Build system prompt
         let systemPrompt;
         if (config?.systemPrompt === false) {

package/dist/config.d.ts

@@ -157,8 +157,10 @@ export interface CompilrAgentConfig {
     model?: string;
     /** API key (uses env var if omitted) */
     apiKey?: string;
-    /** Preset to use. Default: 'coding' */
-    preset?: 'coding' | 'read-only' | 'none' | Preset;
+    /** Preset to use. Default: 'coding' (or 'general' for non-software projectCategory) */
+    preset?: 'coding' | 'general' | 'read-only' | 'none' | Preset;
+    /** Project type category — determines default preset when preset is omitted */
+    projectCategory?: 'software' | 'research' | 'writing' | 'business' | 'education' | 'general';
     /** Working directory. Default: process.cwd() */
     cwd?: string;
     /** Maximum iterations for tool use loops. Default: 50 */

package/dist/presets/general.d.ts

@@ -0,0 +1,9 @@
+/**
+ * General preset — project-type-neutral, no software assumptions
+ *
+ * Used for non-software project types (research, business, content, etc.).
+ * The project-type-specific identity comes from the systemPromptSection
+ * in the ProjectTypeConfig, not from the preset.
+ */
+import type { Preset } from './types.js';
+export declare const generalPreset: Preset;

package/dist/presets/general.js

@@ -0,0 +1,37 @@
+/**
+ * General preset — project-type-neutral, no software assumptions
+ *
+ * Used for non-software project types (research, business, content, etc.).
+ * The project-type-specific identity comes from the systemPromptSection
+ * in the ProjectTypeConfig, not from the preset.
+ */
+import { readFileTool, writeFileTool, editTool, bashTool, bashOutputTool, killShellTool, grepTool, globTool, todoWriteTool, todoReadTool, webFetchTool, suggestTool, } from '@compilr-dev/agents';
+const GENERAL_SYSTEM_PROMPT = `You are a versatile AI assistant. You adapt your approach to the user's needs and project context.
+
+You help users with a wide range of tasks including research, writing, analysis, planning, and problem solving.
+
+Guidelines:
+- Read files before modifying them to understand existing content
+- Make focused, minimal changes unless asked for larger rewrites
+- Follow the project's conventions and style
+- Follow any project-specific guidance provided in the system prompt
+- When uncertain, ask the user for clarification`;
+export const generalPreset = {
+    name: 'general',
+    systemPrompt: GENERAL_SYSTEM_PROMPT,
+    tools: [
+        readFileTool,
+        writeFileTool,
+        editTool,
+        bashTool,
+        bashOutputTool,
+        killShellTool,
+        grepTool,
+        globTool,
+        todoWriteTool,
+        todoReadTool,
+        webFetchTool,
+        suggestTool,
+    ],
+    defaultPermissions: 'auto',
+};

package/dist/presets/index.d.ts

@@ -4,8 +4,9 @@
 export type { Preset } from './types.js';
 export { codingPreset } from './coding.js';
 export { readOnlyPreset } from './read-only.js';
+export { generalPreset } from './general.js';
 import type { Preset } from './types.js';
 /**
  * Resolve a preset by name or return a custom preset object
  */
-export declare function resolvePreset(preset: 'coding' | 'read-only' | 'none' | Preset): Preset;
+export declare function resolvePreset(preset: 'coding' | 'general' | 'read-only' | 'none' | Preset): Preset;

package/dist/presets/index.js

@@ -3,8 +3,10 @@
  */
 export { codingPreset } from './coding.js';
 export { readOnlyPreset } from './read-only.js';
+export { generalPreset } from './general.js';
 import { codingPreset } from './coding.js';
 import { readOnlyPreset } from './read-only.js';
+import { generalPreset } from './general.js';
 /**
  * Empty preset — no tools, minimal prompt
  */
@@ -24,6 +26,8 @@ export function resolvePreset(preset) {
     switch (preset) {
         case 'coding':
             return codingPreset;
+        case 'general':
+            return generalPreset;
         case 'read-only':
             return readOnlyPreset;
         case 'none':

package/dist/project-types/configs.js

@@ -65,6 +65,47 @@ export const softwareConfig = {
     projectActions: ['design', 'prd', 'architecture', 'refine', 'scaffold', 'session-notes'],
     workItemActions: ['build', 'refine-item', 'code-review', 'explain'],
     systemPromptContext: 'This is a software development project. The user is building an application.',
+    systemPromptSection: `## Project Context: Software Development
+
+You are assisting with a software development project. Your role is to help the user design, build, test, and maintain an application.
+
+### Development Workflow
+The typical workflow progresses through these phases:
+1. **Design** — Define the application model, entities, and relationships
+2. **Requirements** — Write PRD, define features, acceptance criteria
+3. **Architecture** — System architecture, tech stack decisions
+4. **Implementation** — Build features, write code, run tests
+5. **Review** — Code review, quality checks, refactoring
+6. **Deployment** — Build, deploy, monitor
+
+### Available Tools & Skills
+- \`/design\` — Guide through application design (entities, relationships)
+- \`/prd\` — Write a Product Requirements Document
+- \`/architecture\` — Design system architecture
+- \`/scaffold\` — Generate project code from the Application Model
+- \`/build\` — Implement a specific feature or work item
+- \`/refine\` — Expand and refine backlog items
+
+### Work Items
+Work items in this project represent:
+- **Feature** — a feature or user story to implement
+- **Bug** — a defect to fix
+- **Tech Debt** — code quality improvement
+- **Chore** — maintenance or administrative task
+
+### Writing Conventions
+- Follow the project's existing code style and conventions
+- Read files before modifying to understand context
+- Make focused, minimal changes unless asked otherwise
+- Run tests and lint before considering work complete
+
+### Team Agents
+Specialized agents may be available:
+- **Dev** — implementation, debugging, refactoring
+- **QA** — testing, code review, quality assurance
+- **Architect** — system design, technical decisions
+- **PM** — requirements, backlog management, priorities
+Suggest delegation when a task would benefit from focused expertise.`,
 };
 // =============================================================================
 // General (blank slate)
@@ -84,6 +125,15 @@ export const generalConfig = {
     projectActions: ['session-notes'],
     workItemActions: ['explain'],
     systemPromptContext: 'This is a general-purpose project.',
+    systemPromptSection: `## Project Context: General
+
+You are assisting with a general-purpose project. Adapt your approach to whatever the user needs — writing, research, analysis, planning, or any other task.
+
+### Approach
+- Ask about the project's goals and context if not clear
+- Use work items to track tasks and progress
+- Use documents to store important artifacts
+- Suggest team agents if the project would benefit from specialization`,
 };
 // =============================================================================
 // Research Paper / Academic
@@ -166,7 +216,7 @@ export const researchConfig = {
         'peer-review',
         'session-notes',
     ],
-    workItemActions: ['draft-section', 'explain'],
+    workItemActions: ['draft-section', 'refine-item', 'explain'],
     workItemLabels: {
         feature: { short: 'SC', full: 'Section' },
         bug: { short: 'RV', full: 'Revision' },
@@ -310,6 +360,35 @@ export const businessPlanConfig = {
         chore: { short: 'TK', full: 'Task' },
     },
     systemPromptContext: 'This is a business plan project. The user is developing a business plan or startup pitch. Focus on market analysis, financial viability, and clear communication.',
+    systemPromptSection: `## Project Context: Business Plan
+
+You are assisting with a business plan or startup project. Your role is to help the user develop a compelling, well-researched business plan.
+
+### Workflow
+1. **Vision & Problem** — Define the problem being solved and the value proposition
+2. **Market Research** — Analyze target market, customer segments, market size
+3. **Competitive Analysis** — Identify competitors, positioning, differentiation
+4. **Business Model** — Revenue streams, pricing, cost structure
+5. **Go-to-Market** — Marketing strategy, channels, launch plan
+6. **Financial Projections** — Revenue forecasts, expense modeling, break-even
+7. **Pitch Narrative** — Executive summary, investor pitch
+
+### Work Items
+- **Milestone** (type: feature) — a major deliverable or section to complete
+- **Issue** (type: bug) — a problem or gap to address
+- **Research** (type: tech-debt) — market data or analysis needed
+- **Task** (type: chore) — administrative or formatting work
+
+### Writing Conventions
+- Use clear, professional business language
+- Support claims with data and market research
+- Be realistic about projections — investors spot inflated numbers
+- Structure arguments: problem → solution → evidence → opportunity
+
+### Team Agents
+- **Analyst** — market research, competitive intelligence, data analysis
+- **Strategist** — business model, go-to-market, positioning
+- **Writer** — pitch narrative, executive summary, investor communication`,
 };
 // =============================================================================
 // Content / Blog / Marketing
@@ -366,6 +445,36 @@ export const contentConfig = {
         chore: { short: 'TK', full: 'Task' },
     },
     systemPromptContext: 'This is a content/marketing project. The user is creating articles, blog posts, or marketing content. Focus on engaging writing, SEO awareness, and brand consistency.',
+    systemPromptSection: `## Project Context: Content & Marketing
+
+You are assisting with a content creation project. Your role is to help the user produce engaging, well-structured content.
+
+### Workflow
+1. **Strategy** — Define content goals, audience, brand voice
+2. **Ideation** — Generate topic ideas, angles, headlines
+3. **Research** — Gather supporting information, statistics, quotes
+4. **Drafting** — Write first drafts following the brand guide
+5. **Editing** — Revise for clarity, engagement, consistency
+6. **Optimization** — SEO, readability, formatting for platform
+7. **Publishing** — Final review and publication
+
+### Work Items
+- **Content Piece** (type: feature) — an article, post, or page to create
+- **Fix** (type: bug) — content corrections or updates needed
+- **Research** (type: tech-debt) — background research or data to gather
+- **Task** (type: chore) — formatting, scheduling, or administrative work
+
+### Writing Conventions
+- Match the project's established brand voice and tone
+- Lead with value — don't bury the point
+- Use short paragraphs and clear headings for scannability
+- Include a clear call-to-action where appropriate
+- Consider SEO: keywords, meta descriptions, internal linking
+
+### Team Agents
+- **Writer** — drafting, creative writing, storytelling
+- **Editor** — style consistency, grammar, clarity, tone
+- **Analyst** — audience research, content performance, SEO data`,
 };
 // =============================================================================
 // Technical Documentation
@@ -422,6 +531,35 @@ export const techDocsConfig = {
         chore: { short: 'TK', full: 'Task' },
     },
     systemPromptContext: 'This is a technical documentation project. The user is writing documentation such as API references, user guides, or tutorials. Focus on clarity, accuracy, and developer experience.',
+    systemPromptSection: `## Project Context: Technical Documentation
+
+You are assisting with a technical documentation project. Your role is to help the user produce clear, accurate, and developer-friendly documentation.
+
+### Workflow
+1. **Planning** — Define documentation scope, audience, information architecture
+2. **Outline** — Structure the documentation hierarchy (guides, references, tutorials)
+3. **Drafting** — Write content with code examples and clear explanations
+4. **Review** — Technical accuracy review, consistency check
+5. **Polish** — Copy editing, formatting, cross-referencing
+
+### Work Items
+- **Page** (type: feature) — a documentation page or guide to write
+- **Fix** (type: bug) — corrections, outdated information, broken links
+- **Refactor** (type: tech-debt) — restructuring or consolidation of docs
+- **Task** (type: chore) — formatting, navigation, publishing
+
+### Writing Conventions
+- Write for the reader's skill level — don't assume knowledge unless stated
+- Lead with "what" and "why" before "how"
+- Include working code examples for every concept
+- Use consistent terminology — define terms on first use
+- Cross-reference related pages and concepts
+- Keep code examples minimal and focused — don't include unnecessary complexity
+
+### Team Agents
+- **Writer** — drafting documentation, tutorials, guides
+- **Editor** — clarity, consistency, grammar, readability
+- **Reviewer** — technical accuracy, completeness, correctness`,
 };
 // =============================================================================
 // Course / Training Material
@@ -484,4 +622,34 @@ export const courseConfig = {
         chore: { short: 'TK', full: 'Task' },
     },
     systemPromptContext: 'This is an educational project. The user is creating a course or training material. Focus on clear explanations, progressive complexity, and effective learning design.',
+    systemPromptSection: `## Project Context: Course / Training Material
+
+You are assisting with an educational project. Your role is to help the user create an effective, well-structured learning experience.
+
+### Workflow
+1. **Curriculum Design** — Define learning objectives, prerequisites, progression
+2. **Module Structure** — Organize into modules/lessons with clear scope
+3. **Content Creation** — Write lessons with explanations, examples, visuals
+4. **Exercises** — Create practice activities, coding challenges, projects
+5. **Assessment** — Design quizzes, tests, rubrics
+6. **Review** — Pedagogical review, difficulty calibration, accessibility
+
+### Work Items
+- **Lesson** (type: feature) — a lesson or module to create
+- **Fix** (type: bug) — corrections, confusing explanations to clarify
+- **Refactor** (type: tech-debt) — restructuring content flow or difficulty curve
+- **Task** (type: chore) — formatting, media assets, publishing
+
+### Writing Conventions
+- Start every lesson with clear learning objectives (use Bloom's taxonomy)
+- Build knowledge progressively — prerequisites before advanced concepts
+- Include hands-on exercises for every concept taught
+- Use varied examples — abstract + concrete, simple + complex
+- Provide "check your understanding" moments before moving forward
+- Consider different learning styles (reading, doing, watching)
+
+### Team Agents
+- **Instructor** — curriculum design, lesson planning, pedagogy
+- **Writer** — content creation, explanations, narratives
+- **Reviewer** — accuracy, difficulty assessment, completeness`,
 };

package/dist/system-prompt/modules.d.ts

@@ -147,4 +147,5 @@ export declare function shouldIncludeModule(module: SystemPromptModule, context:
     hasProject?: boolean;
     hasRoleIdentity?: boolean;
     hasVisualOutput?: boolean;
+    hasSystemPromptSection?: boolean;
 }): boolean;

package/dist/system-prompt/modules.js

@@ -441,8 +441,8 @@ export function shouldIncludeModule(module, context) {
     }
     const { conditions } = module;
     // Check noRoleIdentity condition - only include if NO role identity is specified
-    // This allows team agents to define their own identity without conflict
-    if (conditions.noRoleIdentity && context.hasRoleIdentity) {
+    // This allows team agents AND type-specific systemPromptSections to define identity
+    if (conditions.noRoleIdentity && (context.hasRoleIdentity || context.hasSystemPromptSection)) {
         return false;
     }
     // Check hasGit condition

package/dist/team/types.js

@@ -28,7 +28,7 @@ export const PREDEFINED_ROLE_IDS = [
  * Used in the team roster to help agents understand each other's strengths
  */
 export const ROLE_EXPERTISE = {
-    default: ['general assistance', 'coding', 'problem solving'],
+    default: ['general assistance', 'problem solving', 'planning'],
     pm: ['planning', 'task tracking', 'coordination', 'timeline estimation', 'status updates'],
     arch: [
         'system design',

package/package.json

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