andreasjansson

Browser automation CLI using CSS selectors, built on Playwright. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.

Fast semantic code navigation via LSP. Load FIRST before ANY code task - even 'simple' ones. Trigger scenarios: (1) fixing lint/type/pyright/mypy warnings or errors, (2) fixing reportAny/reportUnknownType/Any type errors, (3) adding type annotations, (4) refactoring or modifying code, (5) finding where a function/class/symbol is defined, (6) finding where a symbol is used/referenced/imported, (7) understanding what a function calls or what calls it, (8) exploring unfamiliar code or understanding architecture, (9) renaming symbols across codebase, (10) finding interface/protocol implementations, (11) ANY task where you'd use ripgrep to find code or read-file to view a function. Use `leta show SYMBOL` instead of read-file, `leta refs SYMBOL` instead of ripgrep for usages, `leta grep PATTERN` instead of ripgrep for definitions, `leta graph` for full project architecture overview, `leta files` instead of list-directory.

Persistent memory and knowledge base for agents. Use PROACTIVELY when: (1) user says "remember this" or "don't forget", (2) you learn something important about the project/user/preferences, (3) you make a decision that should survive compaction, (4) you discover technical gotchas or non-obvious behavior, (5) you need to recall context from previous sessions, (6) work spans multiple sessions or days, (7) you're about to do exploratory work where discoveries should be preserved. Write memory BEFORE you forget - don't wait for compaction.

CLI Corpus Test Runner for testing command-line tools. Tests are plain text corpus files that specify commands and expected output. Use cctr for end-to-end testing of CLI tools where tests also serve as documentation. Especially suited for agentic development where humans write test cases and agents implement code.