
Claude Skills by solofounder-ai
github.com/solofounder-aiUse when any agent produces output, makes claims, or encounters errors — enforces the Five Iron Laws across all stages, roles, and deliverables
Use before recommending any technology, framework, library, API, model version, or pricing — LLM training data is always stale, verify with live documentation before any recommendation
Use when a stage needs visual preview — wireframes, mockups, design comparisons, multi-variant voting, or design system showcases
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when implementing any feature or bugfix, before writing implementation code
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
Use after every completed flow — analyzes the entire conversation to identify improvements, updates cross-project learning, and generates retrospective
Use when any user request arrives — analyzes the request, designs the optimal flow of stages with specialist roles, and orchestrates execution through each stage's review/verification gates
Use after a flow is approved — generates specialist role definitions with domain-specific expertise, review checklists, and exception criteria for each role in the flow
Use when starting any conversation — bootstraps the SoloFounder system, loads Iron Laws, injects cross-project learning, and hands off to Flow Composer