Claude Code Skills for Solo and Team Shipping

Skill Directory Setup

The author defines all agent skills in an agents/skills directory, which OpenAI Codex and Gemini CLI read natively. Claude Code ignores this open standard and reads only .claude/skills, so the author creates a symlink: .claude/skills links to agents/skills for a single source of truth across tools.

Personal Developer Workflow

Before building features, the author invokes grill-me skill (forked from MattPCO's GitHub repo), which questions unresolved technical and product requirements. Follows with phased-plan skill to output a plan broken into user-testable phases grouped by feature similarity, avoiding giant PRs (e.g., 2000+ lines).

phased-implementation skill executes one phase at a time; it commits changes only after manual approval, preventing unchecked multi-phase implementations (e.g., 5000 lines).

babysit-pr skill runs in a Claude Code loop 1m babysit-pr cron: monitors PR mergeability, auto-fixes CI/CD errors (reviews, tests, deployments), alerts when green (configurable to auto-merge).

Implementation skills import vendor best practices: yorby-logging copies PostHog's logging guide verbatim; similar for Supabase Postgres best practices.

Example: Building Yorby's AI UGC Studio uses grill-me + phased-plan for the large feature.

Non-Technical Team Enablement

onboarding skill contains full local dev setup guide (migrated from Notion), covering all Yorby services.

vibecode orchestrates for non-tech co-founder/intern: invokes grill-me, phased-plan, phased-implementation, onboarding. Rules include: read-only prod access via yorby-supabase-prod-mcp; one phase per PR; defer architectural/database questions (e.g., migrations, schema) to CTO by leaving open in plans/ dir PRs, which get tagged for review.