Technical conversation log with factual accuracy and precision tailored specifically for DEVELOPER and ENGINEER profiles. Provides systematic guidance for capturing decisions, outcomes, and next steps. Use when user asks to create technical conversation logs for reviews, architecture discussions, or implementation sessions.
Creates technical conversation logs for developer/engineer sessions, capturing decisions, outcomes, and next steps with factual accuracy. Used when documenting architecture discussions, reviews, or implementation sessions.
/plugin marketplace add axivo/claude/plugin install conversation-log@axivoThis skill inherits all available tools. When active, it can use any tool Claude has access to.
LICENSETechnical session documentation with factual accuracy and precision. Captures decisions, outcomes, and next steps for technical work, reviews, architecture discussions, and implementation sessions.
[!IMPORTANT] Framework observations provide complete document structure and file paths. Always read the conversation log template instructions specified in framework observations before creating conversation logs.
Systematic documentation for technical sessions with factual accuracy and precision. Extends DEVELOPER and ENGINEER profiles with technical writing guidance for session documentation.
[!IMPORTANT] The skill embodies Observe → Capture → Document → Archive
- Process skill instructions systematically
- Take time to read, understand, and apply each section's logic carefully
- Rushing past documented procedures causes fatal execution errors
Documentation quality improves through consistent application of these principles:
Apply technical writing standards to all conversation log sections.
src/auth/middleware.ts modified" not "authentication code updated"Include these technical details when documenting sessions:
Technical sessions typically use these tag patterns:
#infrastructure, #systems, #software, #architecture, #operations#review, #debugging, #implementation, #refactoring, #design#completed, #blocked, #research-needed, #follow-up-requiredEach session type has specific focus areas that guide documentation content. Use these patterns to ensure comprehensive coverage of relevant technical details.
Focus on:
Focus on:
Focus on:
Focus on:
Before creating a conversation log:
A well-documented session includes:
[!IMPORTANT] The conversation log serves as technical reference for session continuation and knowledge retention across the collaboration relationship.
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.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.