writers-pattern

Generate new platform writers with absolute paths and ES module imports.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Buckeyes22/weather-app --skill writers-pattern-buckeyes22
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writers-pattern
Source: https://github.com/Buckeyes22/weather-app/tree/main/docs/corpora/caliber/skills/writers-pattern
Command: npx skills add https://github.com/Buckeyes22/weather-app --skill writers-pattern-buckeyes22

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Adds a new platform writer in src/writers/ following existing patterns (claude, cursor, codex). Returns string[] of generated file paths. Integrates with writeSetup() orchestration. Use when implementing 'add platform', 'new writer', 'support new agent'. Do NOT use for refactoring existing writers or modifying writers/index.ts exports.

Core Features & Use Cases

  • Create directory structure
  • Implement writer function signature
  • Export writer in src/writers/index.ts
  • Follow existing pattern to ensure absolute paths, tests, and typings
  • Reuse patterns from claude/cursor/codex writers to maintain consistency

Quick Start

Create a new writer under src/writers/{platform}, implement the write function, and wire it into the exports so it returns absolute paths.

Frequently Asked Questions about writers-pattern

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a new platform writer to my codebase?

You add a new platform writer by creating src/writers/{platform}/index.ts, implementing the writer function signature with WriterConfig and SkillLine interfaces, and exporting it to integrate with the writeSetup orchestration.

What is the required pattern for implementing TypeScript writer functions?

The required pattern enforces using WriterConfig and SkillLine interfaces, returning absolute file paths as a string array, handling errors, and using ES module imports to ensure compatibility with existing claude, cursor, and codex writers.

Can I use this pattern to refactor existing platform writers?

No, this pattern is designed solely for adding new platform writers and should not be used for refactoring existing writers or modifying the writers/index.ts exports.

How do I ensure my new writer is compatible with the writeSetup orchestration?

Compatibility with writeSetup orchestration requires your writer to follow established conventions: return absolute paths in a string array, adhere to the WriterConfig interface, and ensure ES module imports match the existing claude, cursor, and codex writer patterns.

What steps are needed to export a new writer in src/writers/index.ts?

Exporting a new writer involves creating the directory structure, implementing the write function signature to return absolute file paths, and then wiring the new module into src/writers/index.ts to ensure it follows the existing platform writer patterns.