From sayou
Saves key findings, decisions, notes, bugs, and guides from conversations to sayou workspace as versioned Markdown files with YAML frontmatter via workspace_write.
npx claudepluginhub pixell-global/sayou --plugin sayouThis skill uses the workspace's default tool permissions.
Save key knowledge from the current conversation to the sayou workspace as a structured, versioned file.
Captures decisions, conventions, patterns, issues, and concepts from conversations into docs/ markdown nodes using triage output. Auto-activates on save intents or decision signals.
Saves decisions, patterns, learnings, and error fixes to the knowledge base as structured markdown notes. Use /mem-save to document for future reference.
Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.
Share bugs, ideas, or general feedback.
Save key knowledge from the current conversation to the sayou workspace as a structured, versioned file.
Analyze the conversation — identify the most important knowledge to save:
Choose a logical path based on content type:
decisions/ — architectural decisions, technology choices, design rationaleresearch/ — competitive analysis, market research, technical investigationnotes/ — meeting notes, brainstorms, general notesbugs/ — bug investigations, root causes, fixes appliedguides/ — how-to guides, setup instructions, runbooksWrite with YAML frontmatter — always include structured metadata:
---
type: decision | research | note | bug-report | guide
status: draft | reviewed | approved | archived
topic: short-topic-name
date: YYYY-MM-DD
tags: [relevant, tags]
---
Use workspace_write to save the file. Use a descriptive filename in kebab-case (e.g., auth-token-refresh-fix.md).
Confirm what was saved — show the path, key frontmatter fields, and mention it's versioned (they can update it later and the old version is preserved).
If the conversation discussed choosing PostgreSQL over MySQL:
---
type: decision
status: approved
topic: database-selection
date: 2026-02-19
tags: [database, infrastructure]
---
# Database Selection: PostgreSQL
## Decision
PostgreSQL over MySQL for the new service.
## Reasoning
- Better JSON support (JSONB) for our flexible schema needs
- Superior full-text search (eliminates need for Elasticsearch)
- Row-level security for multi-tenant isolation
## Alternatives Considered
- MySQL: Familiar to team but weaker JSON/FTS support
- MongoDB: Overkill for our relational data patterns
Save to: decisions/database-selection.md
workspace_write (not regular Write tool) — this goes to the persistent workspace, not the local filesystemworkspace_write creates a new version (nothing is overwritten)