implement-adapter

Coordinate adapter layer implementation and review across sub-agents.

Updated Feb 27, 2025
One-click install
npx skills add https://github.com/tuanemuy/dotfiles --skill implement-adapter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement-adapter
Source: https://github.com/tuanemuy/dotfiles/tree/main/config/claude/skills/implement-adapter
Command: npx skills add https://github.com/tuanemuy/dotfiles --skill implement-adapter

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enables implementing adapters for a project based on the design defined in spec/database and domain port interfaces, while ensuring quality through a structured review cycle. The main agent handles orchestration and coordination, delegating actual code work to sub-agents.

Core Features & Use Cases

  • Preparation & Alignment: Validate spec/database and domain ports, read CLAUDE.md/README.md to determine language, directory structure, rules, and commands.
  • Phased Implementation: Manage Phase 1 (preparation), Phase 2 (implementation by sub-agents), Phase 3 (reviews), and Phase 4 completion, updating progress docs and ADRs as needed.
  • Quality Gate & Traceability: Enforce typecheck & lint checks, report deviations, and store review notes in .review/adapter.

Quick Start

Instruct the system to implement adapters following the CLAUDE.md guidance and start the phased workflow.

Frequently Asked Questions about implement-adapter

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

FAQPage Schema
How do I implement adapter layers to conform to domain port interfaces?

Adapter implementation is orchestrated end-to-end by validating spec and database definitions against domain ports, delegating code generation to sub-agents, and enforcing typecheck plus lint gates to guarantee port conformance and structural integrity.

What is the phased workflow for adapter implementation and code review?

The phased adapter implementation workflow spans four stages: validating spec and database alignment, delegating sub-agent code generation, executing peer reviews, and finalizing completion while updating progress documents and architecture decision records.

Do I need design docs and spec definitions before implementing adapters?

Yes, design docs are required. The adapter implementation process relies on pre-existing spec and database definitions plus domain port interfaces to validate alignment, extract language rules from CLAUDE.md, and ensure the generated code layer conforms strictly.

How does orchestration handle typecheck and lint checks during adapter implementation?

Orchestration enforces typecheck and lint gates during sub-agent implementation and peer review phases. When checks fail or design deviations occur, the system reports issues and stores detailed review notes within the .review/adapter directory for traceability.

Can I use sub-agents for adapter implementation across different project structures?

Yes, sub-agents execute adapter implementation across varying project structures by reading CLAUDE.md and README.md during the preparation phase to identify the target language, directory structure, lint rules, and typecheck commands before generating code.