Writers Pattern

Implement writer function signature

• Import WriterConfig and SkillLine from src/writers/index.ts
• Export default async function: export default async function write{Platform}(config: WriterConfig, skillLines: SkillLine[]): Promise<string[]>
• Function receives config with properties: cwd, platform, agent, token (optional), quiet (boolean)
• Function receives skillLines array of objects with name, description, path, markdown properties
• Return array of absolute file paths written (e.g., ['/path/to/file1', '/path/to/file2'])

Implement core write logic

• Determine target directory from config.cwd (entry point for all writes)
• For each skill in skillLines, generate platform-specific file(s)
• Match file structure of existing writer: inspect src/writers/claude/index.ts lines 1–50 for pattern (typically generates SKILL.md or equivalent)
• Use await fs.promises.writeFile() or Caliber's writeFile() helper if available
• Catch and handle write errors — log to stderr if config.quiet is false
• Use path.resolve() and path.join() for all path operations

Add test file

• Create src/writers/{platform}/__tests__/index.test.ts with vitest imports
• Test the writer function with mock WriterConfig and SkillLine[] inputs
• Assert that returned string[] contains expected file paths
• Mock file I/O if needed using memfs or spy on fs.promises.writeFile
• Verify at least one skill is written per test case

Export writer in src/writers/index.ts

• Open src/writers/index.ts
• Add import: import write{Platform} from './{platform}/index.js'
• Export as named export in the module exports object (inspect existing claude, cursor, codex exports)
• Verify import uses .js extension (ESM convention in this project)

Verify integration

• Run npm run build — must compile without errors
• Run npm run test -- src/writers/{platform}/__tests__/ — all tests pass
• Run npm run lint — no linting errors in new writer code
• Inspect src/writers/index.ts to confirm new writer is exported and callable