Artifact Publisher Skill

Step 1: Identify Artifact Type

Determine the artifact type and appropriate location:

Type	Location	Format
Plan	.claude/context/plans/	plan-{id}.md
Report	.claude/context/reports/	report-{type}-{date}.md
Architecture	.claude/context/artifacts/	architecture-{name}.md
Schema	.claude/context/artifacts/	schema-{name}.json
Config	.claude/context/artifacts/	config-{name}.yaml

Step 2: Add Metadata

Include standard metadata in the artifact:

---
id: artifact-{timestamp}
type: plan|report|architecture|schema|config
title: Artifact Title
created: 2026-01-23T12:00:00Z
author: agent-name
workflow_id: workflow-123
status: draft|final
tags: [tag1, tag2]
---

Step 3: Save Artifact

Write the artifact to the appropriate location:

# Example: Save a plan artifact
Write file_path=".claude/context/plans/plan-auth-2026-01-23.md" content="..."

Step 4: Update References

If the artifact is part of a workflow, update the workflow documentation:

## Artifacts

- Plan: `.claude/context/plans/plan-auth-2026-01-23.md`
- Architecture: `.claude/context/artifacts/architecture-auth.md`

Step 5: Notify Completion

Report the artifact location:

## Artifact Published

**Type**: Plan
**Location**: `.claude/context/plans/plan-auth-2026-01-23.md`
**Status**: Final

</execution_process>

<best_practices>

1. Consistent Naming: Use {type}-{name}-{date} format
2. Include Metadata: Always add creation date and author
3. Version Important Artifacts: Keep history of major changes
4. Link Dependencies: Reference related artifacts
5. Use Appropriate Directory: Follow project conventions

</best_practices>

Save this architecture design as a final artifact

Response:

## Artifact Published

**Type**: Architecture
**Title**: User Authentication System
**Location**: `.claude/context/artifacts/architecture-auth-2026-01-23.md`
**Status**: Final

### Metadata

- Created: 2026-01-23T12:00:00Z
- Author: architect
- Tags: authentication, security, jwt

</usage_example>

Rules

• Always include metadata in artifacts
• Use consistent naming conventions
• Save to appropriate project directories

Memory Protocol (MANDATORY)

Before starting:

cat .claude/context/memory/learnings.md

After completing:

• New pattern -> .claude/context/memory/learnings.md
• Issue found -> .claude/context/memory/issues.md
• Decision made -> .claude/context/memory/decisions.md

ASSUME INTERRUPTION: Your context may reset. If it's not in memory, it didn't happen.