cf-workers-integration

Integrate separate codebases into a single Cloudflare Workers project.

2|7|Updated Jun 19, 2026
One-click install
npx skills add https://github.com/humanerd-drew/opencode-drewgent --skill cf-workers-integration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cf-workers-integration
Source: https://github.com/humanerd-drew/opencode-drewgent/tree/main/skills/software-development/cf-workers-integration
Command: npx skills add https://github.com/humanerd-drew/opencode-drewgent --skill cf-workers-integration

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of integrating separate codebases into a single Cloudflare Workers project, streamlining the process and enhancing project coherence.

Core Features & Use Cases

  • Codebase Integration: Merge separate codebases (e.g., NAS controllers, analysis engines, LLM callers) into a single Cloudflare Workers project.
  • Refactoring: Transition from monolithic Worker.ts to a router pattern, improving modularity and maintainability.
  • LLM Consolidation: Unify LLM caller logic to avoid duplication and ensure consistency.
  • API Response Enrichment: Enhance API responses with additional data without breaking existing consumers.
  • Data Transformation: Facilitate data transformation between different data formats within the router layer.
  • Layered Analysis: Implement progressive computation layers (L0→L3) for enhanced analysis capabilities.
  • SPA Routing: Solve issues with same-hash navigation in Single Page Applications (SPA).

Quick Start

Use the cf-workers-integration skill to refactor your Cloudflare Workers project and integrate multiple codebases into a single coherent project.

Frequently Asked Questions about cf-workers-integration

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

FAQPage Schema
How do I integrate separate codebases into a single Cloudflare Workers project?

Integrate separate codebases into a single Cloudflare Workers project by merging NAS controllers, analysis engines, and LLM callers into one coherent structure. This process refactors monolithic files into a modular router pattern to improve maintainability.

What is the best way to refactor a monolithic Cloudflare Worker into a router pattern?

Refactoring a monolithic Worker.ts into a router pattern transitions your codebase to modular routing. This improves maintainability and enables layered analysis by separating data transformation and API enrichment logic into distinct processing layers.

How do I consolidate duplicate LLM caller logic in Cloudflare Workers?

Consolidate duplicate LLM caller logic by unifying API request handling within your router layer. This ensures consistent data transformation and API response enrichment across all integrated codebases without breaking existing consumers.

How do I fix same-hash navigation issues in SPA routing on Cloudflare Workers?

Fix same-hash navigation issues in SPA routing by implementing router-level resolution within your Cloudflare Workers project. This resolves single page application navigation conflicts while enriching API responses with required data.

Can I enrich API responses in Cloudflare Workers without breaking existing consumers?

Enrich API responses in Cloudflare Workers by adding additional data within the router layer. This transformation enhances response payloads while maintaining backward compatibility, ensuring existing consumers continue functioning normally.

How do I implement layered analysis across L0 to L3 computation layers in Cloudflare Workers?

Implement layered analysis by establishing progressive computation layers from L0 to L3 within your Cloudflare Workers project. This architecture enables enhanced analysis capabilities by structuring data transformations sequentially in the router layer.