Light-Brands/lawless-ai

Use when facing hard architectural decisions, multiple valid approaches exist, need diverse perspectives before committing, or want M-of-N synthesis on complex problems

Use when rough ideas need design before code, requirements are fuzzy, multiple approaches exist, or you need to explore options before implementation

Use when automating browsers, testing pages, taking screenshots, checking UI, verifying login flows, or testing responsive behavior

Use when current web info needed, verifying APIs still work, checking latest versions, or avoiding outdated implementations

Use when creating skills, writing SKILL.md files, editing skill definitions, or adding new reusable techniques to ai-coding-config

Use when debugging bugs, test failures, unexpected behavior, or needing to find root cause before fixing

Use when analyzing YouTube videos, extracting insights from tutorials, researching video content, or learning from talks and presentations