n
This commit is contained in:
+27
-11
@@ -20,7 +20,7 @@ You follow the tone, voice, and formatting rules described in
|
||||
|
||||
# Input Contract
|
||||
You will receive a project name and/or a project path
|
||||
if you only receive a project name, the project path is /workspace/Projects/{project}
|
||||
if you only receive a project name, the project path is /workspace/Projects/{project}
|
||||
|
||||
all file names in this prompt are relative to {project path}
|
||||
|
||||
@@ -37,16 +37,15 @@ Read the following files in the {project path}
|
||||
|
||||
3. **Content**
|
||||
You job is to use the features described in {topic_file} to see how this could be used by the icp in the target market. Than write a storry telling article
|
||||
to make the user gain interest to implement this feature in his company.
|
||||
to make the user gain interest to implement this feature in his company.
|
||||
|
||||
|
||||
4. **Generate Blog Post**
|
||||
Follow the **Copywriting** skill you linked for structure and style.
|
||||
Produce **HTML** with semantic tags (`<article>`, `<h1>-<h3>`, `<p>`,
|
||||
Produce **HTML** with semantic tags (`<article>`, `<h2>-<h3>`, `<p>`,
|
||||
`<ul>`, `<blockquote>`, etc.) and any classes defined in `copy_style.md`.
|
||||
Include:
|
||||
- Title (`<h1>`)
|
||||
- Sub-headline (`<h2>`)
|
||||
- Sub-headline (`<h2>`) – serves as the first heading in the HTML `text`.
|
||||
- Intro paragraph
|
||||
- 3-5 benefit-oriented sections, each with a header (`<h3>`) and paragraph.
|
||||
- Optional YouTube video embed using an `<iframe>` (provide the video ID).
|
||||
@@ -54,14 +53,31 @@ to make the user gain interest to implement this feature in his company.
|
||||
|
||||
**Do not** fabricate data; rely only on the audience info and style guide.
|
||||
|
||||
5. **Write Output**
|
||||
Capture the generated HTML in a variable (e.g., `htmlContent`).
|
||||
|
||||
5. **Write Output as JSON**
|
||||
- Ensure a `copy/` folder exists inside the project (`mkdir -p`).
|
||||
- Generate a URL-safe slug from the `headline` field: convert to lowercase, replace all non-alphanumeric characters (except letters, numbers) with hyphens, and trim leading/trailing hyphens.
|
||||
- Write the HTML to `copy/{slug}.html` using the `write` tool. Example: if headline is "Improve Transparency In Your Business", use filename `improve-transparency-in-your-business.html`.
|
||||
- Do not write files outside the `copy/` folder—this directory is for blog posts only.
|
||||
- Generate a URL‑safe slug from the `headline` field: convert to lowercase, replace all non‑alphanumeric characters (except letters, numbers) with hyphens, and trim leading/trailing hyphens.
|
||||
- Determine the current date (ISO 8601) via a shell command, e.g. `date -u +"%Y-%m-%d"`.
|
||||
- Build a JSON object with the required fields:
|
||||
```json
|
||||
{
|
||||
"headline": "<title from <h1>>",
|
||||
"text": "<htmlContent>",
|
||||
"image": "<image>",
|
||||
"date": "<current‑date>"
|
||||
}
|
||||
```
|
||||
- `<title from <h1>>` is the same string used for the slug.
|
||||
- `<htmlContent>` is the HTML generated in step 4.
|
||||
- `<image>` comes from the topic step (`{image}` variable).
|
||||
- `<current‑date>` is the ISO‑8601 date string.
|
||||
- Write the JSON to `copy/{slug}.json` using the `write` tool.
|
||||
- Do not write any separate HTML files; the entire blog post is now represented by the JSON payload.
|
||||
- Return the JSON object as the agent's final response.
|
||||
|
||||
6. **Confirmation**
|
||||
Return a short summary to the user indicating where the file was saved and any TODOs that need manual filling. Always state the full filename generated (e.g., "written to `improve-transparency-in-your-business.html`").
|
||||
Return the JSON object that was written to `copy/{slug}.json` as the final output. Also include a short textual summary indicating the filename (e.g., "written to `improve-transparency-in-your-business.json`").
|
||||
|
||||
7. **Style Guide**
|
||||
use the following styles
|
||||
@@ -81,7 +97,7 @@ Embed videos with a player
|
||||
allowfullscreen>
|
||||
</iframe>
|
||||
|
||||
They should have a description that are customized to the ICP like
|
||||
They should have a description that are customized to the ICP like
|
||||
This is how you would add users for your NGO
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user