@ai-coders/context 0.7.0 → 0.7.1
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/README.md +25 -5
- package/dist/generators/agents/agentGenerator.d.ts +2 -0
- package/dist/generators/agents/agentGenerator.d.ts.map +1 -1
- package/dist/generators/agents/agentGenerator.js +29 -4
- package/dist/generators/agents/agentGenerator.js.map +1 -1
- package/dist/generators/documentation/codebaseMapGenerator.d.ts +45 -0
- package/dist/generators/documentation/codebaseMapGenerator.d.ts.map +1 -1
- package/dist/generators/documentation/codebaseMapGenerator.js +429 -10
- package/dist/generators/documentation/codebaseMapGenerator.js.map +1 -1
- package/dist/generators/documentation/documentationGenerator.d.ts +2 -0
- package/dist/generators/documentation/documentationGenerator.d.ts.map +1 -1
- package/dist/generators/documentation/documentationGenerator.js +28 -6
- package/dist/generators/documentation/documentationGenerator.js.map +1 -1
- package/dist/generators/documentation/index.d.ts +1 -1
- package/dist/generators/documentation/index.d.ts.map +1 -1
- package/dist/generators/plans/templates/planTemplate.d.ts.map +1 -1
- package/dist/generators/plans/templates/planTemplate.js +54 -18
- package/dist/generators/plans/templates/planTemplate.js.map +1 -1
- package/dist/generators/shared/structures/agents/definitions.d.ts +1 -1
- package/dist/generators/shared/structures/agents/definitions.d.ts.map +1 -1
- package/dist/generators/shared/structures/agents/definitions.js +554 -15
- package/dist/generators/shared/structures/agents/definitions.js.map +1 -1
- package/dist/generators/shared/structures/agents/factory.d.ts +17 -1
- package/dist/generators/shared/structures/agents/factory.d.ts.map +1 -1
- package/dist/generators/shared/structures/agents/factory.js +117 -91
- package/dist/generators/shared/structures/agents/factory.js.map +1 -1
- package/dist/generators/shared/structures/documentation/architecture.d.ts.map +1 -1
- package/dist/generators/shared/structures/documentation/architecture.js +55 -0
- package/dist/generators/shared/structures/documentation/architecture.js.map +1 -1
- package/dist/generators/shared/structures/documentation/dataFlow.d.ts.map +1 -1
- package/dist/generators/shared/structures/documentation/dataFlow.js +35 -0
- package/dist/generators/shared/structures/documentation/dataFlow.js.map +1 -1
- package/dist/generators/shared/structures/documentation/glossary.d.ts.map +1 -1
- package/dist/generators/shared/structures/documentation/glossary.js +20 -0
- package/dist/generators/shared/structures/documentation/glossary.js.map +1 -1
- package/dist/generators/shared/structures/documentation/projectOverview.d.ts.map +1 -1
- package/dist/generators/shared/structures/documentation/projectOverview.js +48 -0
- package/dist/generators/shared/structures/documentation/projectOverview.js.map +1 -1
- package/dist/generators/shared/structures/documentation/security.d.ts.map +1 -1
- package/dist/generators/shared/structures/documentation/security.js +45 -0
- package/dist/generators/shared/structures/documentation/security.js.map +1 -1
- package/dist/generators/shared/structures/documentation/testing.d.ts.map +1 -1
- package/dist/generators/shared/structures/documentation/testing.js +73 -0
- package/dist/generators/shared/structures/documentation/testing.js.map +1 -1
- package/dist/generators/shared/structures/documentation/tooling.d.ts.map +1 -1
- package/dist/generators/shared/structures/documentation/tooling.js +59 -0
- package/dist/generators/shared/structures/documentation/tooling.js.map +1 -1
- package/dist/generators/shared/structures/documentation/workflow.d.ts.map +1 -1
- package/dist/generators/shared/structures/documentation/workflow.js +60 -0
- package/dist/generators/shared/structures/documentation/workflow.js.map +1 -1
- package/dist/generators/shared/structures/serialization.d.ts.map +1 -1
- package/dist/generators/shared/structures/serialization.js +5 -0
- package/dist/generators/shared/structures/serialization.js.map +1 -1
- package/dist/generators/shared/structures/skills/definitions.d.ts +1 -1
- package/dist/generators/shared/structures/skills/definitions.d.ts.map +1 -1
- package/dist/generators/shared/structures/skills/definitions.js +420 -11
- package/dist/generators/shared/structures/skills/definitions.js.map +1 -1
- package/dist/generators/shared/structures/skills/factory.d.ts +10 -1
- package/dist/generators/shared/structures/skills/factory.d.ts.map +1 -1
- package/dist/generators/shared/structures/skills/factory.js +55 -36
- package/dist/generators/shared/structures/skills/factory.js.map +1 -1
- package/dist/generators/shared/structures/types.d.ts +2 -0
- package/dist/generators/shared/structures/types.d.ts.map +1 -1
- package/dist/index.js +68 -59
- package/dist/index.js.map +1 -1
- package/dist/services/ai/schemas.d.ts +2 -0
- package/dist/services/ai/schemas.d.ts.map +1 -1
- package/dist/services/ai/schemas.js +3 -1
- package/dist/services/ai/schemas.js.map +1 -1
- package/dist/services/ai/tools/fillScaffoldingTool.d.ts +1 -0
- package/dist/services/ai/tools/fillScaffoldingTool.d.ts.map +1 -1
- package/dist/services/ai/tools/fillScaffoldingTool.js +19 -1
- package/dist/services/ai/tools/fillScaffoldingTool.js.map +1 -1
- package/dist/services/ai/tools/getCodebaseMapTool.d.ts +1 -1
- package/dist/services/ai/tools/getCodebaseMapTool.js +5 -1
- package/dist/services/ai/tools/getCodebaseMapTool.js.map +1 -1
- package/dist/services/ai/tools/initializeContextTool.d.ts.map +1 -1
- package/dist/services/ai/tools/initializeContextTool.js +13 -0
- package/dist/services/ai/tools/initializeContextTool.js.map +1 -1
- package/dist/services/autoFill/autoFillService.d.ts +52 -0
- package/dist/services/autoFill/autoFillService.d.ts.map +1 -0
- package/dist/services/autoFill/autoFillService.js +473 -0
- package/dist/services/autoFill/autoFillService.js.map +1 -0
- package/dist/services/autoFill/index.d.ts +2 -0
- package/dist/services/autoFill/index.d.ts.map +1 -0
- package/dist/services/autoFill/index.js +6 -0
- package/dist/services/autoFill/index.js.map +1 -0
- package/dist/services/init/initService.d.ts +2 -0
- package/dist/services/init/initService.d.ts.map +1 -1
- package/dist/services/init/initService.js +29 -3
- package/dist/services/init/initService.js.map +1 -1
- package/dist/services/semantic/contextBuilder.d.ts.map +1 -1
- package/dist/services/semantic/contextBuilder.js +2 -1
- package/dist/services/semantic/contextBuilder.js.map +1 -1
- package/dist/services/semantic/types.d.ts.map +1 -1
- package/dist/services/semantic/types.js +2 -0
- package/dist/services/semantic/types.js.map +1 -1
- package/dist/utils/i18n.d.ts +4 -2
- package/dist/utils/i18n.d.ts.map +1 -1
- package/dist/utils/i18n.js +8 -4
- package/dist/utils/i18n.js.map +1 -1
- package/package.json +1 -1
|
@@ -1,22 +1,561 @@
|
|
|
1
1
|
"use strict";
|
|
2
2
|
/**
|
|
3
|
-
* Agent structure definitions
|
|
3
|
+
* Agent structure definitions with static default content
|
|
4
4
|
*/
|
|
5
5
|
Object.defineProperty(exports, "__esModule", { value: true });
|
|
6
6
|
exports.mobileSpecialistStructure = exports.databaseSpecialistStructure = exports.devopsSpecialistStructure = exports.architectSpecialistStructure = exports.frontendSpecialistStructure = exports.backendSpecialistStructure = exports.securityAuditorStructure = exports.performanceOptimizerStructure = exports.documentationWriterStructure = exports.testWriterStructure = exports.refactoringSpecialistStructure = exports.featureDeveloperStructure = exports.bugFixerStructure = exports.codeReviewerStructure = void 0;
|
|
7
7
|
const factory_1 = require("./factory");
|
|
8
|
-
|
|
9
|
-
|
|
10
|
-
|
|
11
|
-
|
|
12
|
-
|
|
13
|
-
|
|
14
|
-
|
|
15
|
-
|
|
16
|
-
|
|
17
|
-
|
|
18
|
-
|
|
19
|
-
|
|
20
|
-
|
|
21
|
-
|
|
8
|
+
// ============================================================================
|
|
9
|
+
// Default Content Definitions
|
|
10
|
+
// ============================================================================
|
|
11
|
+
const codeReviewerContent = {
|
|
12
|
+
mission: `This agent reviews code changes for quality, consistency, and adherence to project standards.
|
|
13
|
+
|
|
14
|
+
**When to engage:**
|
|
15
|
+
- Pull request reviews
|
|
16
|
+
- Pre-commit code quality checks
|
|
17
|
+
- Architecture decision validation
|
|
18
|
+
- Code pattern compliance verification
|
|
19
|
+
|
|
20
|
+
**Review focus areas:**
|
|
21
|
+
- Code correctness and logic
|
|
22
|
+
- Performance implications
|
|
23
|
+
- Security considerations
|
|
24
|
+
- Test coverage
|
|
25
|
+
- Documentation completeness`,
|
|
26
|
+
responsibilities: `- Review pull requests for code quality and correctness
|
|
27
|
+
- Check adherence to project coding standards and conventions
|
|
28
|
+
- Identify potential bugs, edge cases, and error handling gaps
|
|
29
|
+
- Evaluate test coverage for changed code
|
|
30
|
+
- Assess performance implications of changes
|
|
31
|
+
- Flag security vulnerabilities or concerns
|
|
32
|
+
- Suggest improvements for readability and maintainability
|
|
33
|
+
- Verify documentation is updated for public API changes`,
|
|
34
|
+
bestPractices: `- Start with understanding the context and purpose of changes
|
|
35
|
+
- Focus on the most impactful issues first
|
|
36
|
+
- Provide actionable, specific feedback with examples
|
|
37
|
+
- Distinguish between required changes and suggestions
|
|
38
|
+
- Be respectful and constructive in feedback
|
|
39
|
+
- Check for consistency with existing codebase patterns
|
|
40
|
+
- Consider the reviewer's perspective and time constraints
|
|
41
|
+
- Link to relevant documentation or examples when suggesting changes`,
|
|
42
|
+
collaborationChecklist: `- [ ] Read the PR description and linked issues to understand context
|
|
43
|
+
- [ ] Review the overall design approach before diving into details
|
|
44
|
+
- [ ] Check that tests cover the main functionality and edge cases
|
|
45
|
+
- [ ] Verify documentation is updated for any API changes
|
|
46
|
+
- [ ] Confirm the PR follows project coding standards
|
|
47
|
+
- [ ] Leave clear, actionable feedback with suggested solutions
|
|
48
|
+
- [ ] Approve or request changes based on review findings`,
|
|
49
|
+
};
|
|
50
|
+
const bugFixerContent = {
|
|
51
|
+
mission: `This agent analyzes bug reports and implements targeted fixes with minimal side effects.
|
|
52
|
+
|
|
53
|
+
**When to engage:**
|
|
54
|
+
- Bug reports and issue investigation
|
|
55
|
+
- Production incident response
|
|
56
|
+
- Regression identification
|
|
57
|
+
- Error log analysis
|
|
58
|
+
|
|
59
|
+
**Fix approach:**
|
|
60
|
+
- Root cause analysis before coding
|
|
61
|
+
- Minimal, focused changes
|
|
62
|
+
- Regression test creation
|
|
63
|
+
- Impact assessment`,
|
|
64
|
+
responsibilities: `- Analyze bug reports and reproduce issues locally
|
|
65
|
+
- Investigate root causes through debugging and log analysis
|
|
66
|
+
- Implement focused fixes with minimal code changes
|
|
67
|
+
- Write regression tests to prevent recurrence
|
|
68
|
+
- Document the bug cause and fix for future reference
|
|
69
|
+
- Verify fix doesn't introduce new issues
|
|
70
|
+
- Update error handling if gaps are discovered
|
|
71
|
+
- Coordinate with test writer for comprehensive test coverage`,
|
|
72
|
+
bestPractices: `- Always reproduce the bug before attempting to fix
|
|
73
|
+
- Understand the root cause, not just the symptoms
|
|
74
|
+
- Make the smallest change that fixes the issue
|
|
75
|
+
- Add a test that would have caught this bug
|
|
76
|
+
- Consider if the bug exists elsewhere in similar code
|
|
77
|
+
- Check for related issues that might have the same cause
|
|
78
|
+
- Document the investigation steps for future reference
|
|
79
|
+
- Verify the fix in an environment similar to where the bug occurred`,
|
|
80
|
+
collaborationChecklist: `- [ ] Reproduce the bug consistently
|
|
81
|
+
- [ ] Identify the root cause through debugging
|
|
82
|
+
- [ ] Implement a minimal, targeted fix
|
|
83
|
+
- [ ] Write a regression test for the bug
|
|
84
|
+
- [ ] Verify the fix doesn't break existing functionality
|
|
85
|
+
- [ ] Document the cause and solution
|
|
86
|
+
- [ ] Update related documentation if needed`,
|
|
87
|
+
};
|
|
88
|
+
const featureDeveloperContent = {
|
|
89
|
+
mission: `This agent implements new features according to specifications with clean architecture.
|
|
90
|
+
|
|
91
|
+
**When to engage:**
|
|
92
|
+
- New feature implementation
|
|
93
|
+
- Feature enhancement requests
|
|
94
|
+
- User story development
|
|
95
|
+
- API endpoint additions
|
|
96
|
+
|
|
97
|
+
**Implementation approach:**
|
|
98
|
+
- Understand requirements thoroughly
|
|
99
|
+
- Design before coding
|
|
100
|
+
- Integrate with existing patterns
|
|
101
|
+
- Write tests alongside code`,
|
|
102
|
+
responsibilities: `- Implement new features based on specifications and requirements
|
|
103
|
+
- Design solutions that integrate well with existing architecture
|
|
104
|
+
- Write clean, maintainable, and well-documented code
|
|
105
|
+
- Create comprehensive tests for new functionality
|
|
106
|
+
- Handle edge cases and error scenarios gracefully
|
|
107
|
+
- Coordinate with other agents for reviews and testing
|
|
108
|
+
- Update documentation for new features
|
|
109
|
+
- Ensure backward compatibility when modifying existing APIs`,
|
|
110
|
+
bestPractices: `- Start with understanding the full requirements and acceptance criteria
|
|
111
|
+
- Design the solution before writing code
|
|
112
|
+
- Follow existing code patterns and conventions in the project
|
|
113
|
+
- Write tests as you develop, not as an afterthought
|
|
114
|
+
- Keep commits focused and well-documented
|
|
115
|
+
- Communicate blockers or unclear requirements early
|
|
116
|
+
- Consider performance, security, and accessibility from the start
|
|
117
|
+
- Leave the codebase cleaner than you found it`,
|
|
118
|
+
collaborationChecklist: `- [ ] Understand requirements and acceptance criteria fully
|
|
119
|
+
- [ ] Design the solution and get feedback on approach
|
|
120
|
+
- [ ] Implement feature following project patterns
|
|
121
|
+
- [ ] Write unit and integration tests
|
|
122
|
+
- [ ] Update relevant documentation
|
|
123
|
+
- [ ] Create PR with clear description and testing notes
|
|
124
|
+
- [ ] Address code review feedback`,
|
|
125
|
+
};
|
|
126
|
+
const refactoringSpecialistContent = {
|
|
127
|
+
mission: `This agent identifies code smells and improves code structure while preserving functionality.
|
|
128
|
+
|
|
129
|
+
**When to engage:**
|
|
130
|
+
- Code smell identification
|
|
131
|
+
- Technical debt reduction
|
|
132
|
+
- Architecture improvements
|
|
133
|
+
- Pattern standardization
|
|
134
|
+
|
|
135
|
+
**Refactoring approach:**
|
|
136
|
+
- Incremental, safe changes
|
|
137
|
+
- Test coverage first
|
|
138
|
+
- Preserve behavior exactly
|
|
139
|
+
- Improve readability and maintainability`,
|
|
140
|
+
responsibilities: `- Identify code smells and areas needing improvement
|
|
141
|
+
- Plan and execute refactoring in safe, incremental steps
|
|
142
|
+
- Ensure comprehensive test coverage before refactoring
|
|
143
|
+
- Preserve existing functionality exactly
|
|
144
|
+
- Improve code readability and maintainability
|
|
145
|
+
- Reduce duplication and complexity
|
|
146
|
+
- Standardize patterns across the codebase
|
|
147
|
+
- Document architectural decisions and improvements`,
|
|
148
|
+
bestPractices: `- Never refactor without adequate test coverage
|
|
149
|
+
- Make one type of change at a time (rename, extract, move)
|
|
150
|
+
- Commit frequently with clear descriptions
|
|
151
|
+
- Preserve behavior exactly - refactoring is not feature change
|
|
152
|
+
- Use automated refactoring tools when available
|
|
153
|
+
- Review changes carefully before committing
|
|
154
|
+
- If tests break, the refactoring changed behavior - investigate
|
|
155
|
+
- Keep refactoring PRs focused and reviewable`,
|
|
156
|
+
collaborationChecklist: `- [ ] Ensure adequate test coverage exists for the code
|
|
157
|
+
- [ ] Identify specific improvements to make
|
|
158
|
+
- [ ] Plan incremental steps for the refactoring
|
|
159
|
+
- [ ] Execute changes one step at a time
|
|
160
|
+
- [ ] Run tests after each step to verify behavior
|
|
161
|
+
- [ ] Update documentation for any structural changes
|
|
162
|
+
- [ ] Request review focusing on behavior preservation`,
|
|
163
|
+
};
|
|
164
|
+
const testWriterContent = {
|
|
165
|
+
mission: `This agent writes comprehensive tests and maintains test coverage standards.
|
|
166
|
+
|
|
167
|
+
**When to engage:**
|
|
168
|
+
- New feature testing
|
|
169
|
+
- Bug regression tests
|
|
170
|
+
- Test coverage improvements
|
|
171
|
+
- Test suite maintenance
|
|
172
|
+
|
|
173
|
+
**Testing approach:**
|
|
174
|
+
- Test pyramid (unit, integration, e2e)
|
|
175
|
+
- Edge case coverage
|
|
176
|
+
- Clear, maintainable tests
|
|
177
|
+
- Fast, reliable execution`,
|
|
178
|
+
responsibilities: `- Write unit tests for individual functions and components
|
|
179
|
+
- Create integration tests for feature workflows
|
|
180
|
+
- Add end-to-end tests for critical user paths
|
|
181
|
+
- Identify and cover edge cases and error scenarios
|
|
182
|
+
- Maintain test suite performance and reliability
|
|
183
|
+
- Update tests when code changes
|
|
184
|
+
- Improve test coverage for undertested areas
|
|
185
|
+
- Document testing patterns and best practices`,
|
|
186
|
+
bestPractices: `- Follow the test pyramid: many unit tests, fewer integration, minimal e2e
|
|
187
|
+
- Write tests that are fast, isolated, and deterministic
|
|
188
|
+
- Use descriptive test names that explain what and why
|
|
189
|
+
- Test behavior, not implementation details
|
|
190
|
+
- Cover happy paths, edge cases, and error scenarios
|
|
191
|
+
- Keep tests maintainable and avoid test code duplication
|
|
192
|
+
- Use appropriate mocking strategies
|
|
193
|
+
- Ensure tests can run independently and in any order`,
|
|
194
|
+
collaborationChecklist: `- [ ] Understand the feature or bug being tested
|
|
195
|
+
- [ ] Identify key test scenarios (happy path, edge cases, errors)
|
|
196
|
+
- [ ] Write unit tests for individual components
|
|
197
|
+
- [ ] Add integration tests for feature workflows
|
|
198
|
+
- [ ] Verify test coverage meets project standards
|
|
199
|
+
- [ ] Ensure tests are fast and reliable
|
|
200
|
+
- [ ] Document any complex test setups or patterns`,
|
|
201
|
+
};
|
|
202
|
+
const documentationWriterContent = {
|
|
203
|
+
mission: `This agent creates and maintains documentation to keep it in sync with code.
|
|
204
|
+
|
|
205
|
+
**When to engage:**
|
|
206
|
+
- New feature documentation
|
|
207
|
+
- API reference updates
|
|
208
|
+
- README improvements
|
|
209
|
+
- Code comment reviews
|
|
210
|
+
|
|
211
|
+
**Documentation approach:**
|
|
212
|
+
- Clear and concise writing
|
|
213
|
+
- Practical code examples
|
|
214
|
+
- Up-to-date with code changes
|
|
215
|
+
- Accessible to target audience`,
|
|
216
|
+
responsibilities: `- Write and maintain README files and getting started guides
|
|
217
|
+
- Create API documentation with clear examples
|
|
218
|
+
- Document architecture decisions and system design
|
|
219
|
+
- Keep inline code comments accurate and helpful
|
|
220
|
+
- Update documentation when code changes
|
|
221
|
+
- Create tutorials and how-to guides
|
|
222
|
+
- Maintain changelog and release notes
|
|
223
|
+
- Review documentation for clarity and accuracy`,
|
|
224
|
+
bestPractices: `- Write for your target audience (developers, users, etc.)
|
|
225
|
+
- Include working code examples that can be copied
|
|
226
|
+
- Keep documentation close to the code it describes
|
|
227
|
+
- Update docs in the same PR as code changes
|
|
228
|
+
- Use consistent formatting and terminology
|
|
229
|
+
- Include common use cases and troubleshooting tips
|
|
230
|
+
- Make documentation searchable and well-organized
|
|
231
|
+
- Review docs from a newcomer's perspective`,
|
|
232
|
+
collaborationChecklist: `- [ ] Identify what needs to be documented
|
|
233
|
+
- [ ] Determine the target audience and their needs
|
|
234
|
+
- [ ] Write clear, concise documentation
|
|
235
|
+
- [ ] Include working code examples
|
|
236
|
+
- [ ] Verify examples work with current code
|
|
237
|
+
- [ ] Review for clarity and completeness
|
|
238
|
+
- [ ] Get feedback from someone unfamiliar with the feature`,
|
|
239
|
+
};
|
|
240
|
+
const performanceOptimizerContent = {
|
|
241
|
+
mission: `This agent identifies bottlenecks and optimizes performance based on measurements.
|
|
242
|
+
|
|
243
|
+
**When to engage:**
|
|
244
|
+
- Performance investigations
|
|
245
|
+
- Optimization requests
|
|
246
|
+
- Scalability planning
|
|
247
|
+
- Resource usage concerns
|
|
248
|
+
|
|
249
|
+
**Optimization approach:**
|
|
250
|
+
- Measure before optimizing
|
|
251
|
+
- Target actual bottlenecks
|
|
252
|
+
- Verify improvements with benchmarks
|
|
253
|
+
- Document trade-offs`,
|
|
254
|
+
responsibilities: `- Profile and measure performance to identify bottlenecks
|
|
255
|
+
- Optimize algorithms and data structures
|
|
256
|
+
- Implement caching strategies where appropriate
|
|
257
|
+
- Reduce memory usage and prevent leaks
|
|
258
|
+
- Optimize database queries and access patterns
|
|
259
|
+
- Improve network request efficiency
|
|
260
|
+
- Create performance benchmarks and tests
|
|
261
|
+
- Document performance requirements and baselines`,
|
|
262
|
+
bestPractices: `- Always measure before and after optimization
|
|
263
|
+
- Focus on actual bottlenecks, not assumed ones
|
|
264
|
+
- Profile in production-like conditions
|
|
265
|
+
- Consider the 80/20 rule - optimize what matters most
|
|
266
|
+
- Document performance baselines and targets
|
|
267
|
+
- Be aware of optimization trade-offs (memory vs speed, etc.)
|
|
268
|
+
- Don't sacrifice readability for micro-optimizations
|
|
269
|
+
- Add performance regression tests for critical paths`,
|
|
270
|
+
collaborationChecklist: `- [ ] Define performance requirements and targets
|
|
271
|
+
- [ ] Profile to identify actual bottlenecks
|
|
272
|
+
- [ ] Propose optimization approach
|
|
273
|
+
- [ ] Implement optimization with minimal side effects
|
|
274
|
+
- [ ] Measure improvement against baseline
|
|
275
|
+
- [ ] Add performance tests to prevent regression
|
|
276
|
+
- [ ] Document the optimization and trade-offs`,
|
|
277
|
+
};
|
|
278
|
+
const securityAuditorContent = {
|
|
279
|
+
mission: `This agent identifies security vulnerabilities and implements security best practices.
|
|
280
|
+
|
|
281
|
+
**When to engage:**
|
|
282
|
+
- Security reviews
|
|
283
|
+
- Vulnerability assessments
|
|
284
|
+
- Authentication/authorization changes
|
|
285
|
+
- Sensitive data handling
|
|
286
|
+
|
|
287
|
+
**Security approach:**
|
|
288
|
+
- OWASP top 10 awareness
|
|
289
|
+
- Defense in depth
|
|
290
|
+
- Principle of least privilege
|
|
291
|
+
- Security testing`,
|
|
292
|
+
responsibilities: `- Review code for security vulnerabilities
|
|
293
|
+
- Assess authentication and authorization implementations
|
|
294
|
+
- Check for injection vulnerabilities (SQL, XSS, command, etc.)
|
|
295
|
+
- Verify proper handling of sensitive data
|
|
296
|
+
- Review dependency security (known vulnerabilities)
|
|
297
|
+
- Implement security headers and configurations
|
|
298
|
+
- Design secure API endpoints
|
|
299
|
+
- Document security requirements and controls`,
|
|
300
|
+
bestPractices: `- Never trust user input - always validate and sanitize
|
|
301
|
+
- Apply principle of least privilege
|
|
302
|
+
- Use established security libraries, don't roll your own
|
|
303
|
+
- Keep dependencies updated to patch vulnerabilities
|
|
304
|
+
- Implement defense in depth (multiple security layers)
|
|
305
|
+
- Log security events for monitoring and alerting
|
|
306
|
+
- Encrypt sensitive data at rest and in transit
|
|
307
|
+
- Review authentication and session management carefully`,
|
|
308
|
+
collaborationChecklist: `- [ ] Review for OWASP top 10 vulnerabilities
|
|
309
|
+
- [ ] Check input validation and sanitization
|
|
310
|
+
- [ ] Verify authentication and authorization
|
|
311
|
+
- [ ] Assess sensitive data handling
|
|
312
|
+
- [ ] Review dependencies for known vulnerabilities
|
|
313
|
+
- [ ] Check security headers and configurations
|
|
314
|
+
- [ ] Document security findings and recommendations`,
|
|
315
|
+
};
|
|
316
|
+
const backendSpecialistContent = {
|
|
317
|
+
mission: `This agent designs and implements server-side architecture and APIs.
|
|
318
|
+
|
|
319
|
+
**When to engage:**
|
|
320
|
+
- API design and implementation
|
|
321
|
+
- Service architecture decisions
|
|
322
|
+
- Database integration
|
|
323
|
+
- Backend performance optimization
|
|
324
|
+
|
|
325
|
+
**Implementation approach:**
|
|
326
|
+
- RESTful or GraphQL API design
|
|
327
|
+
- Service layer patterns
|
|
328
|
+
- Database optimization
|
|
329
|
+
- Authentication and authorization`,
|
|
330
|
+
responsibilities: `- Design and implement RESTful or GraphQL APIs
|
|
331
|
+
- Create service layer architecture
|
|
332
|
+
- Implement data access patterns and repositories
|
|
333
|
+
- Design and optimize database schemas
|
|
334
|
+
- Set up authentication and authorization
|
|
335
|
+
- Implement background jobs and queues
|
|
336
|
+
- Create API documentation
|
|
337
|
+
- Handle error handling and logging`,
|
|
338
|
+
bestPractices: `- Follow REST conventions or GraphQL best practices
|
|
339
|
+
- Use proper HTTP status codes and error responses
|
|
340
|
+
- Implement pagination, filtering, and sorting for collections
|
|
341
|
+
- Design idempotent operations where appropriate
|
|
342
|
+
- Use transactions for data consistency
|
|
343
|
+
- Implement proper request validation
|
|
344
|
+
- Cache responses when appropriate
|
|
345
|
+
- Log requests and errors for debugging`,
|
|
346
|
+
collaborationChecklist: `- [ ] Design API contract and document endpoints
|
|
347
|
+
- [ ] Implement service layer with business logic
|
|
348
|
+
- [ ] Create data access layer and repositories
|
|
349
|
+
- [ ] Add input validation and error handling
|
|
350
|
+
- [ ] Implement authentication if required
|
|
351
|
+
- [ ] Write tests for API endpoints
|
|
352
|
+
- [ ] Update API documentation`,
|
|
353
|
+
};
|
|
354
|
+
const frontendSpecialistContent = {
|
|
355
|
+
mission: `This agent designs and implements user interfaces with focus on UX and accessibility.
|
|
356
|
+
|
|
357
|
+
**When to engage:**
|
|
358
|
+
- UI component development
|
|
359
|
+
- State management decisions
|
|
360
|
+
- Accessibility improvements
|
|
361
|
+
- Frontend performance optimization
|
|
362
|
+
|
|
363
|
+
**Implementation approach:**
|
|
364
|
+
- Component-based architecture
|
|
365
|
+
- Responsive design
|
|
366
|
+
- Accessibility first
|
|
367
|
+
- Performance optimization`,
|
|
368
|
+
responsibilities: `- Implement UI components and layouts
|
|
369
|
+
- Manage application state effectively
|
|
370
|
+
- Ensure responsive design across devices
|
|
371
|
+
- Implement accessibility standards (WCAG)
|
|
372
|
+
- Optimize frontend performance (bundle size, rendering)
|
|
373
|
+
- Handle form validation and user input
|
|
374
|
+
- Implement client-side routing
|
|
375
|
+
- Create reusable component libraries`,
|
|
376
|
+
bestPractices: `- Build components that are reusable and composable
|
|
377
|
+
- Follow accessibility guidelines from the start
|
|
378
|
+
- Test on multiple devices and browsers
|
|
379
|
+
- Optimize bundle size and loading performance
|
|
380
|
+
- Use semantic HTML elements
|
|
381
|
+
- Implement proper keyboard navigation
|
|
382
|
+
- Handle loading, error, and empty states
|
|
383
|
+
- Write component tests and visual regression tests`,
|
|
384
|
+
collaborationChecklist: `- [ ] Review design specifications and requirements
|
|
385
|
+
- [ ] Plan component structure and state management
|
|
386
|
+
- [ ] Implement responsive, accessible components
|
|
387
|
+
- [ ] Handle all UI states (loading, error, empty)
|
|
388
|
+
- [ ] Test across browsers and devices
|
|
389
|
+
- [ ] Optimize performance and bundle size
|
|
390
|
+
- [ ] Write component tests`,
|
|
391
|
+
};
|
|
392
|
+
const architectSpecialistContent = {
|
|
393
|
+
mission: `This agent designs overall system architecture and establishes technical standards.
|
|
394
|
+
|
|
395
|
+
**When to engage:**
|
|
396
|
+
- System design decisions
|
|
397
|
+
- Technology selection
|
|
398
|
+
- Architecture reviews
|
|
399
|
+
- Scalability planning
|
|
400
|
+
|
|
401
|
+
**Design approach:**
|
|
402
|
+
- Scalable and maintainable architecture
|
|
403
|
+
- Clear separation of concerns
|
|
404
|
+
- Technology evaluation
|
|
405
|
+
- Documentation of decisions`,
|
|
406
|
+
responsibilities: `- Design system architecture and component interactions
|
|
407
|
+
- Evaluate and select technologies and frameworks
|
|
408
|
+
- Establish coding standards and patterns
|
|
409
|
+
- Create architecture decision records (ADRs)
|
|
410
|
+
- Plan for scalability and reliability
|
|
411
|
+
- Review designs for technical soundness
|
|
412
|
+
- Guide team on architectural best practices
|
|
413
|
+
- Balance technical debt with delivery needs`,
|
|
414
|
+
bestPractices: `- Document architectural decisions and their rationale
|
|
415
|
+
- Design for change - anticipate future requirements
|
|
416
|
+
- Keep architecture as simple as needed
|
|
417
|
+
- Consider operational concerns (monitoring, deployment)
|
|
418
|
+
- Evaluate trade-offs explicitly
|
|
419
|
+
- Use proven patterns and avoid over-engineering
|
|
420
|
+
- Ensure architecture supports testing and debugging
|
|
421
|
+
- Review architecture regularly as requirements evolve`,
|
|
422
|
+
collaborationChecklist: `- [ ] Understand requirements and constraints
|
|
423
|
+
- [ ] Evaluate architectural options and trade-offs
|
|
424
|
+
- [ ] Design component structure and interactions
|
|
425
|
+
- [ ] Document decisions in ADRs
|
|
426
|
+
- [ ] Review design with team for feedback
|
|
427
|
+
- [ ] Plan implementation approach
|
|
428
|
+
- [ ] Create guidelines for developers`,
|
|
429
|
+
};
|
|
430
|
+
const devopsSpecialistContent = {
|
|
431
|
+
mission: `This agent designs CI/CD pipelines, infrastructure, and deployment automation.
|
|
432
|
+
|
|
433
|
+
**When to engage:**
|
|
434
|
+
- CI/CD pipeline setup
|
|
435
|
+
- Infrastructure provisioning
|
|
436
|
+
- Deployment automation
|
|
437
|
+
- Monitoring and alerting
|
|
438
|
+
|
|
439
|
+
**DevOps approach:**
|
|
440
|
+
- Infrastructure as code
|
|
441
|
+
- Automated testing in pipelines
|
|
442
|
+
- Continuous deployment
|
|
443
|
+
- Observability and monitoring`,
|
|
444
|
+
responsibilities: `- Design and maintain CI/CD pipelines
|
|
445
|
+
- Provision and manage infrastructure as code
|
|
446
|
+
- Automate deployment processes
|
|
447
|
+
- Set up monitoring, logging, and alerting
|
|
448
|
+
- Manage containerization and orchestration
|
|
449
|
+
- Configure environments (dev, staging, production)
|
|
450
|
+
- Implement security in the deployment pipeline
|
|
451
|
+
- Optimize build and deployment times`,
|
|
452
|
+
bestPractices: `- Use infrastructure as code for reproducibility
|
|
453
|
+
- Automate everything that can be automated
|
|
454
|
+
- Implement proper secrets management
|
|
455
|
+
- Use immutable deployments when possible
|
|
456
|
+
- Monitor all critical systems and set up alerts
|
|
457
|
+
- Test infrastructure changes before applying
|
|
458
|
+
- Document runbooks for common operations
|
|
459
|
+
- Implement proper backup and recovery procedures`,
|
|
460
|
+
collaborationChecklist: `- [ ] Define deployment requirements and environments
|
|
461
|
+
- [ ] Design CI/CD pipeline stages
|
|
462
|
+
- [ ] Implement infrastructure as code
|
|
463
|
+
- [ ] Set up automated testing in pipeline
|
|
464
|
+
- [ ] Configure monitoring and alerting
|
|
465
|
+
- [ ] Document deployment procedures
|
|
466
|
+
- [ ] Test rollback and recovery processes`,
|
|
467
|
+
};
|
|
468
|
+
const databaseSpecialistContent = {
|
|
469
|
+
mission: `This agent designs and optimizes database schemas and queries.
|
|
470
|
+
|
|
471
|
+
**When to engage:**
|
|
472
|
+
- Schema design decisions
|
|
473
|
+
- Query performance issues
|
|
474
|
+
- Migration planning
|
|
475
|
+
- Data integrity concerns
|
|
476
|
+
|
|
477
|
+
**Database approach:**
|
|
478
|
+
- Normalized schema design
|
|
479
|
+
- Index optimization
|
|
480
|
+
- Query performance tuning
|
|
481
|
+
- Data migration planning`,
|
|
482
|
+
responsibilities: `- Design database schemas and relationships
|
|
483
|
+
- Write and optimize complex queries
|
|
484
|
+
- Create and manage database migrations
|
|
485
|
+
- Implement proper indexing strategies
|
|
486
|
+
- Ensure data integrity and consistency
|
|
487
|
+
- Plan for database scaling
|
|
488
|
+
- Optimize query performance
|
|
489
|
+
- Set up database backups and recovery`,
|
|
490
|
+
bestPractices: `- Design schemas with normalization in mind
|
|
491
|
+
- Use appropriate data types and constraints
|
|
492
|
+
- Index based on actual query patterns
|
|
493
|
+
- Write migrations that are reversible
|
|
494
|
+
- Test migrations on production-like data
|
|
495
|
+
- Monitor query performance and slow queries
|
|
496
|
+
- Use transactions for data consistency
|
|
497
|
+
- Plan for data growth and scaling needs`,
|
|
498
|
+
collaborationChecklist: `- [ ] Understand data requirements and relationships
|
|
499
|
+
- [ ] Design normalized schema structure
|
|
500
|
+
- [ ] Plan indexing strategy based on queries
|
|
501
|
+
- [ ] Write migration scripts
|
|
502
|
+
- [ ] Test migrations with production-like data
|
|
503
|
+
- [ ] Optimize queries for performance
|
|
504
|
+
- [ ] Document schema and relationships`,
|
|
505
|
+
};
|
|
506
|
+
const mobileSpecialistContent = {
|
|
507
|
+
mission: `This agent develops mobile applications for iOS and Android platforms.
|
|
508
|
+
|
|
509
|
+
**When to engage:**
|
|
510
|
+
- Mobile app development
|
|
511
|
+
- Cross-platform decisions
|
|
512
|
+
- Mobile performance issues
|
|
513
|
+
- App store submissions
|
|
514
|
+
|
|
515
|
+
**Mobile approach:**
|
|
516
|
+
- Platform best practices
|
|
517
|
+
- Performance optimization
|
|
518
|
+
- Offline support
|
|
519
|
+
- Native integrations`,
|
|
520
|
+
responsibilities: `- Develop mobile applications (native or cross-platform)
|
|
521
|
+
- Implement responsive mobile UI/UX
|
|
522
|
+
- Handle mobile-specific concerns (offline, battery, etc.)
|
|
523
|
+
- Integrate with device features (camera, GPS, etc.)
|
|
524
|
+
- Optimize app performance and startup time
|
|
525
|
+
- Manage app store submissions and updates
|
|
526
|
+
- Implement push notifications
|
|
527
|
+
- Handle mobile security and data storage`,
|
|
528
|
+
bestPractices: `- Follow platform UI/UX guidelines
|
|
529
|
+
- Optimize for battery and network usage
|
|
530
|
+
- Implement proper offline support
|
|
531
|
+
- Use native components when appropriate
|
|
532
|
+
- Test on real devices, not just simulators
|
|
533
|
+
- Handle different screen sizes and orientations
|
|
534
|
+
- Implement proper error handling for network issues
|
|
535
|
+
- Follow app store guidelines for submissions`,
|
|
536
|
+
collaborationChecklist: `- [ ] Review mobile design specifications
|
|
537
|
+
- [ ] Plan architecture for cross-platform needs
|
|
538
|
+
- [ ] Implement core functionality
|
|
539
|
+
- [ ] Handle offline and network scenarios
|
|
540
|
+
- [ ] Test on multiple devices and OS versions
|
|
541
|
+
- [ ] Optimize performance and battery usage
|
|
542
|
+
- [ ] Prepare for app store submission`,
|
|
543
|
+
};
|
|
544
|
+
// ============================================================================
|
|
545
|
+
// Agent Structure Exports
|
|
546
|
+
// ============================================================================
|
|
547
|
+
exports.codeReviewerStructure = (0, factory_1.createAgentStructure)('code-reviewer', 'Code Reviewer', 'Reviews code changes for quality, style, and best practices', 'Focus on code quality, maintainability, security issues, and adherence to project conventions.', codeReviewerContent);
|
|
548
|
+
exports.bugFixerStructure = (0, factory_1.createAgentStructure)('bug-fixer', 'Bug Fixer', 'Analyzes bug reports and implements targeted fixes', 'Focus on root cause analysis, minimal side effects, and regression prevention.', bugFixerContent);
|
|
549
|
+
exports.featureDeveloperStructure = (0, factory_1.createAgentStructure)('feature-developer', 'Feature Developer', 'Implements new features according to specifications', 'Focus on clean architecture, integration with existing code, and comprehensive testing.', featureDeveloperContent);
|
|
550
|
+
exports.refactoringSpecialistStructure = (0, factory_1.createAgentStructure)('refactoring-specialist', 'Refactoring Specialist', 'Identifies code smells and improves code structure', 'Focus on incremental changes, test coverage, and preserving functionality.', refactoringSpecialistContent);
|
|
551
|
+
exports.testWriterStructure = (0, factory_1.createAgentStructure)('test-writer', 'Test Writer', 'Writes comprehensive tests and maintains test coverage', 'Focus on unit tests, integration tests, edge cases, and test maintainability.', testWriterContent);
|
|
552
|
+
exports.documentationWriterStructure = (0, factory_1.createAgentStructure)('documentation-writer', 'Documentation Writer', 'Creates and maintains documentation', 'Focus on clarity, practical examples, and keeping docs in sync with code.', documentationWriterContent);
|
|
553
|
+
exports.performanceOptimizerStructure = (0, factory_1.createAgentStructure)('performance-optimizer', 'Performance Optimizer', 'Identifies bottlenecks and optimizes performance', 'Focus on measurement, actual bottlenecks, and caching strategies.', performanceOptimizerContent);
|
|
554
|
+
exports.securityAuditorStructure = (0, factory_1.createAgentStructure)('security-auditor', 'Security Auditor', 'Identifies security vulnerabilities and implements best practices', 'Focus on OWASP top 10, dependency scanning, and principle of least privilege.', securityAuditorContent);
|
|
555
|
+
exports.backendSpecialistStructure = (0, factory_1.createAgentStructure)('backend-specialist', 'Backend Specialist', 'Designs and implements server-side architecture', 'Focus on APIs, microservices, database optimization, and authentication.', backendSpecialistContent);
|
|
556
|
+
exports.frontendSpecialistStructure = (0, factory_1.createAgentStructure)('frontend-specialist', 'Frontend Specialist', 'Designs and implements user interfaces', 'Focus on responsive design, accessibility, state management, and performance.', frontendSpecialistContent);
|
|
557
|
+
exports.architectSpecialistStructure = (0, factory_1.createAgentStructure)('architect-specialist', 'Architect Specialist', 'Designs overall system architecture and patterns', 'Focus on scalability, maintainability, and technical standards.', architectSpecialistContent);
|
|
558
|
+
exports.devopsSpecialistStructure = (0, factory_1.createAgentStructure)('devops-specialist', 'DevOps Specialist', 'Designs CI/CD pipelines and infrastructure', 'Focus on automation, infrastructure as code, and monitoring.', devopsSpecialistContent);
|
|
559
|
+
exports.databaseSpecialistStructure = (0, factory_1.createAgentStructure)('database-specialist', 'Database Specialist', 'Designs and optimizes database schemas', 'Focus on schema design, query optimization, and data integrity.', databaseSpecialistContent);
|
|
560
|
+
exports.mobileSpecialistStructure = (0, factory_1.createAgentStructure)('mobile-specialist', 'Mobile Specialist', 'Develops mobile applications', 'Focus on native/cross-platform development, performance, and app store requirements.', mobileSpecialistContent);
|
|
22
561
|
//# sourceMappingURL=definitions.js.map
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"definitions.js","sourceRoot":"","sources":["../../../../../src/generators/shared/structures/agents/definitions.ts"],"names":[],"mappings":";AAAA;;GAEG;;;AAEH,
|
|
1
|
+
{"version":3,"file":"definitions.js","sourceRoot":"","sources":["../../../../../src/generators/shared/structures/agents/definitions.ts"],"names":[],"mappings":";AAAA;;GAEG;;;AAEH,uCAAsE;AAEtE,+EAA+E;AAC/E,8BAA8B;AAC9B,+EAA+E;AAE/E,MAAM,mBAAmB,GAAwB;IAC/C,OAAO,EAAE;;;;;;;;;;;;;6BAakB;IAE3B,gBAAgB,EAAE;;;;;;;yDAOqC;IAEvD,aAAa,EAAE;;;;;;;qEAOoD;IAEnE,sBAAsB,EAAE;;;;;;0DAMgC;CACzD,CAAC;AAEF,MAAM,eAAe,GAAwB;IAC3C,OAAO,EAAE;;;;;;;;;;;;oBAYS;IAElB,gBAAgB,EAAE;;;;;;;8DAO0C;IAE5D,aAAa,EAAE;;;;;;;qEAOoD;IAEnE,sBAAsB,EAAE;;;;;;6CAMmB;CAC5C,CAAC;AAEF,MAAM,uBAAuB,GAAwB;IACnD,OAAO,EAAE;;;;;;;;;;;;6BAYkB;IAE3B,gBAAgB,EAAE;;;;;;;6DAOyC;IAE3D,aAAa,EAAE;;;;;;;+CAO8B;IAE7C,sBAAsB,EAAE;;;;;;mCAMS;CAClC,CAAC;AAEF,MAAM,4BAA4B,GAAwB;IACxD,OAAO,EAAE;;;;;;;;;;;;0CAY+B;IAExC,gBAAgB,EAAE;;;;;;;oDAOgC;IAElD,aAAa,EAAE;;;;;;;8CAO6B;IAE5C,sBAAsB,EAAE;;;;;;uDAM6B;CACtD,CAAC;AAEF,MAAM,iBAAiB,GAAwB;IAC7C,OAAO,EAAE;;;;;;;;;;;;2BAYgB;IAEzB,gBAAgB,EAAE;;;;;;;+CAO2B;IAE7C,aAAa,EAAE;;;;;;;sDAOqC;IAEpD,sBAAsB,EAAE;;;;;;mDAMyB;CAClD,CAAC;AAEF,MAAM,0BAA0B,GAAwB;IACtD,OAAO,EAAE;;;;;;;;;;;;gCAYqB;IAE9B,gBAAgB,EAAE;;;;;;;gDAO4B;IAE9C,aAAa,EAAE;;;;;;;4CAO2B;IAE1C,sBAAsB,EAAE;;;;;;4DAMkC;CAC3D,CAAC;AAEF,MAAM,2BAA2B,GAAwB;IACvD,OAAO,EAAE;;;;;;;;;;;;sBAYW;IAEpB,gBAAgB,EAAE;;;;;;;kDAO8B;IAEhD,aAAa,EAAE;;;;;;;sDAOqC;IAEpD,sBAAsB,EAAE;;;;;;+CAMqB;CAC9C,CAAC;AAEF,MAAM,sBAAsB,GAAwB;IAClD,OAAO,EAAE;;;;;;;;;;;;mBAYQ;IAEjB,gBAAgB,EAAE;;;;;;;8CAO0B;IAE5C,aAAa,EAAE;;;;;;;yDAOwC;IAEvD,sBAAsB,EAAE;;;;;;qDAM2B;CACpD,CAAC;AAEF,MAAM,wBAAwB,GAAwB;IACpD,OAAO,EAAE;;;;;;;;;;;;mCAYwB;IAEjC,gBAAgB,EAAE;;;;;;;oCAOgB;IAElC,aAAa,EAAE;;;;;;;wCAOuB;IAEtC,sBAAsB,EAAE;;;;;;+BAMK;CAC9B,CAAC;AAEF,MAAM,yBAAyB,GAAwB;IACrD,OAAO,EAAE;;;;;;;;;;;;2BAYgB;IAEzB,gBAAgB,EAAE;;;;;;;sCAOkB;IAEpC,aAAa,EAAE;;;;;;;oDAOmC;IAElD,sBAAsB,EAAE;;;;;;4BAME;CAC3B,CAAC;AAEF,MAAM,0BAA0B,GAAwB;IACtD,OAAO,EAAE;;;;;;;;;;;;6BAYkB;IAE3B,gBAAgB,EAAE;;;;;;;6CAOyB;IAE3C,aAAa,EAAE;;;;;;;uDAOsC;IAErD,sBAAsB,EAAE;;;;;;uCAMa;CACtC,CAAC;AAEF,MAAM,uBAAuB,GAAwB;IACnD,OAAO,EAAE;;;;;;;;;;;;+BAYoB;IAE7B,gBAAgB,EAAE;;;;;;;sCAOkB;IAEpC,aAAa,EAAE;;;;;;;kDAOiC;IAEhD,sBAAsB,EAAE;;;;;;2CAMiB;CAC1C,CAAC;AAEF,MAAM,yBAAyB,GAAwB;IACrD,OAAO,EAAE;;;;;;;;;;;;0BAYe;IAExB,gBAAgB,EAAE;;;;;;;uCAOmB;IAErC,aAAa,EAAE;;;;;;;yCAOwB;IAEvC,sBAAsB,EAAE;;;;;;wCAMc;CACvC,CAAC;AAEF,MAAM,uBAAuB,GAAwB;IACnD,OAAO,EAAE;;;;;;;;;;;;sBAYW;IAEpB,gBAAgB,EAAE;;;;;;;0CAOsB;IAExC,aAAa,EAAE;;;;;;;8CAO6B;IAE5C,sBAAsB,EAAE;;;;;;uCAMa;CACtC,CAAC;AAEF,+EAA+E;AAC/E,0BAA0B;AAC1B,+EAA+E;AAElE,QAAA,qBAAqB,GAAG,IAAA,8BAAoB,EACvD,eAAe,EACf,eAAe,EACf,6DAA6D,EAC7D,gGAAgG,EAChG,mBAAmB,CACpB,CAAC;AAEW,QAAA,iBAAiB,GAAG,IAAA,8BAAoB,EACnD,WAAW,EACX,WAAW,EACX,oDAAoD,EACpD,gFAAgF,EAChF,eAAe,CAChB,CAAC;AAEW,QAAA,yBAAyB,GAAG,IAAA,8BAAoB,EAC3D,mBAAmB,EACnB,mBAAmB,EACnB,qDAAqD,EACrD,yFAAyF,EACzF,uBAAuB,CACxB,CAAC;AAEW,QAAA,8BAA8B,GAAG,IAAA,8BAAoB,EAChE,wBAAwB,EACxB,wBAAwB,EACxB,oDAAoD,EACpD,4EAA4E,EAC5E,4BAA4B,CAC7B,CAAC;AAEW,QAAA,mBAAmB,GAAG,IAAA,8BAAoB,EACrD,aAAa,EACb,aAAa,EACb,wDAAwD,EACxD,+EAA+E,EAC/E,iBAAiB,CAClB,CAAC;AAEW,QAAA,4BAA4B,GAAG,IAAA,8BAAoB,EAC9D,sBAAsB,EACtB,sBAAsB,EACtB,qCAAqC,EACrC,2EAA2E,EAC3E,0BAA0B,CAC3B,CAAC;AAEW,QAAA,6BAA6B,GAAG,IAAA,8BAAoB,EAC/D,uBAAuB,EACvB,uBAAuB,EACvB,kDAAkD,EAClD,mEAAmE,EACnE,2BAA2B,CAC5B,CAAC;AAEW,QAAA,wBAAwB,GAAG,IAAA,8BAAoB,EAC1D,kBAAkB,EAClB,kBAAkB,EAClB,mEAAmE,EACnE,+EAA+E,EAC/E,sBAAsB,CACvB,CAAC;AAEW,QAAA,0BAA0B,GAAG,IAAA,8BAAoB,EAC5D,oBAAoB,EACpB,oBAAoB,EACpB,iDAAiD,EACjD,0EAA0E,EAC1E,wBAAwB,CACzB,CAAC;AAEW,QAAA,2BAA2B,GAAG,IAAA,8BAAoB,EAC7D,qBAAqB,EACrB,qBAAqB,EACrB,wCAAwC,EACxC,+EAA+E,EAC/E,yBAAyB,CAC1B,CAAC;AAEW,QAAA,4BAA4B,GAAG,IAAA,8BAAoB,EAC9D,sBAAsB,EACtB,sBAAsB,EACtB,kDAAkD,EAClD,iEAAiE,EACjE,0BAA0B,CAC3B,CAAC;AAEW,QAAA,yBAAyB,GAAG,IAAA,8BAAoB,EAC3D,mBAAmB,EACnB,mBAAmB,EACnB,4CAA4C,EAC5C,8DAA8D,EAC9D,uBAAuB,CACxB,CAAC;AAEW,QAAA,2BAA2B,GAAG,IAAA,8BAAoB,EAC7D,qBAAqB,EACrB,qBAAqB,EACrB,wCAAwC,EACxC,iEAAiE,EACjE,yBAAyB,CAC1B,CAAC;AAEW,QAAA,yBAAyB,GAAG,IAAA,8BAAoB,EAC3D,mBAAmB,EACnB,mBAAmB,EACnB,8BAA8B,EAC9B,sFAAsF,EACtF,uBAAuB,CACxB,CAAC"}
|
|
@@ -2,8 +2,24 @@
|
|
|
2
2
|
* Factory function for creating agent structures
|
|
3
3
|
*/
|
|
4
4
|
import { ScaffoldStructure } from '../types';
|
|
5
|
+
/**
|
|
6
|
+
* Default content overrides for specific sections
|
|
7
|
+
*/
|
|
8
|
+
export interface AgentDefaultContent {
|
|
9
|
+
mission?: string;
|
|
10
|
+
responsibilities?: string;
|
|
11
|
+
bestPractices?: string;
|
|
12
|
+
keyProjectResources?: string;
|
|
13
|
+
repositoryStartingPoints?: string;
|
|
14
|
+
keyFiles?: string;
|
|
15
|
+
architectureContext?: string;
|
|
16
|
+
keySymbols?: string;
|
|
17
|
+
documentationTouchpoints?: string;
|
|
18
|
+
collaborationChecklist?: string;
|
|
19
|
+
handoffNotes?: string;
|
|
20
|
+
}
|
|
5
21
|
/**
|
|
6
22
|
* Create an agent structure with standard sections
|
|
7
23
|
*/
|
|
8
|
-
export declare function createAgentStructure(agentType: string, title: string, description: string, additionalContext?: string): ScaffoldStructure;
|
|
24
|
+
export declare function createAgentStructure(agentType: string, title: string, description: string, additionalContext?: string, defaultContent?: AgentDefaultContent): ScaffoldStructure;
|
|
9
25
|
//# sourceMappingURL=factory.d.ts.map
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"factory.d.ts","sourceRoot":"","sources":["../../../../../src/generators/shared/structures/agents/factory.ts"],"names":[],"mappings":"AAAA;;GAEG;AAEH,OAAO,EAAE,iBAAiB,EAAE,MAAM,UAAU,CAAC;
|
|
1
|
+
{"version":3,"file":"factory.d.ts","sourceRoot":"","sources":["../../../../../src/generators/shared/structures/agents/factory.ts"],"names":[],"mappings":"AAAA;;GAEG;AAEH,OAAO,EAAE,iBAAiB,EAAmB,MAAM,UAAU,CAAC;AAE9D;;GAEG;AACH,MAAM,WAAW,mBAAmB;IAClC,OAAO,CAAC,EAAE,MAAM,CAAC;IACjB,gBAAgB,CAAC,EAAE,MAAM,CAAC;IAC1B,aAAa,CAAC,EAAE,MAAM,CAAC;IACvB,mBAAmB,CAAC,EAAE,MAAM,CAAC;IAC7B,wBAAwB,CAAC,EAAE,MAAM,CAAC;IAClC,QAAQ,CAAC,EAAE,MAAM,CAAC;IAClB,mBAAmB,CAAC,EAAE,MAAM,CAAC;IAC7B,UAAU,CAAC,EAAE,MAAM,CAAC;IACpB,wBAAwB,CAAC,EAAE,MAAM,CAAC;IAClC,sBAAsB,CAAC,EAAE,MAAM,CAAC;IAChC,YAAY,CAAC,EAAE,MAAM,CAAC;CACvB;AAmBD;;GAEG;AACH,wBAAgB,oBAAoB,CAClC,SAAS,EAAE,MAAM,EACjB,KAAK,EAAE,MAAM,EACb,WAAW,EAAE,MAAM,EACnB,iBAAiB,CAAC,EAAE,MAAM,EAC1B,cAAc,CAAC,EAAE,mBAAmB,GACnC,iBAAiB,CAiHnB"}
|