@vfarcic/dot-ai 0.118.0 → 0.124.0
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/assets/images/logo.png +0 -0
- package/assets/project-setup/discovery-config.json +671 -0
- package/assets/project-setup/templates/ADOPTERS.md.hbs +119 -0
- package/assets/project-setup/templates/CODE_OF_CONDUCT.md.hbs +132 -0
- package/assets/project-setup/templates/CONTRIBUTING.md.hbs +159 -0
- package/assets/project-setup/templates/LICENSE.hbs +933 -0
- package/assets/project-setup/templates/NOTICE.hbs +5 -0
- package/assets/project-setup/templates/README.md.hbs +11 -0
- package/assets/project-setup/templates/SECURITY.md.hbs +44 -0
- package/assets/project-setup/templates/SUPPORT.md.hbs +146 -0
- package/assets/project-setup/templates/docs/GOVERNANCE.md.hbs +127 -0
- package/assets/project-setup/templates/docs/MAINTAINERS.md.hbs +49 -0
- package/assets/project-setup/templates/docs/ROADMAP.md.hbs +63 -0
- package/assets/project-setup/templates/renovate.json.hbs +38 -0
- package/dist/tools/project-setup/discovery.js +3 -3
- package/dist/tools/project-setup/generate-scope.js +2 -2
- package/package.json +2 -1
- package/shared-prompts/prd-done.md +226 -4
|
@@ -0,0 +1,44 @@
|
|
|
1
|
+
# Security Policy
|
|
2
|
+
|
|
3
|
+
## Reporting Security Vulnerabilities
|
|
4
|
+
|
|
5
|
+
**Please do not report security vulnerabilities through public GitHub issues.**
|
|
6
|
+
|
|
7
|
+
If you discover a security vulnerability, please report it by emailing [{{securityEmail}}](mailto:{{securityEmail}}).
|
|
8
|
+
|
|
9
|
+
Please include the following information in your report:
|
|
10
|
+
|
|
11
|
+
- Description of the vulnerability
|
|
12
|
+
- Steps to reproduce the issue
|
|
13
|
+
- Affected versions
|
|
14
|
+
- Potential impact
|
|
15
|
+
- Any suggested fixes (if available)
|
|
16
|
+
|
|
17
|
+
## Response Timeline
|
|
18
|
+
|
|
19
|
+
We will acknowledge your report within **3 business days** and provide a detailed response within **7 business days** indicating the next steps in handling your report.
|
|
20
|
+
|
|
21
|
+
We will keep you informed of the progress towards a fix and may ask for additional information or guidance.
|
|
22
|
+
|
|
23
|
+
## Security Updates
|
|
24
|
+
|
|
25
|
+
Security updates will be released as soon as possible after a fix is available. We recommend keeping your installation up to date with the latest releases.
|
|
26
|
+
|
|
27
|
+
{{#if supportedVersions}}
|
|
28
|
+
## Supported Versions
|
|
29
|
+
|
|
30
|
+
{{supportedVersions}}
|
|
31
|
+
{{/if}}
|
|
32
|
+
|
|
33
|
+
## Security Best Practices
|
|
34
|
+
|
|
35
|
+
When using {{projectName}}, we recommend:
|
|
36
|
+
|
|
37
|
+
- Keep the software updated to the latest version
|
|
38
|
+
- Follow the principle of least privilege
|
|
39
|
+
- Review and audit your configurations regularly
|
|
40
|
+
{{#if additionalSecurityGuidance}}
|
|
41
|
+
- {{additionalSecurityGuidance}}
|
|
42
|
+
{{/if}}
|
|
43
|
+
|
|
44
|
+
Thank you for helping to keep {{projectName}} and our users safe!
|
|
@@ -0,0 +1,146 @@
|
|
|
1
|
+
# Support
|
|
2
|
+
|
|
3
|
+
Welcome to {{projectName}}! We're here to help you get the most out of the project.
|
|
4
|
+
|
|
5
|
+
## Getting Help
|
|
6
|
+
|
|
7
|
+
There are several ways to get help with {{projectName}}, listed in order of recommendation:
|
|
8
|
+
|
|
9
|
+
### 1. Documentation
|
|
10
|
+
|
|
11
|
+
Start with our [documentation]({{docsUrl}}) which includes:
|
|
12
|
+
- Getting started guides
|
|
13
|
+
- API references
|
|
14
|
+
- Troubleshooting guides
|
|
15
|
+
- Best practices
|
|
16
|
+
|
|
17
|
+
Most common questions are answered in the docs.
|
|
18
|
+
|
|
19
|
+
### 2. GitHub Discussions
|
|
20
|
+
|
|
21
|
+
For questions, ideas, and community discussions, use [GitHub Discussions]({{discussionsUrl}}).
|
|
22
|
+
|
|
23
|
+
**Best for:**
|
|
24
|
+
- How-to questions
|
|
25
|
+
- Feature discussions
|
|
26
|
+
- Sharing use cases
|
|
27
|
+
- Community Q&A
|
|
28
|
+
|
|
29
|
+
{{#if stackOverflowTag}}
|
|
30
|
+
### Stack Overflow
|
|
31
|
+
|
|
32
|
+
Ask questions on [Stack Overflow](https://stackoverflow.com/questions/tagged/{{stackOverflowTag}}) using the `{{stackOverflowTag}}` tag.
|
|
33
|
+
|
|
34
|
+
**Best for:**
|
|
35
|
+
- Technical questions
|
|
36
|
+
- Implementation guidance
|
|
37
|
+
- Troubleshooting specific scenarios
|
|
38
|
+
|
|
39
|
+
{{/if}}
|
|
40
|
+
{{#if slackUrl}}
|
|
41
|
+
### Slack
|
|
42
|
+
|
|
43
|
+
Join our Slack workspace at [{{slackUrl}}]({{slackUrl}}) for real-time chat with maintainers and community members.
|
|
44
|
+
|
|
45
|
+
**Best for:**
|
|
46
|
+
- Quick questions
|
|
47
|
+
- Real-time collaboration
|
|
48
|
+
- Community networking
|
|
49
|
+
|
|
50
|
+
{{/if}}
|
|
51
|
+
{{#if discordUrl}}
|
|
52
|
+
### Discord
|
|
53
|
+
|
|
54
|
+
Join our Discord server at [{{discordUrl}}]({{discordUrl}}) for real-time discussions.
|
|
55
|
+
|
|
56
|
+
**Best for:**
|
|
57
|
+
- Quick questions
|
|
58
|
+
- Real-time support
|
|
59
|
+
- Community chat
|
|
60
|
+
|
|
61
|
+
{{/if}}
|
|
62
|
+
{{#if forumUrl}}
|
|
63
|
+
### Forum
|
|
64
|
+
|
|
65
|
+
Visit our [community forum]({{forumUrl}}) for threaded discussions and long-form conversations.
|
|
66
|
+
|
|
67
|
+
{{/if}}
|
|
68
|
+
|
|
69
|
+
## Reporting Bugs
|
|
70
|
+
|
|
71
|
+
**Please use GitHub Issues ONLY for bug reports and feature requests.**
|
|
72
|
+
|
|
73
|
+
Before creating a new issue:
|
|
74
|
+
1. Check existing issues to avoid duplicates
|
|
75
|
+
2. Review the [troubleshooting guide]({{docsUrl}}/troubleshooting)
|
|
76
|
+
3. Gather relevant information (logs, versions, reproduction steps)
|
|
77
|
+
|
|
78
|
+
[Report a bug]({{projectUrl}}/issues/new?template=bug_report.md)
|
|
79
|
+
|
|
80
|
+
## What NOT to Report as Issues
|
|
81
|
+
|
|
82
|
+
Please **do not** use GitHub Issues for:
|
|
83
|
+
- ❌ General questions (use Discussions{{#if stackOverflowTag}} or Stack Overflow{{/if}})
|
|
84
|
+
- ❌ Support requests (use Discussions{{#if slackUrl}} or Slack{{/if}})
|
|
85
|
+
- ❌ How-to questions (check documentation first)
|
|
86
|
+
{{#if slackUrl}}
|
|
87
|
+
- ❌ Real-time help (use Slack{{#if discordUrl}} or Discord{{/if}})
|
|
88
|
+
{{/if}}
|
|
89
|
+
|
|
90
|
+
Issues that don't follow this guideline may be closed and redirected to the appropriate channel.
|
|
91
|
+
|
|
92
|
+
## Response Time Expectations
|
|
93
|
+
|
|
94
|
+
{{#if maintainerCount}}
|
|
95
|
+
This project is maintained by {{maintainerCount}} maintainer(s).
|
|
96
|
+
{{/if}}
|
|
97
|
+
|
|
98
|
+
**Response times vary based on:**
|
|
99
|
+
- Severity and impact of the issue
|
|
100
|
+
- Maintainer availability
|
|
101
|
+
- Community engagement
|
|
102
|
+
|
|
103
|
+
**Typical response times:**
|
|
104
|
+
- Critical bugs: {{criticalResponseTime}}
|
|
105
|
+
- Feature requests: {{featureResponseTime}}
|
|
106
|
+
- Questions: {{questionResponseTime}}
|
|
107
|
+
|
|
108
|
+
Please be patient and respectful. This is an open-source project, and responses depend on volunteer time.
|
|
109
|
+
|
|
110
|
+
{{#if commercialSupportAvailable}}
|
|
111
|
+
## Commercial Support
|
|
112
|
+
|
|
113
|
+
Professional support is available through {{commercialSupportProvider}}.
|
|
114
|
+
|
|
115
|
+
For enterprise support inquiries, contact: {{commercialSupportEmail}}
|
|
116
|
+
|
|
117
|
+
Commercial support includes:
|
|
118
|
+
- Dedicated support team
|
|
119
|
+
- SLA guarantees
|
|
120
|
+
- Custom feature development
|
|
121
|
+
- Priority bug fixes
|
|
122
|
+
- Training and consulting
|
|
123
|
+
|
|
124
|
+
{{/if}}
|
|
125
|
+
## Security Vulnerabilities
|
|
126
|
+
|
|
127
|
+
**Do not report security vulnerabilities through public GitHub issues.**
|
|
128
|
+
|
|
129
|
+
Please follow our [Security Policy]({{projectUrl}}/security/policy) for responsible disclosure.
|
|
130
|
+
|
|
131
|
+
Report vulnerabilities to: {{securityEmail}}
|
|
132
|
+
|
|
133
|
+
## Contributing
|
|
134
|
+
|
|
135
|
+
If you'd like to contribute to {{projectName}}, please read our [Contributing Guide]({{projectUrl}}/blob/main/CONTRIBUTING.md).
|
|
136
|
+
|
|
137
|
+
We welcome:
|
|
138
|
+
- Bug fixes
|
|
139
|
+
- Feature implementations
|
|
140
|
+
- Documentation improvements
|
|
141
|
+
- Test coverage
|
|
142
|
+
- Community support
|
|
143
|
+
|
|
144
|
+
---
|
|
145
|
+
|
|
146
|
+
**Thank you for using {{projectName}}!** We appreciate your patience and engagement with the community.
|
|
@@ -0,0 +1,127 @@
|
|
|
1
|
+
# Project Governance
|
|
2
|
+
|
|
3
|
+
This document describes the governance model for {{projectName}}.
|
|
4
|
+
|
|
5
|
+
## Overview
|
|
6
|
+
|
|
7
|
+
{{projectName}} is committed to transparent and inclusive decision-making. This document outlines how decisions are made and who has authority over different aspects of the project.
|
|
8
|
+
|
|
9
|
+
## Roles
|
|
10
|
+
|
|
11
|
+
### Contributors
|
|
12
|
+
|
|
13
|
+
Anyone who contributes to the project through code, documentation, issues, or discussions.
|
|
14
|
+
|
|
15
|
+
### Maintainers
|
|
16
|
+
|
|
17
|
+
Maintainers have write access to the repository and are responsible for:
|
|
18
|
+
|
|
19
|
+
- Reviewing and merging pull requests
|
|
20
|
+
- Triaging issues
|
|
21
|
+
- Making technical decisions
|
|
22
|
+
- Ensuring code quality
|
|
23
|
+
- Releasing new versions
|
|
24
|
+
|
|
25
|
+
See [MAINTAINERS.md](MAINTAINERS.md) for the current list of maintainers.
|
|
26
|
+
|
|
27
|
+
{{#if hasCommitters}}
|
|
28
|
+
### Committers
|
|
29
|
+
|
|
30
|
+
Committers have demonstrated expertise and commitment to the project. They can approve pull requests and participate in technical decisions.
|
|
31
|
+
|
|
32
|
+
{{/if}}
|
|
33
|
+
{{#if hasSteeringCommittee}}
|
|
34
|
+
### Steering Committee
|
|
35
|
+
|
|
36
|
+
The Steering Committee provides strategic direction and makes decisions on project scope, governance changes, and maintainer appointments.
|
|
37
|
+
|
|
38
|
+
{{/if}}
|
|
39
|
+
|
|
40
|
+
## Decision-Making Process
|
|
41
|
+
|
|
42
|
+
### Routine Decisions
|
|
43
|
+
|
|
44
|
+
Day-to-day technical decisions are made by maintainers through:
|
|
45
|
+
|
|
46
|
+
- Pull request reviews
|
|
47
|
+
- Issue discussions
|
|
48
|
+
- Direct commits for minor changes
|
|
49
|
+
|
|
50
|
+
{{#if requiresConsensus}}
|
|
51
|
+
### Major Decisions
|
|
52
|
+
|
|
53
|
+
Significant changes require consensus among maintainers:
|
|
54
|
+
|
|
55
|
+
- Architecture changes
|
|
56
|
+
- Breaking changes
|
|
57
|
+
- New feature additions
|
|
58
|
+
- Governance changes
|
|
59
|
+
|
|
60
|
+
**Consensus Process:**
|
|
61
|
+
|
|
62
|
+
1. Proposal is documented in an issue or discussion
|
|
63
|
+
2. Maintainers discuss and provide feedback
|
|
64
|
+
3. If no objections within 7 days, consensus is reached
|
|
65
|
+
4. If objections exist, continue discussion or call for a vote
|
|
66
|
+
|
|
67
|
+
{{/if}}
|
|
68
|
+
{{#if hasVoting}}
|
|
69
|
+
### Voting
|
|
70
|
+
|
|
71
|
+
When consensus cannot be reached, decisions are made by vote:
|
|
72
|
+
|
|
73
|
+
- Each maintainer has one vote
|
|
74
|
+
- Decisions require {{votingThreshold}} of maintainers to pass
|
|
75
|
+
- Votes are recorded in the relevant issue or pull request
|
|
76
|
+
|
|
77
|
+
{{/if}}
|
|
78
|
+
|
|
79
|
+
## Becoming a Maintainer
|
|
80
|
+
|
|
81
|
+
Contributors can become maintainers by:
|
|
82
|
+
|
|
83
|
+
1. **Sustained Contributions** - Regular, high-quality contributions over {{maintainerPeriod}}
|
|
84
|
+
2. **Technical Expertise** - Demonstrated understanding of the codebase
|
|
85
|
+
3. **Community Engagement** - Helpful reviews and issue triage
|
|
86
|
+
4. **Nomination** - Existing maintainer nominates the contributor
|
|
87
|
+
5. **Approval** - {{#if hasVoting}}Majority vote{{else}}Consensus{{/if}} from current maintainers
|
|
88
|
+
|
|
89
|
+
## Removing Maintainers
|
|
90
|
+
|
|
91
|
+
Maintainers may step down voluntarily or be removed if:
|
|
92
|
+
|
|
93
|
+
- Inactive for more than {{inactivityPeriod}}
|
|
94
|
+
- Violation of Code of Conduct
|
|
95
|
+
- Consistent disregard for project processes
|
|
96
|
+
|
|
97
|
+
{{#if hasVoting}}
|
|
98
|
+
Removal requires {{votingThreshold}} of remaining maintainers.
|
|
99
|
+
{{else}}
|
|
100
|
+
Removal requires consensus of remaining maintainers.
|
|
101
|
+
{{/if}}
|
|
102
|
+
|
|
103
|
+
## Changes to Governance
|
|
104
|
+
|
|
105
|
+
Changes to this governance document require:
|
|
106
|
+
|
|
107
|
+
{{#if hasVoting}}
|
|
108
|
+
- Proposal in a GitHub issue
|
|
109
|
+
- Discussion period of at least 14 days
|
|
110
|
+
- {{votingThreshold}} approval from maintainers
|
|
111
|
+
{{else}}
|
|
112
|
+
- Proposal in a GitHub issue
|
|
113
|
+
- Discussion period of at least 14 days
|
|
114
|
+
- Consensus from all active maintainers
|
|
115
|
+
{{/if}}
|
|
116
|
+
|
|
117
|
+
## Questions or Concerns
|
|
118
|
+
|
|
119
|
+
If you have questions about governance, please:
|
|
120
|
+
|
|
121
|
+
1. Open a GitHub Discussion
|
|
122
|
+
2. Contact the maintainers at {{maintainerEmail}}
|
|
123
|
+
3. Attend a community meeting (if applicable)
|
|
124
|
+
|
|
125
|
+
---
|
|
126
|
+
|
|
127
|
+
*This governance model may evolve as the project grows. All changes will be documented in this file's history.*
|
|
@@ -0,0 +1,49 @@
|
|
|
1
|
+
# Maintainers
|
|
2
|
+
|
|
3
|
+
This document lists the maintainers of {{projectName}}.
|
|
4
|
+
|
|
5
|
+
## Current Maintainers
|
|
6
|
+
|
|
7
|
+
{{#if maintainersList}}
|
|
8
|
+
{{maintainersList}}
|
|
9
|
+
{{else}}
|
|
10
|
+
| Name | Email | GitHub | Role |
|
|
11
|
+
|------|-------|--------|------|
|
|
12
|
+
| {{maintainerName}} | {{maintainerEmail}} | @{{maintainerGithub}} | Lead Maintainer |
|
|
13
|
+
{{/if}}
|
|
14
|
+
|
|
15
|
+
## Responsibilities
|
|
16
|
+
|
|
17
|
+
Maintainers are responsible for:
|
|
18
|
+
|
|
19
|
+
- Reviewing and merging pull requests
|
|
20
|
+
- Triaging and responding to issues
|
|
21
|
+
- Making technical decisions about the project
|
|
22
|
+
- Ensuring code quality and project standards
|
|
23
|
+
- Releasing new versions
|
|
24
|
+
- Mentoring contributors
|
|
25
|
+
|
|
26
|
+
## Becoming a Maintainer
|
|
27
|
+
|
|
28
|
+
Maintainers are typically promoted from active contributors who have:
|
|
29
|
+
|
|
30
|
+
- Demonstrated expertise in the project
|
|
31
|
+
- Contributed high-quality code and reviews
|
|
32
|
+
- Shown commitment to the project's success
|
|
33
|
+
- Earned the trust of existing maintainers
|
|
34
|
+
|
|
35
|
+
If you're interested in becoming a maintainer, start by contributing regularly and engaging with the community.
|
|
36
|
+
|
|
37
|
+
## Emeritus Maintainers
|
|
38
|
+
|
|
39
|
+
{{#if emeritusMaintainers}}
|
|
40
|
+
We thank the following people for their past contributions as maintainers:
|
|
41
|
+
|
|
42
|
+
{{emeritusMaintainers}}
|
|
43
|
+
{{else}}
|
|
44
|
+
_No emeritus maintainers at this time._
|
|
45
|
+
{{/if}}
|
|
46
|
+
|
|
47
|
+
---
|
|
48
|
+
|
|
49
|
+
*Note: This list may be incomplete. Maintainers can direct questions to the appropriate person.*
|
|
@@ -0,0 +1,63 @@
|
|
|
1
|
+
# Roadmap
|
|
2
|
+
|
|
3
|
+
This document outlines the planned direction and priorities for {{projectName}}.
|
|
4
|
+
|
|
5
|
+
{{#if roadmapIntro}}
|
|
6
|
+
{{roadmapIntro}}
|
|
7
|
+
{{else}}
|
|
8
|
+
This roadmap is a living document and may change based on community feedback and project priorities.
|
|
9
|
+
{{/if}}
|
|
10
|
+
|
|
11
|
+
{{#if githubProjectUrl}}
|
|
12
|
+
**Live Progress**: Track detailed progress on our [GitHub Project Board]({{githubProjectUrl}})
|
|
13
|
+
{{/if}}
|
|
14
|
+
|
|
15
|
+
## Short-term (Next 1-3 Months)
|
|
16
|
+
|
|
17
|
+
{{#if shortTermGoals}}
|
|
18
|
+
{{shortTermGoals}}
|
|
19
|
+
{{else}}
|
|
20
|
+
- Core functionality implementation
|
|
21
|
+
- Documentation and examples
|
|
22
|
+
- Initial testing and bug fixes
|
|
23
|
+
- First stable release
|
|
24
|
+
{{/if}}
|
|
25
|
+
|
|
26
|
+
## Medium-term (3-6 Months)
|
|
27
|
+
|
|
28
|
+
{{#if mediumTermGoals}}
|
|
29
|
+
{{mediumTermGoals}}
|
|
30
|
+
{{else}}
|
|
31
|
+
- Additional features based on user feedback
|
|
32
|
+
- Performance improvements
|
|
33
|
+
- Expanded documentation
|
|
34
|
+
- Community building
|
|
35
|
+
{{/if}}
|
|
36
|
+
|
|
37
|
+
## Long-term (6-12 Months)
|
|
38
|
+
|
|
39
|
+
{{#if longTermGoals}}
|
|
40
|
+
{{longTermGoals}}
|
|
41
|
+
{{else}}
|
|
42
|
+
- Advanced features and integrations
|
|
43
|
+
- Ecosystem development
|
|
44
|
+
- Stability and maturity improvements
|
|
45
|
+
{{/if}}
|
|
46
|
+
|
|
47
|
+
{{#if futureConsiderations}}
|
|
48
|
+
## Future Considerations
|
|
49
|
+
|
|
50
|
+
{{futureConsiderations}}
|
|
51
|
+
{{/if}}
|
|
52
|
+
|
|
53
|
+
## How to Contribute
|
|
54
|
+
|
|
55
|
+
We welcome contributions toward any roadmap items:
|
|
56
|
+
|
|
57
|
+
1. Check the [issue tracker]({{repositoryUrl}}/issues) for related work
|
|
58
|
+
2. Comment on issues or open discussions
|
|
59
|
+
3. See [CONTRIBUTING.md](../CONTRIBUTING.md) for guidelines
|
|
60
|
+
|
|
61
|
+
---
|
|
62
|
+
|
|
63
|
+
*This roadmap reflects current plans but is subject to change.*
|
|
@@ -0,0 +1,38 @@
|
|
|
1
|
+
{
|
|
2
|
+
"$schema": "https://docs.renovatebot.com/renovate-schema.json",
|
|
3
|
+
"extends": [
|
|
4
|
+
"config:recommended"
|
|
5
|
+
],
|
|
6
|
+
"labels": ["dependencies"],
|
|
7
|
+
"prConcurrentLimit": {{prConcurrentLimit}},
|
|
8
|
+
"prHourlyLimit": {{prHourlyLimit}},
|
|
9
|
+
"dependencyDashboard": {{enableDependencyDashboard}},
|
|
10
|
+
{{#isTrue enableDependencyDashboard}}
|
|
11
|
+
"dependencyDashboardTitle": "Dependency Dashboard",
|
|
12
|
+
{{/isTrue}}
|
|
13
|
+
"osvVulnerabilityAlerts": {{enableVulnerabilityAlerts}},
|
|
14
|
+
"schedule": [
|
|
15
|
+
"{{schedule}}"
|
|
16
|
+
],
|
|
17
|
+
"packageRules": [
|
|
18
|
+
{{#isTrue groupDependencies}}
|
|
19
|
+
{
|
|
20
|
+
"description": "Group all non-major dependencies together",
|
|
21
|
+
"matchUpdateTypes": ["minor", "patch", "pin", "digest"],
|
|
22
|
+
"groupName": "all non-major dependencies",
|
|
23
|
+
"groupSlug": "all-minor-patch"
|
|
24
|
+
},
|
|
25
|
+
{{/isTrue}}
|
|
26
|
+
{
|
|
27
|
+
"description": "Automerge non-major updates",
|
|
28
|
+
"matchUpdateTypes": ["minor", "patch", "pin", "digest"],
|
|
29
|
+
"automerge": {{automergeMinor}}
|
|
30
|
+
},
|
|
31
|
+
{
|
|
32
|
+
"description": "Security updates",
|
|
33
|
+
"matchUpdateTypes": ["security"],
|
|
34
|
+
"labels": ["security"],
|
|
35
|
+
"automerge": {{automergeSecurity}}
|
|
36
|
+
}
|
|
37
|
+
]
|
|
38
|
+
}
|
|
@@ -52,9 +52,9 @@ const generic_session_manager_1 = require("../../core/generic-session-manager");
|
|
|
52
52
|
async function handleDiscovery(logger, requestId) {
|
|
53
53
|
return await error_handling_1.ErrorHandler.withErrorHandling(async () => {
|
|
54
54
|
logger.debug('Starting project setup discovery', { requestId });
|
|
55
|
-
// Load discovery config from
|
|
56
|
-
// From dist/tools/project-setup/ -> ../../../ gets to project root, then
|
|
57
|
-
const configPath = path.join(__dirname, '..', '..', '..', '
|
|
55
|
+
// Load discovery config from assets directory
|
|
56
|
+
// From dist/tools/project-setup/ -> ../../../ gets to project root, then assets/project-setup/
|
|
57
|
+
const configPath = path.join(__dirname, '..', '..', '..', 'assets', 'project-setup', 'discovery-config.json');
|
|
58
58
|
const configContent = fs.readFileSync(configPath, 'utf8');
|
|
59
59
|
const allConfig = JSON.parse(configContent);
|
|
60
60
|
// Collect all files from all scopes
|
|
@@ -155,13 +155,13 @@ function generateFileContent(fileName, answers, logger) {
|
|
|
155
155
|
try {
|
|
156
156
|
// Load template using shared prompt loader with Handlebars support
|
|
157
157
|
// Templates use .hbs extension (e.g., README.md -> README.md.hbs)
|
|
158
|
-
const content = (0, shared_prompt_loader_1.loadPrompt)(fileName, answers, '
|
|
158
|
+
const content = (0, shared_prompt_loader_1.loadPrompt)(fileName, answers, 'assets/project-setup/templates', '.hbs' // Add .hbs extension to template files
|
|
159
159
|
);
|
|
160
160
|
return content;
|
|
161
161
|
}
|
|
162
162
|
catch (error) {
|
|
163
163
|
logger.error('Failed to generate file content', error, { fileName });
|
|
164
|
-
return `# ${fileName}\n\nError: Could not generate content for this file.\nTemplate may be missing at:
|
|
164
|
+
return `# ${fileName}\n\nError: Could not generate content for this file.\nTemplate may be missing at: assets/project-setup/templates/${fileName}.hbs\n`;
|
|
165
165
|
}
|
|
166
166
|
}
|
|
167
167
|
/**
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@vfarcic/dot-ai",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.124.0",
|
|
4
4
|
"description": "AI-powered development productivity platform that enhances software development workflows through intelligent automation and AI-driven assistance",
|
|
5
5
|
"mcpName": "io.github.vfarcic/dot-ai",
|
|
6
6
|
"main": "dist/index.js",
|
|
@@ -76,6 +76,7 @@
|
|
|
76
76
|
"dist",
|
|
77
77
|
"prompts",
|
|
78
78
|
"shared-prompts",
|
|
79
|
+
"assets",
|
|
79
80
|
"scripts",
|
|
80
81
|
"README.md",
|
|
81
82
|
"LICENSE"
|