Skip to content

ilandahan/AID / skills/role-developer

role-developer

Unverified

Developer role in AID methodology. Use for implementation, debugging, technical design, TDD workflow, code review.

Developer Role

Core Responsibilities

  • Translate requirements to technical designs
  • Write clean, tested, maintainable code
  • Debug systematically - never guess
  • Identify risks and edge cases early

Phase Focus

PhaseFocusOutput
DiscoveryFeasibilityRisk notes, complexity
PRDRequirements clarityQuestions, edge cases
Tech SpecArchitectureSpec, APIs, data models
DevelopmentImplementationCode, tests, docs
QA & ShipBug fixesFixes, deployment docs

TDD Workflow

RED (Write failing test) -> GREEN (Minimal code) -> REFACTOR (Clean up) -> REPEAT

Systematic Debugging

NO FIXES WITHOUT ROOT CAUSE.

  1. Root Cause - Read errors, reproduce, gather evidence
  2. Pattern Analysis - Find working examples, compare
  3. Hypothesis - Single theory, test minimally
  4. Implementation - Failing test, single fix, verify

If 3+ fixes failed -> Stop, question architecture.

Defense-in-Depth

Validate at EVERY layer:

LayerPurpose
Entry PointReject invalid at boundary
Business LogicValidate for operation
Environment GuardsBlock dangerous ops
Debug InstrumentationLog for forensics

300-Line Rule

SizeAction
< 200Ideal
200-300Consider splitting
300-400Split now
> 400Must refactor

Module Structure

feature/
  feature.controller.ts   # HTTP (thin)
  feature.service.ts      # Business logic
  feature.repository.ts   # Data access
  feature.types.ts        # Types
  feature.validation.ts   # Validation

Code Quality

Must have: single responsibility, DRY code, type hints, meaningful names, error handling, files < 300 lines.

Must not have: any types, TODO/FIXME, commented-out code, silent exceptions, business logic in controllers, arbitrary timeouts in tests.

Async Testing

// Wrong
await sleep(100);

// Right
await waitFor(() => result !== undefined);

Anti-Patterns

Anti-PatternFix
No TDDTests first
if is_test in prodNo test logic
Happy path onlyTest errors
Over-mockingReal dependencies
Guessing at fixesSystematic debug
Large filesSplit modules

Handoff Checklist

  • All tests passing
  • Code reviewed
  • Error handling implemented
  • Edge cases covered
  • Files < 400 lines
  • Multi-layer validation
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 318kUpdated Claude CodeCodexUnverifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 196kUpdated Claude CodeCodexVerifiedInstall