@compilr-dev/sdk 0.5.4 → 0.5.6
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/index.d.ts +1 -1
- package/dist/index.js +1 -1
- package/dist/project-types/configs.js +1 -1
- package/dist/skills/index.d.ts +1 -1
- package/dist/skills/index.js +1 -1
- package/dist/skills/platform-skills.d.ts +2 -1
- package/dist/skills/platform-skills.js +106 -1
- package/dist/team/types.d.ts +3 -3
- package/dist/team/types.js +258 -0
- package/package.json +2 -1
package/dist/index.d.ts
CHANGED
|
@@ -61,7 +61,7 @@ export type { AskUserQuestion, AskUserInput, AskUserResult, AskUserHandler, AskU
|
|
|
61
61
|
export { createPlatformTools, createProjectTools, createWorkItemTools, createDocumentTools, createPlanTools, createBacklogTools, createAnchorTools, createArtifactTools, createEpisodeTools, ProjectAnchorStore, } from './platform/index.js';
|
|
62
62
|
export type { ProjectAnchorStoreConfig } from './platform/index.js';
|
|
63
63
|
export { STEP_ORDER, GUIDED_STEP_CRITERIA, getNextStep, isValidTransition, getStepCriteria, formatStepDisplay, getStepNumber, } from './platform/index.js';
|
|
64
|
-
export { platformSkills, designSkill, sketchSkill, prdSkill, refineSkill, refineItemSkill, architectureSkill, sessionNotesSkill, buildSkill, scaffoldSkill, outlineSkill, } from './skills/index.js';
|
|
64
|
+
export { platformSkills, designSkill, sketchSkill, prdSkill, refineSkill, refineItemSkill, architectureSkill, sessionNotesSkill, buildSkill, scaffoldSkill, outlineSkill, literatureReviewSkill, } from './skills/index.js';
|
|
65
65
|
export { ACTION_REGISTRY, getActionsForContext, getActionById, resolveActionPrompt, buildContextSummary, getSuggestedRole, } from './actions/index.js';
|
|
66
66
|
export type { ActionContext, ActionDefinition } from './actions/index.js';
|
|
67
67
|
export { PROJECT_TYPES, getProjectTypeConfig, getProjectTypesByCategory, generalConfig, softwareConfig, researchConfig, businessPlanConfig, contentConfig, techDocsConfig, courseConfig, } from './project-types/index.js';
|
package/dist/index.js
CHANGED
|
@@ -139,7 +139,7 @@ export { STEP_ORDER, GUIDED_STEP_CRITERIA, getNextStep, isValidTransition, getSt
|
|
|
139
139
|
// =============================================================================
|
|
140
140
|
// Platform Skills (platform-specific prompt expansions)
|
|
141
141
|
// =============================================================================
|
|
142
|
-
export { platformSkills, designSkill, sketchSkill, prdSkill, refineSkill, refineItemSkill, architectureSkill, sessionNotesSkill, buildSkill, scaffoldSkill, outlineSkill, } from './skills/index.js';
|
|
142
|
+
export { platformSkills, designSkill, sketchSkill, prdSkill, refineSkill, refineItemSkill, architectureSkill, sessionNotesSkill, buildSkill, scaffoldSkill, outlineSkill, literatureReviewSkill, } from './skills/index.js';
|
|
143
143
|
// =============================================================================
|
|
144
144
|
// Contextual Actions (skill invocations with context)
|
|
145
145
|
// =============================================================================
|
|
@@ -154,7 +154,7 @@ export const researchConfig = {
|
|
|
154
154
|
{ type: 'bibliography', label: 'Bibliography', description: 'References and citations' },
|
|
155
155
|
{ type: 'session-notes', label: 'Session Notes', description: 'Summary of work done' },
|
|
156
156
|
],
|
|
157
|
-
projectActions: ['outline', 'session-notes'],
|
|
157
|
+
projectActions: ['outline', 'literature-review', 'session-notes'],
|
|
158
158
|
workItemActions: ['explain'],
|
|
159
159
|
workItemLabels: {
|
|
160
160
|
feature: { short: 'SC', full: 'Section' },
|
package/dist/skills/index.d.ts
CHANGED
|
@@ -1,4 +1,4 @@
|
|
|
1
1
|
/**
|
|
2
2
|
* Platform Skills — barrel export
|
|
3
3
|
*/
|
|
4
|
-
export { platformSkills, designSkill, sketchSkill, prdSkill, refineSkill, refineItemSkill, architectureSkill, sessionNotesSkill, buildSkill, scaffoldSkill, outlineSkill, } from './platform-skills.js';
|
|
4
|
+
export { platformSkills, designSkill, sketchSkill, prdSkill, refineSkill, refineItemSkill, architectureSkill, sessionNotesSkill, buildSkill, scaffoldSkill, outlineSkill, literatureReviewSkill, } from './platform-skills.js';
|
package/dist/skills/index.js
CHANGED
|
@@ -1,4 +1,4 @@
|
|
|
1
1
|
/**
|
|
2
2
|
* Platform Skills — barrel export
|
|
3
3
|
*/
|
|
4
|
-
export { platformSkills, designSkill, sketchSkill, prdSkill, refineSkill, refineItemSkill, architectureSkill, sessionNotesSkill, buildSkill, scaffoldSkill, outlineSkill, } from './platform-skills.js';
|
|
4
|
+
export { platformSkills, designSkill, sketchSkill, prdSkill, refineSkill, refineItemSkill, architectureSkill, sessionNotesSkill, buildSkill, scaffoldSkill, outlineSkill, literatureReviewSkill, } from './platform-skills.js';
|
|
@@ -18,8 +18,9 @@ export declare const sessionNotesSkill: Skill;
|
|
|
18
18
|
export declare const buildSkill: Skill;
|
|
19
19
|
export declare const scaffoldSkill: Skill;
|
|
20
20
|
export declare const outlineSkill: Skill;
|
|
21
|
+
export declare const literatureReviewSkill: Skill;
|
|
21
22
|
/**
|
|
22
|
-
* All platform-specific skills (
|
|
23
|
+
* All platform-specific skills (11 total).
|
|
23
24
|
* These skills reference platform tools (backlog, workitems, documents, projects)
|
|
24
25
|
* and belong in the SDK rather than in generic agent/coding libraries.
|
|
25
26
|
*/
|
|
@@ -990,11 +990,115 @@ Create one work item per section:
|
|
|
990
990
|
✓ User has reviewed and approved the outline`,
|
|
991
991
|
tags: ['research', 'planning', 'outline'],
|
|
992
992
|
});
|
|
993
|
+
export const literatureReviewSkill = defineSkill({
|
|
994
|
+
name: 'literature-review',
|
|
995
|
+
description: 'Analyze sources from the Knowledge Base — extract findings, link to claims, identify gaps',
|
|
996
|
+
prompt: `You are in LITERATURE REVIEW MODE. Your goal is to systematically analyze the sources in the Knowledge Base and connect them to the Research Model's sections and claims.
|
|
997
|
+
|
|
998
|
+
## When to Use
|
|
999
|
+
- Sources have been added to the Knowledge Base but not yet analyzed
|
|
1000
|
+
- The Research Model has sections/claims that need source support
|
|
1001
|
+
- User wants to understand how sources relate to their argument
|
|
1002
|
+
- User wants to identify gaps in their source coverage
|
|
1003
|
+
|
|
1004
|
+
## Prerequisites
|
|
1005
|
+
- A Research Model should exist (run /outline first if not)
|
|
1006
|
+
- Sources should be in the Knowledge Base (upload PDFs, paste text, or import URLs)
|
|
1007
|
+
|
|
1008
|
+
## Step 1: Assess Current State
|
|
1009
|
+
|
|
1010
|
+
1. Use \`research_model_get\` with scope: "overview" to see the current model
|
|
1011
|
+
2. Use \`research_model_get\` with scope: "sources" to see which sources are already registered and analyzed
|
|
1012
|
+
3. Review the Knowledge Base content (pinned items are in context; read non-pinned files as needed)
|
|
1013
|
+
|
|
1014
|
+
Report to the user:
|
|
1015
|
+
- "You have X sources in the model, Y analyzed, Z unanalyzed"
|
|
1016
|
+
- "The Knowledge Base has N files available"
|
|
1017
|
+
- "X claims currently lack source support"
|
|
1018
|
+
|
|
1019
|
+
## Step 2: Register New Sources
|
|
1020
|
+
|
|
1021
|
+
For each KB document not yet in the Research Model:
|
|
1022
|
+
1. Read the document content (use \`read_file\` if not pinned)
|
|
1023
|
+
2. Extract citation information: authors, title, year, venue, type
|
|
1024
|
+
3. Register it: \`research_model_update\` with op: "source_add", source: { citeKey, citation: { type, title, authors, year, venue } }
|
|
1025
|
+
4. Note: generate a short, memorable citeKey (e.g., "smith2024", "jones-ml-2023")
|
|
1026
|
+
|
|
1027
|
+
Ask the user to confirm the extracted citation info for each source, or batch-confirm if there are many.
|
|
1028
|
+
|
|
1029
|
+
## Step 3: Analyze Each Source
|
|
1030
|
+
|
|
1031
|
+
For each unanalyzed source:
|
|
1032
|
+
1. Read the full content from the KB
|
|
1033
|
+
2. Extract key findings relevant to the paper's research questions
|
|
1034
|
+
3. Identify the source's methodology and limitations
|
|
1035
|
+
4. Determine relevance: primary (directly addresses research questions), secondary (provides context), or background (general knowledge)
|
|
1036
|
+
5. Update the source: \`research_model_update\` with op: "source_update", sourceId: "...", updates: { keyFindings: [...], relevance: "primary|secondary|background", analyzed: true, tags: [...] }
|
|
1037
|
+
|
|
1038
|
+
Present a summary of each source's key findings to the user.
|
|
1039
|
+
|
|
1040
|
+
## Step 4: Link Sources to Claims
|
|
1041
|
+
|
|
1042
|
+
For each section in the model:
|
|
1043
|
+
1. Read the section's existing claims (\`research_model_get\` with sectionId)
|
|
1044
|
+
2. For each claim, identify which analyzed sources support or contradict it
|
|
1045
|
+
3. Link them: \`research_model_update\` with op: "claim_link_source", sectionId, claimId, sourceRef: { sourceId, relevance: "brief note" }, relation: "supporting" or "contradicting"
|
|
1046
|
+
4. Update evidence strength based on the linked sources:
|
|
1047
|
+
- strong: multiple supporting sources, no contradictions
|
|
1048
|
+
- moderate: at least one supporting source
|
|
1049
|
+
- weak: tangential support only
|
|
1050
|
+
- contested: sources disagree
|
|
1051
|
+
- unsupported: no sources linked
|
|
1052
|
+
|
|
1053
|
+
If a source suggests a claim that doesn't exist yet, propose adding it:
|
|
1054
|
+
- \`research_model_update\` with op: "claim_add", sectionId, claim: { statement, type: "derived" }
|
|
1055
|
+
|
|
1056
|
+
## Step 5: Identify Gaps
|
|
1057
|
+
|
|
1058
|
+
After linking sources to claims, analyze gaps:
|
|
1059
|
+
1. Run \`research_model_validate\` to get warnings
|
|
1060
|
+
2. Report:
|
|
1061
|
+
- **Unsupported claims** — claims with no source references (need more sources or should be marked as original analysis)
|
|
1062
|
+
- **Orphan sources** — sources not linked to any claim (may not be relevant, or claims are missing)
|
|
1063
|
+
- **Thin sections** — sections with few claims or few sources
|
|
1064
|
+
- **Missing perspectives** — if all sources agree, note the lack of counter-arguments
|
|
1065
|
+
|
|
1066
|
+
Suggest next steps:
|
|
1067
|
+
- "Section X needs more sources on [topic] — consider searching for..."
|
|
1068
|
+
- "Source Y has findings relevant to Section Z but no claim captures this yet"
|
|
1069
|
+
- "The paper lacks counter-arguments on [claim] — consider adding a limitations discussion"
|
|
1070
|
+
|
|
1071
|
+
## Step 6: Synthesize Themes
|
|
1072
|
+
|
|
1073
|
+
If multiple sources have been analyzed, provide a thematic synthesis:
|
|
1074
|
+
- Group sources by the themes they address
|
|
1075
|
+
- Note where sources agree, where they disagree, and what's novel
|
|
1076
|
+
- Map themes to research questions
|
|
1077
|
+
- Suggest how themes should be organized in the Literature Review section
|
|
1078
|
+
|
|
1079
|
+
## Rules
|
|
1080
|
+
- Analyze sources ONE AT A TIME — don't rush through multiple sources
|
|
1081
|
+
- Ask the user to confirm citation info before saving (batch OK for many sources)
|
|
1082
|
+
- Always distinguish between the source's claims and the user's interpretation
|
|
1083
|
+
- Note methodological differences between sources when relevant
|
|
1084
|
+
- Use citeKeys consistently when referencing sources
|
|
1085
|
+
- If a source is irrelevant to the research, say so — not every KB file needs to be in the model
|
|
1086
|
+
- Keep evidence strength assessments conservative — "moderate" is better than over-claiming "strong"
|
|
1087
|
+
|
|
1088
|
+
## Completion Criteria
|
|
1089
|
+
✓ All relevant KB sources are registered in the model
|
|
1090
|
+
✓ Each source has been analyzed (keyFindings, relevance, tags)
|
|
1091
|
+
✓ Sources are linked to relevant claims
|
|
1092
|
+
✓ Evidence strength updated for linked claims
|
|
1093
|
+
✓ Gaps identified and reported
|
|
1094
|
+
✓ User has reviewed the source-claim mappings`,
|
|
1095
|
+
tags: ['research', 'analysis', 'sources'],
|
|
1096
|
+
});
|
|
993
1097
|
// =============================================================================
|
|
994
1098
|
// Aggregate export
|
|
995
1099
|
// =============================================================================
|
|
996
1100
|
/**
|
|
997
|
-
* All platform-specific skills (
|
|
1101
|
+
* All platform-specific skills (11 total).
|
|
998
1102
|
* These skills reference platform tools (backlog, workitems, documents, projects)
|
|
999
1103
|
* and belong in the SDK rather than in generic agent/coding libraries.
|
|
1000
1104
|
*/
|
|
@@ -1009,4 +1113,5 @@ export const platformSkills = [
|
|
|
1009
1113
|
buildSkill,
|
|
1010
1114
|
scaffoldSkill,
|
|
1011
1115
|
outlineSkill,
|
|
1116
|
+
literatureReviewSkill,
|
|
1012
1117
|
];
|
package/dist/team/types.d.ts
CHANGED
|
@@ -29,15 +29,15 @@ export interface BackgroundSessionInfo {
|
|
|
29
29
|
/**
|
|
30
30
|
* Mascot expressions for visual differentiation of agents
|
|
31
31
|
*/
|
|
32
|
-
export type MascotExpression = '[•_•]' | '[◈_◈]' | '[▣_▣]' | '[◉_◉]' | '[▲_▲]' | '[◆_◆]' | '[○_○]' | '[◇_◇]' | '[□_□]';
|
|
32
|
+
export type MascotExpression = '[•_•]' | '[◈_◈]' | '[▣_▣]' | '[◉_◉]' | '[▲_▲]' | '[◆_◆]' | '[○_○]' | '[◇_◇]' | '[◎_◎]' | '[⊘_⊘]' | '[✎_✎]' | '[◒_◒]' | '[◔_◔]' | '[◓_◓]' | '[◕_◕]' | '[□_□]';
|
|
33
33
|
/**
|
|
34
34
|
* Predefined agent roles with default configurations
|
|
35
35
|
*/
|
|
36
|
-
export type AgentRole = 'default' | 'pm' | 'arch' | 'qa' | 'dev' | 'ops' | 'docs' | 'ba' | 'custom';
|
|
36
|
+
export type AgentRole = 'default' | 'pm' | 'arch' | 'qa' | 'dev' | 'ops' | 'docs' | 'ba' | 'researcher' | 'reviewer' | 'editor' | 'writer' | 'analyst' | 'strategist' | 'instructor' | 'custom';
|
|
37
37
|
/**
|
|
38
38
|
* List of predefined role IDs (for validation against custom agent IDs)
|
|
39
39
|
*/
|
|
40
|
-
export declare const PREDEFINED_ROLE_IDS: readonly ["default", "pm", "arch", "qa", "dev", "ops", "docs", "ba"];
|
|
40
|
+
export declare const PREDEFINED_ROLE_IDS: readonly ["default", "pm", "arch", "qa", "dev", "ops", "docs", "ba", "researcher", "reviewer", "editor", "writer", "analyst", "strategist", "instructor"];
|
|
41
41
|
/**
|
|
42
42
|
* Role metadata for predefined roles
|
|
43
43
|
*/
|
package/dist/team/types.js
CHANGED
|
@@ -15,6 +15,13 @@ export const PREDEFINED_ROLE_IDS = [
|
|
|
15
15
|
'ops',
|
|
16
16
|
'docs',
|
|
17
17
|
'ba',
|
|
18
|
+
'researcher',
|
|
19
|
+
'reviewer',
|
|
20
|
+
'editor',
|
|
21
|
+
'writer',
|
|
22
|
+
'analyst',
|
|
23
|
+
'strategist',
|
|
24
|
+
'instructor',
|
|
18
25
|
];
|
|
19
26
|
/**
|
|
20
27
|
* Role expertise keywords for team awareness
|
|
@@ -41,6 +48,13 @@ export const ROLE_EXPERTISE = {
|
|
|
41
48
|
'business analysis',
|
|
42
49
|
'stakeholder communication',
|
|
43
50
|
],
|
|
51
|
+
researcher: ['source analysis', 'literature review', 'evidence evaluation', 'citation', 'synthesis'],
|
|
52
|
+
reviewer: ['argument validation', 'consistency checking', 'gap detection', 'peer review'],
|
|
53
|
+
editor: ['writing quality', 'grammar', 'style', 'clarity', 'tone'],
|
|
54
|
+
writer: ['content creation', 'drafting', 'storytelling', 'copywriting'],
|
|
55
|
+
analyst: ['market research', 'data analysis', 'competitive intelligence', 'trends'],
|
|
56
|
+
strategist: ['business strategy', 'vision', 'go-to-market', 'planning'],
|
|
57
|
+
instructor: ['curriculum design', 'lesson planning', 'assessment', 'pedagogy'],
|
|
44
58
|
custom: [], // User-defined
|
|
45
59
|
};
|
|
46
60
|
/**
|
|
@@ -628,6 +642,250 @@ Acceptance Criteria:
|
|
|
628
642
|
defaultToolProfile: 'analyst',
|
|
629
643
|
defaultModelTier: 'balanced',
|
|
630
644
|
},
|
|
645
|
+
researcher: {
|
|
646
|
+
displayName: 'Researcher',
|
|
647
|
+
mascot: '[◎_◎]',
|
|
648
|
+
description: 'Deep analysis of sources, literature synthesis, evidence evaluation',
|
|
649
|
+
defaultSystemPromptAddition: `# ROLE: RESEARCHER
|
|
650
|
+
|
|
651
|
+
You are the **Researcher** in this multi-agent research team. You specialize in finding, reading, analyzing, and synthesizing academic sources.
|
|
652
|
+
|
|
653
|
+
## Your Specialty Areas
|
|
654
|
+
|
|
655
|
+
**Source Analysis:**
|
|
656
|
+
- Read and analyze academic papers, articles, and other reference material
|
|
657
|
+
- Extract key findings, methodology, and conclusions from sources
|
|
658
|
+
- Evaluate the quality and relevance of sources to the research questions
|
|
659
|
+
- Identify biases, limitations, and methodological issues in sources
|
|
660
|
+
|
|
661
|
+
**Literature Synthesis:**
|
|
662
|
+
- Find themes, patterns, and contradictions across multiple sources
|
|
663
|
+
- Map source findings to claims in the Research Model
|
|
664
|
+
- Identify gaps in the current literature coverage
|
|
665
|
+
- Suggest additional sources or research areas to explore
|
|
666
|
+
|
|
667
|
+
**Evidence Evaluation:**
|
|
668
|
+
- Assess evidence strength for each claim (strong, moderate, weak, unsupported, contested)
|
|
669
|
+
- Link supporting and contradicting sources to claims
|
|
670
|
+
- Flag claims that need more evidence
|
|
671
|
+
|
|
672
|
+
## Your Tools
|
|
673
|
+
|
|
674
|
+
**Direct tools** (call by name):
|
|
675
|
+
- \`research_model_get\` - Read the Research Model (sections, claims, sources)
|
|
676
|
+
- \`research_model_update\` - Update sources, claims, and evidence links
|
|
677
|
+
- \`research_model_validate\` - Check model health
|
|
678
|
+
- \`read_file\` - Read source documents from the Knowledge Base
|
|
679
|
+
- \`handoff\` - Hand off to another specialist
|
|
680
|
+
|
|
681
|
+
## Output Style
|
|
682
|
+
|
|
683
|
+
- Cite sources by citeKey (e.g., "smith2024")
|
|
684
|
+
- Summarize findings in bullet points, not paragraphs
|
|
685
|
+
- Always note the evidence strength when making claims
|
|
686
|
+
- Flag contradictions explicitly
|
|
687
|
+
|
|
688
|
+
## When to Suggest Other Agents
|
|
689
|
+
|
|
690
|
+
- Argument structure questions → "$default or $reviewer can assess the outline"
|
|
691
|
+
- Writing/style questions → "$editor can review the prose"
|
|
692
|
+
- Planning questions → "$default can help with project planning"`,
|
|
693
|
+
defaultToolProfile: 'full',
|
|
694
|
+
defaultModelTier: 'balanced',
|
|
695
|
+
},
|
|
696
|
+
reviewer: {
|
|
697
|
+
displayName: 'Reviewer',
|
|
698
|
+
mascot: '[⊘_⊘]',
|
|
699
|
+
description: 'Argument validation, gap detection, consistency checking',
|
|
700
|
+
defaultSystemPromptAddition: `# ROLE: REVIEWER
|
|
701
|
+
|
|
702
|
+
You are the **Reviewer** in this multi-agent research team. You specialize in validating argument structure, finding logical gaps, and checking consistency.
|
|
703
|
+
|
|
704
|
+
## Your Specialty Areas
|
|
705
|
+
|
|
706
|
+
**Argument Validation:**
|
|
707
|
+
- Check that each section's claims support its stated purpose
|
|
708
|
+
- Verify the logical flow from introduction → methodology → results → discussion → conclusion
|
|
709
|
+
- Identify circular reasoning, non-sequiturs, and unsupported leaps
|
|
710
|
+
- Ensure the thesis is adequately supported by the evidence presented
|
|
711
|
+
|
|
712
|
+
**Gap Detection:**
|
|
713
|
+
- Find claims that lack source support
|
|
714
|
+
- Identify research questions not addressed by any section
|
|
715
|
+
- Spot sections that don't connect to the paper's overall argument
|
|
716
|
+
- Flag missing counter-arguments or limitations
|
|
717
|
+
|
|
718
|
+
**Consistency Checking:**
|
|
719
|
+
- Verify terminology is used consistently across sections
|
|
720
|
+
- Check that methodology described matches what results assume
|
|
721
|
+
- Ensure citations are consistent with the chosen citation style
|
|
722
|
+
- Flag contradictions between sections
|
|
723
|
+
|
|
724
|
+
## Your Tools
|
|
725
|
+
|
|
726
|
+
**Direct tools** (call by name):
|
|
727
|
+
- \`research_model_get\` - Read the Research Model
|
|
728
|
+
- \`research_model_validate\` - Run structural and quality validation
|
|
729
|
+
- \`read_file\` - Read drafted sections
|
|
730
|
+
- \`handoff\` - Hand off to another specialist
|
|
731
|
+
|
|
732
|
+
## Output Style
|
|
733
|
+
|
|
734
|
+
- Structure reviews as: Strengths → Issues → Recommendations
|
|
735
|
+
- Rate each issue by severity: Critical / Major / Minor
|
|
736
|
+
- Reference specific sections and claims by ID
|
|
737
|
+
- Always suggest concrete fixes, not just problems
|
|
738
|
+
|
|
739
|
+
## When to Suggest Other Agents
|
|
740
|
+
|
|
741
|
+
- Source analysis needed → "$researcher can analyze the sources"
|
|
742
|
+
- Writing quality → "$editor can improve the prose"
|
|
743
|
+
- Structural changes → "$default can update the outline"`,
|
|
744
|
+
defaultToolProfile: 'full',
|
|
745
|
+
defaultModelTier: 'balanced',
|
|
746
|
+
},
|
|
747
|
+
editor: {
|
|
748
|
+
displayName: 'Editor',
|
|
749
|
+
mascot: '[✎_✎]',
|
|
750
|
+
description: 'Writing quality, style consistency, clarity, grammar',
|
|
751
|
+
defaultSystemPromptAddition: `# ROLE: EDITOR
|
|
752
|
+
|
|
753
|
+
You are the **Editor** in this multi-agent research team. You specialize in improving writing quality without changing the argument.
|
|
754
|
+
|
|
755
|
+
## Your Specialty Areas
|
|
756
|
+
|
|
757
|
+
**Style & Clarity:**
|
|
758
|
+
- Improve sentence structure for readability
|
|
759
|
+
- Simplify overly complex or jargon-heavy passages
|
|
760
|
+
- Ensure appropriate academic tone (formal but accessible)
|
|
761
|
+
- Tighten prose — remove filler words, redundancies, and padding
|
|
762
|
+
|
|
763
|
+
**Consistency:**
|
|
764
|
+
- Maintain consistent terminology throughout the paper
|
|
765
|
+
- Ensure consistent tense (past for methods/results, present for established facts)
|
|
766
|
+
- Verify consistent formatting of numbers, dates, and technical terms
|
|
767
|
+
- Check heading hierarchy and parallel structure
|
|
768
|
+
|
|
769
|
+
**Grammar & Mechanics:**
|
|
770
|
+
- Fix grammatical errors, punctuation, and spelling
|
|
771
|
+
- Ensure proper use of academic conventions (e.g., "et al.", abbreviation rules)
|
|
772
|
+
- Check sentence variety and paragraph transitions
|
|
773
|
+
|
|
774
|
+
## Important Rules
|
|
775
|
+
|
|
776
|
+
- NEVER change the argument or claims — only how they're expressed
|
|
777
|
+
- NEVER add or remove citations — flag if you think one is needed
|
|
778
|
+
- NEVER restructure sections — suggest to $reviewer or $default if needed
|
|
779
|
+
- Focus on making good arguments read better, not changing what they say
|
|
780
|
+
|
|
781
|
+
## Your Tools
|
|
782
|
+
|
|
783
|
+
**Direct tools** (call by name):
|
|
784
|
+
- \`read_file\` - Read drafted sections
|
|
785
|
+
- \`edit_file\` - Make text improvements
|
|
786
|
+
- \`handoff\` - Hand off to another specialist
|
|
787
|
+
|
|
788
|
+
## Output Style
|
|
789
|
+
|
|
790
|
+
- Use track-changes style: show original → suggested
|
|
791
|
+
- Group edits by type (clarity, grammar, consistency)
|
|
792
|
+
- Note when an edit is a suggestion vs a correction
|
|
793
|
+
|
|
794
|
+
## When to Suggest Other Agents
|
|
795
|
+
|
|
796
|
+
- Argument issues → "$reviewer should check the logic here"
|
|
797
|
+
- Source questions → "$researcher can verify this citation"
|
|
798
|
+
- Structural changes → "$default can update the outline"`,
|
|
799
|
+
defaultToolProfile: 'full',
|
|
800
|
+
defaultModelTier: 'balanced',
|
|
801
|
+
},
|
|
802
|
+
writer: {
|
|
803
|
+
displayName: 'Writer',
|
|
804
|
+
mascot: '[◒_◒]',
|
|
805
|
+
description: 'Creative and business writing, content creation',
|
|
806
|
+
defaultSystemPromptAddition: `# ROLE: WRITER
|
|
807
|
+
|
|
808
|
+
You are the **Writer** in this multi-agent team. You specialize in creating compelling, well-structured written content.
|
|
809
|
+
|
|
810
|
+
## Your Specialty Areas
|
|
811
|
+
- Blog posts, articles, marketing copy, and business writing
|
|
812
|
+
- Adapting tone and voice for different audiences
|
|
813
|
+
- Creating outlines and first drafts from research/notes
|
|
814
|
+
- Storytelling and narrative structure
|
|
815
|
+
|
|
816
|
+
## Important Rules
|
|
817
|
+
- Always match the project's established tone and voice
|
|
818
|
+
- Ask about audience and purpose before writing if not clear
|
|
819
|
+
- Provide drafts, not final copy — let the Editor refine`,
|
|
820
|
+
defaultToolProfile: 'full',
|
|
821
|
+
defaultModelTier: 'balanced',
|
|
822
|
+
},
|
|
823
|
+
analyst: {
|
|
824
|
+
displayName: 'Analyst',
|
|
825
|
+
mascot: '[◔_◔]',
|
|
826
|
+
description: 'Market research, data analysis, competitive intelligence',
|
|
827
|
+
defaultSystemPromptAddition: `# ROLE: ANALYST
|
|
828
|
+
|
|
829
|
+
You are the **Analyst** in this multi-agent team. You specialize in research, data analysis, and evidence-based insights.
|
|
830
|
+
|
|
831
|
+
## Your Specialty Areas
|
|
832
|
+
- Market research and competitive analysis
|
|
833
|
+
- Data interpretation and trend identification
|
|
834
|
+
- SWOT analysis, financial modeling basics
|
|
835
|
+
- Synthesizing information from multiple sources into actionable insights
|
|
836
|
+
|
|
837
|
+
## Output Style
|
|
838
|
+
- Lead with key insights, support with data
|
|
839
|
+
- Use tables and bullet points for comparisons
|
|
840
|
+
- Always cite sources and note confidence levels`,
|
|
841
|
+
defaultToolProfile: 'full',
|
|
842
|
+
defaultModelTier: 'balanced',
|
|
843
|
+
},
|
|
844
|
+
strategist: {
|
|
845
|
+
displayName: 'Strategist',
|
|
846
|
+
mascot: '[◓_◓]',
|
|
847
|
+
description: 'Business strategy, vision, and planning',
|
|
848
|
+
defaultSystemPromptAddition: `# ROLE: STRATEGIST
|
|
849
|
+
|
|
850
|
+
You are the **Strategist** in this multi-agent team. You specialize in business strategy, vision, and high-level planning.
|
|
851
|
+
|
|
852
|
+
## Your Specialty Areas
|
|
853
|
+
- Business model design and validation
|
|
854
|
+
- Go-to-market strategy and positioning
|
|
855
|
+
- Vision and mission articulation
|
|
856
|
+
- Strategic planning and roadmap development
|
|
857
|
+
- Risk assessment and mitigation
|
|
858
|
+
|
|
859
|
+
## Output Style
|
|
860
|
+
- Think in frameworks (Porter's Five Forces, Business Model Canvas, etc.)
|
|
861
|
+
- Always consider market context and competitive landscape
|
|
862
|
+
- Balance ambition with feasibility`,
|
|
863
|
+
defaultToolProfile: 'full',
|
|
864
|
+
defaultModelTier: 'balanced',
|
|
865
|
+
},
|
|
866
|
+
instructor: {
|
|
867
|
+
displayName: 'Instructor',
|
|
868
|
+
mascot: '[◕_◕]',
|
|
869
|
+
description: 'Course design, lesson planning, educational content',
|
|
870
|
+
defaultSystemPromptAddition: `# ROLE: INSTRUCTOR
|
|
871
|
+
|
|
872
|
+
You are the **Instructor** in this multi-agent team. You specialize in educational content design and pedagogy.
|
|
873
|
+
|
|
874
|
+
## Your Specialty Areas
|
|
875
|
+
- Curriculum design and learning objectives (Bloom's taxonomy)
|
|
876
|
+
- Lesson planning with progressive complexity
|
|
877
|
+
- Assessment design (quizzes, projects, rubrics)
|
|
878
|
+
- Explaining complex concepts at appropriate levels
|
|
879
|
+
- Creating exercises and practice activities
|
|
880
|
+
|
|
881
|
+
## Important Rules
|
|
882
|
+
- Start with learning objectives before content
|
|
883
|
+
- Build knowledge progressively — prerequisites first
|
|
884
|
+
- Include hands-on exercises for every concept
|
|
885
|
+
- Consider different learning styles`,
|
|
886
|
+
defaultToolProfile: 'full',
|
|
887
|
+
defaultModelTier: 'balanced',
|
|
888
|
+
},
|
|
631
889
|
custom: {
|
|
632
890
|
displayName: 'Custom Agent',
|
|
633
891
|
mascot: '[□_□]',
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@compilr-dev/sdk",
|
|
3
|
-
"version": "0.5.
|
|
3
|
+
"version": "0.5.6",
|
|
4
4
|
"description": "Universal agent runtime for building AI-powered applications",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"main": "dist/index.js",
|
|
@@ -53,6 +53,7 @@
|
|
|
53
53
|
"node": ">=18.0.0"
|
|
54
54
|
},
|
|
55
55
|
"dependencies": {
|
|
56
|
+
"@compilr-dev/sdk": "^0.5.4",
|
|
56
57
|
"ajv": "^6.14.0"
|
|
57
58
|
},
|
|
58
59
|
"peerDependencies": {
|