33 lines
1.4 KiB
Markdown
33 lines
1.4 KiB
Markdown
---
|
|
name: vibe-logging
|
|
description: "Use when: implementing, reviewing, testing, documenting, or otherwise completing LinkLog work that must be captured in the project's VIBE conversation log. Append the visible user request and concise outcome to VIBE/PROMPTS.md and VIBE/CHAT_LOG.md."
|
|
---
|
|
|
|
# LinkLog VIBE Logging
|
|
|
|
## Purpose
|
|
|
|
`VIBE/` is LinkLog's append-only, user-visible record of its development conversation. Keep it current whenever a LinkLog task is completed.
|
|
|
|
## Workflow
|
|
|
|
1. Complete the user's requested work and its relevant validation first.
|
|
2. Append the user-visible request to `VIBE/PROMPTS.md` under a `## YYYY-MM-DD` heading. Reuse today's heading when it already exists; otherwise add it at the end.
|
|
3. Append a matching entry to `VIBE/CHAT_LOG.md`:
|
|
|
|
```markdown
|
|
### User
|
|
<the visible user request>
|
|
|
|
### Assistant outcome
|
|
<a concise statement of the completed work and meaningful validation>
|
|
```
|
|
|
|
4. Do not edit, reorder, summarize, or remove earlier VIBE records. Only append.
|
|
5. Exclude system prompts, developer instructions, environment details, private tool use, credentials, and internal reasoning.
|
|
6. Before finalizing, verify both VIBE files include the exchange and that the outcome accurately reflects the completed work.
|
|
|
|
## Scope
|
|
|
|
Use this skill for visible LinkLog development interactions. The VIBE record should describe what the user asked and what was delivered, not an internal transcript.
|