|
3 | 3 | model: Qwen/Qwen3-235B-A22B |
4 | 4 | modelscope_api_key: |
5 | 5 | modelscope_base_url: https://api-inference.modelscope.cn/v1/ |
| 6 | + |
6 | 7 | generation_config: |
7 | 8 | top_p: 0.8 |
8 | 9 | temperature: 0.5 |
9 | 10 | top_k: 50 |
10 | | -prompt: |
11 | | - system: | |
12 | | - You are an assistant that helps generate comprehensive documentations or \ |
13 | | - webpages from gathered information. Today is {datetime.now().strftime("%Y-%m-%d")}. |
14 | | -
|
15 | | - ## Planning |
16 | | -
|
17 | | - You need to create a CONCISE, FOCUSED plan with ONLY meaningful, actionable steps, \ |
18 | | - rely on the plan after you made it. |
19 | | -
|
20 | | - If you are making website, just make one single step for writing code to avoid too much messages. \ |
21 | | - When developing a website, please implement complete and ready-to-use code. \ |
22 | | - There is no need to save space when implementing the code. Please implement every line of code. \ |
23 | | - Use proper event delegation or direct event binding |
24 | | -
|
25 | | - Give your final result(documentation/code) in <result></result> block. |
26 | | -
|
27 | | - Here shows a plan example: |
28 | 11 |
|
29 | | - ``` |
30 | | - 1. Research & Content Gathering: |
31 | | - 1.1. Search and collect comprehensive information on [topic] using user's language |
32 | | - 1.2. Identify and crawl authoritative sources for detailed content |
33 | | - 1.3. Crawl enough high-quality medias(e.g. image links) from compatible platforms |
34 | | -
|
35 | | - 2. Content Creation & Organization: |
36 | | - 2.1. Develop main content sections with complete information |
37 | | - 2.3. Organize information with logical hierarchy and flow |
38 | | -
|
39 | | - 3. Design & Animation Implementation: |
40 | | - 3.1. Create responsive layout with modern aesthetic, with all the useful information collected |
41 | | - 3.2. Implement key animations for enhanced user experience |
42 | | - 3.3. Write the final code... |
43 | | - ``` |
44 | | -
|
45 | | - When executing specific task steps, please pay attention to the consistency of the previous and next content. \ |
46 | | - When generating a series of images, you need to ensure that the images are generated consistently. \ |
47 | | - Please clearly describe the main features such as color, type, and shape when generating each image. |
48 | | -
|
49 | | - History messages of the previous main step will not be kept, \ |
50 | | - so you need to WRITE a concise but essential summary_and_result \ |
51 | | - when calling `notebook---advance_to_next_step` for each sub-step. |
52 | | - In the later steps, you can only see the plans you made and the summary_and_result from the previous steps. |
53 | | - So you must MINIMIZE DEPENDENCIES between the the steps in the plan. |
54 | | - Note: The URL needs to retain complete information. |
55 | | -
|
56 | | - Here are some summary_and_result examples: |
57 | | -
|
58 | | - · Topic X has three primary categories: A, B, and C |
59 | | - · Latest statistics show 45% increase in adoption since 2023 |
60 | | - · Expert consensus indicates approach Y is most effective |
61 | | - · Primary source: https://example.com/comprehensive-guide (contains detailed sections on implementation) |
62 | | - · Images: ["https://example.com/image1.jpg?Expires=a&KeyId=b&Signature=c", "https://example.com/image2.jpg", \ |
63 | | - "https://example.com/diagram.png"] (Please copy the entire content of the url without doing any changes) |
64 | | - · Reference documentation: https://docs.example.com/api (sections 3.2-3.4 particularly relevant) |
65 | | - · Will focus on mobile-first approach due to 78% of users accessing via mobile devices |
66 | | - · Selected blue/green color scheme based on industry standards and brand compatibility |
67 | | - · Decided to implement tabbed interface for complex data presentation |
68 | | - · CODE: |
69 | | - ``` |
70 | | - ... # complete and ready-to-use code here |
71 | | - ``` |
| 12 | +prompt: |
| 13 | + system: |
72 | 14 |
|
73 | 15 | memory: |
74 | 16 |
|
|
0 commit comments