diff options
| -rw-r--r-- | fish/conf.d/update.fish | 2 | ||||
| -rw-r--r-- | prompts/skills/compose-blog-post/SKILL.md | 8 | ||||
| -rw-r--r-- | prompts/skills/project-taskwarrior/1-create-task.md | 2 |
3 files changed, 7 insertions, 5 deletions
diff --git a/fish/conf.d/update.fish b/fish/conf.d/update.fish index 2f77f2e..fcccd6b 100644 --- a/fish/conf.d/update.fish +++ b/fish/conf.d/update.fish @@ -1,4 +1,4 @@ -function update::tools +unction update::tools set pids echo "Installing/updating gofumpt" diff --git a/prompts/skills/compose-blog-post/SKILL.md b/prompts/skills/compose-blog-post/SKILL.md index 8059fd1..ddbbfbe 100644 --- a/prompts/skills/compose-blog-post/SKILL.md +++ b/prompts/skills/compose-blog-post/SKILL.md @@ -1,11 +1,11 @@ --- name: compose-blog-post -description: Compose a blog post in gemtext format for foo.zone. Use this skill when the user wants to write or draft a new post for the gemfeed; follow existing style (title, date, TOC, optional ASCII art, images, links, closing) and add the post to the gemfeed index. +description: Compose a blog post in gemtext format for foo.zone. Use this skill when the user wants to write or draft a new post for the gemfeed; follow existing style (title, date, TOC, optional ASCII art, images, links, closing) and add the post to the gemfeed index. Only create or edit .gmi.tpl template files—never write or modify .gmi files. --- # Compose blog post -Compose a blog post in gemtext (`.gmi`) for the foo.zone gemfeed. Output goes under `~/git/foo.zone-content/gemtext/gemfeed/`. Keep the skill generic so it works for any topic (how-to, review, setup, list, etc.). +Compose a blog post in gemtext for the foo.zone gemfeed. **Only write or modify `.gmi.tpl` template files** under `~/git/foo.zone-content/gemtext/gemfeed/`. Do not create or edit `.gmi` files (those are generated from templates). Keep the skill generic so it works for any topic (how-to, review, setup, list, etc.). ## When to Use @@ -14,14 +14,14 @@ Compose a blog post in gemtext (`.gmi`) for the foo.zone gemfeed. Output goes un ## Instructions -1. **Match existing style.** Read 2–3 recent posts from `~/git/foo.zone-content/gemtext/gemfeed/*.gmi` to mirror: +1. **Match existing style.** Read 2–3 recent posts from `~/git/foo.zone-content/gemtext/gemfeed/*.gmi` or `*.gmi.tpl` (for style only; do not modify those .gmi files) to mirror: - Title and published date format - Optional ASCII art - Table of Contents format - Section levels and link style - Closing (related posts, E-Mail, Back to main site) -2. **Decide filename and date.** Use `YYYY-MM-DD-slug.gmi`. Ask for the publish date and slug if the user doesn’t specify them. +2. **Decide filename and date.** Use `YYYY-MM-DD-slug.gmi.tpl` for the template file. Ask for the publish date and slug if the user doesn’t specify them. 3. **Structure the post** in this order: - `# Title` (first line) diff --git a/prompts/skills/project-taskwarrior/1-create-task.md b/prompts/skills/project-taskwarrior/1-create-task.md index 8c37500..62a430b 100644 --- a/prompts/skills/project-taskwarrior/1-create-task.md +++ b/prompts/skills/project-taskwarrior/1-create-task.md @@ -4,6 +4,7 @@ Use with `00-context.md`. Project name and global rules apply. New tasks get `+a ## Rules for new tasks +- **When creating a new task, always check whether the new task depends on other (existing) tasks.** If it does, add the dependency to the new task (e.g. `depends:<id>` or `depends:<id1>,<id2>`). Use IDs of tasks that have `+agent` in this project. - **Create tasks in smaller chunks that fit into the context window.** Break work into multiple tasks so that each task’s scope, description, and required context (refs, files, docs) can fit in one context window when the agent works on it with a fresh context. Do not create single tasks that would require more context than available. - **Every task MUST have at least one tag** for sub-project/feature/area (e.g. `+integrationtests`, `+flamegraph`, `+bpf`, `+cli`, `+refactor`, `+bugfix`). - **When an agent creates a task, always add the tag `+agent`** so agent-created tasks can be identified. @@ -27,5 +28,6 @@ Multiple dependencies: `depends:<id1>,<id2>`. - **Keep tasks small:** each task should be a chunk that fits in the context window (description + refs + work to do). Split large efforts into multiple dependent tasks. - Pick or create a meaningful tag for the sub-project or feature. +- **Always check for dependencies:** before adding a task, determine if it depends on other tasks in the project; if so, add `depends:<id>` (or multiple IDs) to the new task. - Add dependencies when one task must complete before another can start. - When creating a task, add references to all required context (files, docs, specs) so the task is self-contained for fresh-context work. |