Skip to content

Commit 7da2d78

Browse files
Merge branch 'Gerome-Elassaad:main' into main
2 parents 59ce882 + bf549bc commit 7da2d78

File tree

489 files changed

+802
-86485
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

489 files changed

+802
-86485
lines changed

FAQ.md

Lines changed: 105 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,105 @@
1+
# Frequently Asked Questions (FAQ)
2+
3+
<details>
4+
<summary><strong>What are the best models for codinit.dev?</strong></summary>
5+
6+
For the best experience with codinit.dev, we recommend using the following models:
7+
8+
- **Claude 3.5 Sonnet (old)**: Best overall coder, providing excellent results across all use cases
9+
- **Gemini 2.0 Flash**: Exceptional speed while maintaining good performance
10+
- **GPT-4o**: Strong alternative to Claude 3.5 Sonnet with comparable capabilities
11+
- **DeepSeekCoder V2 236b**: Best open source model (available through OpenRouter, DeepSeek API, or self-hosted)
12+
- **Qwen 2.5 Coder 32b**: Best model for self-hosting with reasonable hardware requirements
13+
14+
**Note**: Models with less than 7b parameters typically lack the capability to properly interact with codinit!
15+
16+
</details>
17+
18+
<details>
19+
<summary><strong>How do I get the best results with codinit.dev?</strong></summary>
20+
21+
- **Be specific about your stack**:
22+
Mention the frameworks or libraries you want to use (e.g., Astro, Tailwind, ShadCN) in your initial prompt. This ensures that codinit.dev scaffolds the project according to your preferences.
23+
24+
- **Use the enhance prompt icon**:
25+
Before sending your prompt, click the _enhance_ icon to let the AI refine your prompt. You can edit the suggested improvements before submitting.
26+
27+
- **Scaffold the basics first, then add features**:
28+
Ensure the foundational structure of your application is in place before introducing advanced functionality. This helps codinit.dev establish a solid base to build on.
29+
30+
- **Batch simple instructions**:
31+
Combine simple tasks into a single prompt to save time and reduce API credit consumption. For example:
32+
_"Change the color scheme, add mobile responsiveness, and restart the dev server."_
33+
</details>
34+
35+
<details>
36+
<summary><strong>How do I contribute to codinit.dev?</strong></summary>
37+
38+
Check out our [Contribution Guide](CONTRIBUTING.md) for more details on how to get involved!
39+
40+
</details>
41+
42+
<details>
43+
<summary><strong>What are the future plans for codinit.dev?</strong></summary>
44+
45+
Visit our [Roadmap](https://roadmap.sh/r/ottodev-roadmap-2ovzo) for the latest updates.
46+
New features and improvements are on the way!
47+
48+
</details>
49+
50+
<details>
51+
<summary><strong>Why are there so many open issues/pull requests?</strong></summary>
52+
53+
codinit.dev began as a small showcase project on @ColeMedin's YouTube channel to explore editing open-source projects with local LLMs. However, it quickly grew into a massive community effort!
54+
55+
We're forming a team of maintainers to manage demand and streamline issue resolution. The maintainers are rockstars, and we're also exploring partnerships to help the project thrive.
56+
57+
</details>
58+
59+
<details>
60+
<summary><strong>How do local LLMs compare to larger models like Claude 3.5 Sonnet for codinit.dev?</strong></summary>
61+
62+
While local LLMs are improving rapidly, larger models like GPT-4o, Claude 3.5 Sonnet, and DeepSeek Coder V2 236b still offer the best results for complex applications. Our ongoing focus is to improve prompts, agents, and the platform to better support smaller local LLMs.
63+
64+
</details>
65+
66+
<details>
67+
<summary><strong>Common Errors and Troubleshooting</strong></summary>
68+
69+
### **"There was an error processing this request"**
70+
71+
This generic error message means something went wrong. Check both:
72+
73+
- The terminal (if you started the app with Docker or `pnpm`).
74+
- The developer console in your browser (press `F12` or right-click > _Inspect_, then go to the _Console_ tab).
75+
76+
### **"x-api-key header missing"**
77+
78+
This error is sometimes resolved by restarting the Docker container.
79+
If that doesn't work, try switching from Docker to `pnpm` or vice versa. We're actively investigating this issue.
80+
81+
### **Blank preview when running the app**
82+
83+
A blank preview often occurs due to hallucinated bad code or incorrect commands.
84+
To troubleshoot:
85+
86+
- Check the developer console for errors.
87+
- Remember, previews are core functionality, so the app isn't broken! We're working on making these errors more transparent.
88+
89+
### **"Everything works, but the results are bad"**
90+
91+
Local LLMs like Qwen-2.5-Coder are powerful for small applications but still experimental for larger projects. For better results, consider using larger models like GPT-4o, Claude 3.5 Sonnet, or DeepSeek Coder V2 236b.
92+
93+
### **"Received structured exception #0xc0000005: access violation"**
94+
95+
If you are getting this, you are probably on Windows. The fix is generally to update the [Visual C++ Redistributable](https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170)
96+
97+
### **"Miniflare or Wrangler errors in Windows"**
98+
99+
You will need to make sure you have the latest version of Visual Studio C++ installed (14.40.33816), more information here https://github.com/Gerome-Elassaad/CodingIT/issues/19.
100+
101+
</details>
102+
103+
---
104+
105+
Got more questions? Feel free to reach out or open an issue in our GitHub repo!

0 commit comments

Comments
 (0)