Internal skill for progress journal management. Other skills append to docs/progress.md for cross-session context. Not invoked directly by users.
Maintains a shared progress journal for cross-session context and task history.
/plugin marketplace add howells/arc/plugin install arc@howellsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Internal patterns for maintaining cross-session context via docs/progress.md.
Location: docs/progress.md
# Progress Journal
## YYYY-MM-DD HH:MM — /arc:[command]
**Task:** [Brief description]
**Outcome:** [Complete / In Progress / Blocked]
**Files:** [Key files created/modified]
**Decisions:**
- [Key decision 1]
- [Key decision 2]
**Next:** [What comes next, if any]
---
All Arc skills should append to the progress journal on completion.
Use this pattern at the end of any skill:
<progress_append>
After completing the skill's main work, append to the progress journal:
**Entry format:**
## YYYY-MM-DD HH:MM — /arc:[skill-name]
**Task:** [What was requested]
**Outcome:** [Complete / In Progress / Blocked]
**Files:** [Key files, comma-separated]
**Decisions:**
- [Decision 1]
**Next:** [Suggested next step]
---
</progress_append>
Skills that benefit from progress context should read recent entries first.
<progress_context>
**Use Read tool:** `docs/progress.md` (first 50 lines)
Look for:
- Recent work on related features
- Decisions that affect current work
- In-progress items that might be continued
</progress_context>
| Skill | What to Log |
|---|---|
/arc:ideate | Feature designed, key decisions, approach chosen |
/arc:implement | Tasks completed, tasks remaining, blockers |
/arc:build | What was built, files changed |
/arc:testing | Test results, coverage changes |
/arc:review | Plan reviewed, changes made |
/arc:audit | Audit completed, issue counts by severity |
/arc:design | UI designed, aesthetic direction |
/arc:letsgo | Deployment status, checklist progress |
/arc:document | Solution documented, category |
/arc:commit | What was committed, branch |
/arc:suggest (read-only)Activates when the user asks about AI prompts, needs prompt templates, wants to search for prompts, or mentions prompts.chat. Use for discovering, retrieving, and improving prompts.
Search, retrieve, and install Agent Skills from the prompts.chat registry using MCP tools. Use when the user asks to find skills, browse skill catalogs, install a skill for Claude, or extend Claude's capabilities with reusable AI agent components.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.